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.

Phone not detecting in PC - Windows 10 . [Only charging]

Hey everyone,
recently I got a YU Yureka (bought it 2nd hand), and it was all working very well. I installed a custom theme pack and was enjoying the phone for hardly one day. Things started to go wrong when I thought to root my phone. So I plugged my phone into the PC. But the phone wouldn't show. I tried different cable and different ports but couldn't get it to work. It won't even show in the device manager. No android device or No other troubleshoot devices were found in device manager. I tried unplugging and re-plugging while device manager is on screen, and I didn't noticed it refreshing or detecting the device in anyway. I also tried enabling USB debugging and tried to turn it on and off but still no luck. The phone is charging when connected to PC but its not detecting as a device. When I selected USB connection mode in Settings>Storage, it says 'USB is now disconnected'. So I thought I would do a simple restart and see if fixes the problem then came the worst. My phone is now kind of soft bricked. I said that I installed a theme pack before, and I think that was the problem. The theme had replaced my bootlogo so that might have been the problem. So I wiped my device in recovey mode and restarted. Now my phone is not turning on, Its stuck at CYANOGEN screen. The Worse Case Scenario - I can't even flash stock rom cause my phone isn't connecting to PC not even in Fastboot. I'm totally screwed.
Well I don't know if its a hardware issue. and if someone had this issue earlier and solved it, please share your solution kindly..
Thank you

sXhokage said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post70563666
Click to expand...
Click to collapse
Fixed. It was a hardware problem. Phone is working perfect now

what is real problem i can't say , but if you want to detect your phone by windows automatically ,
shut down your system , unplug power of your computer from main board / turn off ups > unplug ups from main switch > wait 2 minutes .> now in phone developer options > enable android debugging > restart phone > connect phone to pc with usb cable and now plug your computer power in main switch > start your computer that's all

Install windows media feture pack in the computer
Sent from my YU5510 using Tapatalk

Galaxy A3 A300F Too many issues. Look at the list.

Hello guys, my friend give me Galaxy A3 A300F. This device has many issues.
1. Device stuck on black screen with text "Samsung Galaxy A3" in middle & "Powered by android" in bottom. (I'm talking about the very first screen)
2. After 20 minutes, it proceeds to coloured samsung logo animation and boots up.
3. I noticed that it heats up during booting process & after too.
4. After boot up, it will restart automatically after few minutes.
5. If it holds up after booting for few minutes, i tested whether my computer detects it but i got no signal. I check it under DEVICE MANAGER and i found nothing. (With & without USB debugging enabled)
6. When i connect it to computer, the device start charging but there's no notification of USB plugged in.
7. I dial up *#0808# or whatever to configure usb settings to USB + ADB. Still there is no connectivity.
8. No IMEI found.
9. I put it in DOWNLOAD mode and connect it to PC but still there is no detection.
10. The still have access to stock recovery but no sign of detection. No adb devices found.
11. And ofcourse, ODIN did nothing.
I think that if somehow, PC detect it, then i'll do something.
Now, if you guys have any method left, plz share it. I'm so interested to fix this device. Waiting for your messages.

adnanahmed008 said:
Hello guys, my friend give me Galaxy A3 A300F. This device has many issues.
1. Device stuck on black screen with text "Samsung Galaxy A3" in middle & "Powered by android" in bottom. (I'm talking about the very first screen)
2. After 20 minutes, it proceeds to coloured samsung logo animation and boots up.
3. I noticed that it heats up during booting process & after too.
4. After boot up, it will restart automatically after few minutes.
5. If it holds up after booting for few minutes, i tested whether my computer detects it but i got no signal. I check it under DEVICE MANAGER and i found nothing. (With & without USB debugging enabled)
6. When i connect it to computer, the device start charging but there's no notification of USB plugged in.
7. I dial up *#0808# or whatever to configure usb settings to USB + ADB. Still there is no connectivity.
8. No IMEI found.
9. I put it in DOWNLOAD mode and connect it to PC but still there is no detection.
10. The still have access to stock recovery but no sign of detection. No adb devices found.
11. And ofcourse, ODIN did nothing.
I think that if somehow, PC detect it, then i'll do something.
Now, if you guys have any method left, plz share it. I'm so interested to fix this device. Waiting for your messages.
Click to expand...
Click to collapse
First thing that you need to do is to talk with your friend if he has a valid warranty and tell the problems to him.
Method 1 (if he can't fix it, then it's your time to make a difference)
If you ever get the connection, try to google as fast as possible on how to install the stock rom for the A300F to your device (if you need any help, I will... just toss me a ???PRIVATE??? message and...yeah :good: )
Just try, it's always good to try and since this is the socail era, you have help just everywhere in the internet

ADB phone access via Windows 10 (broken screen)

Unfortunately I broke the screen of my beloved 6P today and have spent the last 8 hours trying to figure out how to recover everything from it. It's still working as I can hear notifications and phone calls but the screen is blank.
After searching everywhere (xda, stackoverflow etc.), I'm a bit stuck and was wondering if anyone can help. Here's my plan/what I know:
1) I want to emulate the phone screen on my PC via USB using Android Control
2) I need USB debugging mode to access the phone via ADB
3) I need the correct (Google) USB drivers installed on my PC to access ADB
I have downloaded several tools/drivers and this is how far I got:
1) Windows sees/recognizes the phone under Devices and in Device Manager (as It does normally) - I am unable to access the phone because it's not in file transfer mode
2) When I run adb devices, the list is empty
3) I tried to update the driver to the latest Google USB driver but Windows 10 won't let me (windows has determined the best drivers etc. etc.)
I can't be sure what is blocking access via ADB. I'm sure I enabled USB debugging when I first got the phone but it was a long time ago. I read that I might need to disable Windows Driver Signing to install the latest Google driver but I haven't tried it yet.
My question is, how can I tell if it's USB debugging or the Driver? Any help would be greatly appreciated!

If you have your bootloader open, then this should be easy. You can install (if not already installed) TWRP recovery with "fastboot flash recovery file.img". When you then boot blindly into the recovery (its always the same amount of button presses in bootloader) then you can access the storage of your phone.
Other cheap solution: Get a phone with bootloop issue and use that screen from it. Then you have again a fully working phone.