Develop Bugs

failed to flash ob 10 and can only boot into recovery now

Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.

Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.

You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?

zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).

SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.

After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .

zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.

I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.

Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.

Did you manage to fix it? I have the same probem.

Flashing January security update (with TWRP and Magisk)

Just wondering how everyone else has applied the Jan security update (with TWRP and Magisk installed)?
FlashFire doesn't play nicely with my phone, so that's not an option. I've also tried uninstalling Magisk and flashing stock recovery boot.img before sideloading via ADB - no joy there either; I just receive the below error.
E:Failed to verify package compatibility (result 1): Runtime info and framework compatibility matrix are incompatible: AVB version 0.0 does not match framework matrix 1.0​
How has everyone else done it so far? I really would prefer to dirty flash and don't want to have to go through a full wipe again.

I just downloaded the Pixel 2 XL Jan update images, removed the "-w" from the flash-all.bat, and then ran it.
After, I just went back into download mode and flashed my boot image.
Then booted into TWRP with "fastboot boot twrp.img."
Last thing I did was flash TWRP (so it just stays on the device) and Magisk right after. In that order.

Ariac Konrel said:
I just downloaded the Pixel 2 XL Jan update images, removed the "-w" from the flash-all.bat, and then ran it.
After, I just went back into download mode and flashed my boot image.
Then booted into TWRP with "fastboot boot twrp.img."
Last thing I did was flash TWRP (so it just stays on the device) and Magisk right after. In that order.
Click to expand...
Click to collapse
Hmmm interesting. Does the -w switch preserve system apps and settings, or just user storage?

LeifAlbor said:
Hmmm interesting. Does the -w switch preserve system apps and settings, or just user storage?
Click to expand...
Click to collapse
-W is the part that wipes the phone.
Without it, nothing is wiped.

