Database Users

TWRP blowing away OS - user error?

Everytime I install TWRP and boot into it. It shows Zero internal storage and when I reboot it outlines there isnt an OS installed.
The system OS isnt wiped (although I thought that the first 50 times). When I enter fastboot again TWRP inst installed.
No idea what going on... tried latest and previous TWRP files.
thanks in advance
Heres the Log
-------------
Z:\NewNexus7Root\platform-tools>adb reboot bootloader
Z:\NewNexus7Root\platform-tools>fastboot flash recovery twrp-2.8.7.0-flo.img
sending 'recovery' (8956 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.271s]
finished. total time: 0.564s
Z:\NewNexus7Root\platform-tools>adb reboot recovery
error: device not found
error: device not found

Got it working after I found the MultiRom fix on this site.
Seems I had one of those unique "locked down" Nexus's 2013; mines from Amazon.

Can't get fastboot flash recovery twrp.img to TAKE after factory reset??? Help>

I originally did a boot unlock, a fash of twrp-2.8.7.2-angler.img, and when I could not get the pattern on twrp recovery to function, I did a sideload of the twrp.img instead of an install.
This failed in a boot loop.
SO I did a flash back to stock with angler-mdb08m-factory-dbc17940.tgz (after unpacking this).
Then I restored all my apk, etc.
BUT now when I do:
fastboot flash recovery twrp-2.8.7.2-angler.img, I SEE:
target reported max download size of 494927872 bytes
sending 'recovery' (16880 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.247s]
finished. total time: 0.809s
---- all looks fine, but the device itself does not seem to react and when I reboot, and select recovery, it just goes into Google recovery.
Has anyone else seen this, and do you know how to get past this?
I already tried to unlock again and it tells me error, already unlocked.
So my next step would be to do a lock and then an unlock again, but that would probably cause me to take several hours restoring after another flash to stock, and I fear that I will be back where I am now??? any thoughts??

SOLVED!
It seems that somehow, I just hadn't waited long enough. I was able to now reboot into recovery.
Thanks to any that looked at this issue.

Can't Flash TWRP

Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.

bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img

Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT

bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.

Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse

Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?

Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P

Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?

Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app

Sorry, you can't sdcard upgrade

I did the b10 update yesterday, fully stock.
After the update it keeps getting stuck at the boot screen.
Luckily recovery still works.
I downloaded an official rom package, put the update.zip on 3 different sdcards.
all 3 cards get the same response from recovery. 'Sorry, you can't sdcard upgrade'.... great... fine sideload it is.
so tried to sideload, got this message:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Then tried to fastboot twrp
got this message:
C:\adb>fastboot flash recovery twrp-3.0.4-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.402s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.424s
I have had several galaxy phones in the past, but never encountered this troubles.
Does anybody have a idea what's going on? im kinda lost here.

FREEKR said:
I did the b10 update yesterday, fully stock.
After the update it keeps getting stuck at the boot screen.
Luckily recovery still works.
I downloaded an official rom package, put the update.zip on 3 different sdcards.
all 3 cards get the same response from recovery. 'Sorry, you can't sdcard upgrade'.... great... fine sideload it is.
so tried to sideload, got this message:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Then tried to fastboot twrp
got this message:
C:\adb>fastboot flash recovery twrp-3.0.4-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.402s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.424s
I have had several galaxy phones in the past, but never encountered this troubles.
Does anybody have a idea what's going on? im kinda lost here.
Click to expand...
Click to collapse
Your battery percentage is low. Make sure you charge it until at least 80%
EDIT: Enable OEM unlock in developper settings

Flashing recovery (I know not right spot, I don't have a high enough post count)

So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from here and it's still not giving me root after flashing SU to the device.

KevinDel said:
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from and it's still not giving me root after flashing SU to the device.
Click to expand...
Click to collapse
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?

Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
I got the TWRP to actually work now, now it's trying to get SU to work. I got TWRP from here I can't get majisk or SU to run at all though now.

Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
Also it's the XT1768 model.

Try installing magisk the new way (without a custom recovery). There are instructions in the main magisk thread.