[Q] Am I bricked? How do I get out? - Captivate Q&A, Help & Troubleshooting

So I installed Darky's 8.1 Rom (needed an older 2.21 rom). I guess it only works on I-9000? When I try to boot, I can't get past a screen which shows "Galaxy S GT-I900). I didn't know it only worked for I-9000's I guess.
Anyway, I can get into download mode. When I try to go into recovery mode, it will just keep resetting and recycling through the screen which shows me the I-9000.
When I am in download mode, I ran odin stock recovery (odin3 one click) from my desktop with admin. Usually, it works, but this time, the phone does not show up in the program (it has worked before with a Com0 and a yellow icon in the corner).
Can anyone help me? Am I bricked and what is the easiest way to recover? Phone is not showing up as a USB device either.
update: It looks like I can get into clockwork recovery mod eventually, but when I try applying update.zip or selecting the option to wipe data/factory reset these don't change the condition of the phone.

Uninstall your drivers, then check program files on your computer got a folder labeled Samsung. After verifyingnothing you need if in it, delete it. Reinstall your drivers. Use aUSB on back of computer. Restart your computer. If that doesn't work, think about using a Linux environment. Just google WUBI installer, it will show you how to install Ubuntu add a dual boot on your computer.

mrhaley30705 said:
Uninstall your drivers, then check program files on your computer got a folder labeled Samsung. After verifyingnothing you need if in it, delete it. Reinstall your drivers. Use aUSB on back of computer. Restart your computer. If that doesn't work, think about using a Linux environment. Just google WUBI installer, it will show you how to install Ubuntu add a dual boot on your computer.
Click to expand...
Click to collapse
Thanks. I'm up and running again.

Related

{SOLVED-HARDWARE} USB "DEVICE NOT RECOGNIZED" - After SRE, ADW, etc.

Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!

