[Q] Unlocking Bootloader (error "malfunctioning USB device", Windows 8, Neo V)
I'm currently trying to unlock the bootloader of my Xperia Neo V using the official instructions: unlockbootloader.sonymobile.com/instructions
But I'm stuck at point 12/13. I can't correctly connect my device with the computer. I'm pressing Fastboot and pluging in the USB Cable (I tried it in every possible order and at the same time). Fastboot is the Menu-key on my device.
On Windows (8) I get the following error message:
At first I got an error saying that my decive is malfunctioning or so.
I tried to install the driver anyways. In every possible way I know of. But I keeps saying "error encounted while attempting to install".
What am I doing wrong?
I'm on Windows 8 Pro, my device is a Sony Ericcson Xperia Neo V (rooted, default ROM 2.3.4)
My computer has USB 3 only in case that matters.
Here are some screenshots of me trying to install the drive:
multiurl.com/ga/ScreenshotsNeoVFastboot
I hope you can help me. :/m
Best regards,
Ferivon
edit: I jsut realize that I never closed the error I got at first. Here is a screenshot: 250kb.de/u/140526/p/hrRGbwE1NWwk.png
edit2: I finally got a chance to test it on windows 7 and it worked instantly... just screw windows 8 ...
...
oops, wrong place
Related
Hi there,
I'm the owner of a new Xperia Mini - which is broken now because:
When Unlocking 2011 XPERIAs’ Bootloader without losing DRM (with Testpoint method) my Windows XP system crashed in the end of the install of the Zeus Flash Driver.
After that I got it installed on another stable system (Windows XP & Windows 7), but after that in the final step in s1tool it always says "can't get S1 command header LOADER NOT RESPONDING" after pressing "Testpoint READY" (Process2) button.
Now, if I connect the phone via usb (even without pressing testpoint) the "Zeus Flash Device" appears in device manager. But thats the only sign of life I got from my phone (no lights, no vibration, etc.)...
But furthermore there is one important thing: even if it shows no green light it appears as "SEMC Flash Device" after running the s1tool step from above (with this "LOADER NOT RESPONDING" error message), and this seems-like-a-flashmode-mode stays as long as the cable is connected!
I really hope that this is enough to repair it. For example with the "Restore" button in s1tool ... but before doing it, I wanted to here your expert opinion.
Thanks for any help and hints!
.
Try wotanserver to restore firmware
What he said
Sent from my ST18i using xda premium
i'm using test point method for unlocking bootloader on my neo v (http://forum.xda-developers.com/showthread.php?t=1409269&highlight=zeus+flash)
step 2 is: "Connect test point to the ground and attach USB cable. Wait while Windows shows finding new device, disconnect test point immediately. Windows won't find appropriate drivers... select drivers manually from the archive of SEtool. Agree to install 'untrusted' drivers.
3. Reboot your PC"
I disconected test point when windows showed "finding new device" but... my windows 7 DID find and installed new device (I didn't select drivers manually from the archive of SEtool)
is it safe to continue to step 3 and 4?
3. Reboot your PC
4. Run s1tool, press 'Patch semcboot' and follow tho on-screen instruction.
is there any chance that it will brick my neo v?
Are you sure you picked correct test point?
When you connect test point and cable, which device appears in device manager?
Yes I chose right test point.
Cant remember name of device.... It was something qx.... W.... B... (I uninstalled it)
But in properties it was zeus flash drive..... or zeus usb drive....
When I was rooting my neo I installed some drivers for neo v. Is that maybe the reason why windows installed this automaticly?
prdek said:
Yes I chose right test point.
Cant remember name of device.... It was something qx.... W.... B... (I uninstalled it)
But in properties it was zeus flash drive..... or zeus usb drive....
When I was rooting my neo I installed some drivers for neo v. Is that maybe the reason why windows installed this automaticly?
Click to expand...
Click to collapse
It's : "ZEUS Flash Device"
Hi everybody,
I've been searching on forums, tried multiple solutions but nothing helps. Though I'm familiar with all this, I'm just stuck on one point which makes all this unlocking process very frustrating. My phone is a Xperia P (JB) and I went to Sony's dev page in order to unlock the bootloader. Unfortunately, even if my phone is eligible for unlocking, I just cannot pass one of the point: fastboot mode.
Basically, when I power on, vol up, fastboot mode is enabled for a few seconds only (led) then disconnects from my device manager and stays with an amber (orange) led on. I just can't have my phone stay in fastboot mode. Same if I go with the command line adb reboot bootloader...
After looking for this problem on various forums, I've tried to update the drivers to (S1 fastboot) found on multiple posts, didn't help. I thought it was a problem with my PC (Win 7_64) so I tried with a fresh install in 32bits on another disk, didn't help. Tried even with Win 8 64 and 32, no chance... USB debbuging is on.
Is anyone experiencing the same problem or has anyone a solution for this? I'm just getting mad by not being able to unlock it.
Hi! I think that the driver is not properly installed! Another site I found this description to see if it helps!
Install Sony Xperia (P / U / Sola / Go) Driver and fastboot in Windows 7
Sony Xperia Driver Installation
Go to Setting > Development
Check USB Debugging
connect Xperia (P / U / Sola / Go) to PC / laptop
Open device manager
Right Click on SEMC HUSB (it should have a yellow triangle warning)
Then select “Update driver software”
Choose “Browse My computer for driver software”
Choose “let me pick from list of device driver on my computer”
Click “have disk” button
Browse to Xperia_P_Xperia_U_Xperia_sola_drivers extract folder
Select sa0104adb.inf
Approve all confirmation
Click OK
Sony Xperia Fastboot Installation
Turn off Xperia
Open Windows 7 device manager
Press and hold Volume[+] Sony Xperia button
Connect to Pc / Laptop
Right click on yellow triangle warning (device warning)
Choose “Update driver software”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list of device driver on my computer”
click “Have a disk” button
Browse to fastboot driver extract folder
Select android_winusb.inf
Approve all confirmation
Done
Note:
A sign that fastboot connection is success is LED will stay in purple
In fastboot installation, open device manager before connect the device is a trick. A yellow triangle (device warning) only appears around 5 sec
It`s better to restart the windows after driver and fastboot installation
Download Support Files
Download Sony Xperia (P / U / Sola / Go) Driver
Download Sony Xperia Fastboot driver
Hi Rajen,
Thanks for your help... I've done all this before, repeated it now step by step but no luck... Cannot have my P to stay with purple light on (fastboot). It still stays purple for 3-4 seconds then amber.
Any other idea?
@swissman you should open device manager on Windows 7 first then connect your phone......when its connected youll see anerror or something sign there and click it then choose install driver from pc......navigate to those drivers and Finish....hope this helped....
Sent from Space!
Hi! Thank you... I really did that... I think almost 20 times but nothing helps. I think I've done almost everything possible (Imagine, thinking that it might be a 64bits issue and Win 7, I've even tried to downgrade to Win 7 32 and Win 8 32! ..
But nothing helps. It installs correctly the drivers, computer reboot (or even not), replug the phone with Vol up and still getting a 3-4 seconds purple LED and then disconnection. I'm getting mad as I tried almost everything I found on XDA or others but nothing helps.
The only thing I haven't tried yet is to downgrade to ICS, try to unlock the bootloader and upgrade back to JB
Ok, I finally have been able to unlock it. What I did, VM with Windows 7 64, booted in fastboot and updated drivers with "Android ADB Interface" drivers from Google directly (not the one provided with SE modifications)... My phone stays now in fastboot and has been successfully unlocked.
Don't ask me how it did happen, I'm just being happy to have it fully under my control
Anyway thanks guys for your help!
When the purple led doesn't last it means you haven't installed it correctly......the thing we are teaching you is I think, a shortcut method,just in order not to install to many files.......so I recommend installing the whole android SDK if you have time......
Sent from Space!
Thats right good work
Sent from my ST27i using xda app-developers app
After browsing forums this what I found http://forum.xda-developers.com/showthread.php?p=23794050.........that is the exact way that you should do....
Sent from Space!
Hi, can anybody help me. I just flashed my locked bootloader x10i with Feralab kernel- [LB]FeraKernel-v15.1-GB just like it instructed ( at this point it is still fine).Then i flashed the Feralab rom -FeraLab_v30.5_Final through CWM ,After that, i try to reboot it ,but the phone just stuck at the sony ericsson text .
When i want to flash it back to stock with flashtool, it wont detect my phone ,it say error , flashing aborted .When i try to flash it to stock with Flashtool 0,291 , it says ERROR - USB\VID_0FCE&PID_ADDE\5&1E642C5D&0&1 and my computer says USB DEVICE CANT BE RECOGNIZED ,I think this is driver related problem cause when I check through Device Manager , I can see a yellow warning mark beside
SEMC Flash Device(it says "A request for the USB BOS descriptor failed." ) and USB Mass Storage Device .I already reinstall PC companion in my windows 8 computer but the problem still persist.
Can anyone help me with this , I mean i cant even get it into flash mode after doing the pressing back while connecting the USB thing to flash it back to stock.
pulldtrigger said:
Hi, can anybody help me. I just flashed my locked bootloader x10i with Feralab kernel- [LB]FeraKernel-v15.1-GB just like it instructed ( at this point it is still fine).Then i flashed the Feralab rom -FeraLab_v30.5_Final through CWM ,After that, i try to reboot it ,but the phone just stuck at the sony ericsson text .
When i want to flash it back to stock with flashtool, it wont detect my phone ,it say error , flashing aborted .When i try to flash it to stock with Flashtool 0,291 , it says ERROR - USB\VID_0FCE&PID_ADDE\5&1E642C5D&0&1 and my computer says USB DEVICE CANT BE RECOGNIZED ,I think this is driver related problem cause when I check through Device Manager , I can see a yellow warning mark beside
SEMC Flash Device(it says "A request for the USB BOS descriptor failed." ) and USB Mass Storage Device .I already reinstall PC companion in my windows 8 computer but the problem still persist.
Can anyone help me with this , I mean i cant even get it into flash mode after doing the pressing back while connecting the USB thing to flash it back to stock.
Click to expand...
Click to collapse
The bootloader should be unlocked first if am not wrong.
ronaksworld said:
The bootloader should be unlocked first if am not wrong.
Click to expand...
Click to collapse
Really , well I thought you can flash Feralab even on locked bootloader Well I guess I get that part wrong . Do you have any idea how to fix the problem above
Solved!
Well guess what , I finally able to flash my phone. First, I detect the all the driver that related with x10i and uninstall its driver completely. Then, I install the driver by disabling driver signature enforcement in windows 8.After that , the usual flashing to stock.
pulldtrigger said:
Well guess what , I finally able to flash my phone. First, I detect the all the driver that related with x10i and uninstall its driver completely. Then, I install the driver by disabling driver signature enforcement in windows 8.After that , the usual flashing to stock.
Click to expand...
Click to collapse
Maybe ask someone in ***FeraLab*** Official - Break The Limits. threat?
http://forum.xda-developers.com/showthread.php?t=1458001
as even am new around here i would suggest you to make at least 10 post then u can visit the above link and ask for help in that threat.
as you said the boot loader was locked and the flashing failed and you are stuck at sony erricson screen, i think you can use Sony PC Suite and restore it to factory (consult someone else too or search in the forums),
BLU in the Flash Tool is the one you should use first to Unlock bootloader, before that backup the device,
Advance\Trim Area\S1 and Raw Device., i did both the methods and i didnt knew what was the best
This [ROM] AOSP JB 4.2.2 - Unlock Bootloader Only, is the one i used and works perfectly fine on my xperia x10i :victory:
http://forum.xda-developers.com/showthread.php?t=2197387
Hi everyone,
I recently tried to flash a newer stock ROM (2.1..1.A.0.28) on my X10 Mini Pro (U20i) in order to go on with higher tinkering (i.e. installing Gingerbread)(yes, I know, this is the century of the fruitbat, but I bought the phone a few days ago because of its nice format).
I used FlashTool 0.9.22.3 on PC Ubuntu 14.04. The phone was recognized properly. At some point, the flash process died with error (while processing loader1.sin). Of course now the phone does not boot anything (although it turns on and do something, as I explain below). I want to flash a more standard stock ROM (2.1.1.C.0.0, say) to regain access to the phone.
My problem: I cannot flash it anymore (PC Companion, Xperia companion, SEUS on Win7 or FlashTool on Linux). The symptom is the following: when I turn the phone on it is in flash mode (seen in dmesg as a "SEMC USB Flash" device, lsusb command gives
Code:
ID 0fce:adde Sony Ericsson Mobile Communications AB C2005 (Xperia M dual) in service mode
After about 20s that device disconnects and reconnects as a "SEMC HSUSB" device (as seen in dmesg, lsusb gives
Code:
ID 0fce:3138 Sony Ericsson Mobile Communications AB Xperia X10 mini pro
and I have a "funny" logo with a warning sign. After about 20s it reboots (I guess) and reverts back to flash mode. And so on.
This behaviors occurs even when the phone is not connected to the PC via USB.
My device is not recognized anymore in FlashTool, it is briefly recognized under Win7 when switching to HSUSB mode (well, I have Win7 in a VM so additional issues may arise from that setting). The device does not stay in either mode long enough for anything usefull to happen or be allowed to happen.
So: I'm stuck. I hope the device is not hopelessly bricked. Any help from specialists here would be greatly appreciated !
EDIT: flashtool finally managed to flash a 2.1.1.A.0.6 kernel (this thread), allowing me to boot it normally. I don't know why it accepted that flash and not the other. Yet the device is still not recognized (says "USB debugging off" although it is marked "on" in the phone settings). I'll keep the thread updated if I make any progress.
EDIT: device was not recognized because it was in "charging" mode Ok, now I need to find a suitable stock ROM which is both recognized by flashtool (I've got a couple of them not showing up in the dialog) *and* downloadable on the net nowadays