Customer probably flashed a kernel which failed. Now the phone has lost ESN (null). No download mode, no recovery. Device operates other things very well.
Interestingly it rarley shows ESN. I reboot the phone tens of times, maybe only at once of 100 boots it shows up. If it shows up, voice and mobile data works, but otherwise, you need to reboot the phone, untill you can see the ESN.
Additionaly, the same applies for USB connection. I plug the cable and it says "Unknown USB Device" maybe 499 of 500 times. Now I have been trying for two days to flash IMEI /ESN back with EFS Professional, but never managed to get rid of "unknown device" error again. Tried re-installing, using another computer, Windows 7/8 and Ubuntu. No luck. I also tried the method to manually flash memory blocks as described here. But cannot get that far.
At the time once it showed up the ESN, I managed to upgrade the phone from KitKat to Lollipop, using official LG Support Tool. So it is original stock ROM and device is unrooted. But everything is still the same. After the upgrade, original recovery works now, but it has nothing to do with the situation.
Now in device manager it says "USB Device Descriptor failed". Still no download mode. I tried to copy registry values of a working G2, but couldn't manage to make it work.
Now, any other suggestions?
Related
I've read through so many threads on so many forums trying to fix this, and I'm about to throw this thing through the wall.
I'm running CyanogenMod 7 nightly on 2.3.7
When I connect the phone to any PC (I've tried Win7 64/32 bit, XP SP3, XP SP2) I get a charging icon in my notification bar, but the USB Storage mode never opens to enable/disable. After about 10 seconds I see "USB Device Not Recognized." Happens the same on every PC. I can still access my internal storage via FTP, just not via USB. The device shows in my device manager as "Unknown USB Device."
Not sure if it's related, but when I boot into FastBoot it runs USB Control/USB Control init and then just freezes. Even after downloading a ROM update with ROM Manager it says "NO ROM FOUND"
This is what I've tried:
USBDeview to uninstall all Android-related drivers, reinstalled Samsung and Google SDK rev 4 drivers.
USB data wipe (for the hell of it, really.)
Multiple PC's with different OS and 3 different USB data cables, including the original.
At this point I'd like to try a factory reset. When I try to unroot with SuperOneClick the program just crashes. When I try a reset from the phone it fails to boot into recovery, and using the Factory data reset produces a "null" error.
I know just enough to be dangerous. If I'm missing something please let me know, and I appreciate any help.
--------------------------------------------------------------
Tried loading a CM9 rom from the SD card that I FTP'd over via ClockworkMod Recovery. It asks for data+cache wipe, then just boots into recovery. I get "NO IMG FOUND" and USB CONTROL INIT and USB CONTROL INIT END.
Try installing pdanet on your computer. Its what I did in order for my computer to recognize my phone. Hope it helps.
Should have mentioned earlier that I also installed PDANet after I wiped my drivers. It couldn't detect the phone being connected and did not completely install.
So my nexus 4 is rooted and unlocked. Well actually Im not sure, because after updating with the OTA it seems to have lost that capability. Even though there are SU Binaries still there. I cannot get my phone to show up in my computer or Device manager. I have the drivers install and all. I have tried with usb debugging on and off. I have tried in the Fastboot mode. I have tried after a factory reset.
its charging on my computer when its off and with another cable its charginging even its on
I'm at a lost as to what I can do....When I try to go to recovery it says "No Command" or something
help me
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.
Hello:
First of all, excuse me, I'm using a translator because my English is not very good. I was using a custom rom and wanted to back to stock so I flashed the correct firmware for my model (A-510M ARO NOUGAT) via ODIN. The process ended and had no errors. When I turned on the phone and connected it to my pc and it does not recognize it, it only charges the battery. I tried to format from the recovery and it shows the message "failed to find / misc partition"
- I tried with other USB cables.
- I tested it with other USB ports.
- I've updated Samsung drivers.
- I tried the secret menu and it does not work.
- does not recognize the download mode either
- I can not use ODIN to reinstall the firmware.
- Samsung Kies does not recognize the phone.
- Does not recognize ADB mode
The truth is that I am desperate and I do not know what to do. I can not reinstall the firmware if the PC does not recognize it. If anyone knows a possible solution I am very grateful.
thanks to all
i came across your situation long ago. it is the pc that doesn't recognize your phone. try with different pc. also you can try to format using settings>backup & reset menu. I ended up resetting my pc in order to recognize my phone.
[email protected] said:
i came across your situation long ago. it is the pc that doesn't recognize your phone. try with different pc. also you can try to format using settings>backup & reset menu. I ended up resetting my pc in order to recognize my phone.
Click to expand...
Click to collapse
Hi! I tried but is not working. I discover a new problem: when i connect the USB cable the phone shows me a message: "the battery temperature is very low. Charge stopped". Could be another the problem?
Thank you all
dhg2015 said:
Hello:
First of all, excuse me, I'm using a translator because my English is not very good. I was using a custom rom and wanted to back to stock so I flashed the correct firmware for my model (A-510M ARO NOUGAT) via ODIN. The process ended and had no errors. When I turned on the phone and connected it to my pc and it does not recognize it, it only charges the battery. I tried to format from the recovery and it shows the message "failed to find / misc partition"
- I tried with other USB cables.
- I tested it with other USB ports.
- I've updated Samsung drivers.
- I tried the secret menu and it does not work.
- does not recognize the download mode either
- I can not use ODIN to reinstall the firmware.
- Samsung Kies does not recognize the phone.
- Does not recognize ADB mode
The truth is that I am desperate and I do not know what to do. I can not reinstall the firmware if the PC does not recognize it. If anyone knows a possible solution I am very grateful.
thanks to all
Click to expand...
Click to collapse
I have similar problem but i did nothing like rom flashing. One day, the pc just don't recognise the phone, even in download mode. I tried differents pc, differents cables and ports...nothing. i tried *#0808#, drivers reinstallation, nothing... when i connect the phone, the pc display "unknown device code 43" and the phone just get charging. OTG doesn't work
Sent from my Samsung SM-A9000 using XDA Labs
I have a similar problem...I downloaded the correct firm ware...restart the phone hard restate the phone but I still get error failed to find misc/partion...please help me...and it stays in ftp lock
Trent69 said:
I have a similar problem...I downloaded the correct firm ware...restart the phone hard restate the phone but I still get error failed to find misc/partion...please help me...and it stays in ftp lock
Click to expand...
Click to collapse
No worries. We don't have misc partition so it's normal.
FRP lock won't reset on firmware flash. You need to enter your google account on boot.
To disable frp lock before factory reset next time, either remove your google account from your phone, or disable screen lock before reset.
You can't flash new firmware from download mode if you are in frp lock.
Problem: The OnePlus 6T cannot boot into fastboot mode or ADB mode. When regularly booting, I get a "device is corrupt, can't be trusted" message. I achieved this by rooting my phone through suggested methods, then uninstalling Magisk, and locking my bootloader through the all in one tool. The all in one tool can no longer detect the device under any circumstance.
Attempted Solutions: I downloaded the MSM download tool and it says "Connected." The device shows as "Quallcomm HS-USB QDLoader 9005 (Com 5)" I also got it working for Com 6. The driver and connection appears to be fully functioning. USB debugging was enabled before I bricked my phone. When I start the download, I get stuck in the param preload phase, with the error message "DEVICE DOES NOT MATCH IMAGE." The "Verify" button works perfectly and says it's working.
I have downloaded every version of the MSMDownloadTool I could possibly find. I assume I have the most recent update of the OS -- It updated quite recently. I tried every single version I could find, including the most recent one (fajita_41_J.50_210121) and got this error every time. I know it's running Android 10, unless Android 11 for 6T is a thing.
I ran the program as an administrator.
I tried multiple USB ports, all with the driver properly installed.
I reinstalled drivers (signature patching is disabled and I don't assume drivers are the issue)
I restarted both the phone and computer multiple times.
I disconnected and reconnected the USB over and over, holding both volume buttons.
Why would I be getting a "device does not match image" and how can I bypass it to force the upload anyway?
I am using an INTERNATIONAL unlocked version. NOT a T-Mobile version. Since I can't access fastboot mode, I was not able to adjust certain settings. USB debugging was enabled, though, could this be the issue?
Hi,
Wrong Section please post in the correct thread to receive optimal answers.
arjunbalan1994 said:
Hi,
Wrong Section please post in the correct thread to receive optimal answers.
Click to expand...
Click to collapse
So what thread should this be posted in? Because I have the same problem/question and can't seem to find an answer. . .