I'm having trouble getting this POS rooted. Got it unlocked with little problem, but now that it comes to rooting, it's extremely confusing to follow the tutorials. Is there any working one-click methods? I'm no stranger to Android OS, I had my Dinc2 rooted in about 5 minutes after unboxing. But this abomination is really working my nerves. Help please?
There is no "One-Click Root"
But rooting using the given instructions is not difficult at all.
Its as simple as downloading a few files, and typing a few codes.
what have you tried so far? and what firmware are you running?
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Cat_On_Droid said:
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Click to expand...
Click to collapse
the wait for recovery to load is HORRIBLE!! lol. push the menu button once in a while if you are unsure. i did. it makes the wait (for me) less painful but installing the .zip and rebooting successfully with a rooted phone is AWESOME!!
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
chattguy said:
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
Click to expand...
Click to collapse
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
mehdi.moha said:
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
Click to expand...
Click to collapse
Sony Ericsson sa0102 is installed, but I'm not seeing anything in my device manager about S1 Fastboot. Hmm...how would one go about installing it? I have the fastboot folder on my desktop. It has two subfolders, Fastboot and USB_drivers .
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
In this case if it's either still 'waiting for device' or trying to boot recoveryPLAY.img, then you're safe to try again since nothing is being flashed
When connected next time, in fastboot mode, before booting the .img, type this:
fastboot devices 'enter'
It will show a list of devices attached.
It might be that your missing some drivers so fastboot is not working correctly and won't detect your device. Have you pc companion installed? I don't remember if there came any drivers with the fastboot download but check that, there might be some drivers you didn't install.
Regards Dousan...
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
chattguy said:
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
Click to expand...
Click to collapse
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
AndroHero said:
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
chattguy said:
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
Click to expand...
Click to collapse
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
AndroHero said:
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
Click to expand...
Click to collapse
Mother. Of. God.
I did it. No, f**k that, you did it. All of you, thank you so much. You guys really helped me out bigtime, without berating me and calling me a noob lol. I sincerely appreciate it.
Also a special thanks to Alejandrissimo for unlocking the bootloader. Without you, this wouldn't have even been possible. Yay this blasted phone is finally rooted...
...and nobody had to die in the process.
That's what we are all here for. Learning about things through each other. We were all without knowledge at one point
Sent from my R800i using XDA App
Related
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
cybrkada said:
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
Click to expand...
Click to collapse
How are you installing it ???
Via flash tool??
And nope your phone won't brick
I disconnected the cord. Turned on the phone and noticed that USB Debugging is ticked/checked. So I repeated the process but I am still getting..
< waiting for device >
What should I do?
soulhackereborn said:
How are you installing it ???
Via flash tool??
And nope your phone won't brick
Click to expand...
Click to collapse
Yes, via Flastool. Yeah my phone did not get bricked! :good:
cybrkada said:
Yes, via Flastool. Yeah my phone did not get bricked! :good:
Click to expand...
Click to collapse
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
soulhackereborn said:
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
Click to expand...
Click to collapse
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
cybrkada said:
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
Click to expand...
Click to collapse
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
soulhackereborn said:
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
cybrkada said:
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
Click to expand...
Click to collapse
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
soulhackereborn said:
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Click to expand...
Click to collapse
I dont see PM here, i think I am still restricted.
see if the link helps, i removed w w w
android.gs/install-clockworkmod-recovery-sony-xperia-s
i'm rebooting them after this.. thanks
LiveSquare said:
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
Click to expand...
Click to collapse
Which drivers? I have already downloaded SDK and I believe the S1 driver is installed yesterday when i unlock the bootloader.
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
cybrkada said:
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
Click to expand...
Click to collapse
Dude as far as I know there is no need to check/ tick USB debugging for fastboot... It's just for flashtool..
Try re -installing the drivers again manually or let windows search over internet...
Finally, i made it! thanks to both of you!
fastboot.exe seems to be corrupted!
Problem solved!
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
cybrkada said:
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
Click to expand...
Click to collapse
Yes ur rooted!!
Thanks!
I'm currently downloading Cyanogenmod ver 9.1. Hopefully it works! Thank you so much buddy! You have been very helpful! If I get problems on flashing CM9.1, i'll contact you , hehe
One of the reminders on isntalling CM9 is:
Make sure that your Xperia S is already running a rooted firmware, and that it has the ClockworkMod Recovery properly installed.
How do I know I have a rooted firmware? Do I still need to flash FTF file?
By the way, I am getting a boot loop from CWM recovery, I cant go to the homescreen, no option to turn off! It only reboots the CWM.
(Still downloading CM9 as of the moment)
I have a blind N10 on bootloader that is it doesnt show anything on fastboot mode but it does go there. I researched and found other people with similar problem http://rootzwiki.com/topic/37629-bootloader-fastboot-weirdness/ . However they managed to unlock the device by clicking the vol+ once and then power key as I also saw on youtube videos. IT WORKED. and then it went downhill. it got stuck on bootloop. SO i tried to go into fastboot again and it went and then pressed vol+ twice to go into recovery and there was a android with "!" red sign on middle.
and of course it won't boot. So I tried to use the Wugs toolkit, put it on back to stock with bootloop option. and it started to do its work, but got stuck at the sending bootloader (1280KB) sign for more than 10-15 mins. I pressed the power button and it failed that step saying too many links and wugs kit continued the process got stuck again and then completed and my device still goes to fastboot, but cant go into recovery anymore I think as it shows blank screen. Please mind that I am still blind on the screen and nothing comes. my only way of knowing it goes to fastboot is through cmd line. PLEASE HELP, dont wanna brick this.
Is there any way to ODIN it. I cant find online any ODIN insturctions? help help
I cant even turn it off now! Its always going to fastboot. Please help
mustafansu said:
I cant even turn it off now! Its always going to fastboot. Please help
Click to expand...
Click to collapse
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
ricco333 said:
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
Click to expand...
Click to collapse
Hi ricco333
thanks for the reply. I have updated the SDK and tried to run the command as you mentioned. However it is the same thing. Its getting stuck at sending bootloader. I am attaching a screenshot here. it stays there until i press ctrl+c. then it tries to continue and gets stuck again at sending boot. which is the second screenshot.
Is there any other way to restore factory image. i thought samsung devices had ODIN system. Thanks again for the reply.
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Also try re downloading the stock images...
Maybe you have a corrupted file.
Have you tried using the Nexus 10 Toolkit?
http://forum.xda-developers.com/showthread.php?t=2001868
IT WORKED!!
ricco333 said:
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Click to expand...
Click to collapse
Thanks so much guys.After trying 2 different cables and a new computer, a fresh installation of ADB and samsung drivers it finally worked. Thanks again. HUGE SIGH of RELIEF
Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. 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.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.
Hey,
I've been trying to unlock the bootloader and root my Xperia Z2, but the command prompt cannot find my phone when I have put it in fastboot mode. I also double checked the USB debugging mode. Weirder is, Sony PC Companion cannot find it either. Can anyone help me out with this? thx
Riyge said:
Hey,
I've been trying to unlock the bootloader and root my Xperia Z2, but the command prompt cannot find my phone when I have put it in fastboot mode. I also double checked the USB debugging mode. Weirder is, Sony PC Companion cannot find it either. Can anyone help me out with this? thx
Click to expand...
Click to collapse
try going to developer.sonymobile.com and looking there for the drivers
Envious_Data said:
try going to developer.sonymobile.com and looking there for the drivers
Click to expand...
Click to collapse
Yeah I already did that, but I can't install them for some reason. Might be doing it wrong. Can you explain me how to install it properly?
Riyge said:
Yeah I already did that, but I can't install them for some reason. Might be doing it wrong. Can you explain me how to install it properly?
Click to expand...
Click to collapse
if your on windows 8 then you will have to search around as i cant help you
windows 7 you just open the exe
When I was following the guide for installing Cyanogenmod on the Z2, located here: http://wiki.cyanogenmod.org/w/Install_CM_for_sirius
I discovered the guide was wrong. You don't hold volume down to enter Fastboot, you hold volume up.
Someone should probably correct that guide...
There's probably other guides on the 'net that say to hold volume down to enter Fastboot for the Z2, so if you've been following one of those, try volume up instead.
Envious_Data said:
if your on windows 8 then you will have to search around as i cant help you
windows 7 you just open the exe
Click to expand...
Click to collapse
Win7 yes. On the Sony dev site you don't get a .exe file. You only get a zipped file containing some .dll stuff.
sodaboy581 said:
When I was following the guide for installing Cyanogenmod on the Z2, located here: http://wiki.cyanogenmod.org/w/Install_CM_for_sirius
I discovered the guide was wrong. You don't hold volume down to enter Fastboot, you hold volume up.
Someone should probably correct that guide...
There's probably other guides on the 'net that say to hold volume down to enter Fastboot for the Z2, so if you've been following one of those, try volume up instead.
Click to expand...
Click to collapse
Yeah I figured that one out. Problem is, I connect my phone in fastboot to my pc, but it wont recognize it as fastboot. Probably something wrong with my drivers.
Just go download the Flashtool driver pack, pick and install the appropriate ones for the Z2. That's what I did. (Comes with Flash and Fastboot drivers.)
http://forum.xda-developers.com/showthread.php?t=2635830
sodaboy581 said:
Just go download the Flashtool driver pack, pick and install the appropriate ones for the Z2. That's what I did. (Comes with Flash and Fastboot drivers.)
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
Tried that too. Still stuck in the command prompt when i type: fastboot devices. same thing when i type: adb devices.
Riyge said:
Tried that too. Still stuck in the command prompt when i type: fastboot devices. same thing when i type: adb devices.
Click to expand...
Click to collapse
Are you sure you are in the right directory? I know chances are you are obviously but it could be something as small as that which could make a difference. Alternatively, make sure you actually have up to date ADB/fastboot files! I had old ones and they wouldn't work. I have attached platform tools to this message. Extract the .zip to your desktop, open the folder and then hold shift + right click and click on "open a command window here". Make sure you have the "fastboot drivers" installed from the flashtool page (http://forum.xda-developers.com/showthread.php?t=2635830).
Devzz said:
Are you sure you are in the right directory? I know chances are you are obviously but it could be something as small as that which could make a difference. Alternatively, make sure you actually have up to date ADB/fastboot files! I had old ones and they wouldn't work. I have attached platform tools to this message. Extract the .zip to your desktop, open the folder and then hold shift + right click and click on "open a command window here". Make sure you have the "fastboot drivers" installed from the flashtool page (http://forum.xda-developers.com/showthread.php?t=2635830).
Click to expand...
Click to collapse
Turned out mine weren't up to date as well... Thankyou!
Backup TA partition prior to unlock.
i tried to do it my self. follow an instruction from a official website and other
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
https://www.getdroidtips.com/how-to...-plus-i3213-i4213-i4293-i3223/#Pre-Requisites
which i got stuck at, when i boot into bootloader mode . the phone seem to restart and appear only black screen with blue indicator.
then i tried to check if it still connect to adb or not, with {adb devices} its not listed there
PS.
-the drivers work fine
-my Xperia 10 plus model is I4293
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Zaben said:
The LED is all you get. The screen stays black for fastboot and flash modes. Not sure why adb devices isn't working.
Click to expand...
Click to collapse
one thing weird
i using a Xperia Tool (Xperia Companion) and it display the text that my phone need to unlock the screen or allow to use data tranfer
which i already check a USB debugging to be on, and every time i connect it to my PC, it still ask me a permission to be allow or not
maybe this is a problem here ?
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Haxk20 said:
It cant be listed in ADB if the android isnt running.
Blue LED means fastboot mode. So to check if the device is in that mode you do "fastboot devices".
Once the LED is blue you can unlock the bootloader with the command "fastboot oem unlock 0x<insert your unlock code>".
Click to expand...
Click to collapse
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
ZimpleThing said:
When I pressed to volume up button and plug the cable in, led turned red>blue>off. I tried releasing the button at a different colour, but my phone still did not go into fastboot mode. Did I do something wrong?
Click to expand...
Click to collapse
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Haxk20 said:
I guess you are using windows. This is issue on windows when you don't install adb drivers. There should be tutorial on Sony site how to install them.
Click to expand...
Click to collapse
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
ZimpleThing said:
Yes, I am using Windows 10, but let me clarify my understanding first.
From what you said, I need to manually install the ADB driver by Device Manager > Portable Devices > Xperia 10 Plus > Browse my com... And that driver, I should get it from Sony site, but I only see Xperia 1, 5 and 8, not 10 nor 10 Plus.
However, I could see my phone by using command adb devices through minimal ADB and Fastboot. Does this imply that the driver is installed already?
Click to expand...
Click to collapse
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Haxk20 said:
Adb and fastboot are not the same thing so you have to get fastboot driver.
I have no clue where this driver is as I use Linux only which includes the driver by default.
Click to expand...
Click to collapse
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
ZimpleThing said:
I see. There is a fastboot driver on Sony site, but it was uploaded since 2014. I successfully installed it, but still nothing seems to work. I will try on Ubuntu later. Thanks for your help.
Click to expand...
Click to collapse
There is a thanks button. Hit it instead of saying it.
Haxk20 said:
There is a thanks button. Hit it instead of saying it.
Click to expand...
Click to collapse
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Glad I could help
I know its been a long time but maybe someone can help me.
I can get into the bootloader but when I trie to use the unlock code, mentioned above, and the sony unlock key it always says waiting for device but nothing happens. Any clue?
Edit fixed the Problem
Xperia 10 plus stuck on waiting for device
ZimpleThing said:
I just manage to correctly installed driver, my phone is now rooted, and everything is working fine now.
Click to expand...
Click to collapse
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
I was using windows 10. From what I can remember, my problem is that I didn't install driver correctly (I'm not sure which one). I am not really sure if this fastboot driver the one I used. I saw my device in Device Manager, but I got waiting on device... just like you. So what I have done was locate my device in Device Manager and install the sony driver over that device. If sony's driver was not the correct one, then it was another driver that I can't remember, but the instruction still the same. Sorry for an unclear message, but I can barely remember anything now.
travy said:
Hi can you please tell me did you end up getting to work on windows 10 or have to VM ubuntu. I try everything reboot to bootloader and try to fastboot unlock. But get waiting on device. How do you fix this issue please and thanks any help be great.
Click to expand...
Click to collapse
Go in Windows Device Manager and check the device . If needed install drivers manually