Develop Bugs

[Q]GSM GNex soft bricked, doesn't connect to PC

I have a soft bricked GNex that goes into a bootloop of the "Google" splash logo. I can volume up + down + power and get it into the screen that gives options for recovery mode. However, when I click recovery mode, it takes me to a screen with a dead android with the red triangle sign on it. When I connect the phone to my PC, it is not even registering that a device was plugged in.
Are there any other methods or options I have to attempt to get the phone up and running?

1) thats stock recovery
2) if you want your pc to recognize it, just boot into fastboot and install the universal naked drivers.

Zepius said:
1) thats stock recovery
2) if you want your pc to recognize it, just boot into fastboot and install the universal naked drivers.
Click to expand...
Click to collapse
It's not that my PC doesn't recognize it because I don't have the drivers, I have another GNex and it plugs in just fine. My PC acts as if there was no device plugged in, there is no notification, no unknown device detected, nada. The owner claims there was water damage to the phone so maybe it's hardware bricked?

update: tried a different USB cable and got my PC to recognize the device. Using the toolkit to try and flash stock rom on there. Will keep updated if all goes well

toolkit goes through the whole stock rom flash process but phone is still doing bootloops. any other ideas?

Do it the right way. Follow the sticky on setting up adb and fast boot and put some hair on tour chest. Toolkits are terrible.

063_XOBX said:
Do it the right way. Follow the sticky on setting up adb and fast boot and put some hair on tour chest. Toolkits are terrible.
Click to expand...
Click to collapse
Ok, been following the instructions via this topic: http://forum.xda-developers.com/showthread.php?t=1529058
Have gotten all the way to the part where it's telling me to restart in recovery mode and that's when the dead android with the red warning triangle shows up. I also want to make note that I received the phone in this condition so I'm pretty sure the USB debugging mode has not been enabled.

[Q] GS3 stuck in bootloop

Hey guys. just tried to flash CM 10.1.3 after some bugs in Carbon started getting on my nerves. Used ROM Toolbox and ended up getting my device stuck in some kind of weird boot loop. The phone boots up with the samsung logo and (recovery booting) text at the top left hand corner. For some reason, it boots up, but nothing on the display. it vibrates every few seconds, but nothing. I tried to boot into recovery manually, but the same thing happens. So i figure I'll just to into Odin and flash my stock copy on, no big deal. For some reason, my PC, nor Odin are recognizing that the GS3 is plugged in and in download mode. No Unkown Devices, nothing shows up anywhere. Anyone know a fix, or am I completely ****ed?

If your PC does not recognize download mode, you can try to check the cable, plug it into a different USB port, or pull your battery and try again.
If none of that works, you are not screwed. Be lucky you have an android It's possible for an android to boot from an SDcard such as a windows boot disk on desktop.
Click V
http://forum.xda-developers.com/showthread.php?t=2439367 DIRECTIONS TO UNBRICK: Their download link for unbrick.img is for T-MOBILE only
http://forum.xda-developers.com/showthread.php?t=2345860 AT THE BOTTOM OF THIS THREAD, contains a link for an AT&T SGH-i747 debrick.img which should work ( I will edit my post when I complete, I am in the process of repairing my old brick now)
I an not responsible for any damage done to the device, or any sudden loss of limbs.
Thanks

[Q] Tab 3 8.0 not charging, no boot, no download mode. Any help?

Hello friends. I´m new in the forums, but I have now a huge problem in my hands.
I have a Samsung SM-T311 and it stopped working days ago. It wouldn't boot or charge. Recently, a message appeared in the screen, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
I can start in Download Mode screen sometimes, with the USB cable in my PC. But as soon as I press "vol up" to enter the Download Mode, it restarts into the "Firmware upgrade encountered..." screen.
So, I have now an incredibly unstable tablet, that won´t boot or charge unless connected in my PC. And even connected, the only thing it shows is that message in the screen. Download Mode is not reachable, so I cant restore it in Kies or Odin, since it cannot be detected.
I know, it´s a mess. But before I send it to any repair services, there´s anything I can do to try and restore my device?
Thanks in advance.