Since OTA isn't working with root, I tried using this method too. My Pixel 2 XL is unlocked, USB debugging is enabled, my computer is trusted and I'm in the bootloader.
I cd into the directory where my adb/fastboot stuff is located (I've also stored the factory image contents there). To check if everything's fine, I type in ./fastboot devices and my device is displayed.
But when I try to run ./flash-all.sh (Mac), nothing happens. No error message, just nothing.
Any ideas?

Use Flashfire: https://forum.xda-developers.com/pixel-2-xl/how-to/tutorial-flashing-ota-updates-unlocked-t3714744

eturk01 said:
Use Flashfire: https://forum.xda-developers.com/pixel-2-xl/how-to/tutorial-flashing-ota-updates-unlocked-t3714744
Click to expand...
Click to collapse
Did you read the thread you've linked? Even the OP of that thread is saying it is not working. He says it in the OP, and he says it in the last post. I wish we could use FF, but until it's updated it's going to be a minefield trying to use it.

v12xke said:
Did you read the thread you've linked? Even the OP of that thread is saying it is not working. He says it in the OP, and he says it in the last post. I wish we could use FF, but until it's updated it's going to be a minefield trying to use it.
Click to expand...
Click to collapse
darn!

I figured the Mac script is simply not working so I switched to my Windows PC and used the flash-all.bat. That did the trick.

XA2 - Broken screen after rebooting to slot b with TWRP

TL;DR: After rebooting to slot b with TWRP following a failed LineageOS flash, my XA2's screen is broken: showing only flashing vertical lines. This problem persists after an attempted reversion to stock firmware and software using Emma.
Apologies for the long post, but I'm at a total loss even after a lot of reading, and would appreciate any suggestions to turn this £180 paperweight back into a phone. I'm not trying to blame the LineageOS or TWRP teams here; any error is my own
What I've done to install TWRP on my XA2:
Installed the newest system updates (including an update to Android 9)
Unlocked the bootloader
Enabled developer options and USB debugging
Installed TWRP as per the instructions on TWRP's XA2 page (i.e.: not flashing TWRP using fastboot)
Happily rebooted into fully-functional TWRP
I then tried to flash LineageOS using TWRP:
Formatted data
Wiped system, cache, and internal storage partitions
Attempted to flash LineageOS (lineage-16.0-20190916-nightly-pioneer-signed.zip)
Flash failed with "ERROR: 1"; "Error applying Update: 18 (ErrorCode:: kdownloadPayloadPubKeyVerificationError)"
After some reading I found a post which suggested rebooting into slot b to fix this problem
Used TWRP to reboot into slot b
Screen is now glitching: flashing vertical lines on a black background; Sony splashscreen doesn't show during boot, nor does the unlocked bootloader screen
Here's what I've tried to fix it:
Flashed stock firmware, and then software, using Emma (which showed both operations as being successful)
Attempted to reboot to slot a using fastboot
The current state of the device:
Broken screen showing only flashing lines and colours (no splashscreens)
Boots to voice-assisted setup (!?) despite the broken screen. From what voice assist is saying, there seems to be a system there (e.g.: I can take screenshots)
Can be powered on and off, and put into flash mode (green LED)
Is still recognised by (and can be controlled using) fastboot
Thanks for reading. Any help is much appreciated

Update: I've tried using Newflash to flash stock firmware downloaded via Xperifirm.
The operation complete successfully, and the device boots (thankfully not to voice-assisted setup), but the screen is still broken, as described in my OP.
Does anyone have any suggestions?

Alright, on the off-chance that anyone comes here with the same problem (i.e.: XA2, broken screen), I seem to have fixed it by:
Powering off the device
Putting it into flash mode (green LED)
Fastbooting a special TWRP .img with "fastboot boot /path/to/twrp.img"
Rebooting the device normally
I have no idea whether my previous step of using Newflash is a dependency of this working, or whether it works on its own
Now my screen works again, but every attempt to flash LineageOS zips with TWRP fails as described in my OP:
Error applying update: 18 (ErrorCode: : kDownloadPayloadPubKeyVerificationError )
Updater process ended with ERROR: 1
Error installing zip file
This happens:
With several different nightly pioneer builds
With several different versions of TWRP
Trying to flash the .zip from SD card
Trying to adb push the .zip
Trying to flash from the fastboot booted .img
Trying to flash from different versions of the TWRP .zip, flashed from the fastboot booted .img
Despite having already flashed the older firmware version (50.1.A.13)
So I am again at a loss

Google Translate
did you see this guide?
https://forum.xda-developers.com/xperia-xa2/how-to/guide-flashing-lineageos-16-0-sony-xa2-t3944964

bane.twit said:
Google Translate
did you see this guide?
https://forum.xda-developers.com/xperia-xa2/how-to/guide-flashing-lineageos-16-0-sony-xa2-t3944964
Click to expand...
Click to collapse
Hi Bane, thanks for your reply
The guide you've linked is the guide I was attempting to follow. However, I get "Error applying update: 18 ..." at step 22.
Do you know how I can fix this error (perhaps bypassing verification)?

Google Translate
works with me with twrp-3.3.1-1-pioneer.img

bane.twit said:
Google Translate
works with me with twrp-3.3.1-1-pioneer.img
Click to expand...
Click to collapse
Interesting; I encountered the error using either twrp-3.3.1-1.img alone, or using twrp-3.3.1-1 to flash twrp-install-pioneer-3.2.2-0.zip
I've also tried various combinations of twrp.img and twrp.zip, but to no avail.
This was despite: flashing the Oreo firmware to both slots, formatting data, and wiping the system partitions.
Is there something I'm missing? Following the guide you kindly linked, everything works, until step 22 when I encounter this error and can't flash lineage.

Google Translate
- follow the guide instructions...
- via ADB, only twrp-3.3.1-1-pioneer.img ...
- adb sideload lineage ... the latest build ...

bane.twit said:
Google Translate
- follow the guide instructions...
- via ADB, only twrp-3.3.1-1-pioneer.img ...
- adb sideload lineage ... the latest build ...
Click to expand...
Click to collapse
Amongst other things I've tried:
-Flashing Oreo firmware (with Emma or Newflasher)
-Rebooting to fastboot (?); blue LED
-"fastboot boot ./twrp-3.3.1-1-pioneer.img" to boot TWRP
-Formatting data and wiping system partitions
-Trying to flash lineage, either from SD card or by sideloading
...but I always run into error 18, and flashing fails
Am I missing any steps here?

i can't help you

bane.twit said:
i can't help you
Click to expand...
Click to collapse
Ah OK, thanks for your help though
I'll try again in a week or so (I'm away from home for a while) and if I get it working I'll post the solution here.

Stuck in bootloader after attempting Oct update

Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!

