Database Users

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

FAILED (remote: Permission denied!)

Hi guys,
I need some help, I'm rooted running on the stock rom.
I was running the 6.0 L and decided to update to 6.0.1 vie fastboot.
I followed this guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) section 10- and did the exact same thing.
Every thing was flashing fine till I reached system.img and this is what I get.
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
I did not flash the recovery because it says it's optional. I proceeded with the vendor and rebooted the device. When the device starts I get a pop up saying : There's an internal problem with your device. Contact your manufacture for details.
In the setting im still on 6.0 L build but bootloader and radios are on the latest firmware.
any suggestions?
Thanks
I did some search and couldn't find a decent answer.

If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
C:\SDK\android-sdk-windows\platform-tools\6.0.1>fastboot flash sysytem C:\SDK\android-sdk-windows\platform-tools\6.0.1\system.img
target reported max download size of 494927872 bytes
sending sparse 'sysytem' (463062 KB)...
OKAY [ 10.395s]
writing 'sysytem'...
FAILED (remote: Permission denied!)
finished. total time: 10.410s
Click to expand...
Click to collapse
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.

SlimSnoopOS said:
If this is copy/paste directly from Terminal, then you misspelled "system" in your initial command:
Notice the bold, the command is looking for "sysytem" which does not exist. You'll be good to go, if the typo is removed.
Click to expand...
Click to collapse
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?

mr.dj26 said:
:| facepalm...... thanks man, I should not flash things at 1 AM.
I assume I dont need to flash the BL and radios again? just wipe cache install boot, system and vendor?
Click to expand...
Click to collapse
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Correct, as long as you flashed the proper bootloader and radio. Just keep it all matching and you should be set. I try to avoid doing phone tinkering at night lol just never feel like troubleshooting at that time if I mess up.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
lol, ya i'm falling asleep so i'll do it tomorrow, thanks again and good night.

Bootloop PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!

Hey everyone, I've spent the last 5 hours trying to fix my phone and I'm not getting anywhere.
It gets to the second part of the starting up process, where it makes the sound as well and it just keeps glowing over and over.
I'm able to access the recovery mode, I've already tried clearing the partition cache & I've also done a factory reset.
I've tried flashing recovery.img & boot.img from B170 which I read somewhere, I've done that successfully but it doesn't seem to do anything.
I had this before and I fixed it by flashing system.img but for some reason it keeps giving me an error when I try to do it now: "error: cannot load 'system.img'"
Also flashing the bootloader doesn't seem to work:
"C:\Users\Leron\Desktop>fastboot flash bootloader twrp-2.8.7.1-p8.img
target reported max download size of 471859200 bytes
sending 'bootloader' (25880 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
FAILED (remote: partition does not exist)"
I've read something about buying a card adapter but as I said, I have no money...
I tried to root my phone, bad f***ing move because for some reason it's impossible on the Huawei P8, excuse my bad language but im extremely frustrated i should have never done this. any help is welcome
thanks

usleronus said:
Also flashing the bootloader doesn't seem to work:
"C:\Users\Leron\Desktop>fastboot flash bootloader twrp-2.8.7.1-p8.img
target reported max download size of 471859200 bytes
sending 'bootloader' (25880 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
FAILED (remote: partition does not exist)"
Click to expand...
Click to collapse
Big mistake, no wonder it won't flash.
TWRP is NOT a bootloader but is a recovery, so therefore the correct fastboot command is:-
fastboot flash recovery twrp.img
The P8 is quite easily rooted see here:-
https://forum.xda-developers.com/showpost.php?p=74206273&postcount=305
and here:-
https://forum.xda-developers.com/huawei-p8/how-to/rooting-huawei-p8-marshmallow-emui4-0-1-t3431249

Oh my bad haha.
I fixed it using SRKToolHuawei, which is very useful. I'm very new to this so that's why I screwed up so bad lol
Thanks for the help though. I'll check out the links you sent me and try to root again. Hopefully this time I won't break my phone lmao.

[HELP] Bricked phone while trying to install custom rom

I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked

Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk

seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...

ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it

yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...

Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?

What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk

Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.

ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!

We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.

I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........

ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?

same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...

ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?

ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)

I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.

Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.

My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry

Pixel 2XL - Android 11 Dev Preview install issue: Not enough space

Hello,
I spent the last two evenings trying to install the Android 11 preview in my old "spare" Pixel 2 XL, however I run into some issues.
I unlocked the bootloader, and tried to install the preview via adb sideload, this didn't work, error was some Signature Verification error.
I noticed my Pixel 2 XL was still on the October 2019 patch level, but it would not find an update using system update in settings.
So I downloaded the February 2020 factory image, tried to install is via adb sideload as well, same issue, Signature Verification error.
I tried the November 2019 OTA file, and was able to sideload and install it, phone booted and it finally started finding updates, so I updated to the latest Security patch level February 2020 using system updates.
I hopped this will solve my issues but still, the same Signature Verification error, with both 11 dev preview as well as the current full factory image.
I then moved on to using the flash-all.bat file. It would start, installing the bootloader and radio, but it is not able to install the image-taimen-qq1a.200205.002.zip, I'll always get this "error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space"
And this issue I cannot solve, well, both the validation issue and the "not enough space" issue.
By now I installed twrp recovery, not luck either, running into the same issues when trying to install the image.zip after pushing it to the phone.
"not enough space" Error
=================================
\platform-tools\taimen-qq1a.200205.002>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36352 KB)...
OKAY [ 0.811s]
writing 'bootloader'...
OKAY [ 0.267s]
finished. total time: 1.080s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.352s]
writing 'radio'...
OKAY [ 0.800s]
finished. total time: 2.153s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space
Press any key to exit...
=================================
I also tried to follow some "manual" flashing guides, but those are all for Android 8, the file names and file system format has changed a lot, so that would not work either.
I believe I completely corrupted one of the two partitions doing that, luckily after a few failed boots the device booted from the other partition, for some reason that had thrown me back to December 2019 patch level, so I updated up to February 2020 using the standard system update feature, that fixed both partition slots A and B, so I am back to a normal functioning device with twrp installed. But I cannot solve this issue.
Would be glad if someone has a solution for this, or suggestions on how to tackle this.
[EDIT]: As I mentioned this is a spare test device, I am not worried about any data, the device was completely wiped anyway. Also it is the 128GB version.
Regards,
Alex

