Database Users

can't flash any ROM's - SD card problem

Can anyone extend some help to a TF300T n00b?
I flashed the unofficial CM10 Jellybean ROM to my tf300t, and since the storage isn't working I can't move another ROM or even the stock firmware file to my SD card to flash. So, basically I'm stuck on the unofficial CM10 for now...
posted here because I can't post in the actual developement thread

just connect the tablet to a pc and copy the rom to the tablet. I dont rember if windows sees the internal storage. If it dosent linux should or you can install adb and push the file to /sdcard from your computer.

go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.

mikaole said:
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
Click to expand...
Click to collapse
I couldn't get the fast ADB pusher to work, nor the actual ADB. Fast pusher said it succeeded a few times but I couldn't find the new ROM on my SD card in CWM.

http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb

MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
Click to expand...
Click to collapse
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldnt recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.

ljungberg3 said:
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldn't recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
Click to expand...
Click to collapse
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly

paedz718 said:
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
Click to expand...
Click to collapse
I installed the drivers exactly as the guide directed, then tried using regular ADB, which didnt work. So I tried to use the ADB fast push and it didn't work either, under the "information" tab on the fast adb program it says
"Failed to mount as R/W"
is this a problem?

I got files to push via ADB, installation was aborted on the stock rom
I will try to find another stock rom to flash and update you guys. thanks for all the help so far

Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.

mikaole said:
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
Click to expand...
Click to collapse
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!

ljungberg3 said:
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
Click to expand...
Click to collapse
Np

So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
That thread lead me to this one, as I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet, however, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?
http://s12.postimage.org/unt8ag1vh/adbcmd.jpg
Created new thread as OP solved his problem.

[WIP] Rooting Procedure for X2

Hello there users. I'm currently a dev for Nokia X but I would love to help you guys out.
So, I'll be giving out ways on how you can try to get Root on your device. This is a discussion thread.
As I don't have the device myself, I'm counting on people who have purchased it.
So lets start. In order to get development for your device, you need to get a system dump of your whole/entire device.
But for that, you need Root. Heres an app that I think might root the device. http://www.cydiaimpactor.com/
Goto the link, download it and test it out. Give feedback.

And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.

stutofa aregercisr are
Thanks for your help, I tried it out and got this error all the time

Altivex said:
And nothing happens. Maybe I`ve done somthing wrong...
So, in a dev options i`ve point usb debuging.
On my pc i got two new devices - Nokia composite adb interface and nokia 2 with yellow mark.
Then run cidia from admin name - usb - driver scan - no device found.
I tried with rooted nokia xl - just to see what happens - error - no such device.
Click to expand...
Click to collapse
tdiddy.2 said:
Thanks for your help, I tried it out and got this error all the time
Click to expand...
Click to collapse
Okay, so that didnt work.
Now, goto this link and download the adb and fastboot drivers for Nokia X and install them.
After that, go HERE and flash CWM Recovery for Nokia X using the instructions given in the thread.
DONT DO THE ABOVE METHOD! As there is no backup, if something goes wrong, you'll lose the device. For now, wait and let me find more exploits. Till then, do install the adb and fastboot divers.
After that, goto ADB folder and Open command prompt from there (Shift + Right mouse button). Then type this:
Code:
adb reboot bootloader
fastboot -i 0x0421 devices
And see if the device gets recognized.
Then type:
Code:
fastboot -i 0x0421 reboot

You can try this method too: http://forum.xda-developers.com/showthread.php?t=803682

Okay will try. For the recovery, I tried both Nokia X's CWM and TWRP already, none of them worked However it's not going to brick my device haha

On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...

