Hi all,
I have a Pixel 2, at January 8.1.0 version (OPM1.171019.013). It was rooted with Magisk latest version. Today I decided to reflash the firmware, without wipe, and the flashing was not successful. Now I'm afraid I have a small brick in my hands.
I'm now using the latest fastboot (0.0.1-4500957) and adb (1.0.39 / 0.0.1-4500957) versions. I don't know if I was on the latest versions when I tried to flash the firmware.
I always flashed the firmware using a USB A port on my Dell XPS 9560 notebook. Today I flashed from a USB C port, I don't know if this was the cause for the failed flash. I'm at the office, and I don't have a USB A x USB C cable available.
My Pixel 2 is stuck at the bootloader. Recovery mode and Download mode options don't do anything, it just goes back to the bootloader screen. Bootloader version is mw8998-002.0059.00. It tells me I'm on slot b, and I can't change slots, issuing fastboot --set-active=a either returns:
Code:
error: Device does not support slots
OR:
Code:
FAILED (remote: unknown command)
When I issue fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img either one of these messages is displayed:
Code:
error: Failed to identify current slot
OR:
Code:
target didn't report max-download-size
sending 'bootloader' (38644 KB)...
FAILED (remote: Uploaded data exceeds max-download-size)
finished. total time: 0.000s
I'm almost returning home early to try my USB A x USB C cable and see if anything changes. Am I without hope?
Never mind, the culprit was the USB C x USB C cable I was using at the office. Back home, I used my USB A x USB C cable and was able to recover the device.
I am having this exact same problem right now. Switching cables doesn't seem to help. Any advice in relation to the OP's first post?
rg2 said:
I am having this exact same problem right now. Switching cables doesn't seem to help. Any advice in relation to the OP's first post?
Click to expand...
Click to collapse
Try using the flash-all script that comes with the factory image from google. This will wipe your data unless you remove the -w option.
enzyne said:
Try using the flash-all script that comes with the factory image from google. This will wipe your data unless you remove the -w option.
Click to expand...
Click to collapse
Thanks for the reply. I have tried this already; I get FAILED with the following "Uploaded data exceeds max-download-size", along with error "Failed to identify current slot".
rg2 said:
Thanks for the reply. I have tried this already; I get FAILED with the following "Uploaded data exceeds max-download-size", along with error "Failed to identify current slot".
Click to expand...
Click to collapse
Just did a quick search. Seems that the cables have been the culprit or it could be the computer your using. Are your drivers up to date? Can you use another PC? What kind of cables have you used specifically?
enzyne said:
Just did a quick search. Seems that the cables have been the culprit or it could be the computer your using. Are your drivers up to date? Can you use another PC? What kind of cables have you used specifically?
Click to expand...
Click to collapse
Tried switching cables, no luck. Will try a different computer when I get home, and will let you know. I have been using an Anker c-->a USB cable, worked flawlessly until now. Tried another brand c-->a cable, same result.
No way to use the included USB-C to C cable?
enzyne said:
No way to use the included USB-C to C cable?
Click to expand...
Click to collapse
I don't have an adapter, and my computer(s) don't have a native port.
rg2 said:
I don't have an adapter, and my computer(s) don't have a native port.
Click to expand...
Click to collapse
Ok. Well I would try a different PC if you can. That will help to narrow down the issue. If that doesn't work let me know. I will try to figure something else out.
rg2 said:
I don't have an adapter, and my computer(s) don't have a native port.
Click to expand...
Click to collapse
Did you try flashing an older version of a factory image for the Google pixel 2?
Just do the same process you would usually do to flash a factory image but flash a build with an older version of your bootloader.
I had the same issue and used the November build
enzyne said:
Ok. Well I would try a different PC if you can. That will help to narrow down the issue. If that doesn't work let me know. I will try to figure something else out.
Click to expand...
Click to collapse
Thanks so much for the assistance. Late last night I tried another computer; this time it worked! I utilized Deuces Bootloop tool found here:
https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778
Then just to be safe I flashed the latest Factory image, and all is well again.
---------- Post added at 10:34 AM ---------- Previous post was at 10:32 AM ----------
Colday96 said:
Did you try flashing an older version of a factory image for the Google pixel 2?
Just do the same process you would usually do to flash a factory image but flash a build with an older version of your bootloader.
I had the same issue and used the November build
Click to expand...
Click to collapse
Just saw your reply. I fixed my issue, but FYI I did try older images, to no avail. Everything ended up working on another computer.
i am stuck at this bootloader nothing is working tried all the solutions mentioned above please help..
Related
Hello,
I received my NVIDIA Shield K1 a couple of days ago and upgraded to Android 6.0. I wanted to root my device, but when I try flashing the img file found in the Android 6.0 Marshmallow Update thread, it gives me an error. I noticed that when I put the phone in bootloader mode, it says "Device - locked," so I followed the instructions on how to unlock it using the "fastboot oem unlock" command, however, I keep getting the follow error message: FAILED (command write failed (Unknown error)
When I enter "fastboot devices" in command prompt, my device's serial does come up, so it is recognized. I just don't know what to do from this point on.
I would appreciate any help (step-by-step if possible, please).
Thanks
I'm having the same problem and am currently hung-up on unlocking the bootloader
Glitterjesus said:
I'm having the same problem and am currently hung-up on unlocking the bootloader
Click to expand...
Click to collapse
Were you able to figure it out, Glitterjesus? No luck here.
Two guesses
Be sure you are using a high quality USB cable and or try another port in pc, also be sure you have latest adb/fastboot binaries on pc
demkantor said:
Two guesses
Be sure you are using a high quality USB cable and or try another port in pc, also be sure you have latest adb/fastboot binaries on pc
Click to expand...
Click to collapse
Hi demkantor...I was using the cable that came with the controller and had it plugged into a USB 2.0 port. I'll try it when I get home and let you know.
Seems like your going to have to restore 5.1.1, unlock, and then root via flashing the available files
demkantor said:
Two guesses
Be sure you are using a high quality USB cable and or try another port in pc, also be sure you have latest adb/fastboot binaries on pc
Click to expand...
Click to collapse
I tried using it in a USB 3.0 port and it was able to unlock. Thanks for the recommendation, demkantor.
My phone is not recognized by any computer even if it's in download mode, I have twrp, and I am willing to do the nandroid backup method, the question is, if this process failed for any reason, would I be able to get a previous working status that I am on right now?
I am on a custom ROM LeeDroid Nougat 7.1 and latest TWRP.
Please advise me on how to get my phone working normally as it was, thanks.
M0EMEN said:
My phone is not recognized by any computer even if it's in download mode, I have twrp, and I am willing to do the nandroid backup method, the question is, if this process failed for any reason, would I be able to get a previous working status that I am on right now?
I am on a custom ROM LeeDroid Nougat 7.1 and latest TWRP.
Please advise me on how to get my phone working normally as it was, thanks.
Click to expand...
Click to collapse
is USB debugging enabled under developer options in settings.
also your sdk tools may need updated.
Aldo101t said:
is USB debugging enabled under developer options in settings.
also your sdk tools may need updated.
Click to expand...
Click to collapse
Yes, the USB debugging is enabled and also the MTP is mounted as well, but how do I check to update the sdk tools?
If you are talking about the computer, I think the issue is in the phone, and that's because when I discovered this issue I noticed that when I connect my original charger, it was telling me Charging Rapidly, and now ain't say so but still charging well.
Your response is much appreciated.
M0EMEN said:
Yes, the USB debugging is enabled and also the MTP is mounted as well, but how do I check to update the sdk tools?
If you are talking about the computer, I think the issue is in the phone, and that's because when I discovered this issue I noticed that when I connect my original charger, it was telling me Charging Rapidly, and now ain't say so but still charging well.
Your response is much appreciated.
Click to expand...
Click to collapse
It's more than likely a USB issue. Try different ports or different cables.
miffymiffy said:
It's more than likely a USB issue. Try different ports or different cables.
Click to expand...
Click to collapse
I have tried everything you can imagine, different cables, different ports and even different computers (desktop and laptop) I think the issue is in my device as it used to write rapidly charging while connected to the DC charger with the original cable and tried multiple ones with no success, it still charge well but I think something is missing in recognition the device USB, I am totally lost the connectivity between my phone and the computer even if I am in the download mode and/or recovery mode.
Any further ideas would be much appreciated.
I have found a thread that posted document for RUU installation and that includes Nandroid backup recovery file which is doable for me to copy the file into the recovery folder and to do the restore from the recovery (TWRP latest version) this file has a stock firmware for Oreo version, but I am not sure if I proceed with this what would happen as I mentioned earlier, I have no connection between my device and any computer which is mandatory to recover the device from any brick could happen, I need a confirmation on this step (Nandroid restore) so I can check, thanks in advance.
M0EMEN said:
I have tried everything you can imagine, different cables, different ports and even different computers (desktop and laptop) I think the issue is in my device as it used to write rapidly charging while connected to the DC charger with the original cable and tried multiple ones with no success, it still charge well but I think something is missing in recognition the device USB, I am totally lost the connectivity between my phone and the computer even if I am in the download mode and/or recovery mode.
Any further ideas would be much appreciated.
I have found a thread that posted document for RUU installation and that includes Nandroid backup recovery file which is doable for me to copy the file into the recovery folder and to do the restore from the recovery (TWRP latest version) this file has a stock firmware for Oreo version, but I am not sure if I proceed with this what would happen as I mentioned earlier, I have no connection between my device and any computer which is mandatory to recover the device from any brick could happen, I need a confirmation on this step (Nandroid restore) so I can check, thanks in advance.
Click to expand...
Click to collapse
Have you tried installing the HTC Sync Manager on your PC to see if that will recognize your phone. Just a thought.
M0EMEN said:
I have tried everything you can imagine, different cables, different ports and even different computers (desktop and laptop) I think the issue is in my device as it used to write rapidly charging while connected to the DC charger with the original cable and tried multiple ones with no success, it still charge well but I think something is missing in recognition the device USB, I am totally lost the connectivity between my phone and the computer even if I am in the download mode and/or recovery mode.
Any further ideas would be much appreciated.
I have found a thread that posted document for RUU installation and that includes Nandroid backup recovery file which is doable for me to copy the file into the recovery folder and to do the restore from the recovery (TWRP latest version) this file has a stock firmware for Oreo version, but I am not sure if I proceed with this what would happen as I mentioned earlier, I have no connection between my device and any computer which is mandatory to recover the device from any brick could happen, I need a confirmation on this step (Nandroid restore) so I can check, thanks in advance.
Click to expand...
Click to collapse
U can try cleaning your charging port also...
Sent from my 2PZC5 using Tapatalk
hammered58 said:
Have you tried installing the HTC Sync Manager on your PC to see if that will recognize your phone. Just a thought.
Click to expand...
Click to collapse
Yes indeed, I have tried it 1st thing but it was useless, because whenever I connect my phone to the computer it gives me error "The USB is malfunctioned and won't work properly" something like that, it gives me this error once I connect my device.
Any ideas on how to fix this issue?
Thanks in advance.
strive53 said:
U can try cleaning your charging port also...
Sent from my 2PZC5 using Tapatalk
Click to expand...
Click to collapse
I will do it, but I think it's clean already but will double clean it maybe it works, and I will keep you updated, thanks for your interest in my issue, much appreciated, also if you figured out any solution to my case, just let me know, have a nice day.
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.
As I mentioned I my pc can't seem to detect my phone at all..it just goes into charging mode as soon as I connect..no adb no MTP or anything.
But my other phone connects just fine.
Things I've tried but failed,
Turning on adb debugging
Setting default usb configuration to MTP
Installing OnePlus drivers in pc
Adb and fastboot drivers along with qfil and miflash tool installed.
Pls guys help me figure this out.
I'm using latest oxygen os 11.1.1.1
Did you boot into other modes and tried to connect? recovery, fastboot etc.
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
Havnt tried this..I'll get back to u soon...my bootloader is locked btw
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot
Click to expand...
Click to collapse
croperas said:
Did you boot into other modes and tried to connect? recovery, fastboot etc.
Click to expand...
Click to collapse
I've tried bro but doesn't detect there either
i.Desygner said:
I've tried bro but doesn't detect there either
Click to expand...
Click to collapse
If it's stock then i'm thinking hw issue but keep trying things.
Try this:
Fastboot Not Recognized
I am not able to get Fastboot to reconginze my One Plus 6T. I have reinstalled the drivers numerous times to no avail. I have changed ports to no avail. I have change USB cables to no avail. Is anyone else having a similar problem and if so...
forum.xda-developers.com
And maybe another computer just in case.
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
i.Desygner said:
Thanks bro..but somehow I managed to get it to work with another usb cable..even that wasn't recognised at first,had to try and install various drivers and update them manually.
Do u think my one plus cable is broken now
Click to expand...
Click to collapse
Could be but keep in mind it has several pins so even if the data is broken or iffy you could always use it as a charging cable.
Either way use it as backup since it's less reliable
Get this error when trying to unlock OEM via fastboot. I've tried to change the usb port, change the cable (one that i am currently using is original), but still no luck. Any advice?
Try disconnecting all cables
ignaty_b said:
Get this error when trying to unlock OEM via fastboot. I've tried to change the usb port, change the cable (one that i am currently using is original), but still no luck. Any advice?
Click to expand...
Click to collapse
were able to fix this by just waiting