Develop Bugs

Possible driver errors?

Hey there forum. I made an account just to ask this question because I just spent 7 hours looking for the answer to what SHOULD be a simple fix. I have a T-Mobile HTC Wildfire S with the US RUU installed and the 1.09.0099 HBOOT as well. Now, I have tried to unlock my bootloader on the HTC website like you're "supposed" to. But whenever I put my phone into the bootloader and plug in it in as in the guide. Then I cannot get past step 8. Because my bootloader does NOT stay in "FASTBOOT USB" It goes back to FASTBOOT in around 30 seconds. I have gotten the command prompts in before it goes back but to no avail. When it is in FASTBOOT USB mode, it's as if it's not connected. Then when it goes to the regular FASTBOOT mode, then my Windows 8, 64 bit laptop (in case it was important), makes the sound that it does when you connect something with USB. Some help would be GREATLY appreciated because I am stuck with this phone and I need some CFW.

The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.

omnomnomkimiiee said:
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
Click to expand...
Click to collapse
Thanks for the drivers! They successfully installed but I'm still getting the problem where my phone won't stay in FASTBOOT USB...

omnomnomkimiiee said:
The drivers don't work on Win8 iirc.
Follow this
Also, welcome to Xda.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This picture shows what my device manager looks like when my phone is in FASTBOOT USB.
And this picture shows what happens in the device manager after my phone drops out of FASTBOOT USB and into FASTBOOT. The computer makes the little connecting noise and then THAT.

Tbh, I dual-boot win7 and win8 just for my phone :/
Seeing how it seems you're just trying to unlock your bootloader and root, maybe borrow a friend's pc/laptop for the 30 minutes ?

[Q] Is my SPH-L710 Toast?

Hi guys, I've been scouring Google for 3 days now and can't come up with an answer, everything says use Odin for this and use Odin for that... well I can't.
A few days ago I downloaded an app from the Google store Linuxonandriod or something like that, it's pretty much an installer to place Ubuntu on your phone side by side with Android, the instructions began with rooting the phone, I began that process and believe I accidently loaded the incorrect pda to the phone (I have so many files now on my comp, I have no clue which one I selected). Odin rebooted the phone and that's that.
If I try to turn on the phone it goes to the first screen that just says SAMSUNG then turns off, never getting to the Samsung Galaxy III screen. The USB on the phone seems to have been botched, none of my computers will recognize it (Windows or Linux), the phone will not even charge. I can however get into both recovery and download modes without problem.
Naturally, download mode does no good because the USB is useless and I do not have clockwork mod installed on the phone to bypass the verification error.
I tried to simply install clockwork via recovery in hopes that would do something, but I get a verification error with that.
Is there anyway around this using the SD card or am I holding a $300 paperweight?
Thanks

Maybe try this-http://forum.xda-developers.com/showthread.php?t=2369125
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
Maybe try this-http://forum.xda-developers.com/showthread.php?t=2369125
Click to expand...
Click to collapse
Thanks, for the link. I did check it out, but couldn't figure out what the poster was talking about with drive letters and such. That dmesg | tail told me nothing about my sd. I unzipped everything to the card by a different method but my the computer still wouldn't recognize the phone, so booting back into windows did nothing.
Sorry for the delay in response, I've been extremely busy with work.
I'm still at a total loss on this.

[Q] AFTV hangs at white logo. Did I just bricked it?

Hey guys,
I was just doing the process to flash the pre rooted update, I used the AFTV Utility.
The steps:
1 - Unlocked bootlader OK
2 - Changed the bootloader OK
3 - Change recovery PROBLEM
After I changed the recovery, it restarted and now hangs at white logo in startup. Tried the print screen/sys but nothing happened, the funny thing it's that it seems not to be powering USB connection since the keyboard just doesn't even light up or any of the leds when connected (like the num lock led).
Thanks in advance for any help.

The same thing happened to me with I used the AFTV utility,
Yeah I think it's bricked. I returned it for a replacement then manually rooted/unlocked/rboxed following the AFTVnews guide and and it all worked.

gabsporto said:
Hey guys,
I was just doing the process to flash the pre rooted update, I used the AFTV Utility.
The steps:
1 - Unlocked bootlader OK
2 - Changed the bootloader OK
3 - Change recovery PROBLEM
After I changed the recovery, it restarted and now hangs at white logo in startup. Tried the print screen/sys but nothing happened, the funny thing it's that it seems not to be powering USB connection since the keyboard just doesn't even light up or any of the leds when connected (like the num lock led).
Thanks in advance for any help.
Click to expand...
Click to collapse
can you post a screen shot?

Rugged96 said:
can you post a screen shot?
Click to expand...
Click to collapse
Hi Rugged, here it is:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I turn it on and it hangs at this white logo. Thanks for helping me.

Snap to the above.
Tried following the method outlined here: http://forum.xda-developers.com/showthread.php?t=2799779
However I'm not getting any power via the USB at all so can't use a keyboard.
Any ideas?
Can you guys who've bricked plug a USB device in and have it powered?
Cheers

Question [RESOLVED] USB no longer recognized by any computers -

EDIT: RESOLVED
I was in TWRP and decided to format-all (checked all the boxes).
Then, for some reason I decided to switch to the other side (Boot_B) and do the same there.
But the TWRP on that side was broken.
And now I'm stuck with no OS installed.
And my PC won't recognize my phone when I plug it in.
I've tried all three of my known-working cables and both of my computers.
Windows Device Manager doesn't see anything being plugged in.
It's not even coming up as an unrecognized device. Windows pretends like I haven't plugged anything in.
So, no ADB device, no Fastboot device, no Qualcomm device, no unrecognized device.... simply NOTHING.
Now the phone just boots to "The bootloader is unlocked" or to the broken (frozen) TWRP where even a USB-OTG mouse won't work.
With phone plugged in:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

FINALLY got it to boot into fastboot mode!
First, power it all the way off.
Wait a minute then press & hold all three buttons.... Volume (+) & (-) and Power-button until you see fastboot.
And finally my computer sees it.
Cool, and I was able to do a "fastboot set-active a" and then reboot to the properly-working TWRP.
I should be good to go now!
EDIT:
Actually, I still can't get into MSM (nothing in device manager).
And ADB sideload or ROM install from TWRP ends in “kInstallDeviceOpenError”
EDIT 2:
I remembered that TWRP has a "reboot to EDL" option, so I used that and I'm now MSM'ing just fine.

Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.

EtherealRemnant said:
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
Click to expand...
Click to collapse
I use TWRP for full ROM backup & restore purposes.
And it works fine as long as I don't try to get too fancy.

Is this fixable (Fire TV 2nd Gen boots to recovery?)

I have a Fire TV 2nd Gen that I have not used in years. I recently fired it up and after attempting to boot up a few times it ends up on a recovery screen as seen in the photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a way out of this? I would love to be able to factory wipe to stock firmware if at all possible?

PartisanEntity said:
I have a Fire TV 2nd Gen that I have not used in years. I recently fired it up and after attempting to boot up a few times it ends up on a recovery screen as seen in the photo.
View attachment 5733235
Is there a way out of this? I would love to be able to factory wipe to stock firmware if at all possible?
Click to expand...
Click to collapse
Looks like your eMMC is read/only, i.e. faulty.
There are a few reports about something like this, for sloane especially with faulty samsung eMMC chips.
I would sell the box (for parts only).

Thank you, that would be a shame.
However reading through my original post, I failed to mention that this Fire TV had in fact been rooted. I forgot how I did it back then, and as I said, I haven't used it in a really long time.
Do you think, given the new info that this device has previousy been rooted, that it is still is faulty memory?

PartisanEntity said:
Do you think, given the new info that this device has previousy been rooted, that it is still is faulty memory?
Click to expand...
Click to collapse
In case of a rooted box the eMMC may be fine, if something like the GPT or partitions are messed up.
You can always try the unlock/unbrick for sloane.
All you need is an USB a-a cable, a PC running ubuntu, the latest amonet.zip file for sloane and careful hands The last thing is the most important point as you would need to open up the box and short a special point to ground with something soft but conductive like small copper wire (i.e. no steel parts). The point to short is a really small SMD part and if the part gets lost or damaged, the eMMC gets not accessible... The shorting is a bit annoying as you may need about 50 attempts until the unbrick will work (the sloane isn't as easy to short like a firestick, because the box use a power brick and sucks power via usb too).
There is no guarantee at all that this will help you, since a broken eMMC is only fixable with a replacement chip...
but in case it's only a partition problem, a messed up filesystem or something like this you may get the box fixed. Try it.