ylfaer said:
Hello friends. I´m new in the forums, but I have now a huge problem in my hands.
I have a Samsung SM-T311 and it stopped working days ago. It wouldn't boot or charge. Recently, a message appeared in the screen, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
I can start in Download Mode screen sometimes, with the USB cable in my PC. But as soon as I press "vol up" to enter the Download Mode, it restarts into the "Firmware upgrade encountered..." screen.
So, I have now an incredibly unstable tablet, that won´t boot or charge unless connected in my PC. And even connected, the only thing it shows is that message in the screen. Download Mode is not reachable, so I cant restore it in Kies or Odin, since it cannot be detected.
I know, it´s a mess. But before I send it to any repair services, there´s anything I can do to try and restore my device?
Thanks in advance.
Click to expand...
Click to collapse
Download your stock firmware from sammobile.com. Flash it using Odin.
The "firmware encountered an error" screen should work the same as the download mode screen. Just connect to pc when you get to that screen and make sure that it is detected in Odin.
Sent from my SCH-I605

gr8nole said:
Download your stock firmware from sammobile.com. Flash it using Odin.
The "firmware encountered an error" screen should work the same as the download mode screen. Just connect to pc when you get to that screen and make sure that it is detected in Odin.
Sent from my SCH-I605
Click to expand...
Click to collapse
It´s not detected by Odin. But thanks for the quick answer anyway.
EDIT: Well, after some effort, could start in download mode. But my computer can´t recognize the device anyway, either in Odin or Kies. It was working perfectly before, don´t think it´s hardware related.

Try reloading the Samsung drivers onto your PC. This may, or may not help. However, not reloading the drivers will keep you in the same state you are in now. Connecting the device and having Odin not recognize it is there tells me the drivers are invalid or corrupted or no longer there. It could also mean your device bootrom is badly damaged.
You may also want to try different USB ports on the PC. When you plug in the device to the computer, you can go to Computer Management / Device Manager and see which port the Samsung is trying to access.
Can you access recovery mode?

Also, try different USB cables.. They are NOT all created equal.
Some will charge.... but not connect to PC for file transfer..
It's real.. try different cables once you've reached D/L mode..
good luck
PS easy way to goto D/L mode is hold 'power' and 'Vol down' together, ONLY
Dont even mess with trying to hold the 'Home" button too..

Bricked Swift

Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!

Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317

Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.

narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.

narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me

Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*

LG G3 in download mode not detected by Windows

Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
In order to fix this soft-brick I first tried to use recovery by pressing VOL - & POWER. In the menu, I could select and confirm to recover to factory settings, but after some seconds the boot loop appeared again with (seemingly?) no change having been made. The error kept appeaing over and over again.
After trying recovery mode, I attempted to start the phone in download mode by pressing VOL + on the (switched off) phone and connecting a USB cable. The respective menu also opened, here, showing "Firmware Update" and "Do not unplug the USB connection until the process is complete". According to many tutorials I found on the internet, when having installed the required drivers (I used LG United Mobile drivers from here), this procedure should allow you to flash a recovery image through LG's flashing tool (which one can also find on that page).
However, when I connect the LG G3 (D855) to a computer the driver is installed on, there is no new device shown in the Device manager. I tried this out with Windows 10 x64 and Windows 7 x64 and disabled driver validation on both systems and enabled test signing on Windows 10, respectively. Additionally, I followed these instructions, but in this case the screen stays dark and the device is not detected either. It seems like there are not so many people experiencing this error, but I hope we can find a solution.

nVentis said:
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
Click to expand...
Click to collapse
This may sound like a dumb question, but have you tried a new battery yet? If it is one of the original batteries it could have gone bad & started bootlooping...like mine did a few months ago.
As far as the PC not recognizing the phone you can try downloading USBDeview and uninstall anything that has the vendor ID's of 1004 & 18d1(pretty much anything that says android or LGE in the description) & reboot the PC. Hopefully it'll recognize your device and install the drivers the next time you plug it in. If it doesn't find the drivers automatically for you then install LG drivers manually.
Link for usbdeview: http://www.nirsoft.net/utils/usb_devices_view.html
Link for LGE drivers: http://www.lg.com/us/support/software-firmware-drivers
Good luck :fingers-crossed: