Uh-oh I tried installing Easy Magic PhilZ Touch Installer on my Blu Studio C D830U. First using Win 7. Didn't work, so tried it on XP. Pretty much did the same thing (stuck on 'please wait a moment'). However, after unplugging the device, it said that the recovery was successfully installed. I used flashify to reboot to recovery. Phone powered off and now won't power back on at all. Can't remove the battery, because it's built in. Any ideas?
When I connect the phone via USB it's unsuccessfully trying to install Wiko Android USB Ethernet/RNDIS? When I go to device manager, that entry keeps appearing and disappearing. Is the phone stuck in a bootloop?
Related
I'm having one heck of a problem here. So I've got my Nexus 7, on stock Android, but rooted and unlocked.
I wanted to try Paranoid Android, so I installed the TeamWin Recovery using the Nexus Root Toolkit, then flashed the ROM and wiped cache/dalvik. I tried to boot into the new ROM, but it just stayed on the boot animation. So I looked up the issue, and the solution seemed to be return to stock Android, then flash Paranoid Android again.
So I tried to use the 'Flash Stock and unroot functionality' of the Nexus Root Toolkit, which proceeded fine until the copying of 'system' onto the device... This lasted for about an hour without progress, so I decided to try again with a different version of stock Android. This too didn't work.
So then I (foolishly) rebooted the tablet. But when I got back to fast boot, it didn't show up in Windows (on either of the two machines I have here, and with two cables that have both worked previously, in multiple USB ports). The specific error is that it shows up as an unknown device (which is fine) but also in the device manager there is error 43, which states that the USB has malfunctioned so it has stopped.
For that reason, it's impossible for me to connect it to a computer or even re(install) the proper drivers for it. And as it doesn't have a working OS, i can't get to ADB either. So right now I can't think of anything that will work - no fast boot, no recovery, no connection to a PC.
Any ideas?
Really, no ideas? Come on XDA Developers, you're my only hope <3
Hi there!
ive got the same issue and i can tell what is NOT working to fix this problem:
deleting ALL usb drivers from pc and installing adb drivers, windows troubleshoot and nrt
i'm just like confused but i think it's all windows fault, if i could i would trie on linux or any other pc os
Hello. i noticed that my computer(win 8.1) was giving a usb device not recognized error a few days ago. i didn't fix and eagerly updated to android 4.4.3, but forgot to disable freedom and now can't use google play services. i can fix that but the DAMN PHONE STILL ISN'T RECOGNIZABLE BY THE DAMN COMPUTER. i have tried multiple cables and installed win 8 dual boot but still got the same error. i also tried to reinstall drivers. but i think i didnot do it right.
both adb and fastboot are not working. if u could tell me a method to install a custom recovery without root and adb that would sove half my problems but still need help getting the computer to recognized the phone.
Normally this is a problem with charging block of the phone.
You have to root to flash recovery without a computer, towelroot works on 4.4.3. Once rooted you can use goomanager app to flash twrp recovery.
Does the PC making sound of connected I disconnected continually?
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.
Okay, I have searched around by only found solutions for the US variant. I have the Snapdragon Note 4. And flashed the Exynos TWRP by accident. I cannot get my PC to recognise my phone now, as it only boots into Odin mode. If I turn it off and charge, it goes to Odin. Booting up it goes "booting recovery" then odin mode. I have tried with several wires and several ports on Windows 7, 8.1 and 10. No luck on Linux either. Port is fine as no problems charging. Anyway to make it boot without it booting to recovery as I installed via an app and clicked "reboot to recovery" so it's stuck in a loop. O2 could not help as their systems could not pick up the phone. Please suggest. Reinstalling Drivers and changing ports is silly as I've been told this for the last 3 weeks
After restarting my device it became stuck in a boot loop where it only gets to the motorola logo then restarts and does this continually. I did not install or change anything. At this point i have tried using the stock recovery menu and clearing cache and even wiping the entire phone, yet the device still is stuck in the boot loop. Basically i am wondering how i can flash my device with the stock rom while its in this state.
UPDATE: I followed a guide on flashing the rom and the only issue at this point is that rsd lite does not show my device. When i have the device plugged in my machine shows it under device manager as motorola adb interface. I installed the drivers but still nothing in rsd lite.
do it on no Windows 10 pc/notebook
meilbox said:
do it on no Windows 10 pc/notebook
Click to expand...
Click to collapse
Do it on a windows 10 device? Eitherway i tried it on windows 7 and 10 so far and it did not work.
RSD Lite does not work through a usb 3.0 port. It only supports 2.0, so be sure you are using a 2.0 port and cable
Yachter99 said:
RSD Lite does not work through a usb 3.0 port. It only supports 2.0, so be sure you are using a 2.0 port and cable
Click to expand...
Click to collapse
Indeed using using 2.0 cable and port
Having same issue w/ my T2. Simply restarted it last night, and now it is stuck in an infinite boot loop. It appears as if it is booting up normally, lock screen comes up, but after another 10 secs or so it blacks out / reboots. I am able to get to Recovery if I can get it to shutdown before it boot loops. Wiped cache, no effect. Trying to avoid a FDR, as I don't want to lose SMS/calls and other files on the device. Any help is appreciated.
Edit: Pulled mSD card, no more reboots. Now I'm thinking there must have been an app update that is causing a weird issue w/ the mSD during initial load after a reboot.