How do I root my phone ? (I've read your guides but they are CONFUSING!!)

Here is my experience with all this and why I need help ..
(Yes, I am new to all this, maybe that's why I get confused but alright..)
Okay, I want to root my phone with the design of DocRambone. Right, I follow your guide here:
http://forum.xda-developers.com/showthread.php?p=7329960#post7329960
And go to HOWTO#1 which says I need to flash my firmware. And so I start.
I first download Odin, get the 512.pit file and then try to find the desired firmware package(which according to the Doc guide is I9000XWJM8). Okay, I search the link and get to this: (I pick original firmwares -> Europe)
https://www.wuala.com/Samsung Galax...n/Original Firmwares/Europe/?key=AfzUZSU4SpKU
Which leads to my first confusion. I can't find anything named "I9000XWJM8". The closest I find is the one called "GT-I9000_I9000XWJM8_I9000XXJM4_CODE-MODEM.7z". Can I use this one or where is the "I9000XWJM8" ? :S
Right, I then assume it's the right one and continue only to find out that I don't know how to start my phone in "download mode". Or maybe I just can't because I got one of the phones without the 3 button combination. I'm not sure which one it is, and yes I did try all the combinations you state here:
http://forum.xda-developers.com/showthread.php?t=746814&page=2
None works. But how does the screen look like when you are in recorvery mode? Maybe you should add this to the guide, so people know if they can or cannot start in recorvery mode.
Anyway, I assume I have one of the phones without the combination and so I continue to the guide "Release: 3-button combo fix for any firmware version":
http://forum.xda-developers.com/showthread.php?t=785201
I follow the guide and get to step 6 which says "Start a new command prompt and type "adb reboot recovery"". Right, what's this now?
I go back to the big tutorial:
http://forum.xda-developers.com/showthread.php?p=7329960#post7329960
And finds the ADB tutorial to find out that I need Android Software Development Kit .. AND a rooted phone. Right, so I wanted to root my phone in the first place and now I need to root the phone in order to get the 3 button combination so I can root the phone. "Wait what?" was my 1st thought. But then I remembered that I found this guide earlier "[REF] Howto (un)root your SGS I9000 the easy way (keep all your data) (Eclair 2.1)":
http://forum.xda-developers.com/showthread.php?t=728754
Why did I got here? Because it said "the easy way". I thought that maybe it doesn't need the 3 buttom combination and so I found out it doesn't!! YAY finally a breakthrough, I thought. And so I started with this tutorial.
I was then met with this
"ROOT includes:
- Superuser 2.3.6.1
- Busybox 1.16.0 (for use with Titanium Backup)"
which brings me to another question: Does this mean that you get these apps when you use this root method? or do I need to install the apps first?
I thought it was the first one, since it says "includes". And so I start with the "Automated Method!". I dowload the .bat file and start. Follow what it says and reaches to the part where I plug in my phone. Here I get the error message: "Driver installation unsuccessfull" (Or something like it. I Don't recall since when I plug the phone in now I don't get the error. I don't even get a "ready to use removable disk" now. It doesn't even recognize the phone now when it's plugged in). Now I have tryed to connect it to the pc before (although WITHOUT the USB-debugging checked) and it worked fine. And this is as far as I can get. I am now officially stuck!
I have read comments and all but it doesn't help.
I'm realy tired from trolling these forums after being led through like 4-6 guides + the ones I havn't mentioned here (havn't counted, but something like that)..
So can anyone please, for the love of god, tell me which guide I should start with, list the guides so I know which one to go to next and answer the questions above.. My head hurts now :S ..
But in general, please write the guides more "noob friendly" or whatever .. I think alot of them are written by admins for admins(or atleast people who know their way around these phones). Atleast that's the impression I get.
I know it was a long read but I hope you'll help anyway
Thank you in advance!
/JohnTheOne
Sorry if I sound mad or offencive btw.. it's not my itention. I'm just mad and annoyed at myself because I can't make it work
Sent from my GT-I9000 using XDA App
hello there, I can appreciate if you're new to smartphones it can seem a lot to take in.
If you want an easy/simple way to root then there are 2 or 3 methods available on this fantastic forum but try this one:
http://forum.xda-developers.com/showthread.php?t=742403
just go to youtube and search for rooting videos and watch someone do it first, then you do it. very easy once you see how it is done. youtube or theunlockr.com also has great videos
Yea but my problem is now that I can't get access to it when it's in USB debugging mode.
As I posted earlier, the first time I put my phone in USB debugging mode and connected it to my computer it said "Drivers where not successfully installed" (or something like it).. And now, when I connect my phone to my computer in USB debugging mode, it won't even show as an USB. It doesn't pop up and say "USB connected" and I can't find it under My Computer.
Someone who can help me with this?
And when I plug it in, in USB debugging mode, should I press the USB connected button on my phone, like I usually do when I connect the phone to my computer without it being in USB debugging mode?
Okay, I found the device now on my computer, but I can't find any drivers for the phone to be connected in USB-debugging mode. Anyone knows where I can find drivers for this?
JohnTheOne said:
Okay, I found the device now on my computer, but I can't find any drivers for the phone to be connected in USB-debugging mode. Anyone knows where I can find drivers for this?
Click to expand...
Click to collapse
when used as USB Debugging mode, you need no driver if you plan to use it as a mass storage drive
you just pull down the tab and select mount the drive
then you can copy your Update.zip to the phone Internal SD
after it is done select Unmount the mass storage drive from the pull down tab in the phone
and now you can boot into the Recovery Mode, select update.zip
and you are rooted.
reboot back to normal, and enjoy the freedom to install any App you want to play with
The easiest way I found is to go on to Android market, install One Click Lag Fix. Then open the app and select root 2.1. Restart into recovery and select apply update.zip. Your phone reboots and its rooted. Simples!
simplest way to root is
1)go to market search for RyanZA's OCLF 2.0.
or here is link http://www.appbrain.com/app/com.rc.QuickFixLagFix
2)open the app
3) click root.
4)then boot into recovery
5)use volume button to select update.zip and click home button
6)your phone is rooted.
Hi everyone... Can anyone here let me know if these "lagfix" rooting methods work and are SAFE for a LOCKED (I have not unlocked the sim) Bell Galaxy S with stock JH2 rom? I am also a bit of a noob and would like to see what this phone can really do.
Also... Do I have to unroot it if I want to upgrade to froyo when it is released?
Please advise...
Thx.
yiannisthegreek
PS... Once this is rooted, HOW do you unroot with these "lagfix" methods if I ever need to?
i would advice againts installing the LAG FIXes as they can kill your Internal SD
there are over a dozen forum topics with people unable to repair the damage, and end up having to ship the phone back to samsung to have it repaired.
Allgamer...
Thank You for the heads up on this but now I am still confused on how to do it. I have to move the update.zip file to my internal sd card but I too have some issues that I cant figure out.
I learded how to do it on youtube watching someone called tech0stickyasglue and it seems very simple but firstly I am not sure exactly where I have to place the file and if I have to unzip it and then place the 2 folders inside it into the sd card, etc... I also have an issue with the whole "mount" and "unmount" thing.
I can mount the card while in usb debugging but when I go back to the dropdown menu it does not give me an option to "unmount" it only gives me an option to quit usb debugging and when I pick this option I get a warning message saying that I should "make sure I have unmounted form the host" or something to that effect.
Can you give any advice or step by step instructions to me on what and where I need to place these files to make this work?
I would greatly appreciate it...
Yea but the thing is that I can't go into recorvery mode.. The 3 button combination doesn't work (Talking to the people from page 1)
AllGamer said:
when used as USB Debugging mode, you need no driver if you plan to use it as a mass storage drive
you just pull down the tab and select mount the drive
then you can copy your Update.zip to the phone Internal SD
after it is done select Unmount the mass storage drive from the pull down tab in the phone
and now you can boot into the Recovery Mode, select update.zip
and you are rooted.
reboot back to normal, and enjoy the freedom to install any App you want to play with
Click to expand...
Click to collapse
When I put down the tap and select mount the drive(when in USB debugging mode that is) I can't acces the phones folders. I can't even see the extra icons you usually get, under My Computer, when you connect an USB to the computer. I can only find the SAMSUNG_Android under Control Panel -> Hardware and Sound ->Devices and Printers where it lies under the "Unspecified" section and not under the "Devices" section. And when I right click on it, press proporties and go to the Hardware tap, I can see under "Device status:" it says "The drivers for this device are not installed. (Code 28)" ..
So can anyone tell me what's wrong? (I havn't installed Kies btw, dunno if that has got anything to do with it)
JohnTheOne said:
When I put down the tap and select mount the drive(when in USB debugging mode that is) I can't acces the phones folders. I can't even see the extra icons you usually get, under My Computer, when you connect an USB to the computer. I can only find the SAMSUNG_Android under Control Panel -> Hardware and Sound ->Devices and Printers where it lies under the "Unspecified" section and not under the "Devices" section. And when I right click on it, press proporties and go to the Hardware tap, I can see under "Device status:" it says "The drivers for this device are not installed. (Code 28)" ..
So can anyone tell me what's wrong? (I havn't installed Kies btw, dunno if that has got anything to do with it)
Click to expand...
Click to collapse
Ahh... the joy of Android & Kies....
you don't really need to install Kies, I only installed Kies to check for official ROMs, but i was using the phone on the PC even without Kies installed
You can install the Android SDK drivers, inside the Android package that you download from google, there is a sub folder with both 32bit and 64bit drivers, unplug your phone and install them, then plug back the phone, it should be detected now.
in my Work PC, i never installed any driver, and i select mount, and it gets detected as a USB key by Win XP
AllGamer said:
Ahh... the joy of Android & Kies....
you don't really need to install Kies, I only installed Kies to check for official ROMs, but i was using the phone on the PC even without Kies installed
You can install the Android SDK drivers, inside the Android package that you download from google, there is a sub folder with both 32bit and 64bit drivers, unplug your phone and install them, then plug back the phone, it should be detected now.
in my Work PC, i never installed any driver, and i select mount, and it gets detected as a USB key by Win XP
Click to expand...
Click to collapse
Alright, thanks alot But where can I find this Android package then? I'm not sure what you are talking about exactly
Why wont anyone explain WHAT file(s) you put WHERE exactly for this update.zip root method? Is is some sort of "spy secret" or something?
Seriously... I CAN get to see my phone folders on my computer so I am good there but what I dont know is if I am supposed to move the entire .zip file to the root of my sd card or if I need to extract the .zip file to the root of my sd card.
At any rate... I have tried BOTH methods and I always get the same error message when I reboot in 3 button mode... Something to the effect of E: cannot open / install update.zip... Invalid or not found... (I am guessing on this as I am at work but you get the idea)...
Please... ANY help and "step by step" instruction would be GREATLY appreciated!!!
Hi,
One Click Lag Fix (OCLG) downloadable from Android Market will give u an option to root ur phone. And also it gives u an option to fix the lag in galaxy s. I have more than 80 applicatons and widgets installed in my phone. I insist that OCLF is the most useful, powerful and demanded application ever. It is so easy to use and follow. It even offers an option to unroot. So don't be afraid to download and install.
For ur reference, the bench mark speed has been increased from 800 to 2150. Comparable to nexus 1 with 2.2 was 1200. Hope this helps.
Sent from my G-I9000M Ver. UGJH2 using XDA App on Bell Mobility Network
JohnTheOne said:
Alright, thanks alot But where can I find this Android package then? I'm not sure what you are talking about exactly
Click to expand...
Click to collapse
you download it from google
just google up Android SDK download

[Q] zio 2.2 update failed

keep getting this message even though I have installed drivers..pc says they work..phone registers that usb is connected..debugging is selected...what am I doing wrong here...thanks
Update Failed
Please check the PC side and devise side status.
1. Power on your devise and select USB debugging on your phone
-Press Menu and then tap Settings>Applications>Development
-Tap the USB debugging check box if it's not selected
-The USB cable must be connected to your devise and PC
2. Check your driver is installed correctly.
3. Close all other applications in the device and PC.
is your antivirus/internet security shut off?
Have you removed all instances of the drivers (confirmed through device mgr&ctl panel), rebooted an installed the drivers again (making sure phone is not connected until post-install)?
What OS are you running?
running windows7..will check on the antivirus...try reloading USB drives...back in minute with update...lol
32bit or 64bit?
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
topherdownfrown said:
nt sure...wife's laptop..window 7 home premium? Edit...64 bit..sorry
Click to expand...
Click to collapse
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
will try after work..thank you..post result later.
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
Exactly. I tried for 4 hours on my Windows 7 Home Premium 64 bit machine with no luck. Drivers were installing properly from the CD included with the phone, but the update would always fail at 98%. First try on my older Vista 32 bit machine the update went right through the first time with absolutely no issues.
Don't give up
Spz0 said:
There have been multiple people that have been having odd results with updating through win7 x64.
I would suggest running the update on a 32bit machine.
Click to expand...
Click to collapse
I agree. However, I got the "failed to update" message even when I tried to install using my desktop computer that's running Vista32. BUT, then I installed the drivers (the ones that came with the update) to my Toshiba netbook (running Windows 7 Starter). The first update failed, same as before. So I disconnected my Zio, and rebooted it. I plugged it back into the netbook, ran the update installer, and it installed in like 7 minutes. Works great too. So far none of the issues that have been brought up on other threads.
edit: froyo 2.2.1 installed successfully on the Zio in less than 10 mins. i forgot to unmount the damn sd card and this was the really why my phone froze on the "modem download mode" and why the install GUI on pc dissapeared.
piece of cake! thanks a lot guys for posting this update and for creating the Zio forum.
installed the zio m6000 drivers directly from retail cd and ran the kyocera updater. i'm running Win XP on an old-school Dell optiplex.
anyway the update has been taking up at least 20 mins now. the screen on my Zio is black and the message "modem download mode" (i figure that its the tethering part) appears.
why is this update taking so long?
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
itrustno1 said:
OMG!!!! Its happening to me too! HELP!!! I get error code [0x50015001]. SDcard is out, uninstalled modem driver and installed the one that came with the upate, and still 98% then failed. Any help PLEASE?????
Click to expand...
Click to collapse
don't panic!
you have to follow the directions straight to the teeth on the install instructions.
1. make sure that you have the correct Zio usb drivers installed on your PC.
2. when the installer window (GUI) pops up, read the instructions. make sure that USB debugging is 'checked.' usb debugging option is the settings.
3. make sure that you unmount your sd card (not pulled out).
4. i reset my Zio to factory default right before i updated 2.2
5. if the update installer didn't appear at first then run it again and watch the progress.
Turn your phone off, Hold the volume + (up) and - (down) and the power button to place your phone into Modem Download Mode.
Make sure you have the Kyocera M6000 Drivers installed on your machine properly first. Once you are sure the drivers are installed correctly you can plug your phone in... wait a minute or so before you launch the update file.
I have installed the update to my phone 3 times with no problems other than when I extracted the file from the zip, I found it worked best running it without extracting the file. I have Win 7 32bit and it takes about 5 - 6 minutes to update.
If all else fails. You might have to download the sdk manager and use fastboot and flash the boot image then do the update and it will put the phone into recovery.
Spz0 said:
I've heard of varying times. Myself, it only took 6 mins or so, others had to wait more like 20-30.
What does the update program say?
Click to expand...
Click to collapse
By the way, The updater says 5 - 10 minutes.
Success!!!! ok...I dont know if it mattered but I also installed the future dial suite on the zio disk...I went through first and erased all other zio usb drivers before reinstalling the disk versions...plugged in phone..drivers got the OK..then ran the installer..took 5 minutes plus 2 for reboot..lol..
Also...fyi..I did this to my wifes phone but forgot to factory reset...all of her programs and contacts including adw ex remained intact after update (smoke from ears) oh well..thank god for titanium backup..
So does that confirm my thoughts of when I updated the other day to fix a goof after my original update. My apps and everything were still there after the update. So that must mean that the update from 1.6 to 2.2 does not format the phone unless go into the phone settings and do a factory reset.
Im at the end of my chain, please help me. My zio is stuck on the black screen "modem download mode" ever since the 98% thing happened. Try after try i keep getting error code. Im using windows vista 32-bit, i got the disc that came with my zio, i think i may have opened/extracted the zips wrong or didnt install in order or something. I think i uninstalled everything to do with this from my cpu even the zips so i can start fresh with ANY help i can get.
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Mattix724 said:
Uninstall the drivers for your zio that you have currently installed. Install the drivers that are on the site for the update download. Turn the phone off, unplug your battery for about 10 seconds if you need to. Hold + up and - down on the volume and the power button to put your phone into Modem Download Mode manually. Give the computer a minute to recognize the device. Run the updater again and if it fails or gives you an error message I would reccomend downloading the updater again. I have been able to run the updater several times already with no issues.
If you are still having problems, you may need to download sdk-manager if you do not have it already. You can always just use fastboot to erase the system and then run the update. The update will then set up the system partition and update the phone.
I had to do this just a few hours ago after I semi-bricked my phone while messing around with the cpu. What I did to get it working again after "bricking" it was...
1. you will need to have the android folder for the sdk-manager in the root of your hard drive to make it easier, unless you know where it is located.
2. Open command prompt and change to the tools directory within the sdk-manager folder. Mine was located in C:\Android\SDK-Manager\Tools
3. You may need to find the AdbWinApi.dll file, mine was located in the platform-tools directory so I just copied it to the main Android folder then copied fastboot from the tools directory and also placed that into the main Android folder.
4. Put your phone into fastboot. Hold Volume + up and the send and power keys. You can do "fastboot -w" and it will wipe user data and cache. You will need to type "fastboot erase system" and it will erase the system partition. Now type "fastboot reboot" and your phone will restart.
5. Put your phone in Modem Download Mode and run the updater.
Click to expand...
Click to collapse
okay, let me give that a shot, stay with me please!!!!!!

