Database Users

[Q] Stuck in Bootloader

Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?

ADB and fastboot drivers are different.

Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....

http://bit.ly/Zqk7pm

and what do u want me to type in there ? i alrdy used google for the last 7 hours ?

oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....

Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..

no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.

oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck

hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?

oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck

bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...

In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.

thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g

oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img

hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?

oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.

just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio

Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes

SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).

Stuck in 'waiting for any device' when trying to flash factory image with fastboot

Hi, I am trying to revert to stock Android (phone is stuck in a boot loop) by flashing the factory images (Heisenberg's thread, point 12) but am getting the 'waiting for any device' message and nothing happens when trying to execute fastboot commands.
The phone is recognized, however, when I get it into TWRP Recovey and type 'adb devices', shows the serial number and recovery status. When I'm in the bootloader the phone isn't recognized, "connect usb data cable" even though it is connected.
I am stuck at this point / out of my depth and out of any further ideas

go to bootloader and type "fastboot devices"

fastboot devices - no value
fastboot devices - returns no value; adb devices still gives me serial of the connected nexus 6p
could this be a driver (on my pc?) issue?
weird that fastboot devices returns no value

ciliax said:
fastboot devices - returns no value; adb devices still gives me serial of the connected nexus 6p
could this be a driver (on my pc?) issue?
weird that fastboot devices returns no value
Click to expand...
Click to collapse
Sounds like it. Try installing fastboot drivers again.

ok, I give that a shot

OK, so I installed the SDK package on a different PC, tried it with the Google USB drivers and then with the Huawei drivers instead. Same result as before...
ADB Devices shows my phone, fastboot devices returns no value. The phone is only recognized when in recovery Mode (TWRP) - not when in the bootloader.
This is very frustrating.
Any other ideas anyone?

Did you do all the prerequisites from the guide? http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 Or maybe a java being outdated? Last idea is installing usb drivers manually http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver

ciliax said:
Hi, I am trying to revert to stock Android (phone is stuck in a boot loop) by flashing the factory images (Heisenberg's thread, point 12) but am getting the 'waiting for any device' message and nothing happens when trying to execute fastboot commands.
The phone is recognized, however, when I get it into TWRP Recovey and type 'adb devices', shows the serial number and recovery status. When I'm in the bootloader the phone isn't recognized, "connect usb data cable" even though it is connected.
I am stuck at this point / out of my depth and out of any further ideas
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/help/adb-fine-fastboot-t3297277
long story short, blame windows

If you can boot into TWRP, what about pushing the images into the phone via adb push ?
The new TWRP 3.0.0.0 can flash the .img files, but I am not sure if it will be able to flash the system, boot, and so on images... But I would give it a try though..
If not, please someone correct me.

neisor said:
If you can boot into TWRP, what about pushing the images into the phone via adb push ?
The new TWRP 3.0.0.0 can flash the .img files, but I am not sure if it will be able to flash the system, boot, and so on images... But I would give it a try though..
If not, please someone correct me.
Click to expand...
Click to collapse
If TWRP 3.0 can flash system, boot, radio, vendor, etc image files that would be awesome! OP keep us posted.

Pain-N-Panic said:
If TWRP 3.0 can flash system, boot, radio, vendor, etc image files that would be awesome! OP keep us posted.
Click to expand...
Click to collapse
Well, quoting the https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html where it says exactly this: "Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI" in the 4th dot/part of the "What’s new in 3.0.0-0" section.
So, I guess twrp should be able to do the job.

neisor said:
Well, quoting the https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html where it says exactly this: "Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI" in the 4th dot/part of the "What’s new in 3.0.0-0" section.
So, I guess twrp should be able to do the job.
Click to expand...
Click to collapse
Awesome! Anyone know what the select "some parts" of the factory image they're referring to?

Pain-N-Panic said:
Awesome! Anyone know what the select "some parts" of the factory image they're referring to?
Click to expand...
Click to collapse
On Nexus 5X and 6P, TWRP can flash system.img, boot.img, and vendor.img. TWRP cannot flash bootloader and radio.img.
Sent from my Nexus 5X using Tapatalk

Cant install TWRP-MATA_2 error: cannot load 'C:\ADB\recovery.img': No such file or...

I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help

There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.

MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:

MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.

fastboot flash boot_a/boot_b yourTWRP.img
The above command worked for me. Use boot_a or boot_b depending on what you have. In addition use a separate type C cable to your PC instead of stock type C cable and remove all USB accessories plugged in the PC. I know its crazy but working with this phone may require you to do some unexplainable stuff.

MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP

TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.

droidstyle said:
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
Click to expand...
Click to collapse
I am semi new to this community, so I am unsure if it's doing this because I am rooted or not but I've got twrp permanently installed... So from my understanding Slot a can hold your os and slot b basically hold your twrp you just need to remember when you need to switch back.... How I installed was fast booted twrp to slot a, then in twrc switched to slot b to install rom, then switch back to slot a and did a reboot to recovery... Boots into twrp, I switched back to slot b to flash gapps, then restart system... Once inside os and everything is set up if you are rooting reboot to bootloader and flash the patched boot. Img with fastboot on pc... Then reboot system... Now when you want to use twrp all you have to do is reboot bootloader, fastboot to switch to slot a, and then boot recovery... Then Twrp will load then switch to slot b and you are good to go!

barteringram said:
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
Click to expand...
Click to collapse
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise

A_Pac1 said:
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
Click to expand...
Click to collapse
Worth a try I guess but I am maintaining a solid connect to my PC and all other commands seem flawless. My problem has evolved now. I have installed twrp but now the touchscreen wont work.

rignfool said:
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
Click to expand...
Click to collapse
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?

MackHoncho said:
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
Click to expand...
Click to collapse
It's not persistent as in it won't survive the flashing of the stock boot.img.

MackHoncho said:
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
Click to expand...
Click to collapse
I had the same issue with using an older version of Mata TWRP... You need to install TWRP-MATA_11

Solved
My Windows 10 machine isnt set to show file extensions.
was trying to fastboot twrp-11 as I named it; recovery.img
fastboot wanted recovery.img.img
please laugh hardily

aer0zer0 said:
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!

vonstarr said:
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
Click to expand...
Click to collapse
So op6t is easier (I just bought one)
Fastboot boot nameoftwrp.img
It'll boot twrp without flashing it to the phone. Makes life easier. Mata doesn't have this option.

Device bricked

Hi!
I bricked my axon7 g.. I had a running CM15.1 and wanted to restore a CM14.1 backup. First of all i downloaded and flashed the modem and bootloader for cm14.1. after that i wiped system and data and rebootet into recovery. Here I noticed a bug wich i already had when I updated to CM15.1: the data and system partition are unable to mount. So i download and installed a other recovery (nfound) and rebooted. And here is the Problem: I'm unable to go into the recovery.
After some hours of trying different methods I need your help. This is what I found out:
1) I can boot into FFBM and fastboot
2) when I boot into fastboot the windows device manager shwos me Android ADB Device
3) when i try to use the adb tool i says:
Search >>> interface found >>> Android ADB Interface
Checking ADB Interface:
Command execution adb devices >>> !!! Error !!! no answer from phone
This is becuase usb debugging was not enabled.
4) When i use the dfu tool and wnat to confirgure the ports it only says: this device has no usb ports or (when i turn of virus scanner and reboot..) "the tool is running"
Is there any way to flash a recovery?
Thank you!

I solved it via fastboot and adb

Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck

Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.

I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working

Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!

Did you try to format /System/ as EXT4?