Well i think(pretty sure it is) i bricked my phone any suggestions ? i would gladly appreciate it...
carloswii5 said:
Well i think(pretty sure it is) i bricked my phone any suggestions ? i would gladly appreciate it...
Click to expand...
Click to collapse
What have you done ?
Lelus said:
What did you do ?
Click to expand...
Click to collapse
The number one don't xD haha yea I flashed another ROM, tried running fastboot no luck with that any ideas ?
carloswii5 said:
The number one don't xD haha yea I flashed another ROM, tried running fastboot no luck with that any ideas ?
Click to expand...
Click to collapse
what os are you running and why exactly fastboot doesn't work for you ?
Lelus said:
what os are you running and why exactly fastboot doesn't work for you ?
Click to expand...
Click to collapse
computer wise ubuntu maybe if i ran fastboot on windows do you it would work?
carloswii5 said:
computer wise ubuntu maybe if i ran fastboot on windows do you it would work?
Click to expand...
Click to collapse
unzip it
Code:
chmod a+rx start.sh
./start.sh
*you might need to install 32-bit libraries if you are running 64bit ubuntu
Lelus said:
unzip it
Code:
chmod a+rx start.sh
./start.sh
*you might need to install 32-bit libraries if you are running 64bit ubuntu
Click to expand...
Click to collapse
nothing happens (and luckily im using my cousins computer ans she has 32 bit on mine i have 64bit)
carloswii5 said:
nothing happens (and luckily im using my cousins computer ans she has 32 bit on mine i have 64bit)
Click to expand...
Click to collapse
you'll have to be more specific , nothing happens on the computer ? phone ?,what rom did you flash ? what were you running before that ?
Lelus said:
you'll have to be more specific , nothing happens on the computer ? phone ?,what rom did you flash ? what were you running before that ?
Click to expand...
Click to collapse
so after i run the second command it says to disconnect phone and blah blah blah and then press enter after i hit it nothing happens to the phone and on the terminal side all that happens is that is then ready to run another command and that it the ROM i acidently flashed like a idiot was a MIUI V5 LG LU6200 ROM the ROM i was running was pinoytos port of CM 10.1 for the p769......
carloswii5 said:
so after i run the second command it says to disconnect phone and blah blah blah and then press enter after i hit it nothing happens to the phone and on the terminal side all that happens is that is then ready to run another command and that it the ROM i acidently flashed like a idiot was a MIUI V5 LG LU6200 ROM the ROM i was running was pinoytos port of CM 10.1 for the p769......
Click to expand...
Click to collapse
type: fastboot devices when you see command prompt after running start.sh
but you still should be able to enter cwm recovery with [vol+] + [home] + [power]
Lelus said:
type: fastboot devices when you see command prompt after running start.sh
but you still should be able to enter cwm recovery with [vol+] + [home] + [power]
Click to expand...
Click to collapse
after running "fastboot devices" all i get is waiting for devices and that is what i thought but it doesnt even let me boot up to cwm
carloswii5 said:
after running "fastboot devices" all i get is waiting for devices and that is what i thought but it doesnt even let me boot up to cwm
Click to expand...
Click to collapse
what happens when you power on your phone ? does the phone show any sign of life , does anything light up ?
that miui rom, what phone model was it for ?
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
i totally forgot, you have to run start.sh as root or with sudo
Lelus said:
what happens when you power on your phone ? does the phone show any sign of life , does anything light up ?
that miui rom, what phone model was it for ?
Click to expand...
Click to collapse
No the phone is completely dead no lights nothing the MIUI rom was for the LG LU6200
YEA had already ran it with sudo normally every script needs sudo
carloswii5 said:
No the phone is completely dead no lights nothing the MIUI rom was for the LG LU6200
YEA had already ran it with sudo normally every script needs sudo
Click to expand...
Click to collapse
Does your computer recognize the phone when you plug it in with or without the battery ? (just fyi ,lsusb might not show it bc omap4430 cycles itself on/off)
Code:
sudo tail -f /var/log/messages
do you have a link to the miui rom ?
you modified the miui rom didn't you ?
Lelus said:
Does your computer recognize the phone when you plug it in with or without the battery ? (just fyi ,lsusb might not show it bc omap4430 cycles itself on/off)
Code:
sudo tail -f /var/log/messages
do you have a link to the miui rom ?
you modified the miui rom didn't you ?
Click to expand...
Click to collapse
yea i did, i port so....
Lelus said:
Does your computer recognize the phone when you plug it in with or without the battery ? (just fyi ,lsusb might not show it bc omap4430 cycles itself on/off)
Code:
sudo tail -f /var/log/messages
do you have a link to the miui rom ?
you modified the miui rom didn't you ?
Click to expand...
Click to collapse
YES it recognizes it on windows but not on UBUNTU weird but i was trying to install the driver software but i cant says something about digital signature
(Edit) ok so i installed the drivers but for some reason it doesnt read the phone(the terminal)
Related
nvm I solved it
I have problems " waiting for device",..Need help...
Sent from my LG-P760 using xda premium
de.rach29 said:
I have problems " waiting for device",..Need help...
Sent from my LG-P760 using xda premium
Click to expand...
Click to collapse
You need to install fastboot drivers. When you are in fastboot you need to go 'device manager' or something like that on PC. Find android and use update drivers bottom option (install manualy) and point where your fastboot drivers are.
Fastboot driver
where can i find it?
giviman said:
where can i find it?
Click to expand...
Click to collapse
Where you can find what?
giviman said:
where can i find it?
Click to expand...
Click to collapse
Drivers? here:
developer.android.com/sdk/win-usb.html
This is also my problem, i try everything allready. Its just stuck on waiting for device after i try to flash recovery.
When phone is in fastboot mode it said unkonwn usb device, flash omap and fastboot and adb drivers are installed.
Is there any other method for root and recovery install?
Im not noob, i rooted and played with many Android phones, but for this i cant find any solution.
OS is Win Xp but there is same problem on Win 7 also.
who can give me the fastboot backup that i can flash !? I have flash recovery at fastboot :S
Need it for LG P760
thanks
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
hiiiiiiii
hii sir, when i type fastboot flash recovery recovery.img cmd show waiting for device for long time plz hlp
i had many problems trying to run adb commands along with fastboot...most recent was sideloading a rom in CWM.....no device detected...then dl pdanet and that driver fixed the problem...win7 x64....seems every computer is different and process to use adb on this phone...took me a while to find this as well...
help
i installed all the drivers but still it shows waiting for device
maxver0 said:
Where you can find what?
Click to expand...
Click to collapse
Waiting for device problem
maxver0 said:
You need to install fastboot drivers. When you are in fastboot you need to go 'device manager' or something like that on PC. Find android and use update drivers bottom option (install manualy) and point where your fastboot drivers are.
Click to expand...
Click to collapse
Can get the link for the drivers for micromax a58 need a heck of waiting for that to be installed with twrp recovery
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
PROBLEM SOLVED: I switched out the Motherboard c:
merlise said:
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
Click to expand...
Click to collapse
This is from another thread about a boot loop thought it might help you.
powerpoint45 said:
I do not know if this would work or even the steps, but you can download the stock firmware from here: www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201596860
Also the ????????????? Besides your device from "adb devices" just means you need to install the driver for it. That should not be too hard to find out how to do. But really I think you'd need the fastboot drivers more. But in the past I have fixed a bootloop by just looking at the logs to figure out where the crash is coming from via adb logcat, then fixing that issue. But since this is using xposed it'd probably be too complicated to fix manually. Don't ask me for drivers tho cause I use Linux.
Note: the firmware update downloads as a bin file but it is just a zip file. A fastboot update might actually work with it since it is signed by Amazon.
Something like:
Wipe your device. (only if necessary)
fastboot -w
Update your ROM.
fastboot update
---------- Post added at 11:03 PM ---------- Previous post was at 10:45 PM ----------
I've gotten into fastboot on this device. I think it was either "adb reboot bootloader" or "adb reboot fastboot" that works. Keep in mind when in fastboot mode the fire hd6 screen is completely blank.
Click to expand...
Click to collapse
AlbusAngelus said:
This is from another thread about a boot loop thought it might help you.
Click to expand...
Click to collapse
Thanks for trying to help I tried just about everything, but nothing is working.
I decided to just get another used HD 6 and switch out the motherboards and see what happens. I'll come back to the rooting game as soon as there is a working custom recovery and rom up, haha. Thanks.
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
meganoahj said:
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
Click to expand...
Click to collapse
Yours was actually the first I looked at! I tried but I unfortunately couldn't get ADB to recognize the device properly. I've already switched out the motherboards so my problem is somewhat fixed for now.
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
ryanyz10 said:
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
Click to expand...
Click to collapse
I have a fastboot cable, but it still didn't put me into fastboot
merlise said:
I have a fastboot cable, but it still didn't put me into fastboot
Click to expand...
Click to collapse
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
ryanyz10 said:
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
Click to expand...
Click to collapse
I have haha, I honestly tried everything but I just couldn't get it into fastboot. When I'm feeling adventurous, I'll probably try it again, but I just ended up switching out the motherboards with another HD6 for convenience.
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
lucasnoman said:
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
Click to expand...
Click to collapse
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
moto999999 said:
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
Click to expand...
Click to collapse
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
Yes, I did it. But a blue screen appear fast and my smartphone turns off. It does not go into recovery at all, only after I start the phone normally. Funny that I only get message of success since the release of the bootloader until the installation of twrp.
Have you tried "fastboot boot <recovery.img>"?
sudloa said:
Have you tried "fastboot boot <recovery.img>"?
Click to expand...
Click to collapse
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
lucasnoman said:
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
Click to expand...
Click to collapse
fastboot could use in fastboot mode (shutdown then vol down + power) only and windows sohuld recognize this.
But I think your adb usb driver got conflict somehow.
You can try "usbdeview" to uninstall all adb usb drivers then use some knid of universal adb usb driver installer.
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
lucasnoman said:
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Click to expand...
Click to collapse
Hi, You should TITLE your post Why does TWRP not stay resident ?
paulsnz2 said:
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
Hi, You should TITLE your post Why does TWRP not stay resident ?
Click to expand...
Click to collapse
You're Welcome
Antisound said:
You're Welcome
Click to expand...
Click to collapse
I have the 820. Could NOT get windows to see this phone on stock rom. Don't recall exact steps I took, but I do remember the ADB feature within TWRP saved my day. Windows would see the phone in TWRP recovery adb mode, but could never get windows to adb connect with stock rom.
Hey people, sry I'm coming back now. Lightning struck my street and burned my pc. But I come back with another problem, when I connect my phone to the pc nothing happens. I mean, I can't transfer cause MTP doesn't work. I tried install unninstall and install again adb, and all the drivers but it did not work. So I'll need to fix this to try to install twrp again
Guys! I was being too stupid! I found my mistake... I was using another smartphone twrp... So, for who are having same issue, pay attention to this. But, thanks everybody and sry for this hahaha
Ive been trying to install TWRP on my Poco F1 but i am receiving an error message saying " failed write to device failed"
Please Help
im on lastest Official Rom for Poco f1
If i try with ADB flash command, its just stuck
Is your bootloader unlocked? Also, you use the command fastboot boot twrp.img
ekin_strops said:
Is your bootloader unlocked? Also, you use the command fastboot boot twrp.img
Click to expand...
Click to collapse
I tried, still same and yeah the bootloader is unlocked
ekin_strops said:
Is your bootloader unlocked? Also, you use the command fastboot boot twrp.img
Click to expand...
Click to collapse
below is the attached screenshot of the error
Have you tried different PC?
Same error(FAILED (Write to device failed (Invalid argument)) when I try on AMD.. Try on Intel processor PC
cediedc said:
Have you tried different PC?
Same error(FAILED (Write to device failed (Invalid argument)) when I try on AMD.. Try on Intel processor PC
Click to expand...
Click to collapse
Okay will give it a try, previously i did install twrp on my amd fx series processor, recently got an upgrade to ryzen, guess thats the issue.
muham47 said:
Okay will give it a try, previously i did install twrp on my amd fx series processor, recently got an upgrade to ryzen, guess thats the issue.
Click to expand...
Click to collapse
No, Ryzen has nothing to do with it. I'm using Ryzen long time ago.
---------- Post added at 21:36 ---------- Previous post was at 21:34 ----------
muham47 said:
below is the attached screenshot of the error
Click to expand...
Click to collapse
Try downloading Minimal ADB, instal it to C, and run it with Admin rights. Also, try different USB port, try USB 2.0 port as 3.0 sometimes doesn't recognize the phone when it's in fastboot mode.
wait,, why isyour ADB running in drive G???
shouldn't that be installed on drive C?? you should open ADB FOLDER IN C,, then hit SHIFT + right click of the mouse to open up a commad
OPEN POWERSHELL WINDOW HERE in drive C... where your ADB as well as TWRP RECOVERY is in store..
muham47 said:
below is the attached screenshot of the error
Click to expand...
Click to collapse
What's your fastboot version?
Code:
fastboot --version
fastboot version 28.0.1-4986621
Also try as already mentioned:
different USB port - try USB 2.0 port
different cable (!)
santiagoruel13 said:
wait,, why isyour ADB running in drive G???
shouldn't that be installed on drive C?? you should open ADB FOLDER IN C,, then hit SHIFT + right click of the mouse to open up a commad
OPEN POWERSHELL WINDOW HERE in drive C... where your ADB as well as TWRP RECOVERY is in store..
Click to expand...
Click to collapse
tried, still no luck
ekin_strops said:
No, Ryzen has nothing to do with it. I'm using Ryzen long time ago.
---------- Post added at 21:36 ---------- Previous post was at 21:34 ----------
Try downloading Minimal ADB, instal it to C, and run it with Admin rights. Also, try different USB port, try USB 2.0 port as 3.0 sometimes doesn't recognize the phone when it's in fastboot mode.
Click to expand...
Click to collapse
okay so i downloaded minimal ADB and tried via that and i encountered different error this time, i have attached the screenshot
i tried using the command 'fastboot boot twrp-3.2.3-2-beryllium.img' and its just paused
Make.sure your twrp recovery is stored and located in your adb folder where you'll be running the adbpowershelle menu..
1. Fastboot flash recovery name_of_recovery.img
2. Fastboot boot recovery name_of_recovery.img
Have you tried this??
santiagoruel13 said:
Make.sure your twrp recovery is stored and located in your adb folder where you'll be running the adbpowershelle menu..
1. Fastboot flash recovery name_of_recovery.img
2. Fastboot boot recovery name_of_recovery.img
Have you tried this??
Click to expand...
Click to collapse
yes, as soon as i try the "1. Fastboot flash recovery name_of_recovery.img" i get the message 'Error (Failed....)' and when i directly try the 2nd thing you mentioned, it just stays there nothings happening
muham47 said:
yes, as soon as i try the "1. Fastboot flash recovery name_of_recovery.img" i get the message 'Error (Failed....)' and when i directly try the 2nd thing you mentioned, it just stays there nothings happening
Click to expand...
Click to collapse
AMD Ryzen has an issue with Poco F1. Try an Intel PC.
Hmm.. have you tried downloading any other TWRP IMAGE??
santiagoruel13 said:
Hmm.. have you tried downloading any other TWRP IMAGE??
Click to expand...
Click to collapse
yes tried about three of them. I just wanted to flash a custom ROM and now i'm stuck with this irritated
Are you sure your poco has an unlocked boot loader?? Cant say if its because of amd. Coz my pc. Also has amd a7.. with windows 10 pro. And its working fine with me..
Ah. I forgot.. do you have any antivirus? My SMADAV prevented me from accessing any vbsscript or any windoes script. And cant get to work with powershell or adb.. until i find out SMADAV IS THE CULPRIT..
santiagoruel13 said:
Are you sure your poco has an unlocked boot loader?? Cant say if its because of amd. Coz my pc. Also has amd a7.. with windows 10 pro. And its working fine with me..
Ah. I forgot.. do you have any antivirus? My SMADAV prevented me from accessing any vbsscript or any windoes script. And cant get to work with powershell or adb.. until i find out SMADAV IS THE CULPRIT..
Click to expand...
Click to collapse
yes, bootloader unlocked, debugging enabled, no anti-virus, only windows security enabled. Do you think is it related to latest MIUI update which is preventing TWRP to install ?
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