Related
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Have you enabled USB debugging in Developer Options in settings?
Sent from my XT1032 using Tapatalk
Of course I did ^^
battlemaxi said:
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Click to expand...
Click to collapse
For my XT1031, I had to use the Motorola USB drivers for ADB to work, and Kush's Universal ADB drivers for Fastboot to work.
And if you are using Windows 8/8.1, then you have to disable to forced signature verification in order to install the Universal ADB drivers.
Also, for ADB to work in Windows, I had to set the phone's USB computer connection to Camera (PTP), instead of Media Device.
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
battlemaxi said:
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
Click to expand...
Click to collapse
Dude, you need to follow the instructions step by step and provide more info about what's going on.
1. Is your "Enable ADB debugging" enabled? You said yes.. does your phone show "Android debugging enabled" icon when you plug it into your computer? If not, you don't have it enabled !
2. If you see the notification, go to Device Manager (hope you are using Windows, or I can't really help you), then can you find your device there? If the USB drivers are installed correctly, then you should see "Android Device" then a "Motorola ADB Interface" inside it. If not, you will see a yellow exclamation with something like "Motorola device"..
3. Did you change your phone's USB computer connection to Camera (PTP)??
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
liveroy said:
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
Click to expand...
Click to collapse
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
robin0800 said:
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
Just follow those instructions to the letter and any thing you don't understand or get an error message report back here
battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Hmmm... so.. what do you see when you type "adb devices" ?
Also, in your Device Manager, is the Motorola ADB interface properly installed? (no issues)?
And yes, to unlock the bootloader you just need Fastboot... when you boot to Fastboot and type "fastboot devices" do you see anything?
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
battlemaxi said:
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
Click to expand...
Click to collapse
Well, are you sure you fastboot works?
If so, it's very weird why adb won't...
And yeah, ADB is very useful... if not lifesaving...
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Can you see adb in the computer device manager program
battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
liveroy said:
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
Click to expand...
Click to collapse
Even if you revoke, you should see the device listed if you run "adb devices"...
neozen21 said:
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
Click to expand...
Click to collapse
Nope
I guess I have the newest Version, cause I downloaded it from Motorola.com
Yes everything is working no yellow thingys what so eher..
If I use the 'ADB devices' command the ID of my device shows up but as already mentioned it's offline.
Gesendet von meinem XT1032 mit Tapatalk
Well, it happened
I was sitting on a bench and somehow my phone found a way to slide between my fingers and crash. (I must note that it dropped on the bench, which was like 10 cm max fall).
Anyway, I came home, plugged it into my computer and miraculously the phone works even though the screen is all crashed/pixelated/non-responsive.
Is there a way to control my phone with my computer? Like viewing everything on the computer itself?
There are some programs that I need to backup my files there in order to use them on my other phone.
Thanks!
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
timmaaa said:
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
Click to expand...
Click to collapse
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Airbender123 said:
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Click to expand...
Click to collapse
If you're seeing qhsusb_bulk in Windows there's more wrong with the phone than just the screen unfortunately. I think we're going to have to move your thread into the Nexus section so the Nexus experts can lend a hand. Please standby while we have your thread moved.
Good luck!
Transmitted via Bacon
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Airbender123 said:
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Click to expand...
Click to collapse
Does the "adb devices" command return your serial number?
Transmitted via Bacon
timmaaa said:
Does the "adb devices" command return your serial number?
Transmitted via Bacon
Click to expand...
Click to collapse
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
There could be many reasons for that. Unfortunately I'm not terribly experienced with this phone so we'll need to wait for one of the Nexus experts to come and lend a hand.
Airbender123 said:
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
Click to expand...
Click to collapse
Please Google "15 second adb installer". Use that to install adb drivers. Then open a command prompt. Make sure you navigate to where adb gets installed (usually in program files) then adb device
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Sandman-007 said:
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Click to expand...
Click to collapse
Ummm that's kind of hard to do with a shattered display.
OP Just follow sandmans advice to get the drivers right and you'll be able to follow the tools instructions you're trying to use to enable USB debugging. If you just want your data off you could also just use:
Code:
adb pull /sdcard
Is your Bootloader unlocked?
If USB debugging is not enabled in Android and you can not enable it in android due to unreadable screen,
Your only option is to ADB shell from custom recovery such as TWRP.
You can only boot into custom recovery if your bootloader is already UNLOCKED.
theesotericone said:
Ummm that's kind of hard to do with a shattered display.
Click to expand...
Click to collapse
Not really. There are some tools out there that let you view and control your screen on a PC.
Sandman-007 said:
Not really. There are some tools out there that let you view and control your screen on a PC.
Click to expand...
Click to collapse
Yes there are. The OP is trying to use one of them. He has a broken screen and is unable to use the screen on the device. He does not have USB Debug enabled. To use the program to mirror screen you need USB Debug enabled. See the catch-22 there? His only hope is to enable it via recovery and ADB. But as @joegestes points out if he's not already unlocked he needs to unlock for that. Unlocking wipes the phone. Another catch-22.
This thread is still alive?
Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.
Hi guys,
I have this phone (european dual sim version) and tried to update it via Newflasher. Now the phone doesnt start anymore, it is stuck in bootloop, just says sony and then it says that my phone is corrupt and it will not boot. I dont have enough battery to repair it via Companion. Is there any way to avoid going to the Sony Service?
I should mention that I tried to flash firmware 58.0.A.22.21 Europe Customized EEA. What should I flash to get it to start? Any idea is welcome.
Thank you.
leoking3 said:
Hi guys,
I have this phone (european dual sim version) and tried to update it via Newflasher. Now the phone doesnt start anymore, it is stuck in bootloop, just says sony and then it says that my phone is corrupt and it will not boot. I dont have enough battery to repair it via Companion. Is there any way to avoid going to the Sony Service?
I should mention that I tried to flash firmware 58.0.A.22.21 Europe Customized EEA. What should I flash to get it to start? Any idea is welcome.
Thank you.
Click to expand...
Click to collapse
Can you post a log of what newflasher says when you try to flash the EU rom?
TripodKnight said:
Can you post a log of what newflasher says when you try to flash the EU rom?
Click to expand...
Click to collapse
It flashes, finishes, phone is disconnected, then it doesnt start anymore. Please let me know what log are you talking about and how to get it?
leoking3 said:
It flashes, finishes, phone is disconnected, then it doesnt start anymore. Please let me know what log are you talking about and how to get it?
Click to expand...
Click to collapse
Copy all of the newflasher text into a notepad file and post it here so we can review it.
TripodKnight said:
Copy all of the newflasher text into a notepad file and post it here so we can review it.
Click to expand...
Click to collapse
Oh, ok , sure, in 10 minutes.
leoking3 said:
Oh, ok , sure, in 10 minutes.
Click to expand...
Click to collapse
Please see it attached
leoking3 said:
Please see it attached
Click to expand...
Click to collapse
Do you have ADB installed?
Yes I do
leoking3 said:
Yes I do
Click to expand...
Click to collapse
Try launching your phone into fastboot (plug in while holding volume up, wait for blue light)
Once in fastboot, try setting your active partition to partition a with the command below:
fastboot --set-active=a
The restart your phone and see if it loads.
TripodKnight said:
Try launching your phone into fastboot (plug in while holding volume up, wait for blue light)
Once in fastboot, try setting your active partition to partition a with the command below:
fastboot --set-active=a
The restart your phone and see if it loads.
Click to expand...
Click to collapse
it says: unknown option –set-active=a
leoking3 said:
it says: unknown option –set-active=a
Click to expand...
Click to collapse
This website shows the commands to use:
https://www.androidexplained.com/change-active-partition-slot/
Code:
fastboot --set-active=a
TripodKnight said:
This website shows the commands to use:
https://www.androidexplained.com/change-active-partition-slot/
Code:
fastboot --set-active=a
Click to expand...
Click to collapse
Thank you for being patient, unfortunately the device seems mega fu..ed. I dont know what could have happened sooo important that messed it up like this. I used the correct file,I followed the instructions... It goes to fastboot and it is recongnized by the PC, but the command doesnt work, it gives the response from my previous reply.. It seems that I am doomed to go to the service and that is it. Thank you very much man!
leoking3 said:
Thank you for being patient, unfortunately the device seems mega fu..ed. I dont know what could have happened sooo important that messed it up like this. I used the correct file,I followed the instructions... It goes to fastboot and it is recongnized by the PC, but the command doesnt work, it gives the response from my previous reply.. It seems that I am doomed to go to the service and that is it. Thank you very much man!
Click to expand...
Click to collapse
If your fastboot is not working properly then I agree. But I've never seen a fastboot get corrupted. Can you run any fastboot commands at all?
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
leoking3 said:
Thank you for being patient, unfortunately the device seems mega fu..ed. I dont know what could have happened sooo important that messed it up like this. I used the correct file,I followed the instructions... It goes to fastboot and it is recongnized by the PC, but the command doesnt work, it gives the response from my previous reply.. It seems that I am doomed to go to the service and that is it. Thank you very much man!
Click to expand...
Click to collapse
For your information, I have been dealing with a bootloop the last few days. I have now just tried a new USB cable with a new USB port (not the official Sony cable) and have fixed my issues. Perhaps you could give that a try as well.
TripodKnight said:
If your fastboot is not working properly then I agree. But I've never seen a fastboot get corrupted. Can you run any fastboot commands at all?
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
For your information, I have been dealing with a bootloop the last few days. I have now just tried a new USB cable with a new USB port (not the official Sony cable) and have fixed my issues. Perhaps you could give that a try as well.
Click to expand...
Click to collapse
I used the "fastboot devices" command and it worked, it showed me serial number of the phone. So it seems to be connected. But it doesnt want to change the boot partition. .... As for the cable, I first used a very old usb to usb c cable. Then I used one from my iqos charger. Because my laptop doesnt have a usb C port. So you really think the cable could f..k up things while flashing?? Should I try and find another one in the house maybe and try again?
leoking3 said:
I used the "fastboot devices" command and it worked, it showed me serial number of the phone. So it seems to be connected. But it doesnt want to change the boot partition. .... As for the cable, I first used a very old usb to usb c cable. Then I used one from my iqos charger. Because my laptop doesnt have a usb C port. So you really think the cable could f..k up things while flashing?? Should I try and find another one in the house maybe and try again?
Click to expand...
Click to collapse
Your ADB might be out of date and not have the A/B partition fastboot commands. Try updating through instructions here:
https://developer.android.com/studio/releases/platform-tools
I never thought a USB cable would be the issue either, but I tried a new USB port and quality cable and suddenly everything works fine.
Also confirm you're using newflasher to flash the correct firmware for your model. When I flashed the XQ-AS72 firmware on my XQ-AS52 I experienced bootloops like what you're experiencing.
If you still have issues, you can boot to recovery with these instructions and select "power off". You should be able to charge your phone to 80% to use the xperia companion app. https://www.mobilereset99.com/hard-reset-sony-xperia-1-ii/
TripodKnight said:
If your fastboot is not working properly then I agree. But I've never seen a fastboot get corrupted. Can you run any fastboot commands at all?
---------- Post added at 09:21 AM ---------- Previous post was at 09:19 AM ----------
For your information, I have been dealing with a bootloop the last few days. I have now just tried a new USB cable with a new USB port (not the official Sony cable) and have fixed my issues. Perhaps you could give that a try as well.
Click to expand...
Click to collapse
TripodKnight said:
Your ADB might be out of date and not have the A/B partition fastboot commands. Try updating through instructions here:
https://developer.android.com/studio/releases/platform-tools
I never thought a USB cable would be the issue either, but I tried a new USB port and quality cable and suddenly everything works fine.
Also confirm you're using newflasher to flash the correct firmware for your model. When I flashed the XQ-AS72 firmware on my XQ-AS52 I experienced bootloops like what you're experiencing.
If you still have issues, you can boot to recovery with these instructions and select "power off". You should be able to charge your phone to 80% to use the xperia companion app. https://www.mobilereset99.com/hard-reset-sony-xperia-1-ii/
Click to expand...
Click to collapse
Yes, unfortunately is the correct firmware.
I.will try all these solutions, thank you very very much!
leoking3 said:
it says: unknown option –set-active=a
Click to expand...
Click to collapse
You were right, it was to old to know the command. Now it takes the command but says it is not allowed in lock state
leoking3 said:
You were right, it was to old to know the command. Now it takes the command but says it is not allowed in lock state
Click to expand...
Click to collapse
Give your phone a charge and give the Xperia companion app a try.
If you use the included charger and cable, it will charge faster than it drains even if you leave it in bootloop. But you can also try powering down using recovery options.
Let me know if that works.
TripodKnight said:
Give your phone a charge and give the Xperia companion app a try.
If you use the included charger and cable, it will charge faster than it drains even if you leave it in bootloop. But you can also try powering down using recovery options.
Let me know if that works.
Click to expand...
Click to collapse
The issues is that I cannot enter the Recovery and see the options. So you are sayng that even if when I plug it in it keeps saying my phone is corrupt, it still charges?
leoking3 said:
The issues is that I cannot enter the Recovery and see the options. So you are sayng that even if when I plug it in it keeps saying my phone is corrupt, it still charges?
Click to expand...
Click to collapse
It should charge. You should be able to hold volume down on boot (green light top corner, black screen will happen) and try an xperia companion app restore by following the repair options (select "My device is not detected by computer". It should be charging as it restores from your computer as well.
hey, my motorola one vision got this message displaying " your device has failed verification and may not work properly" that i rescued it and replaced firmware with motorola assistant software then after a while it dead again and now hardbricked it is not not even recognized by my pc before it showed at least exynos driver in ports now it displays not recognized, I tried giving it to service center but they returned it and told they can't fix it connsider going come other center...., so is there anything i could do to get it recognized by my pc..?
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
if it is soft bricked at least it should show the processor connected.., bt in my case it just connects and not turning fastboot or cant even do blank flash
jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized
Re-flashing phone's Stock ROM never is done
Ammar595 said:
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized by Fastboot.
Click to expand...
Click to collapse
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
jwoegerbauer said:
Re-flashing phone's Stock ROM never is done
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Click to expand...
Click to collapse
yes tried this too still not recoganized..
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
so what should i do now..?
jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
this is what its showing and phone is completly dead like a brick..
Delete this USB device from within Windows' Device Manager. Re-install the "Android USB Driver".
jwoegerbauer said:
Delete this USB device from within Windows' Device Manager.
Click to expand...
Click to collapse
yes i did that too, stilll not working....
Ammar595 said:
so what should i do now..?
Click to expand...
Click to collapse
Does this work?
Code:
adb devices
jwoegerbauer said:
Does this work?
Code:
adb devices
Click to expand...
Click to collapse
no..... the only thing working is that it shows not recoganized
We could have saved ourselves all this back and forth if this had been known from the start.
jwoegerbauer said:
We could have saved ourselves all this back and forth if this had been known from the start.
Click to expand...
Click to collapse
so there's nothing i could do now...?
Ammar595 said:
so there's nothing i could do now...?
Click to expand...
Click to collapse
my sdcard reader also show that i think thats normal
ineedroot69 said:
my sdcard reader also show that i think thats normal
Click to expand...
Click to collapse
what is normal....? my phone is entirely dead, it isn't responding al it does is shows not recognized
when i connects it to my pc, ya maybe that's normal, bt am asking for solution not a compliment