JJT211 said:
Im stuck!!
I was rooted with Magisk on crosshatch QP1A.190711.020.C3, Sep 2019.
I just tried option #4 keep data and am getting the below (also attached pic) after getting to fastbootd screen during flash:
sending product FAILED (Write to device failed (Invalid argument))
When I try to reboot, it only boots to bootloader. I then tried wiping data same thing. I then tried reverting to the previous .C3 Sep 2019 firmare and again, same thing.
Im currently on slot B and as far as im aware, I havent done anything to slot A. However, in the bootloader screen at the bottom, I see:
Enter reason: no valid slot to boot
Before I try flashing anything else, Id like to try to boot to Slot A and see if I can at least have a usable phone for work tomorrow. Is it possible to boot to slot A from the bootloader screen?
If not, what else can I do?
Thanks in advance!!!!
Click to expand...
Click to collapse
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/

saxmydix said:
Did you try to use the latest SDK https://developer.android.com/studio/releases/platform-tools.html/
Click to expand...
Click to collapse
Yup, im on 29.0.4
So I found the command to switch to slot A
fastboot set_active a
Still stuck in bootloader mode.

Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.

OK I did the regular flash-all as you said and got error. At this point, the CLI says press "any key to exit"
I then exited, selected recovery - apply ADB update - opened CLI - adb devices (saw my serial #) and then entered "adb sideload image-crosshatch-qp1a.191005.007.zip"
And now after im getting:
verifying update package....
E: footer is wrong
Update package verification took .2 s (result 1)
E: signature verifcation failure
E: error: 21
Install from ADB completed with status 2
Installation aborted
EDIT: Im an idiot, I tried to sideload the factory image. Im sideloading the OTA now. Looks like its working. Standby

Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??

JJT211 said:
It worked AND I kept all my data! Suweeet! Damn you saved my ass, I wouldve been ****ed tomorrow at work. Thanks again!
How many hours did it take you to figure that out??
Click to expand...
Click to collapse
Tried several ways to get into recovery (fastboot.d) to sideload the ota after the i/o error... After a hour i got the trick (3. try to begin with flash-all.sh...). Somehow i always got trouble with system space when monthly update is downloaded automatically and can't get applied because i am rooted... Somehow it seems saver to install the full ota with sideload than the flash-all.sh procedure... Glad it also worked on your side.

Donric13 said:
Huuu... Had the same problem. You should try again flash.all from pc. You wait until the i/o error apears. Then you are in fastboot.d mode. From here you choose sideload ota from pc (or simular). Now you are able to execute the adb sideload command from your pc. Then wait and reboot. This saved my ass... Make sure you downloaded the full ota image before.
Click to expand...
Click to collapse
Which file do i sideload? I tried crosshatch-qp1a.191005.007-factory-2989a08d.zip. It failed with same error as guy above. I then tried to adb sideload image-crosshatch-qp1a.191005.007.zip and i got the same error? which file am I supposed to sideload?
EDIT:Never mind. I found the file. downloading and flashing hopefully it works!

Android Recovery - Cannot load Android system - Your data may be corrupt

Hi,
I had this happen about two weeks ago and I wiped my phone and flashed a fresh Android 10 (latest as of two weeks ago). I only restarted my phone because I was having issues with Snapchat so I restarted and it's popped back up again...
I don't want to have to wipe my phone again, I'd just finished logging everything in! I have Magisk and a fingerprint/pin added to my OS so the data in TWRP will be encrypted.
What do I do to fix this? I'd appreciate some help!
Thanks

Hyflex said:
Hi,
I had this happen about two weeks ago and I wiped my phone and flashed a fresh Android 10 (latest as of two weeks ago). I only restarted my phone because I was having issues with Snapchat so I restarted and it's popped back up again...
I don't want to have to wipe my phone again, I'd just finished logging everything in! I have Magisk and a fingerprint/pin added to my OS so the data in TWRP will be encrypted.
What do I do to fix this? I'd appreciate some help!
Thanks
Click to expand...
Click to collapse
If your fastbooting the factory image, try switching to your inactive slot, and fastboot the factory image again with the -w removed.

Badger50 said:
If your fastbooting the factory image, try switching to your inactive slot, and fastboot the factory image again with the -w removed.
Click to expand...
Click to collapse
Uhm... Could you provide a bit more detail? I have this tool https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226 installed to make stuff easier but I still don't know what you mean :/

Hyflex said:
Uhm... Could you provide a bit more detail? I have this tool https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226 installed to make stuff easier but I still don't know what you mean :/
Click to expand...
Click to collapse
The P2XL is a A/B dual partition device. If you fastboot the factory image with the -w intact within the flash-all.bat file, it will flash to both partition slots. When you remove the -w from the flash-all.bat file, it will only flash to one slot/partition and does not wipe your data. I personally don't use tool kits since I like a more hands on approach. Also, are your platform-tools up to date? If not, that can cause headaches as well.

Badger50 said:
The P2XL is a A/B dual partition device. If you fastboot the factory image with the -w intact within the flash-all.bat file, it will flash to both partition slots. When you remove the -w from the flash-all.bat file, it will only flash to one slot/partition and does not wipe your data. I personally don't use tool kits since I like a more hands on approach. Also, are your platform-tools up to date? If not, that can cause headaches as well.
Click to expand...
Click to collapse
So...
Extract the factory image, edit flash-all.bat and remove the -w, run flash-all.bat?
Yep my platform-tools are up to date!

Hyflex said:
So...
Extract the factory image, edit flash-all.bat and remove the -w, run flash-all.bat?
Yep my platform-tools are up to date!
Click to expand...
Click to collapse
Exactly. Just make sure you have all the extracted factory image files in your platform-tools folder. If you have to change slots, the command is......fastboot --set-active=a or b. Depending of course on which slot your currently on.
If you don't know which slot your on, run...fastboot getvar all. :good:

Badger50 said:
Exactly. Just make sure you have all the extracted factory image files in your platform-tools folder. If you have to change slots, the command is......fastboot --set-active=a or b. Depending of course on which slot your currently on.
If you don't know which slot your on, run...fastboot getvar all. :good:
Click to expand...
Click to collapse
So current slot is b? https://i.imgur.com/85l7Y6v.png
Why do I need to have the image files in platform-tools? I have adb setup where I can use it anywhere.
I should do
Code:
fastboot --set-active=a
and then just run the flash-all.bat which I've modified to look like https://i.imgur.com/yGPkqqY.png (removed -w)
I must admit, I don't understand why we have to change from a to b or vice versa... I didn't do that last week when I tried to fix this... I just removed the -w and ran the file which didn't work.

Hyflex said:
So current slot is b? https://i.imgur.com/85l7Y6v.png
Why do I need to have the image files in platform-tools? I have adb setup where I can use it anywhere.
I should do and then just run the flash-all.bat which I've modified to look like https://i.imgur.com/yGPkqqY.png (removed -w)
I must admit, I don't understand why we have to change from a to b or vice versa... I didn't do that last week when I tried to fix this... I just removed the -w and ran the file which didn't work.
Click to expand...
Click to collapse
I don't understand everything all the time either. I just know what I have done in the past to fix this issue. It may not work either if you have corrupted internal files or maybe a hardware issue.

Badger50 said:
I don't understand everything all the time either. I just know what I have done in the past to fix this issue. It may not work either if you have corrupted internal files or maybe a hardware issue.
Click to expand...
Click to collapse
I tried to switch slots and it threw up:
Code:
> fastboot: error: Device does not support slots
My platform tools are from last month

Hyflex said:
I tried to switch slots and it threw up:
My platform tools are from last month
Click to expand...
Click to collapse
Then I would start from scratch. Delete your current platform-tools, and download it again. Also, sometimes your USB cables and ports can cause glitches on the P2XL.....even if they've worked in the past, I've had it happen to me.

Badger50 said:
Then I would start from scratch. Delete your current platform-tools, and download it again. Also, sometimes your USB cables and ports can cause glitches on the P2XL.....even if they've worked in the past, I've had it happen to me.
Click to expand...
Click to collapse
Interesting, I switched cable and it allowed me to flash it... I tried and it still shows the same message so I guess I have to do the full wipe one again.
Does anyone know of any other solutions before i wipe the phone.

Hyflex said:
Interesting, I switched cable and it allowed me to flash it... I tried and it still shows the same message so I guess I have to do the full wipe one again.
Does anyone know of any other solutions before i wipe the phone.
Click to expand...
Click to collapse
So... I got it working, I also broke it again and then got it working.
1. I switched from slot b to a
2. Re-flashed a factory firmware without -w
3. Tried to boot... still broken
4. I switched from slot a back to slot b
5. Re-flashed a factory firmware without -w
6. Tried to boot... still broken
7. Booted into TWRP and then into system
8. Tried to boot... still broken
9. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
10. Tried to boot... it worked
11. Flashed Magisk
12. Tried to boot... it's back to being broken again
13. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
14. Tried to boot... still broken
15. I switched from slot b to slot a
16. Re-flashed a factory firmware without -w
17. Tried to boot... still broken
18. Flashed MagiskUninstaller.zip
19. Tried to boot... it worked
20. Flashed Magisk
20. Tried to boot... it worked
So I guess it was something from Magisk that broke it... one of the modules.

Hyflex said:
So... I got it working, I also broke it again and then got it working.
1. I switched from slot b to a
2. Re-flashed a factory firmware without -w
3. Tried to boot... still broken
4. I switched from slot a back to slot b
5. Re-flashed a factory firmware without -w
6. Tried to boot... still broken
7. Booted into TWRP and then into system
8. Tried to boot... still broken
9. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
10. Tried to boot... it worked
11. Flashed Magisk
12. Tried to boot... it's back to being broken again
13. Flashed TWRP via Toolkit (installs to both slots with a recovery script)
14. Tried to boot... still broken
15. I switched from slot b to slot a
16. Re-flashed a factory firmware without -w
17. Tried to boot... still broken
18. Flashed MagiskUninstaller.zip
19. Tried to boot... it worked
20. Flashed Magisk
20. Tried to boot... it worked
So I guess it was something from Magisk that broke it... one of the modules.
Click to expand...
Click to collapse
Well done my friend. Goes to show that persistence pays off! :good::good:

Another method I do when I run across issue in the past.
I would lock and unlock my bootloader a few times (of course start the devices after each lock and unlock), which erase everything, then my phone will let me flash Google factory imagine..

hi, I tried to install twrp-3.3.0-0 and 3.2.3-1 but neither of two can mount SYSTEM and VENDOR partitionjs, im back to stock Android 10... some help would be appreciated guys how did you installed twrp on Android 10 ...?

estemanito said:
hi, I tried to install twrp-3.3.0-0 and 3.2.3-1 but neither of two can mount SYSTEM and VENDOR partitionjs, im back to stock Android 10... some help would be appreciated guys how did you installed twrp on Android 10 ...?
Click to expand...
Click to collapse
You won't be able to mount system/vendor until twrp updates the recovery to accommodate A10 and the new logical partitions that google implemented. If they choose to do so at all. However, the 330-0 version will still flash zips despite throwing vendor/system errors. The way installed twrp is....have a copy of the twrp 330-0 image, not zip, on your phones internal storage. Then fastboot into twrp. Once there, select install, then select image. Go to where your twrp.img file is located, and select it. You will then get a prompt to which partition you want to flash it to...select recovery ramdisk, and flash it. And that's it :good:

Badger50 said:
You won't be able to mount system/vendor until twrp updates the recovery to accommodate A10 and the new logical partitions that google implemented. If they choose to do so at all. However, the 330-0 version will still flash zips despite throwing vendor/system errors. The way installed twrp is....have a copy of the twrp 330-0 image, not zip, on your phones internal storage. Then fastboot into twrp. Once there, select install, then select image. Go to where your twrp.img file is located, and select it. You will then get a prompt to which partition you want to flash it to...select recovery ramdisk, and flash it. And that's it :good:
Click to expand...
Click to collapse
I cant install from the recovery cause when i try to boot in recovery mode i get a black screen with a little dead droid then a "no command" message. The way i installed before is from fastboot with the .img file

estemanito said:
I cant install from the recovery cause when i try to boot in recovery mode i get a black screen with a little dead ath droid then a "no command" message. The way i installed before is from fastboot with the .img file
Click to expand...
Click to collapse
You have to fastboot the twrp.img file first using your pc.

Badger50 said:
You have to fastboot the twrp.img file first using your pc.
Click to expand...
Click to collapse
ok so i flash first from the pc then i boot in trwp then i re-flash trwp.img from the trwp menu (not the trwp.zip) thats it...?

estemanito said:
ok so i flash first from the pc then i boot in trwp then i re-flash trwp.img from the trwp menu (not the trwp.zip) thats it...,
Click to expand...
Click to collapse
Bingo! You got it :good::laugh: