Develop Bugs

[Q] failed to update to 2.13.401.3

Hi! I have a wildfire s with 2.13.401.2. i want to update to 2.13.401.3 but if i try to check for new updates it says that there aren't new updates. i download the shipped rom from http://forum.xda-developers.com/showthread.php?t=1074445 .
i open the .exe file, click on next a few times but, when it reboot to bootloader, installshield wizard say that the device is not connected so i can't finish the installation. how can i do?

Do you have S-OFF? Check also if debug mode is activated on the phone (Settings-Applications-Development).

You are not suppose to reboot into bootloader, it will do it by itself. That's why the wizard did not detect your device. Also make sure USB debugging is checked under applications/development/USB debugging.
{
"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"
}

maestro_mihagi said:
Do you have S-OFF? Check also if debug mode is activated on the phone (Settings-Applications-Development).
Click to expand...
Click to collapse
S-ON and debug mode is activated
MrTaco505 said:
You are not suppose to reboot into bootloader, it will do it by itself. That's why the wizard did not detect your device. Also make sure USB debugging is checked under applications/development/USB debugging.
Click to expand...
Click to collapse
i don't reboot into bootloader. the wizard says that it reboot itself, but on the mobile appear a black screen with the HTC logo and then it says that there are no mobiles connected

Just to make sure that you can flash a ROM, do you have bootloader unlocked?

i haven't unlocked bootloader. i've flashed a rom two weeks ago, switched from a orange (fr) branded ROM to a Marvel HTC EU one. So i need to update to 2.13.401.3 to unlcok bootloader with HTC Dev

Ah ok.
Sorry but I can't see anything wrong there. You didn't modify the recovery option right? (You couldn't since you are locked).I had some update problems recently because I have Clockwork mode recovery installed and at the restart the system was freezing.
Maybe an admin can help..

Don't know if you solved the problem, but maybe you could restore the initial ROM, and then try again with the latest one. Maybe the 2.13.401.2 is creating the problem.

[Q] Demo mode Kindle Fire, trying to restore to original

Hi,
I recently acquired a Kindle Fire that was previously used as a Demo unit in a store, I'd like to get it out of Demo mode but having tried since Sunday (and following several threads on here with similar problems) with no success I thought I'd see if I can get any help.
This is my first Kindle, so I'm new to that, but I've owned several Android devices in the past, so I'd consider myself fairly familiar with ADB, Fastboot, etc.
Since I can't get into the settings on the Demo unit I haven't been able to enable USB Debugging, to cut a long story short after playing around all day Sunday trying to get KFU to communicate with the device I gave up and ordered a Factory USB Cable to get it into Fastboot mode.
That arrived This morning and the Kindle is now in Fastboot mode, but I'm not sure what to do next, the PC (Windows 8 64bit, but I've also tried on Vista 32bit) sees the device as: Otter2-Prod-04 with a yellow exclamation mark icon and KFU still doesn't seem to be able to communicate with the device.
I'm running out of ideas, any help would be appreciated.
Thanks,
Jason

Never mind, I got KFU to recognise the device finally but I think it's bricked it, it's just black now with no light on the power button or anything.
I don't suppose there's any way to fix that?

JFenlon said:
Never mind, I got KFU to recognise the device finally but I think it's bricked it, it's just black now with no light on the power button or anything.
I don't suppose there's any way to fix that?
Click to expand...
Click to collapse
how did you do to make windows recognize the kindle under otter2-prod-4???

JFenlon said:
Never mind, I got KFU to recognise the device finally but I think it's bricked it, it's just black now with no light on the power button or anything.
I don't suppose there's any way to fix that?
Click to expand...
Click to collapse
My Motivation For work LOL
{
"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"
}
Great cup I like it, looks good, I recommend to get one, thanks!
Redbubble Sale

[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.

[HELP] G532M Can't upload firmware via "DOWNLOAD MODE" since it gets stuck at half!

[HELP] G532M Can't upload firmware via "DOWNLOAD MODE" since it gets stuck at half!
Hello everybody, first thread on XDA.
I will tell you about my problem since it seems to be unusual.
I have a J2 Prime G532M that one day suddenly when I woke up and I turn on my phone a blue screen with the following message appeared "this phone has been flashed with unauthorized software [...]" this made me confused because my phone had the OFFICIAL ROM and I've never rooted it.
So I downloaded the official rom from Sammobile and I tried to flash it via Odin. The weird issue here is that when I try to flash it it stucks at half of the process. Sometimes at 12% exactly when it arrives at 360mb/3.75gb uploaded to the device. I downloaded two differente roms bc I thought that the first was corrupted, but both of the roms makes the same.
Also, when the phone is in Download Mode after disconnecting and reconnecting the phone to the computer Windows shows me:
{
"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"
}
"The last USB device you connected to this computer malfunctioned, and Windows does not recognize it".
When I first connect the phone everything its OK. After a while (10 seconds approx) the phone stop receiving data from Odin and when I
reconnect it Windows shows that.
What my problem could be? i'm reading all the comments. Thanks in advanced.

Try using another usb cable. Maybe it's because of your usb cable. Because my phone is J2 PRIME SM G532G Variant I was FRP locked by google but then when I try to flash my stock rom via Odin it stucks and stops halfway of the process. So what I did is just changed my USB Cable and it worked for me. Hope it works for you too. There are a lot of options changing your usb cable. Or so I could analyze the real problem here include the logs of your Odin here when it stopped halfway. Copy your Log and paste it here.

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.