Database Info

How to update early TWRP withoput adb and spooling rom problem

I'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.

Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13

There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.

If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).

Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks

plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.

plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.

Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.

plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?

berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.

plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished

All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks

Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...

After update, flashed twrp, now booting straight into twrp

So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.

Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good

usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.

fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked

schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.

iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push

schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all

Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).

iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome

[SOLVED] Asking Experts for Solving Bootloop Nokia 8

So, I want to say that my Nokia 8 TA-1004 is having Bootloop. This happens very occasionally and randomly. It just attacks unexpected. I can't see what is the problem or what's the source of it. Thankfully, I have the logcat file. However, I do not understand what was the main cause. So please, I am asking the experts in here to help me identify the source of this error.
The Bootloop just boot like 4-5 times and then stopped Bootloop or sometimes just go straight to DOWNLOAD MODE and I had to restart manually. After that, i was able to gointo system like exploring like usual, and then it happens again. Sometimes not opening the app also happens. Repeat until you gets the nerve.
The phones status is rooted with magisk and unlocked bootloader but no twrp yet. Also, I am at 4.88B SP01 June,01 patch. If you are telling me that the root is the cause, then it is unlikely since it has been weeks since I had it rooted but the problem just came these recently.
Once again, I ask for the help of forumers here. I want to at least enjoy my phone that I love. I dont really want to sell the phone anymore.
Here's the link of logcat:
https://www16.zippyshare.com/v/2W0SVK8t/file.html
I promise. No viruses. Thank you

Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.

error748 said:
Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.
Click to expand...
Click to collapse
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?

godofknife said:
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?
Click to expand...
Click to collapse
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..

sumitinhome said:
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..
Click to expand...
Click to collapse
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.

godofknife said:
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.
Click to expand...
Click to collapse
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.

sumitinhome said:
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.
Click to expand...
Click to collapse
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.

godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
I have it. Wait sometime.. i will upload it on gdrive and share you link

sumitinhome said:
I have it. Wait sometime.. i will upload it on gdrive and share you link
Click to expand...
Click to collapse
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?

godofknife said:
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?
Click to expand...
Click to collapse
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk

sumitinhome said:
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk
Click to expand...
Click to collapse
Ah ha, thank you very much. I just need one more requirement. The driver. Honestly, there are so many drivers for Nokia 8 and none of them seems to work with my device detection. There's also type F, M driver..... Seriously confusing.

@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp

godofknife said:
@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp
Click to expand...
Click to collapse
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.

sumitinhome said:
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.
Click to expand...
Click to collapse
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?

@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.

godofknife said:
@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.
Click to expand...
Click to collapse
well done

sumitinhome said:
well done
Click to expand...
Click to collapse
Thank you.
godofknife said:
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?
Click to expand...
Click to collapse
@sumitinhome, how about this? I still have the issue. NO OS is running.

godofknife said:
Thank you.
@sumitinhome, how about this? I still have the issue. NO OS is running.
Click to expand...
Click to collapse
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button

sumitinhome said:
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button
Click to expand...
Click to collapse
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?

godofknife said:
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?
Click to expand...
Click to collapse
no it doesn't need any key

Trying to restore my oneplus.

So i recently decided to update my Oneplus 7 Pro from the public stable release to the OxygenOS 11 Open Beta 3 on a whim. Tried to go back to the old stable release by flashing fastboot roms from Tool All In One and it somehow broke everything, even though I did it multiple times before.
Phone can't boot into anything -- even with stock roms installed. Simply shows the bootloader is unlocked screen and nothing after. I can get into recovery and edl and fastboot, but nothing else. I think I flashed an older version from TAIO's fastboot rom flasher, making it impossible (!) for my computer to interact with my phone.
MSM Tool also doesn't work. Param preload, even though I have the QC and OP drivers installed.
Anything I can do?

You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times

@soka said:
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
Click to expand...
Click to collapse
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).

VictimOfMagic said:
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
Thanks for replying
Click to expand...
Click to collapse
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com

@soka said:
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao

VictimOfMagic said:
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
Thanks for replying.
Click to expand...
Click to collapse
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.

md5hasher said:
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
Click to expand...
Click to collapse
Running TAIO as an admin? That still only downloads WinUSB.
Can you expand on what you mean?

Under windows 10 open CMD as admin and enter bcdedit /set testsigning on
now reboot. This resolved for me the driver issue and phone was then correctly seen by msm unbrick tool

Question Bricked?

In an attempt to unlock my bootloader and start using my X3 Pro I think I might have partly bricked my phone... I hope anyone can help me bring it back to life...!
I'm on a linux computer and after a wait of around a week I managed to unlock the bootloader! I still can boot into the flashed TWRP recovery
But I think I have done something wrong, I can't flash a rom or .zip, I can't sideload a file, I can't select to mount system partition (because it's not listed)
When I use ADB sideload, the error message is 'can't find partition for path ' /system_root', when I try to flash a zip in TWRP the error message is 'Failed unmounting System'
I think I made a mess of the partitition table or something like that.
So I can:
- use TWRP or Fox recovery
- use fastboot command when in fastboot mode
but I can't
flash a rom nor a fastboot rom
mount the internal storage to transport a .zip file or something

How did you attempt unlocking bootloader under Linux if the official Mi Unlock tool is only available for Windows?

I found this XiaoMiTool V2 project and then this XMT2_Linux_20.7.28.run
and was able to (after the 168 hour wait) unlock my bootloader.

With no official tools available for Linux (especially since the XiaoMiTool V2 is abandoned and not really supported by the creator), I would recommend avoiding such attempts and instead I would attempt to unlock the device on Windows as intended
Have you tried flashing the fastboot image you downloaded using the flash_all.sh script?

I did and I did get error after error, but now I'm trying again to look for the error messages so I could report back...
and now it looks like there is some progression... so I'm hoping

I'm so sorry and a little ashamed, but now it is working and the rom is installed.
Thanks for your time!
And is there a way to archive this thread?

-Fedde- said:
I'm so sorry and a little ashamed, but now it is working and the rom is installed.
Thanks for your time!
And is there a way to archive this thread?
Click to expand...
Click to collapse
Great to hear!
You could probably ask a forum moderator about that, or self-report this thread, but perhaps it may be a good idea to leave this thread here so if anyone else experiences the same problem, this thread may save them some time? Your call though.

Hey, you know why are you getting those errors?
Because the recovery isnt working fully yet!
However, the new ofox (accessible on the official chat on telegram, i dont care putting it here, if you want it directly, pm me) works somehow, i mean, it has wipeable partitions, and flashes eu properly.