Software update cannot be assigned and TWRP cannot be installed!

[gokhanhaskilit]

Hey, When trying to update software with stock rom and recovery, I cannot update with "installation failed" error. So I wanted to do other things with fastboot, but with fastboot only the bootloader can be unlocked. Errors I get while installing TWRP:

FAILED (remote: Requested download size is more than max allowed)

or

stuck on "sending recovery.img"


Officially I'm stuck in the Oreo 8.1 version. No matter how much research I did on this issue, I could not reach a solution. What I tried are the following

- All resets that can be done on the phone.
- Delete and reinstall ADB
- Refreshing rom and recovery files
- adb sideload

Please help.

 

[[email protected]]

Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery (file name).img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..

---------- Post added at 02:59 AM ---------- Previous post was at 02:39 AM ----------

Hey, When trying to update software with stock rom and recovery, I cannot update with "installation failed" error. So I wanted to do other things with fastboot, but with fastboot only the bootloader can be unlocked. Errors I get while installing TWRP:

FAILED (remote: Requested download size is more than max allowed)

or

stuck on "sending recovery.img"


Officially I'm stuck in the Oreo 8.1 version. No matter how much research I did on this issue, I could not reach a solution. What I tried are the following

- All resets that can be done on the phone.
- Delete and reinstall ADB
- Refreshing rom and recovery files
- adb sideload

Please help.

Fastboot boot (filename).img.
It will boot into recovery flash recovery from the recovery.
1)Try to use another usb port in your Pc ,
2)If you still getting those errors reinstall the adb driver may help,
3)Try to clear cache from the existing stock recovery
And execute the command
4)Try renaming the file name (smaller) it's a myth:laugh:
I hope it will fix your problem:good:

 

[gokhanhaskilit]

Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery (file name).img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..

---------- Post added at 02:59 AM ---------- Previous post was at 02:39 AM ----------



Fastboot boot (filename).img.
It will boot into recovery flash recovery from the recovery.
1)Try to use another usb port in your Pc ,
2)If you still getting those errors reinstall the adb driver may help,
3)Try to clear cache from the existing stock recovery
And execute the command
4)Try renaming the file name (smaller) it's a myth:laugh:
I hope it will fix your problem:good:

fastboot erase recovery
fastboot erase cache

When you enter the commands above, it starts but doesn't finish. So it is not Finished. No results were obtained in other operations.

What else can you suggest about this?

 

[[email protected]]

fastboot erase recovery
fastboot erase cache

When you enter the commands above, it starts but doesn't finish. So it is not Finished. No results were obtained in other operations.

What else can you suggest about this?

Have you tried fastboot boot recovery.img

 

[gokhanhaskilit]

Have you tried fastboot boot recovery.img

I tried but failed. Can we talk on Telegram?

 

[optimumpro]

I tried but failed. Can we talk on Telegram?

Hey. You can't flash anything via fastboot on locked bootloader.

The reason you can't update is that your phone doesn't have vendor partition. Recovery can't find it. That's why it stops. You have to flash Pie stock first (preferably the release that introduced vendor partition (treble), then you can upgrade to Android Q.

 

[[email protected]]

I tried but failed. Can we talk on Telegram?

I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0

Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat

I'm also looking for a solution for your problem

---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------

I tried but failed. Can we talk on Telegram?

Hey. You can't flash anything via fastboot on locked bootloader.

The reason you can't update is that your phone doesn't have vendor partition. Recovery can't find it. That's why it stops. You have to flash Pie stock first (preferably the release that introduced vendor partition (treble), then you can upgrade to Android Q.

He already unlocked the bootloader

 

[gokhanhaskilit]

I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0

Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat

I'm also looking for a solution for your problem

---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------





He already unlocked the bootloader

Yes, I guess the problem is in the relationship between ADB and USB 3.0 connectivity.
Desktop PC
Windows 10 Pro 1909
I don't know much about the differences between USB 2.0 and 3.0 but I know the blue ones in the USB port are 3.0 and the black ones are 2.0. Although I have tried all USB ports on the computer, the result does not change. (The problem with USB 2.0 and USB 3.0 is different)

- Minimal ADB and several drivers have been downloaded to this PC for Xioami device. (QUALCOMM, XIOAMI, GOOGLE AND MORE) Is it because they conflict? I tried yesterday on another computer but I am getting the same issue. So I guess the problem isn't just with the PC.

You are right about Telegram. I've tried most operations with my lock on and off. The result does not change.

 

[gokhanhaskilit]

I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0

Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat

I'm also looking for a solution for your problem

---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------





He already unlocked the bootloader

Yes, I guess the problem is in the relationship between ADB and USB 3.0 connectivity.
Desktop PC
Windows 10 Pro 1909
I don't know much about the differences between USB 2.0 and 3.0 but I know the blue ones in the USB port are 3.0 and the black ones are 2.0. Although I have tried all USB ports on the computer, the result does not change. (The problem with USB 2.0 and USB 3.0 is different)

- Minimal ADB and several drivers have been downloaded to this PC for Xioami device. (QUALCOMM, XIOAMI, GOOGLE AND MORE) Is it because they conflict? I tried yesterday on another computer but I am getting the same issue. So I guess the problem isn't just with the PC.

You are right about Telegram. I've tried most operations with my lock on and off. The result does not change.

Also fastboot screen says "PRODUCT NAME: qc referance phone". It used to write my device serial number. So I guess I might have messed up something while installing the final ROM. or Drivers ...

 

[[email protected]]

Also fastboot screen says "PRODUCT NAME: qc referance phone". It used to write my device serial number. So I guess I might have messed up something while installing the final ROM. or Drivers ...

If you want to update your phone use a unbrick tool
(Android pie unbrick tool is available)
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
This may help to replace your old Oxygen os bootloader with latest one so this may help to fix your issue ,we must hope this one will fix
( Do it at your own risk I am not responsible if anything goes wrong)

 

[gokhanhaskilit]

If you want to update your phone use a unbrick tool
(Android pie unbrick tool is available)
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
This may help to replace your old Oxygen os bootloader with latest one so this may help to fix your issue ,we must hope this one will fix
( Do it at your own risk I am not responsible if anything goes wrong)

OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?

 

[[email protected]]

OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?

What do you mean cache removal tool?

 

[gokhanhaskilit]

What do you mean cache removal tool?

Never mind. A translation error has occurred. My OnePlus 5 device is not recognized by the MSM Download Tool (Unbrick Tool). What should I do?

 

[gokhanhaskilit]

Never mind. A translation error has occurred. My OnePlus 5 device is not recognized by the MSM Download Tool (Unbrick Tool). What should I do?

I switched the device to the PIE version. I tried to flash Nougat rom to try it out right away. However, like in Oreo, the loading screen stops for a while and throws it back to the main screen. Presumably the problem with ADB persists.

I guess our problem is more than unbrick tool ..

 

[gokhanhaskilit]

I switched the device to the PIE version. I tried to flash Nougat rom to try it out right away. However, like in Oreo, the loading screen stops for a while and throws it back to the main screen. Presumably the problem with ADB persists.

I guess our problem is more than unbrick tool ..

I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...

 

[[email protected]]

OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?

I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...

I don't understand what you talking about
Did you mean you have successfully installed TWRP?.
Did you installed oos9.11 using the unbrick tool successfully?

---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------

I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...

Try using the new adb driver
Uninstall older driver and install this:
http://www.mediafire.com/file/a4d0p5uvebc0xwp/file