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.
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
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!
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Gonna be a long read but I'd be glad if someone could help me. Plus, it is an interesting issue.
I use stock 6.0.1 with the july update(phone model 2303, locked bootloader, no root, no recovery) Today, I don't know why, all my apps started crashing. I mean all. Dialer, album, music, whatsapp, chrome... Turning my phone off and on did nothing. I tried several times. As everything was working great a just a few hours ago (and for years before that), I thought a factory reset could fix it. It didn't. Now phone starts with that first launch set-up thing and I keep getting errors of various apps crashing and the device does not proceed beyond the initial set-up.
So, I thought flashing a rom could fix it, however I can't seem to do that. I have flashtool however when I go into flashmode I can't see my phone. I have installed the fastboot and flashmode drivers, however couldn't find the xperia m4 aqua drivers on the driver list. Flashtool detects my phone on fastboot mode, but not in flashmode. I have read the guides, still no solutions.
Any suggestions on what to do?
edit: I have found "xperia m4 aqua" drivers on Sony's website, but Windows claims they are not suitable for my device and does not install them.
SOLVED: Using an older version of Flashtool worked for me. I used version 9.18
I bought a " Figo Atrium 5.5 ". The Figo website has instructions to flash the device to 6.0 Marshmallow instead of Lollipop. I believe these instructions are incomplete. Here is the link, I'll detail for you what I've tried using their recommended software SPFlash https://support.figoglobal.com/support/solutions/articles/16000047848-android-6-0-atrium-5-5
I downloaded and extracted both files on Windows 8 64 bit desktop, the SPFlash tool and the other the Atrium ROM itself. The very first instruction is installing the drivers which I do using the install.bat file from the "Driver_Auto_Installer_v1.352.00" folder. I believe my install fails at this point. Opening the Flash_Tool exe after installing the drivers (the tool does say they installed properly) I never get any information in the Chip Info in the Flash_Tool. It appears those drivers are not installed properly.
Researching this, I came across videos that suggest the drivers were not being installed properly because the drivers are Not digitally signed. I followed the instructions to fix the problem by booting to Advanced StartUp options then choosing to run the OS with digital signing checking disabled. Now on installing the drivers I get the popup asking me if I am sure I want to install the drivers I choose Install Anyway. The driver install tool just sits there for a couple of minutes doing nothing, then the popup message comes back asking again, am I sure I want to install the drivers. This is an endless loop, the application never attempts to install the drivers. The phone is plugged into the the PC at this point because I assume it must be for windows to see the phone. Note, at no time except the End of the instructions does it tell me to have the phone plugged in. This confuses me greatly. I don't know if the phone should be plugged into the pc at this point or not. Can someone who if used to doing these kinda flash jobs look over these instructions and help me figure out what I'm doing wrong. Thank you. I will do my best to answer back with more info, I'll be home all day watching this thread.
( btw, the forum on that site is moderated. I have tried over two weeks ago to post forum messages about my issues, but the moderators never posted any of my messages - it seems customer service is non existent)
Please mark this as Solved. I fixed my problem with a bit more research. Figo gives incomplete and also incorrect information on upgrading the Rom ( as you can see) Nowhere do they tell you in the instructions that you need USB Debugging Enabled or how to do it. This is a critical step or the drivers will never see the phone. The drivers did correctly install the first time as I suggested. That was the incomplete information. The incorrect information is this: They tell you to take the battery out to flash the device - which will never work because the phone needs power for the drivers to flash the device. What you have to do while the phone is On and Connected to PC is remove the battery then put it back in - then the phone will flash. This is critical step 2 they were wrong about. I suspect it has something to do with a bad Chinese translation.