Is a sad day for me...i didn't knew about the Hardware Lock of Vibrants and i rooted and applied lag fix to my phone. After this i just updated the phone via Kies to JI6 then when phone rebooted got stucked after the second stage of booting with a blank screen. I tried many methods of get into Recovery or Download to flash again but can't because of Hardware Lock. Anyone knows if my problem have a solution?? Im very sad plz help.
Have you tried holding volume down and power until it boots?
Sent from my T-Mobile G2 using XDA App
Yah....Nothing!!
Try all methods:
http://forum.xda-developers.com/showthread.php?t=771247
I think you may need to use ADB commands to force it to reboot into download.
You may need to do method #4.
You may want to keep adb up and keep typing 'adb devices' to see if it sees the device when you try these different methods. If so - reboot into recovery from that.
You should be able to get into DL mode. Do you have ADB on your computer? If not, get it. Put it on the root of your C:\ and than make sure you get the drivers installed on your PC. Get ODIN and have it open. When that is done, connect your phone to your PC and boot it up. Open a cmd prompt (if you are in windows 7 you may need to open as admin) and navigate to C:\ (or where ever you decided to put ADB). At the command prompt type this exactly minus the parenthesis: "adb reboot download" Should shoot you right into DL mode. At that point you will need to flash a new ROM via ODIN, so make sure you read up.
Hope this works/helps.
I tried all that but cant get into recovery or download mode, my phone is not stuked on vibrant logo it just go to the second logo and then blank screen. Fabrication date is 08-10.
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
slide mon said:
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
Click to expand...
Click to collapse
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
haxin said:
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
Click to expand...
Click to collapse
I was trying to downgrade the phone to ICS using the factory image from google. I picked the wrong image from the google site (picked soju, needed sojus) and flashed it using fastboot. As soon as I flashed the wrong bootloader the USB connection stopped working so I didn't flash the radio or os. I no longer can connect to the phone using fastboot or adb, usb debugging stopped working. The USB debugging option is set in developer options. So, trying to get the phone working now without USB. Hope that makes sense now. :good:
A couple of weeks ago I bricked my HTC Inspire with the ACE toolkit. I've spent the last couple of weeks trying to get it back. At some point I just kept getting the HTC white screen and/or bootloader. While I thought I had ClockworkMod recovery in place, I don't. I've tried copying a PD98IMG.zip directly to the SD card. And, HBOOT will read the PD98IMG.zip, it just doesn't seem to apply it.
So this is what I have done so far to fix it:
1. Installed full Android SDK. With some special USB drivers, I am able to get Froyo files fastboot flashall & its says boot & system were both written successfully.
2. When I reboot the phone it starts the HTC Recovery. Its says "This application will set your phone to factory new condition. It is designed for AT&T Branded HTC Inspire only. Using it...blah,blah,blah....Hit OK to continue or Cancel to reboot to recovery?".
3. So I click OK and it says Running "gfree -s on -c CWS_0001"....Please wait. It goes thru this and seems to install OK & says Success GFree has returned your device to s-on and CID: CWS_001. Press OK to copy factory image to your SD card and continue the process..." So I let it do that with an OK.
4. At the end of the Factory Reset install, it says "Success Your device is s-on and a factory RUU has been copied to your SD card. Pressing OK will reboot you to HBOOT where you will be prompted to go ahead with the RUU install. Press vol-up when prompted." When I look in the Android window behind this message it says: "cp: can't stat 'data/rom.zip' no such file or directory. Copying complete".
5. If I hit OK, one of 3 things happens: a.) HBOOT is shown b.) HTC white screen stays on or c.) it tries to do the Factory Reset install once more.
This is where I am stuck.
6. No matter what I have been able to continue getting Android-SDK to talk to it with fastboot commands using the special USB drivers.
I feel like I am just missing something on this.
UPDATE
I am able to connect to the device with Droid Explorer.
Please, if anyone can help, I would appreciate it.