Im flashing Stock Rom via Mobile Odin after my phone soft bricked. No recovery, only download mode. I phone connect to pc.... Error mesage " USB Device not recognized " Code 43
When I want to turn on the phone, the blue logo appears. It's always restarting again.
Sorry for my bad english.
Please help
Karansa22 said:
Im flashing Stock Rom via Mobile Odin after my phone soft bricked. No recovery, only download mode. I phone connect to pc.... Error mesage " USB Device not recognized " Code 43
When I want to turn on the phone, the blue logo appears. It's always restarting again.
Sorry for my bad english.
Please help
Click to expand...
Click to collapse
Wipe your data and then try......you phone will boot up.......
Sent from my SM-A710F using Tapatalk
Karansa22 said:
Im flashing Stock Rom via Mobile Odin after my phone soft bricked. No recovery, only download mode. I phone connect to pc.... Error mesage " USB Device not recognized " Code 43
When I want to turn on the phone, the blue logo appears. It's always restarting again.
Sorry for my bad english.
Please help
Click to expand...
Click to collapse
Install USB drivers of your android in computer.
AshTechsoft said:
Wipe your data and then try......you phone will boot up.......
Sent from my SM-A710F using Tapatalk
Click to expand...
Click to collapse
Thanks for reply, no boot recovery only download mode
Karansa22 said:
Thanks for reply, no boot recovery only download mode
Click to expand...
Click to collapse
Install your USB drivers in PC then PC recognizes your USB device. Then flash stock rom using Odin in download mode.
Karansa22 said:
Thanks for reply, no boot recovery only download mode
Click to expand...
Click to collapse
Install latest samsung usb driver:-
Here is the link of latest driver:-
http://samsungusbdriver.com/download/samsung-driver-v1-5-61-0
Install this driver then try to connect your phone with pc in download mode.......
Sent from my SM-A710F using Tapatalk
AshTechsoft said:
Install latest samsung usb driver:-
Here is the link of latest driver:-
Install this driver then try to connect your phone with pc in download mode.......
Sent from my SM-A710F using Tapatalk
Click to expand...
Click to collapse
I try it. Not fix
The first connection was no problem, then I always get this error
Karansa22 said:
I try it. Not fix
The first connection was no problem, then I always get this error
Click to expand...
Click to collapse
Try to connect in other PC.......[emoji335]
Sent from my SM-A710F using Tapatalk
AshTechsoft said:
Try to connect in other PC.......[emoji335]
Sent from my SM-A710F using Tapatalk
Click to expand...
Click to collapse
I also tried 4 computers. My computer also recognized it, but the odin an error. " Get pit for mapping file"
Com3 Added stock rom flashing. Stuck at error message... After usb re-connection always received not recognized error
Karansa22 said:
I try it. Not fix
The first connection was no problem, then I always get this error
Click to expand...
Click to collapse
http://www.online-tech-tips.com/computer-tips/usb-device-not-recognized/
Try these solutions. It may help you.
Karansa22 said:
I also tried 4 computers. My computer also recognized it, but the odin an error. " Get pit for mapping file"
Com3 Added stock rom flashing. Stuck at error message... After usb re-connection always received not recognized error
Click to expand...
Click to collapse
Give me the screenshot of your error and odin logs....
Then I'll do something for you
AshTechsoft said:
Give me the screenshot of your error and odin logs....
Then I'll do something for you
Click to expand...
Click to collapse
http://i.hizliresim. com/1Vgd25.jpg delete space
Karansa22 said:
http://i.hizliresim. com/1Vgd25.jpg delete space
Click to expand...
Click to collapse
I want first screenshot from your computer while flashing via odin
And
Second screenshot also from computer when it was not recognize your device.
(You can take screenshot in windows computer by pressing "windows key" + "printscr key" together of keyboard...)
Sent from my SM-A710F using Tapatalk
AshTechsoft said:
Give me the screenshot of your error and odin logs....
Then I'll do something for you
Click to expand...
Click to collapse
Now not recognized usb odin logs not see
Same error win8.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AshTechsoft said:
I want first screenshot from your computer while flashing via odin
And
Second screenshot also from computer when it was not recognize your device.
(You can take screenshot in windows computer by pressing "windows key" + "printscr key" together of keyboard...)
Sent from my SM-A710F using Tapatalk
Click to expand...
Click to collapse
Help me
Help
Karansa22 said:
Help
Click to expand...
Click to collapse
Download windows USB troubleshooter and run on your PC.
Ashwinrg said:
Download windows USB troubleshooter and run on your PC.
Click to expand...
Click to collapse
Thanks for help, I try it.
Only Dedected text message, dont fix problem
Karansa22 said:
Thanks for help, I try it.
Only Dedected text message, dont fix problem
Click to expand...
Click to collapse
Go to device manager. Under USB delete all USB drivers with yellow exclamation mark. Click on properties then go driver tab and click on uninstall and tick on delete driver and uninstall.
Restart your PC and see.
Related
My phone was running KE7 stock (rooted with CFroot 4).
Today I tried to flash a new rom via Odin 1.85. For some reason it failed (red box). Btw re-partition was not checked (I followed instructions to the letter).
Now when I activate the phone with the power button, or with the VolUP+Home+Power button, this is what I get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(edit: now I see that I get this image even when I try to charge the phone when it's off. I don't get the big battery icon anymore...)
I can still get to the download mode (VolDown+Home+Power button), but I tried to flash a new ROM (Lightning 5) via Odin 1.85, and it got stuck at the factoryfs stage. I tried to flash this rom again and now it failed (red box).
I saw that on the Lightning 5 thread he say to make sure to be in debugging mode before going to the download mode (is this true for every rom flashed with Odin ?), but I didn't do this because I can't get into android now to change to debugging mode.
Have I bricked the phone ?, is there anything I can still do ?
Thank you very much to anyone who can help !
Wow, 29 views and not a single reply, I guess this is not good...
Ok, I've downloaded the KE7 stock ROM, and tried to install it via Odin 1.85.
This is the initial Odin screen (before I press start):
And this is what I see after I press start. It stays like this for several minutes so I gues it's stuck
What now ?
What you have to do is wait, it does not say fail yet.
Ok, I was under the impression the sbl.bin stage shouldn't take more than one minute max... (and I gave it about 5 minutes before I gave up).
I started it again and now will give it 30 minutes...
Can flashing via Odin be done without first enabling debug mode in android ?, because I didn't enable it as far as I remember (the guide that I followed forgot to mention this...). Could this be why Odin can't write to the phone ?
Ok, you need to use odin in a very specific way. Follow my directions exactly and see if it works.
Turn off your phone.
Open Odin and load the correct file/files.
Boot your phone into download mode.
Connect your usb cable to the phone/computer.
Once you get the yellow connection block, hit flash.
Do all of this in the right order and you should be ok.
If you have the usb cable plugged in while entering download mode, it won't work.
If you unplug the usb cable and plug it back in while in download mode, it won't work.
If you have the usb cable plugged in before you open odin, it might not work.
Sent from my GT-I9100M
Electroz said:
Ok, you need to use odin in a very specific way. Follow my directions exactly and see if it works.
Turn off your phone.
Open Odin and load the correct file/files.
Boot your phone into download mode.
Connect your usb cable to the phone/computer.
Once you get the yellow connection block, hit flash.
Do all of this in the right order and you should be ok.
If you have the usb cable plugged in while entering download mode, it won't work.
If you unplug the usb cable and plug it back in while in download mode, it won't work.
If you have the usb cable plugged in before you open odin, it might not work.
Sent from my GT-I9100M
Click to expand...
Click to collapse
Thanks Electroz.
I've followed your instructions carefully, to no avail. I'm still stuck at this sbl.bin... (I've waited for 30 minutes, surely something is wrong).
What else can I try ?
I'm using a Nokia micro-usb cable, could this be a problem ?, also, the USB cable is not connected directly to a USB socket in the motherboard, rather to a USB splitter (it worked ok with Kies like this). I tried connecting the phone directly to a USB socket in the motherboard, but I get a "USB Device Not Recognized" message, not sure why...
I don't have whatever phone your using( just saw this as a new post didn't see the name) but I assume it's a samsung. With the epic it's usually the usb cable and get a blackberry cable for 1-2$ that's what helped me. Also try pulling the battery first and plug it into the computer and then go into download mode. Taking the sd card might help too.
Sent from my SPH-D700 using XDA App
Yes, the splitter could be the issue. Try directly to the computer. Also, trying a different cable, also directly connected might work too.
Sent from my GT-I9100M
I am not sure about the s2 but the galaxy s that I have would get the same icon in the screen when Odin failed. Doing Odin again though would always fix it because I could get to download mode. Try using different ports on your PC and if that doesn't work try another PC. Also do you have the stock Odin parts to flash not a new rom.
Sent from my T959 using XDA Premium App
that's definitely not bricked though, that screen of the phone and computer with an error sign is a good sign. Samsung phones are basically unbrickable. But try a different cable and pulling the battery
Sent from my SPH-D700 using XDA App
I'm trying to connect the phone to a USB socket directly on the motherboard (tried with 2 different computers), and every time I get a "USB device not recognized" message. The only way that the phone is recognized correctly is if I connect it to a USB splitter that I have.
Maybe this Nokia cable is not good for the SGS2 (Nokia CA-101 cable), but it is advertized as compatible with the Galaxy devices...
Hopefully this is a cable issue, tomorrow I will try with an original samsung galaxy S cable and maybe this will solve it....
Thanks for all you help for now guys !
Don't bother with the stock samsung cable, it's terrible, like I said before try to find a cheap blackberry cable. All micro usb cables are compatible because they charge and transfer data. But not all are good quality.
Sent from my SPH-D700 using XDA App
I would also suggest downloading new copy of Odin again
Sent from my GT-I9100 using XDA Premium App
First off, no you do not have a bricked phone. Just follow my instructions exactly and you will get everything running again.
1. Download a stock rom from your country from samfirmware.com.
2. Boot your phone into download mode and flash the stock rom.
3. Impotant. Boot your phone into recovery mode immediately after u flahed the stock rom and wipe data/factory reset, and your phone should be running just fine after reboot.
Sent from my GT-I9003 using XDA Premium App
bobthemarley said:
Don't bother with the stock samsung cable, it's terrible, like I said before try to find a cheap blackberry cable. All micro usb cables are compatible because they charge and transfer data. But not all are good quality.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I think you'll find this is not the case. So many people ending up with failed flash because they use Nokia and HTC cables to flash the device.
Just use the Samsung cable to flash and it will complete successfully.
I would also suggest downloading new copy of Odin again
Click to expand...
Click to collapse
I tried, still stuck at sbl.bin
First off, no you do not have a bricked phone. Just follow my instructions exactly and you will get everything running again.
1. Download a stock rom from your country from samfirmware.com.
2. Boot your phone into download mode and flash the stock rom.
3. Impotant. Boot your phone into recovery mode immediately after u flahed the stock rom and wipe data/factory reset, and your phone should be running just fine after reboot.
Click to expand...
Click to collapse
I tried to do what you say, but the thing is that the Odin flash process always get stuck right at the beginning at sbl.bin
I'm starting to think this must be a hardware problem, either the USB cable or the phone's USB port. This could explain the following problems that I have:
1. Stuck at sbl.bin when trying to flash a stock ROM with Odin.
2. Stuck at Factoryfs when trying to flash Lightning Rom 5 with Odin.
3. When the phone was working, I could connect with Kies through USB, but when I went to the "Contact" tab in Kies, it never showed the contacts, it got stuck during the reading process.
4. Everytime I try to connect the phone (when in DL mode) to a USB port directly on the motherboard (and I tried different ports on different computers) I get a "USB Not Recognized" message. The phone is only recognized when connected to a USB splitter.
I already had this kind of problem.
I think i solved it by reinstalling the drivers (you can do it through the Kies interface).
You can also try to launch Odin as administrator.
Another method that gives excellent results is a Jig.
You can buy one on ebay, it's something like 3€
You could try to download everything again. (Odin,drivers,files)
And make sure that KIES is NOT running.
Also directly put the Samsung usb cable in your pc.
You have a good chance to bring it back to life.
If this won't work maybe your Galaxy is bricked because of bad usb cable/usb port or whatever.
BadWolfy said:
Another method that gives excellent results is a Jig.
You can buy one on ebay, it's something like 3€
Click to expand...
Click to collapse
If you had actually read the thread you would have known he has no problem getting into download mode.
Protip smartypants: USB jigs arent magical things that fix everyones phones with a snap of the fingers.
When my Xperia S plugs into FlashMode, he is only 10 seconds and falls quickly, disconnects FlashMode and FlashTools say error.
How to solve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you run flash tools at Linux or vmware windows?
You may use pure window to try again.
Sent from my Galaxy Nexus using XDA
I run in windows vista.
Already solved the problem. I started Flashtools first, after, xperia S.
Thanks.
Close topic.
joaonds said:
I run in windows vista.
Already solved the problem. I started Flashtools first, after, xperia S.
Thanks.
Close topic.
Click to expand...
Click to collapse
I've the same problem, so you solved it turning on the Xperia FlasMOD after opening the FlashTool?
Right?
Braska90 said:
I've the same problem, so you solved it turning on the Xperia FlasMOD after opening the FlashTool?
Right?
Click to expand...
Click to collapse
Yes, open FlashTools first and dont connect Xperia S yet.
Click FlashMode, and Start the Flash.
Wait when the FlashTools say (in a windows pop up): " Turn Off your Device, Unpluged..." you connect your xperia S in your PC (in flashmode) with UBS cable, and solved the problem...
joaonds said:
Yes, open FlashTools first and dont connect Xperia S yet.
Click FlashMode, and Start the Flash.
Wait when the FlashTools say: " Turn Off your Device, Unpluged..." you connect your xperia S in your PC with UBS cable, and solved the problem...
Click to expand...
Click to collapse
Thanks a lot
Why mine always goes on fastboot mode instead of flashmode? I tried both up volume botton and down volume button but every time goes on fastboot..
carmello1911 said:
Why mine always goes on fastboot mode instead of flashmode? I tried both up volume botton and down volume button but every time goes on fastboot..
Click to expand...
Click to collapse
That's impossible,vol down is the green led means flash mode,vol up is blue led means fastboot mode.
Sent from my LT26i using Tapatalk 2
figured it out lol! thanks!
Sent from my BlackBerry Runtime for Android Apps using XDA App
joaonds said:
I run in windows vista.
Already solved the problem. I started Flashtools first, after, xperia S.
Thanks.
Close topic.
Click to expand...
Click to collapse
Same problem here. And this WORKS!! Thanks dude! :good:
Odp: Please: My Xperia S dont conect in FlashMode, solution ?
silvershiver0323 said:
Same problem here. And this WORKS!! Thanks dude! :good:
Click to expand...
Click to collapse
We have new record in refreshing old threads!
Sent from my LT22i using xda-developers app
Vaith said:
We have new record in refreshing old threads!
Sent from my LT22i using xda-developers app
Click to expand...
Click to collapse
Sorry for bringing this one up but I keep having the same problem.
-Start Flashtool
-Look for firmware to flash
-Wait for Flashtool to ask to go into flash mode.
-with device off, holding Vol DOWN I plug the usb cable
-Says connected in Flas Mode and after 10 sec it says device disconnected, USB Debugging OFF
Help
same trouble
WitchMX said:
Sorry for bringing this one up but I keep having the same problem.
-Start Flashtool
-Look for firmware to flash
-Wait for Flashtool to ask to go into flash mode.
-with device off, holding Vol DOWN I plug the usb cable
-Says connected in Flas Mode and after 10 sec it says device disconnected, USB Debugging OFF
Help
Click to expand...
Click to collapse
I've got the same problem.
I've tried everything but the phone just wont stay in flashmode. Is it the phone or its a bug in the Flash tool.
Any workarounds anyone?
noob7373 said:
I've tried everything
Click to expand...
Click to collapse
Wowo that's quite a lot.
Do you mind being more specific?
Made it work!
ChikeD said:
Wowo that's quite a lot.
Do you mind being more specific?
Click to expand...
Click to collapse
It seems a bit tricky, however the workaround previously mentioned in this thread worked for me too. I'll just mention the step by step process for getting through this problem.
>make sure your device is not connected to the computer.
>start FLASH TOOL.
>press flash and select the version of firmware you want to upgrade/downgrade to from the pop up. (Assuming you might have already downloaded the required firmware in your flash tool installed folder.)
>now FLASH TOOL will prompt you to connect the phone. Do so. While pressing the "down vol button" of your switched off device
(for Xperia S/SL). The phone will go into flash mode and you can see green notification light up in your phone.
>There you go, your firmware will flash and phone will be rebooted.
All right. So, important:
If you have WINDOWS 8.1, then don't even try to get flashmode/fastboot. Trust me, it won't work. And yes, different problem than it was on windows 8. As I searched, I think there is a main problem with USB inf files themselves on windows 8.1, and yet you can't put correct drivers on it, because it doesn't even recognize the phone in fastboot or flash mode. Search on google, and you'll find some answers, and there is a fix that maybe works with USB 3.0, but I don't have usb 3.0, so I cant test it
HOW TO UNBRICK A ZOPO ZP950+
After spending some time on Russian forums I found a way to un-brick my device.
Hopefully this will be useful to other people as well .
You will need:
1. SP Flash Tool - ATTACHED
2. preloader.bin from another simillar MT6589 ROM (I used the one from the latest official Iocean X7 ROM) - PRELOADER
3. Latest JB 4.2.1 from Zopo - ZOPO 4.2.1 ROM - http://zopomobile.com/xiazai.php
4. MT6589 drivers - ATTACHED
STEPS:
1. Install the MT6589 drivers on your WINDOWS computer
2. take the battery out of your phone and connect the USB cable, windows should install the required drives. Disconnect the phone
3. Start SP Flash and select the scatter file from the archive you have downloaded
4. DESELECT EVERYTHING except PRELOADER
5. Click on PRELOADER and browse to the newly downloaded PRELOADER_UNBRICK file
6. Click on Download and ignore the message
7. Now, this is very important, while holding the VOLUME + button connect the USB to the phone, do not let go of the VOLUME + button, hold it until the SP FLASH process finishes, mine took about a couple of minutes, while the process bar went to 100% RED and then through a PURPLE if I remember correctly. Only let go of the VOLUME + when you see the last GREEN CIRCLE. ( IF SP FLASH CAN'T SEE THE PHONE WHEN YOU PLUG THE USB, STILL HOLDING THE VOLUME + BUTTON, INSERT THE BATTERY - THE PROCESS IS THEN THE SAME)
8. Now, if this went OK, you should have a brand new working preloader on your phone
9. Disconnect the cable from the phone and Restart SP Flash Tool
10. Same steps as before, select the scatter file, but now DESELECT the PRELOADER
11. click on DOWNLOAD and ignore the message
12. With the battery out reconnect the USB cable to the phone, if the flashing process doesn't start, insert the battery and the flashing process will start. It will take a good few minutes, but you should be OK.
13. DO NOT TAKE THE BATTERY OUT AFTER THE FLASHING PROCESS HAS FINISHED, JUST DISCONNECT THE USB CABLE AND PRESS THE POWER BUTTON
14. FINGERS CROSSED YOUR UNBRICKED DEVICE IS NOW POWERING
GOOD LUCK!
I AM NOT RESPONSIBLE FOR ANY DAMAGE THIS PROCESS MIGHT CAUSE TO YOUR DEVICE.THIS PROCESS MIGHT WORK WITH OTHER MT6589 DEVICES
Did this help you? Please feel free to leave a comment below. I'll try and help as much as I can.
Hi and thanks for the guide,
I just did the steps and my ZP980 2gb does flash preloader and then the rest of the rom, when i boot up its dead.
So flashing works but thats just about it.
No indication that its loading either...
Hi, did you follow the steps exactly? Also, I think you should try flashing a preloader from a Zopo C2.
Sent from my Nexus 4 using Tapatalk 2
punkthemonk said:
Hi, did you follow the steps exactly? Also, I think you should try flashing a preloader from a Zopo C2.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I flashed the phone again and used another usb cable, i Flashed preloader from "ZP980 SET 130818 B vers" holding volume up.
Restarted spflash and did the same procedure according to the guide by holding volume up but this time without the preloader and same scatter "ZP980 SET 130818 B vers" worked perfectly!
The phone is alive!
Super. I'm glad it worked.
Sent from my Nexus 4 using Tapatalk 2
Zeggi said:
I flashed the phone again and used another usb cable, i Flashed preloader from "ZP980 SET 130818 B vers" holding volume up.
Restarted spflash and did the same procedure according to the guide by holding volume up but this time without the preloader and same scatter "ZP980 SET 130818 B vers" worked perfectly!
The phone is alive!
Click to expand...
Click to collapse
Hi Zaggi,
I've faced the same problem with my ZP980-32GB and I try to follow your steps. Unfortunately, it's still does not success. For how long do you have to wait for the 100 % violet strip and Green circle in each time ?
apinun_po said:
Hi Zaggi,
I've faced the same problem with my ZP980-32GB and I try to follow your steps. Unfortunately, it's still does not success. For how long do you have to wait for the 100 % violet strip and Green circle in each time ?
Click to expand...
Click to collapse
It sounds like you need to try another USB cable or another port on your computer.
Are you sure you installed the drivers?
And BTW the phone has to be off, I did the steps with my battery connected.. Hope it helps.
Sorry for the late reply.
Skickat från min GT-I9300 med Tapatalk 4
Found your guide. I have the same issue with Jiayu G4 Advanced. I didn't flashed any rom, but suddenly yesterday the phone stopped to responding. I removed the battery and after put it back the phone switched on but stuck on Jiayu logo for minutes. Battery was charged.
I've noticed on windows device manager that there's no MTK Preloader Driver, only DA and USB PORT.
So I cannot revive my phone with this method. It's a hardware issue then.
eamelas said:
Found your guide. I have the same issue with Jiayu G4 Advanced. I didn't flashed any rom, but suddenly yesterday the phone stopped to responding. I removed the battery and after put it back the phone switched on but stuck on Jiayu logo for minutes. Battery was charged.
I've noticed on windows device manager that there's no MTK Preloader Driver, only DA and USB PORT.
So I cannot revive my phone with this method. It's a hardware issue then.
Click to expand...
Click to collapse
I have your identical problem with the same phone and i'm trying to find a solution too...
I know this is an old post, but did you find anything to it? something that can help me too?
My device does not turn on and only recognizes the USB PORT Single driver, when I try to use the flash this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The above procedure works for this error?
Oh God... My Zopo ZP950+ broken the Power, Vol+ and Vol- buttons, and NOW? What I will do? Please, help me!!!!
He saved my smartphone. Thank you very much.
P.S .: using google translator
Thank you!!!!
I used your method - had to do it a few times over but succeeded at last.
However I had used a few files from the backup i had taken of my phone before it was dead.
Thank you!
P.S. I used this method to unbrick my QMobile Noir Quatro Z4.
http://forum.xda-developers.com/showthread.php?t=3285608
stuck at the preloader step
Hello,
Im trying to unbrick my ZP950+, but im stuck at the preloader step!
I flashed the preloader form the latest official Iocean X7 ROM, as you said and i got the green circle! All good
But the i keep getting 4032 error for the rooms that i download from the zopomobileshop!
Can anyone help me?
Thanks
Pedro
Recently upgraded to MIUI 11, it wiped TWRP and root. Wanting to re-root.
In fastboot mode, device isn't recognised by Windows 10: shows up as "Unknown USB Device (Device Descriptor Request Failed)". ADB works fine, fastboot doesn't.
I've tried installing drivers from Google and Xiaomi, neither work. Pretty sure it's a driver problem, but not sure how to fix it.
Any help would be greatly appreciated, cheers.
Have you tried manual driver installation from device manager?
ijwad said:
Recently upgraded to MIUI 11, it wiped TWRP and root. Wanting to re-root.
In fastboot mode, device isn't recognised by Windows 10: shows up as "Unknown USB Device (Device Descriptor Request Failed)". ADB works fine, fastboot doesn't.
I've tried installing drivers from Google and Xiaomi, neither work. Pretty sure it's a driver problem, but not sure how to fix it.
Any help would be greatly appreciated, cheers.
Click to expand...
Click to collapse
- close digital signature verification in w10 (google it)
- install TOOL ALL IN ONE v2.1 zip (search on xda) and install drivers from it
- you should install xiaomi pc suite, MiFlasher so that any unforseeable drivers also get addressed and installed.
plz try and report back
piakos said:
Have you tried manual driver installation from device manager?
Click to expand...
Click to collapse
Yes, I tried to uninstall + delete the broken driver from device manager. It always goes back to the Unknown driver, and claims it's is up-to-date when trying to install anything else.
YasuHamed said:
- close digital signature verification in w10 (google it)
- install TOOL ALL IN ONE v2.1 zip (search on xda) and install drivers from it
- you should install xiaomi pc suite, MiFlasher so that any unforseeable drivers also get addressed and installed.
plz try and report back
Click to expand...
Click to collapse
OK, I put Win10 in test mode, so it installs any unsigned drivers. Installed the drivers from the ALL IN ONE tool and MiFlasher. Installed PC Suite.
No change, the device is still listed as Unknown while in fastboot and recovery mode.
Also, the device acts like it's being plugged out and plugged back in every few seconds while in fastboot or recovery mode, while completely stationary. This doesn't happen in system. Not sure if that's relevant, but it's weird.
Is there a way to clean out all the drivers I've installed and start fresh? I recall having driver issues with Nexus devices in the past, and wiping all android drivers was the solution.
ijwad said:
Yes, I tried to uninstall + delete the broken driver from device manager. It always goes back to the Unknown driver, and claims it's is up-to-date when trying to install anything else.
OK, I put Win10 in test mode, so it installs any unsigned drivers. Installed the drivers from the ALL IN ONE tool and MiFlasher. Installed PC Suite.
No change, the device is still listed as Unknown while in fastboot and recovery mode.
Also, the device acts like it's being plugged out and plugged back in every few seconds while in fastboot or recovery mode, while completely stationary. This doesn't happen in system. Not sure if that's relevant, but it's weird.
Is there a way to clean out all the drivers I've installed and start fresh? I recall having driver issues with Nexus devices in the past, and wiping all android drivers was the solution.
Click to expand...
Click to collapse
You should try downloading and install Qualcomm drivers manually.
Those drivers are specifically for Qualcomm devices and intended for fastboot mode and EDL mode
Darklouis said:
You should try downloading and install Qualcomm drivers manually.
Those drivers are specifically for Qualcomm devices and intended for fastboot mode and EDL mode
Click to expand...
Click to collapse
Installed the Qualcomm drivers, no luck. Device still unrecognised.
I managed to root it before, so I'm worried this is a weird software issue on my Poco that could be solved with a full format. I'd like to try as many options before getting to that though, my last full backup was a few months ago.
Could you attach some screenshot of error on fastboot
armuttaqin said:
Could you attach some screenshot of error on fastboot
Click to expand...
Click to collapse
Yep, here you go.
ADB works fine, but the device isn't recognised in fastboot mode.
1. ADB works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Fastboot doesn't
You dont have the fastboot driver installed.You have to install it when the phone is in fastboot mode.it happened to me as well.
hexisg said:
You dont have the fastboot driver installed.You have to install it when the phone is in fastboot mode.it happened to me as well.
Click to expand...
Click to collapse
The problem is, the drivers won't install in fastboot mode. This error comes up when I try to manually install drivers from Google, Xiaomi, or Qualcomm directly in Device Manager:
Are you on an AMD RYZEN platform?
Shinichi Kudo said:
Are you on an AMD RYZEN platform?
Click to expand...
Click to collapse
Nope, Intel CPU. The specs are below, if it helps.
Delete this device "Unknown USB device ..." from the device manager when you're connected.
Select "remove driver ..." as well in this process.
Disconnect phone
Reboot PC
Connect phone in fastboot mode
Install fastboot driver manually.
rolex0815 said:
Delete this device "Unknown USB device ..." from the device manager when you're connected.
Select "remove driver ..." as well in this process.
Disconnect phone
Reboot PC
Connect phone in fastboot mode
Install fastboot driver manually.
Click to expand...
Click to collapse
Just tried this. It gave the same error, saying that the best driver is already installed.
Also, the "remove driver" option isn't there when uninstalling:
You need to manually override the driver, e.g. force the installation of the Google Android USB driver.
You can try to remove all the drivers and after the cleanup just let the Mi Unlock software install them for you.
I have done this after a clean windows installation to get all the drivers installed even when my device is already unlocked.
The Mi Unlock tool installs all the necessary drivers for me, you can try this I guess.
I have other problem with mtp transfer works only when adb enabled
Hello IJwad, I have the exact same problem. It occured after installing Miui 11. Is it already solved for you?
Smellie2 said:
Hello IJwad, I have the exact same problem. It occured after installing Miui 11. Is it already solved for you?
Click to expand...
Click to collapse
I'm having the same issue too. any way t0o fix it?? I'm on miui11
---------- Post added at 09:53 PM ---------- Previous post was at 09:28 PM ----------
Shinichi Kudo said:
You can try to remove all the drivers and after the cleanup just let the Mi Unlock software install them for you.
I have done this after a clean windows installation to get all the drivers installed even when my device is already unlocked.
The Mi Unlock tool installs all the necessary drivers for me, you can try this I guess.
Click to expand...
Click to collapse
I tried this but doesn't work
i have the same issue, think the problem is with the miui11 update not the windows's because i can fastboot into other device but no luck with poco.
i hope the next update would fix this or maybe not. anyone tried reolving this issue ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it looks like, and if I try to boot into recovery or system it just says "no operating OS found."
Windows won't recognize it when trying to connect via USB.
Any way to fix this? Help would be greatly appreciated.
DustyFukuyama said:
View attachment 5759871
This is what it looks like, and if I try to boot into recovery or system it just says "no operating OS found."
Windows won't recognize it when trying to connect via USB.
Any way to fix this? Help would be greatly appreciated.
Click to expand...
Click to collapse
It's in fastboot mode. Have you tried using a different cable to connect to the PC? It must be a USB data cable. Also, have you downloaded the Motorola driver's on your PC and the latest driver's for adb/fastboot from Google? Another option is if you have another phone and a OTG adapter
Yeedatoy said:
It's in fastboot mode. Have you tried using a different cable to connect to the PC? It must be a USB data cable. Also, have you downloaded the Motorola driver's on your PC and the latest driver's for adb/fastboot from Google? Another option is if you have another phone and a OTG adapter
Click to expand...
Click to collapse
fsr I can't install Motorola USB Driver. It always says "the parameter is incorrect" when I do it, and I've tried all kinds of solutions to fix it. I'll try install it on my friend's laptop tonight and see if I can fix it there.
Yeedatoy said:
It's in fastboot mode. Have you tried using a different cable to connect to the PC? It must be a USB data cable. Also, have you downloaded the Motorola driver's on your PC and the latest driver's for adb/fastboot from Google? Another option is if you have another phone and a OTG adapter
Click to expand...
Click to collapse
So I successfully installed the Universal ADB Driver and Motorola USB Driver on my other computer and it still won't recognize my phone while in the fastboot mode. Any idea why this is the case?
DustyFukuyama said:
So I successfully installed the Universal ADB Driver and Motorola USB Driver on my other computer and it still won't recognize my phone while in the fastboot mode. Any idea why this is the case?
Click to expand...
Click to collapse
Make sure to install these. They were updated. Then, go to device manager on your PC, click add new drivers and manually find the location of all new drivers and make sure they install. Make sure the phone isn't plugged into the PC when you do this. Reboot the pc. When it boots, plug the phone in but not in fastboot. See if it will get discovered in regular adb. If still nothing, click update drivers manually and the option to choose which. Go to Google adb, click install. Try again
DustyFukuyama said:
So I successfully installed the Universal ADB Driver and Motorola USB Driver on my other computer and it still won't recognize my phone while in the fastboot mode. Any idea why this is the case?
Click to expand...
Click to collapse
I forget you're stuck in fastboot. Can you get it to boot into recovery? It will just show a green android logo with it's stomach opened up and say invalid command or some ****. Hold power and press either volume up or down until you see a new screen that has several other options... That's recovery. From there you can enter fastbootd. See if the pc recognizes fastbootd if you can't get the above solution to work. Also, you can avoid all this driver crap if you have another phone and an otg cable. Download Bugjaeuger adb from Google play and you can use the second device as a replacement for the PC
Yeedatoy said:
I forget you're stuck in fastboot. Can you get it to boot into recovery? It will just show a green android logo with it's stomach opened up and say invalid command or some ****. Hold power and press either volume up or down until you see a new screen that has several other options... That's recovery. From there you can enter fastbootd. See if the pc recognizes fastbootd if you can't get the above solution to work. Also, you can avoid all this driver crap if you have another phone and an otg cable. Download Bugjaeuger adb from Google play and you can use the second device as a replacement for the PC
Click to expand...
Click to collapse
So I solved the problem last night. Apparently, it was the USB cable. My PC won't recognize my phone in fastboot mode using this particular cable fsr. I never thought it was the faulty cable because it was working fine in Recovery and OS prior to brick, just not in fastboot. Thanks for the help, I really appreciate it!
DustyFukuyama said:
So I solved the problem last night. Apparently, it was the USB cable. My PC won't recognize my phone in fastboot mode using this particular cable fsr. I never thought it was the faulty cable because it was working fine in Recovery and OS prior to brick, just not in fastboot. Thanks for the help, I really appreciate it!
Click to expand...
Click to collapse
That's Awesome! Isn't it such a great feeling when it finally works!? Lol. I've been a victim of the faulty/wrong cable situation many times. It's so frustrating I can't begin to explain it. I've had phones that were left inoperable for 6 months because I gave up, and then came back with a clear head and sure as hell, it ended up just needing a different cable, even though I had already tried 4 different ones. It makes me want to destroy things! Lol. Glad you got it running again!