Altivex said:
On fastboot - nothing. I coudn`t install adb from this tread
http://forum.xda-developers.com/showthread.php?t=2744191
Installer told me-unsupported language and close)
I used cmd.exe ,and path to android tools - on fastboot i got nothing. No list of devices. But.
On reboot or others command - answer is - Waiting for device
Super one click - runs adb server around 3 times, then program freez on - Waiting for device =)
If i click on button driver chek - no issues found.
Maybe i`ve got some trouble with drivers ?
I got them from here
http://developer.nokia.com/resources/library/nokia-x/getting-started/device-setup.html
But i haven`t adb_usb.ini where it should be...
Click to expand...
Click to collapse
adb_usb.ini is important as it is the key that recognizes the adb device to the computer.
Do all the above steps in the guide fully including the adb_usb.ini step.

mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)

Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$

I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
http://forum.xda-developers.com/showthread.php?t=2783157
or in attach.
Copy all data to phone, then go to folder "1" install tr.apk
Make shure you`ve got internet connection.
in folder "2" is SUpersu apk.
In folder"3" - root explorer.
Also you`ll find apk for backup phone.

Altivex said:
mmmm, Nokia XL got connected without this file...
I tried all instructions on 3 different pc - this file is missed....
So,i just created this file.
on ADB devices i got answer - 188bde4a device
on command fastboot -i 0x0421 devices-
188bde4a fastboot
then i reboot device.
i`ve try out some comands - i lost recovery....
fastboot -i 0x0421 oem unlock
unlocked
fastboot -i 0x0421 flash recovery recovery img.
7seconds flash - and i coud not boot recovery....
i tyed this one
http://forum.xda-developers.com/showthread.php?t=2704379
but - phone boots up in normal mode...
ok,good news - got stock firmware from navifirm!
Just need stock recovery)
Click to expand...
Click to collapse
Thats it. You got the fastboot recognized. Now try Bin4ry Root Method and see if it'll work.
tdiddy.2 said:
Okay, i tried superoneclick, not work :crying:
---------- Post added at 11:02 AM ---------- Previous post was at 10:58 AM ----------
And for the Fastboot...
Code:
Tungs-MacBook-Air:~ md232llaoption$ fastboot -i 0x0421 devices
f901c863 fastboot
Tungs-MacBook-Air:~ md232llaoption$
Click to expand...
Click to collapse
You also got fastboot recognized. f901c863 is your fastboot device number.
Try Bin4ry root method.
Altivex said:
I think i goot rooted my device....
with root_backup
or towelroot.
So, if I`ll install gaps- that would be great. But i really need custom recovery)
Click to expand...
Click to collapse
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.

Dom3616 said:
Wait. Did you get Root? HOWWW?! Share if you did. Cause this is what the thread is about.
Click to expand...
Click to collapse
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)

Altivex said:
Towelroot in attach. Idk will it work on clear device,or you need to unlock bootloader. Cos on oem unlock- unlocked something=)
Click to expand...
Click to collapse
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045

Dom3616 said:
Very good. I'll be updating this thread soon.
Now, next step is to goto this thread and make a full dump of your device: http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Yes yes!!

Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?

Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
Yes, you can use this also: http://forum.xda-developers.com/showthread.php?t=1620255
After creating the backup, upload it to Google Drive or any other server.

Altivex said:
Hmmm, and online nandroid backup can do this procedure? Or dump and backup- defferent things?
Click to expand...
Click to collapse
I tried to pull and got the recovery img for ya hope this work

Native recovery or custom?)
native I`ve restored yesterday from navifirm. And custom will make our life a bit easyer)