[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb

Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.
It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this
Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?
Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).
For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.
thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?
Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?
He doesnt have clockwork mod installed, you must have CWM installed to flash zips
OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!
I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.
Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]
cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.
EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.
Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.
I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.
Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?

[Q] Am I ****ed? ._.

Hello there, am I ****ed? Here's what happened today:
>Rooted LG revolution froze and crashed with a black screen, even after rebooting with taking the battery out.
>I'll just hard reset my phone.. nbd
>Hard reset phone
>Realized that it's still rooted, ****yea.jpg
>Go on an app deleting frenzy, accidentally deleted an app (sms.apk maybe?)
>Tried to press home and it doesn't work so I restart my phone and it boots normally until I unlock it. (The network bar is still visible but I can't access the home screen)
>Panic, then find this thread: http://forum.xda-developers.com/showthread.php?t=1337386 and complete every step but the phone doesn't show up on LGNPST. (I can't access the connectivity options, but it's usb debugged since the sd card and system folders show up on autorun)
What can I do? Is my phone salvageable? Or will I have to go to Verizon to fix my mess?
Thanks in advance!
If running Windows 7 try disabling UAC then re install the .dll file during the LGNPST setup.
I tried win 7 for a few days and couldn't get it to work. But my XP laptop worked fine. Try XP especially if win 7 is 64 bit.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
should be fairly simple
do u have cwm? and a back up? then load the system from a good backup, or load one... if no cwm then maybe the stock recovery will do it?
keep me informed and ill do what i can and search the thread http://forum.xda-developers.com/showthread.php?t=1564941
As a last resort you can allways pull the battery, then put it back in, then with the phone still off press power and down and hold untill you get option to factory reset, hit power for yes then reflash the .Tot you want and start over rooting.
pawdog said:
If running Windows 7 try disabling UAC then re install the .dll file during the LGNPST setup.
Click to expand...
Click to collapse
UAC has nothing to do with any issues.. type in start menu > search > type in "cmd" or "regedit" and right click and choose "run as administrator" then shouldn't have any issues registering the .dll

Categories

Resources