Just flash the 11 ota with twrp. Works fine.
When you go back to 10 you'll have to format your data

I've encountered the verification error before and what I did was redownload the file and it solved the problem. As for the not enough space I would check out the Google dev site as they have a flash tool you can use to flash as well. Just a suggestion to try. Hope you get figured out.

Edmontonchef said:
Just flash the 11 ota with twrp. Works fine.
When you go back to 10 you'll have to format your data
Click to expand...
Click to collapse
Thanks, that worked! I didn't even knew there are OTA files for the 11 preview.
The announcement stated image flashing only, so I assumed only full factory images are available.
I flashed the stock boot image back as well, so no twrp anymore, no reason, just like to run stock if possible.
Thanks a lot again, such a simple thing.

pantallica420 said:
I've encountered the verification error before and what I did was redownload the file and it solved the problem. As for the not enough space I would check out the Google dev site as they have a flash tool you can use to flash as well. Just a suggestion to try. Hope you get figured out.
Click to expand...
Click to collapse
Thanks, I have redownloaded all images multiple times, no luck, but the 11 previre OTA worked, so it is sorted, even though the underlying issue still persists.

MiLeX84 said:
Hello,
I spent the last two evenings trying to install the Android 11 preview in my old "spare" Pixel 2 XL, however I run into some issues.
I unlocked the bootloader, and tried to install the preview via adb sideload, this didn't work, error was some Signature Verification error.
I noticed my Pixel 2 XL was still on the October 2019 patch level, but it would not find an update using system update in settings.
So I downloaded the February 2020 factory image, tried to install is via adb sideload as well, same issue, Signature Verification error.
I tried the November 2019 OTA file, and was able to sideload and install it, phone booted and it finally started finding updates, so I updated to the latest Security patch level February 2020 using system updates.
I hopped this will solve my issues but still, the same Signature Verification error, with both 11 dev preview as well as the current full factory image.
I then moved on to using the flash-all.bat file. It would start, installing the bootloader and radio, but it is not able to install the image-taimen-qq1a.200205.002.zip, I'll always get this "error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space"
And this issue I cannot solve, well, both the validation issue and the "not enough space" issue.
By now I installed twrp recovery, not luck either, running into the same issues when trying to install the image.zip after pushing it to the phone.
"not enough space" Error
=================================
\platform-tools\taimen-qq1a.200205.002>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (36352 KB)...
OKAY [ 0.811s]
writing 'bootloader'...
OKAY [ 0.267s]
finished. total time: 1.080s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.352s]
writing 'radio'...
OKAY [ 0.800s]
finished. total time: 2.153s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
error: failed to load 'image-taimen-qq1a.200205.002.zip': Not enough space
Press any key to exit...
=================================
I also tried to follow some "manual" flashing guides, but those are all for Android 8, the file names and file system format has changed a lot, so that would not work either.
I believe I completely corrupted one of the two partitions doing that, luckily after a few failed boots the device booted from the other partition, for some reason that had thrown me back to December 2019 patch level, so I updated up to February 2020 using the standard system update feature, that fixed both partition slots A and B, so I am back to a normal functioning device with twrp installed. But I cannot solve this issue.
Would be glad if someone has a solution for this, or suggestions on how to tackle this.
[EDIT]: As I mentioned this is a spare test device, I am not worried about any data, the device was completely wiped anyway. Also it is the 128GB version.
Regards,
Alex
Click to expand...
Click to collapse
You have a spare Pixel 2 XL? ? I am still using duct tape to keep mine together. Lmao.