I`ve made a twrp backup, with nandroid . Backup have files with .win extension....

ZTE Axon 7 axon7tool failed to connect

Hi there!
I'm newby with android and unlocking the device. My device ZTE Axon 7 A2017G
I want a device running on Lineage os. So I try since 3 days to backup and flash the recovery with axon7tool.
I get always the error message: failed to connect.
I try to install the driver with zadig and now i see the Q...BULK device but still become this error...
I was on android 7.1 B01 and now have downgraded to android 6.0.1 (A2017GV1.0.0B10)
Still the same error.
I changed the computer, still this stupid error.
Can anybody help me, I'm frustrated...

I had this issue and solved it by showing all file extensions in windows. When you rename the recovery.img to recovery.bin you have to make sure that it's actually an BIN file and so you need to have show all file extensions on in the windows settings.

thanks for your answer.
I'm realy shure that I have activated this option, because of other development stuff
Even the first command in each tutorial is not working: "axon7tool -r gpt boot recovery"
When I disconnect my axon and then run the command again I become this error: "Device not connected/found, Failed to connect"
So this means, if I connect the device and I see only the error: "Failed to connect"
the axon7tool see my device but can't connect to them?
p.s. after the downgrad from android 7.1 to 6.0.1 I don't see any updates such as android 7 and I haven't a connection to mobile data (3G/4G). Very frustrated when I want to use whatsapp outdoor

Sorry. I don't know what your issue is then. I'm sure someone else here can help you.

Do you have then Qualcomm drivers installed? If not, try this: QUD.WIN.1.1 Installer-10039.2.zip
If it's still not detected, use the Zadig Tool found here

I had a similar issue. You have to grant admin rights when opening a command window.
Send from ZTE A2017G using Tapatalk

KwesiJnr said:
Do you have then Qualcomm drivers installed? If not, try this:
If it's still not detected, use the Zadig Tool found
Click to expand...
Click to collapse
thank you. What should I select in the wizard when he ask me for the following:
Please choose between WWAN(NDIS6.20) and ETHERNET(NDIS 5.1)
- WWAN-DHCIP is not used to get IPAddress
- ETHNER-DHCP is used to get IPAddress

First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.

KwesiJnr said:
First, make sure your device is in EDL mode.
1. On opening the Zadig tool, click on Options from the top, then List All Devices. That should display your phone in the dropdown section now. It should be something like QUSB_BULK.
2. After selecting QUSB_BULK, you can click on the big Replace Driver button. On completion, try the axon7tool once again. It should not fail this time.
Click to expand...
Click to collapse
oh wow! One step further.
The tool waits a second an then I see this error:
C:\Users\bearbeer\Downloads\adb>axon7tool -r boot
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
I dont understand the message.

bearbeer said:
oh wow! One step further.
The tool waits a second an then I see this error:
I dont understand the message.
Click to expand...
Click to collapse
Good, reboot your device into EDL mode once more and try again.

KwesiJnr said:
Good, reboot your device into EDL mode once more and try again.
Click to expand...
Click to collapse
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?

bearbeer said:
yeah!! It works thanks!
Now I have a flashed recovery. Next step is to unlock the bootloader. For all of it I follow this tutorial: https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
After I restart the bootloader "adb reboot bootloader" (step 7) I should see my device with "fastboot devices", but it shows me no device. What can I do?
Click to expand...
Click to collapse
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.

KwesiJnr said:
Okay, it is time to reinstall the Qualcomm Driver. The driver from Zadig was only for EDL mode (at least that's how I saw it). You remember the QUD.WIN.1.1 Installer-10039.2.zip I posted earlier? Install that and reboot your PC.
Note: I'd normally recommend rebooting the PC into Driver Enforcing mode before installing the Qualcomm driver to avoid any install problems. It may not be necessary, but it does make the install foolproof.
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Do remember to check Device Manager to make sure your device is recognized in fastboot mode. If it isn't, try installing the ADB driver from here.
Click to expand...
Click to collapse
thanks again. It works!
What's the next step to become lineageos running on my device? Download and install lineageos or do I need something else before?

If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.

KwesiJnr said:
If your bootloader is unlocked and you have installed TWRP Custom Recovery, all you have to do is flash the Nougat Bootstack. You can then proceed to flash/install all LOS and LOS-based ROMs. I'm currently running ResurrectionRemix.
Click to expand...
Click to collapse
Ok I have flashed the TWRP Recovery (not the latest because the latest boot not up) and unlocked the bootloader. What's the Nougat Bootstack and how do I install it?

Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.

KwesiJnr said:
Visit the Official LineageOS thread for Axon 7. It has all the steps you need to successfully install LOS on your device. Make sure you install the Universal Bootloader & Modem Package specific to your device.
Also, about the TWRP. The newer versions don't work without flashing an older version. Once the older version is installed, you can then upgrade to a newer version.
Click to expand...
Click to collapse
What's the best way to upgrade the twrp?

bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.

bearbeer said:
What's the best way to upgrade the twrp?
Click to expand...
Click to collapse
0. Reboot to TWRP, then copy the desired Recovery Image file you want to upgrade to, (e.g. twrp-3.1.0.0-ailsa_ii.img) to your Internal Storage.
1. Tap Install Image from the lower right corner. Proceed to select the recovery image you just copied to your device.
2. You should now see a radio list. Select Recovery, then swipe to flash.
3. Reboot.
That is all.
Alternatively, you can flash the recovery upgrade file via fastboot, like you did the older version. Just make sure you flash the older version first, THEN the newer. Should work like a charm.
---------- Post added at 10:27 PM ---------- Previous post was at 10:24 PM ----------
metpolds said:
@bearbeer ... In view of the fact that you are new to the forums (9th April 2017) and have started this thread having bricked your A7, and have shown your complete ignorance and lack of understanding of Android, you are extremely fortunate that a member ( @KwesiJnr ) has taken the time to respond to all your subsequent questions with answers that have got you out of trouble - and yet not a single press of the "Thanks" button can be seen by you.
XDA was formed by members who respected the advice and assistance given them and who responded by showing their "THANKS" so please show some common decency and show proper thanks to @KwesiJnr.
Click to expand...
Click to collapse
Lmao. I feel you, bro. Pretty convinced he's new to these forums as you guessed, and I'm sure he likely doesn't know about the 'Thanks' system. You know, benefit of the doubt and all.
Ultimately, I just wanted to help out. I know how frustrating it can be with these things so...

Thank you! Ok I'm now on "twrp-3.1.0-0-ailsa_ii.img" and it works.
Yes this is correct. I don't saw the "thanks" button...
I'm so happy that all of you help me. As a newby there are so many threads, tuts, ... an everywhere all goes right. But on my device nothing works at first try. Thank you a lot! :good: :laugh:

sideloading adb firmware

So I am really stuck and don't know what to do. Unlocked the bootloader, installed twrp just fine and rooted. then I went to install a custom rom after I made sure it was working and then it kicks me back to the normal recovery. twrp is gone and I can't fastboot the firmware cause I wiped it to flash a rom. Now when I go to adb sideload I keep getting error 21 footer is wrong and signature verification has failed. Can someone please point me in the right direction to fix my phone? thanks

Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds

gm007 said:
Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.

tommyjames1992 said:
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.
Click to expand...
Click to collapse
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.

gm007 said:
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.
Click to expand...
Click to collapse
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.

tommyjames1992 said:
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.
Click to expand...
Click to collapse
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.

gm007 said:
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.
Click to expand...
Click to collapse
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.

tommyjames1992 said:
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.
Click to expand...
Click to collapse
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948

gm007 said:
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948
Click to expand...
Click to collapse
So I am still got getting fastboot working to flash stock firmware but I managed to reflash twrp and install AICP custom rom. So at least I can use the device. I will figure out the fastboot stuff later I guess lol.

Software update cannot be assigned and TWRP cannot be installed!

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.

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 ----------
gokhanhaskilit said:
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.
Click to expand...
Click to collapse
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:

[email protected] said:
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:
Click to expand...
Click to collapse
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?

gokhanhaskilit said:
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?
Click to expand...
Click to collapse
Have you tried fastboot boot recovery.img

[email protected] said:
Have you tried fastboot boot recovery.img
Click to expand...
Click to collapse
I tried but failed. Can we talk on Telegram?

gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
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.

gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
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 ----------
gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
optimumpro said:
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.
Click to expand...
Click to collapse
He already unlocked the bootloader

[email protected] said:
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
Click to expand...
Click to collapse
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.

[email protected] said:
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
Click to expand...
Click to collapse
gokhanhaskilit said:
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.
Click to expand...
Click to collapse
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 ...

gokhanhaskilit said:
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 ...
Click to expand...
Click to collapse
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)

[email protected] said:
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)
Click to expand...
Click to collapse
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?

gokhanhaskilit said:
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?
Click to expand...
Click to collapse
What do you mean cache removal tool?

[email protected] said:
What do you mean cache removal tool?
Click to expand...
Click to collapse
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 said:
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?
Click to expand...
Click to collapse
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 said:
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 ..
Click to expand...
Click to collapse
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...

gokhanhaskilit said:
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?
Click to expand...
Click to collapse
gokhanhaskilit said:
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
Click to expand...
Click to collapse
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 ----------
gokhanhaskilit said:
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
Click to expand...
Click to collapse
Try using the new adb driver
Uninstall older driver and install this:
http://www.mediafire.com/file/a4d0p5uvebc0xwp/file