So , I'm trying to unlock my Xperia Ray's boot loader however i come across a problem. Once the pc detects the phone in S1 Fast boot mode , it try's to automatically find the drivers from the windows database thing. This is where i encounter the problem , Sony's Guide says to point it to the android_winusb.inf it asked me to replace earlier , however i see absolutely no option to do so. Any help would be much appreciated
-
Boot loader is unlock-able
[HELP] Root, Optimizations, Overclock, Battery, and More Tutorials (updated for ICS
should help you eneugh, I got the job done anyhow
Related
A friend of mine gave me his x10i phone to play, so i decided to follow all the proper steps to get the device rooted and install 2.3.4 on it.
I have downloaded the flashtool v 0.5.3.0, but it does not detect the device. I have also installed the drivers on the system from flashtool\drivers folder
When I click Check Drivers, i get the following output:
12/041/2011 16:41:47 - INFO - List of connected devices (Device Id) :
12/041/2011 16:41:47 - INFO - - USB\VID_0FCE&PID_612E\CB511ND245: OK
12/041/2011 16:41:47 - INFO - List of ADB devices :
12/041/2011 16:41:47 - INFO - List of fastboot devices :
Another problem I have is that Debug mode is on, but the flashtool always says it is off. I tried all i could including upgrading the stock rom from sonyericsson site, but at this stage, I am ready to give up. I do not see anyone else is experiencing this problem.
Any advice is appreciated.
screw the drivers in that folder
install the legit ones from the SE webstie
install the PC Companion and it will do everything for you
then try. If does not work message me or reply here
tried it all from scratch at home on windows 7 (first attempt was at work on XP).
At home everything worked fine Thanks!
do you want Unlocking you bootloader?
try my way, its stands in my signature.
I think i was able to unlock it. In fact, sorry, I do not know what "unlocking bootloader" is, but what makes me think that I've done it is that i was able to flash Doom kernel with wifi and one of the custom ROMs on it. Also I got root access on the phone. Recovery console (CWM ?) is working too.
Correct me if i am wrong, but this is as far as i can go with this device and nothing else needed to crack/install etc.
One issue i noticed is that GPS does not work and settings are just not there, but i guess it is a ROM/kernel related question which i will explore further.
unlock bootloader
makes it a lot easier and nicer when you install a custom rom
um
use flashtool
under plugins category
So I've been following the bootloader unlock instructions on the Sony-Ericsson site and when I have plugged the phone in and the instructions say it should ask me for drivers it just plays the driver install failed noise, so in device manager I have the S1Boot Fastboot listed but when I point the driver update wizard to the adb folder where the driver is it just says it cannot find it. Anyone had an issue like this or knows how to fix it or have I done something completely idiotic because it's 6am and I haven't slept for 2 days?
you need the google usb drivers (android sdk) good luck !
Yeah I got past this bit and have the phone unlocked now but during the proccess my camera, lockscreen and a couple of other bits have stopped working and I can't simply revert back to the original software as sony's tool won't allow that. Also can't find a clockworkmod recovery image for the device so have no clue how to put the cyanogenmod nightly that's out on.
Can't you use flashtool to flash a stock rom ?
Yup, all recovered now.
It would be much better if this most essential of sites for people mucking around with there android phones had a section for the Xperia Pro, there are already plenty of threads for the device but they are spread over every other Sony section and makes finding the thread that will help quite difficult.
Sorry about this being in the wrong section but it won't let me make a thread in the development thread, basically trying to unlock my bootloader, i've looked online for a few hours now, i follow instructions on unlockbootloader.sonyericsson.com but when i look for the drivers it doesn't find them. step 13 says:
"On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file." the android boot loader interface-file doesnt exist, i'm slowly losing the will to live. someone please help i want custom roms :'(
Hi , the metod of Sony Ericsson are so much slow , in the metod of s1tool in 30 seg
The method on Sony's site (same as on CyanogenMod's site) didn't work for my unbranded Mini Pro (SK17).
Neither did the testpoint (DRM-preserving) method - until I tried using a different USB port. It is indeed fast, when it works.
you need to install fastboot drivers . search fastboot_with_android_usb_file.rar on google, there will you get that file on mediafire.com, extract it. it contains driver. when asked for drivers, manually install drivers by pointing to extracted folder
Hey yeh its all done now and running nerodroid, thats exactly what I did and thanks for the help
Sent from my SK17i using XDA App
Perfect!
I have an Xperia mini pro sk17i with 2.3.4 Android. I'd like to flash newer/custom roms to it, but I've got a few questions/issues.
So far I've removed the sim lock and I *think* (it was a while ago now) I have unlocked the boot loader with the test point method. In service info it says "rooting status: Bootloader unlock allowed :yes", is that what I should see after a test point unlock? I also tried the fastboot.exe unlock, but that comes back saying that "phone is already unlocked". I don't recall whether I've rooted the phone or not.
Next step is I'd really like to take a backup of my stock rom before I reflash it. Is there a way to read the current firmware back off the phone and make an image file of it? Everything I found talks about a slightly different way to get it - using SUS (which doesn't work any more), or PC companion to download the firmware from Sony, and then create an image file from that. PC companion (v2.1) seems to get stuck in an infinite loop. Whenever it detects the phone, it comes up on the phone screen: "do you want to install the pc companion software on your computer". If I say yes it just downloads and installs what is already there. And then it just tells me that my phones memory is not accessible, and to check for sim card and screen unlocked. Even if they both are, it won't detect it.
I also tried to use the Sony program called "Emma", which I think does the same thing, but in bootloader mode? Yesterday I got it started and connected my phone, and I think it said my phone still needed boot loader unlocking first (but I thought it was. maybe not then)?? Today Emma won't even load - it says Win XP isn't supported any more, but I'm sure it worked yesterday on this pc!
I don't want to go any further without backing up the stock firmware if possible, so what should I try next?
Install CWM recovery then do a backup. Look around the stickies for links, there's plenty of tutorials for it. Good luck :
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.