Database Users

[Q] N7 doesn't go past Google logo

I was running an August MIUIAndroid ROM release, with no other modifications.
Downloaded the latest 12/10 release and placed it on my Internal SD. Rebooted to recovery, wiped cache, wiped dalvik cache and flashed the release.
Rebooted tablet, wherein it passed the Google logo and then just stayed blank.
Pressed volume up/down and power for a few seconds, went into fastboot. Tried to go into recovery by selecting that option in fastboot menu, tablet restarts and stays at the Google logo.
Went back into fastboot, connected the tablet to my PC with a view to using mskip's toolkit. PC doesn't recognise the tablet despite drivers being present, and the tablet becomes unresponsive in fastboot mode (can't move between menu options with volume buttons and even on disconnecting USB, have to long press power to restart).
Any help would be appreciated as I'm unsure whether ASUS will honour the warranty...

You said you can still go to bootloader, then try do manual boot(fastboot boot nameofcustomrecovery.img) and restore your backup(that is if you have any).
Tapatalked from my Ace 2

Easy
Connect it to the PC (better use the one you used in the past, with all the drivers... also use the cable that came with it)
turn it on spamming the vol until you get in the screen with start, shut down and recovery.
Go to recovery and boom, you are back to recovery
dont do nothing on the pc, just the fact that its connect will enable it:good:

Thank you for both of your replies.
This is what I did:
Connected my Galaxy Nexus to PC
Switched on USB Debugging, ADB drivers got auto-installed
Rebooted Galaxy Nexus into Bootloader, appropriate driver got installed
Switched on Nexus 7 in Bootloader mode, started praying
Swapped the Galaxy Nexus with the Nexus 7 - this time it didn't hang
Used mskip's toolkit to flash bootloader, stock recovery and stock ROM
Reason the tablet wasn't being recognised in Bootloader mode earlier was because while I had connected it to the PC many times, I'd never had USB debugging enabled (tablet was unlocked and rooted on my laptop) and had never been in Bootloader while tablet was connected to PC. So the PC didn't know what was connected to it, and presumably due to the issues with the tablet, the PC wasn't able to recognise it and download the drivers...
*huge sigh of relief* Thanks again guys!

[Q] Galaxy S-5360 No Download Mode, but Recovery Mode Works

I am new to posting, but I have followed XDA for a long time and used it to install custom ROM's on other phones. However, I now have a problem with my wife's Samsung Galaxy GT-S5360L. I have searched for hours, but can not find a solution.
The phone is stuck in a boot loop. I can enter stock recovery mode. When I try to perform a factory reset, I get the following message:
E:format folume: rfs format failed on /dev/stl11
formatting /cache
Data wipe complete
After wiping the cache partition, the phone continues to be stuck in the same boot loop after reboot (Samsung logo appears on screen, followed by animation, back to Samsung logo).
The phone will not enter into download mode. When I press power+volume down+home, I see a white screen, followed by a black sreen, followed by another white screen. the suggested method of removing the battery, SIM, and SD card, and plugging into the computer while holding both volume buttons does not work. Odin will not recognize that the phone is connected.
I tried to connect the phone to two different computers. One runs Linux mint with Windows XP on a VM. This computer has always worked for flashing ROM's to other phones. Odin would not recognize the phone, and I received messages that the device was not properly installed.
I then tried to connect the phone to another computer with Windows Vista. This PC has Kies installed and Samsung drivers. Kies would not connect to the phone, and I also received messages that the device was not properly installed. Odin would not recognize the phone. I should note that the phone has interfaced with this computer sucessfully before.
This phone has never had a custom recovery or ROMs installed. It only has the original stock ROM. Is the phone's hardware defective, or can it somehow be fixed? Please post any links to threads that I may have missed. Thanks.

Download mode is only effected by a change in bootloader normally by Flashing incompatible firmware or a hardware fault
For flashing via odin kies is not required - its useless as it's not compaitable with the galaxy y for this purpose
You just need the Samsung USB drivers available from my firmware thread (links in signature)
It maybe possible to still flash the device
Once USB drivers installed
Enter download mode
Connect USB to pc
When the white screen appears push Vol up
Wait a few seconds
Open odin
Put the 3 firmware files in their places & flash
If it doesn't flash you will either need to flash a new bootloader via a jtag (repair shop) Or replace the motherboard - either way unless you can get it done very cheap it's more economical to buy a new phone

Thank you marcussmith2626 for your sound advice. The phone is working again. I will share the problems I solved in order to flash the stock ROM. Hopefully this will help anyone else that may have a similar problem.
The Samsung USB drivers had been previously installed on my PC running windows vista. I installed the drivers so that I did not have to use the bloated Kies software. However, when I tried to connect the corrupted phone to the PC via USB, it was not recognized, even though the correct drivers were installed. Below is the procedure I had to follow in order to connect the phone:
1. I connected the phone to the computer via USB. The phone had the battery installed and was powered off. After connecting to the computer, the phone started charging (battery icon on screen). Connecting in download mode at this point did not work. The phone must be powered off.
2. When the "found new hardware" notification box appeared, I had to make a note of each device that had been discovered.
3. I then had to open Device Manager from the control panel and find each device (the name in Device Manager matched the name in the new hardware notification).
4. I right clicked on each unknown device and selected "update driver software"
5. In the next menu, I selected "Browse my computer for driver software"
6. In the following menu, I selected "Let me pick from a list of drivers on my computer"
7. This brought up a list currently installed drivers. I selected the Samsung phone driver.
8. The driver then installed for the selected device..
9. Steps 2 through 9 were repeated for each new device discovered by Windows (each device listed in the "found new hardware" dialog).
10. I started the phone in boot mode (power+home+volume down, phone still connected to PC). I saw only a white screen. However, when I pressed the volume up button, the phone connected to the PC. Odin recoginized the phone and the stock ROM was flashed.
So, even if you only see a white screen, download mode can still be active. In my case, the drivers on the PC were not working correctly, probably due to the corruption of the original stock ROM. The drivers can only be added on my PC using the above method. The option to choose from a list of currently installed drivers was not available from the found new hardware wizzard.
Also, I will also say for reference that in the USA, the stock ROM from Brazil is the one that should be used so that the phone broadcasts on the proper GSM frequencies.

Usb to PC issues

SOLVED:
I just went back to 6.01 android. Nougat also messed up my camera app. Samsung needs to fix their ****. Never should have left Nexus.
My s7 edge on android 7.0 (official update)
randomly stopped showing in file explorer on my PC.
I have USB debugging on and usb mode set to MTP.
it makes a noise when connecting and shows as
MTP in the "Devices and Printers" location
Device manager shows
SM-G935F
SAMSUNG Mobile USB composite device
SAMSUNG Android ADB Interface
I have tried to uninstall the drivers and then reinstall but so far nothing.
Different USB cables don't work.
It was just working recently
thanks to anyone who helps
UPDATE:
now it shows as "MTP" in devices and as SM-G935F in device manager.
I managed to get access to the sd card from the PC but ONLY when in TWRP recovery install tab.

SM-T587P stuck Boot Loop and the Tab is not detected in Windows 10

I have a Sprint Samsung Galaxy Tab A 10.1 (SM-T587P) from Sprint. The device is currently stuck in a boot loop. First, when it powers on, the black screen with the white text "Galaxy Tab A" text have "Recovery Booting" in the upper left corner. Then, proceeds to try to install an system update and it finally reboots to the startup screen ad infum when connect to a power micro usb cable. I have downloaded Odin to flash firmware; however, my PC fails to detect the device. In Device Managers in Windows 10, it states Unknown USB device (Device Descriptor Request Failed). However, when using a functional Galaxy Tab A 10.1 (SM-T587P) device manager can see that and I can transfer files over to the functional Tab A 10.1 via USB. ( I have install the latest Samsung drivers on my PC). Odin can't detect the tablet to install/flash firmware to possible fix tablet. Is there anything that I can do to repair the tablet?

Device not detected with Computer

Hello,
I'm posting to XDA Developers today because I'd appreciate to get some assistance with a Samsung Galaxy A3 (2016) device.
A few weeks ago, a custom rom had been flashed but it unfortunately failed for some reason and now the device is stuck on a bootloop (Stuck on the Samsung logo), and it seems that it doesn't have any IMEI anymore (Field empty).
However, I can still access TWRP and the Download Mode.
The problem here, is that my device is not detected by the computer. When I put the device on Download Mode and connect it, Odin doesn't show it (Which would mean that the device isn't detected by the computer).
Also, when I put my device in sideload mode (With TWRP), it isn't recognized as well.
I've tried to reinstall the drivers but nothing worked.
Thank you all in advance for all your help,
Have a nice day.