i rooted my tf300 when on stock ics. i used the method that doesnt require bootloader unlocking.
couple of days later the jb ota came along, so installed that, and restored root with voodoo
i want to install a custom rom, but i can't get the recovery working. the tablet boots fine, and the behaviour is the same now im on jb, as it was when on ics
basically, i power on + vol down, then select the rck icon, and it loads to an android with a blue loading animation, then changes to a 'dead' android with a red exclamation just above.
the tablet still boots fine otherwise.
question is, do i have to unlock the bootloader before i can install/run the recovery, or is there a way i can do it without unlocking?
edit: i tried also flashing via fastboot (tried first with terminal, when trying twrp for ics) and this is what it comes back with, same thing for cwm and twrp:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery CWM-Touch.blob
sending 'recovery' (6370 KB)...
OKAY [ 2.646s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 5.901s
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)...
OKAY [ 3.538s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 6.779s
You have to unlock to install a custom rom. Think it over and do some more reading. You could build a house since there is no shortage of bricks. :banghead:
Still Charged Up
do you think there's any chance of being able to do this without unlocking in the future?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Nope. One requires the other. Simply put - ASUS does not want to deal with true user-created bricks. That's why they make it optional.
Still Charged Up
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Seahorse said:
I have an unlocked, rooted 300T with JB which I flashed to 10.4.2.13 using the existing installation of TWRP which has now disappeared when booting+Vol Down. I do not seem to be able to re-install TWRP using fast boot as I get this message.
Code:
C:\Users\Mike\Desktop\Fastboot>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)... OKAY [ 2.058s]
writing 'recovery'... FAILED (status read failed (Too many links))
finished. total time: 2.061s
I have searched extensively and cannot find a similar issue, but without TWRP I cannot then flash a custom ROM...:crying:
Click to expand...
Click to collapse
Are you installing the jb compatible twrp? what happens when you try and boot recovery?
Sent from my SGH-I727 using xda app-developers app
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Seahorse said:
I have downloaded the 2.2.2 jb blob from here. When I boot into recovery & select RCK I get an android on his back with an exclamation mark in his stomach.
Click to expand...
Click to collapse
When you used twrp to flash stock it includes recovery which overwrites twrp. Go back to the instructions to fastboot twrp, do so and you should be good.
Good Luck!
Try a new download of twrp!
Reboot your pc, only plugin your asus and no other device, retry fastboot.
Forgot, if on dock remove from dock reboot pc and asus and try again.
Clearing cache maybe? Just a shot in the dark, never seen this one. I can tell you I flashed ota v13 and it blew away my recovery but I was able to get it back easily.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
After following numerous google links - too many links fastboot, I found one resolution. Another device used on pc and usb drivers installed since last use of unit giving links error. Resolution was remove offending drivers, reboot pc and profit.
Good Luck!
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
Click to expand...
Click to collapse
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Blew away cache, used fastboot again on twrp.blob and got same install fail error message. However, on power on + vol down RCK now works with TWRP, which is kind of odd, but there you go. Thanks for all the suggestions...
glad you got it fixed
SITH16 said:
I'm having a bit of a different problem. I have flashed twrp 2.2.2 several times and each time it says okay but it isn't updating it. I still have 2.2.1.5 installed.
Code I'm using...
Quote:
adb reboot bootloader
fastboot -i 0x0B05 flash recovery tf300t-jb.blob
It goes through the install and says OKAY at the end yet it doesn't actually update the recovery blob.
Click to expand...
Click to collapse
Three things come to mind.
1. Try to flash as twrp directions show; without adb reboot bootloader.
2. Verify you are trying to flash the proper version for your bootloader; ics or jb.
3. If the above two items fail redownload proper version for your boot loader and try again.
Note: The twrp page also shows how to flash with adb!
Good Luck!
Terminal Emulator is an easier way to flash TWRP imo. But hey.
babymatteo said:
Terminal Emulator is an easier way to flash TWRP imo. But hey.
Click to expand...
Click to collapse
Terminal method worked. Thanks everyone for helping me out.
TWRP Install Fail
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
this is the tf300t forum. Make sure you are installing a tf700t TWRP
cmendonc2 said:
this is the tf300t forum. Make sure you are installing a tf700t TWRP
Click to expand...
Click to collapse
I noticed that after I hit reply. I was using all of the correct TF700t TWRP and whatnot. I found this in a google search because it was similar to my issue. It turned out that even though I thought I had unlocked my device, it did not unlock. I fixed that and now I am all set.
BadWolf428 said:
Hello,
I am having similar issues, but mine results in the following:
sending 'recovery' (6292 KB)... OKAY [ 2.706s]
writing 'recovery' ... FAILED (remote: (InvalidState))
I have unlocked my TF700T and I have followed all of the instructions I have seen posted everywhere. This is where I am stuck.
Any advice?
Click to expand...
Click to collapse
The warning invalid state normally applies to the bootloader being locked make sure your bootloader is unlocked.
Sent from my Nexus 5 using Tapatalk
Hi, am looking for the stock recovery file/zip p[ease.
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
Thanks.
_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
3c said:
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
Click to expand...
Click to collapse
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
_that said:
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
Click to expand...
Click to collapse
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
3c said:
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
Click to expand...
Click to collapse
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
buhohitr said:
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
Click to expand...
Click to collapse
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
3c said:
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
Click to expand...
Click to collapse
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
buhohitr said:
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
Click to expand...
Click to collapse
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
3c said:
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
Click to expand...
Click to collapse
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
buhohitr said:
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
Click to expand...
Click to collapse
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
3c said:
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
Click to expand...
Click to collapse
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
3c said:
Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
Click to expand...
Click to collapse
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
buhohitr said:
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
Click to expand...
Click to collapse
Actually how do you flash bootloader? I did this: fastboot -i 0x0B05 flash bootloader loader.blob ?
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish! How's that for a crappy software! I wish I never tried to update to JB!
_that said:
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
Click to expand...
Click to collapse
No ADB, just the name of the tablet appears in Device Manager, sort of the SD card access, but no actual access. I updated the driver manually and was proposed some MTP device. No adb or fastboot when this is available.
Here is the input from another thread: I copy it because I believe the information is very important and identify another way to brick the TF700:
Pretoriano80 said:
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Click to expand...
Click to collapse
That's exactly what's happening! I can go in fastboot, but it doesn't flash anything! Though it erase any partition you wish! How smart is that? So I have one thing to say to locked owner: never go in fastboot, ever, it's useless and can actually brick your tablet!!!
I bricked the tablet on my own sure enough, but without this ridiculous fastboot I wouldn't have been able to mess up the tablet in the first place! Sorry for those who love their tablet and Asus, but I find their strategy ridiculous. Except if it's main goal is to make money on RMA.
Thanks Asus for this nice brick!
3c said:
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish!
Click to expand...
Click to collapse
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
_that said:
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
Click to expand...
Click to collapse
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
3c said:
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
Click to expand...
Click to collapse
I don't really know - all I know is:
- TF700's fastboot implementation only supports blobs, no raw partition images
- blobs are usually always written to the staging partition first, then the contained partition images are flashed to the correct partition(s) by the bootloader
I've seen both variants of the fastboot command, so maybe the target partition doesn't matter when sending blobs. I'd try staging first.
Hello,
I have a problem with my Asus TF300T to root.
Today I get my TF300T (Firmware 10.4.2.20)
What I have done.
1. UnLock_Device_App_V7.apk istalled Device is UnLocked now.
2. Start the Tablet in fastboot usb-mode and
Code:
E:\Fastboot>fastboot -i 0x0B05 flash recovery boot.blob
sending 'recovery' (5248 KB)... OKAY [ 1.047s]
writing 'recovery'... OKAY [ 1.047s]
finished. total time: 2.094s
The boot.blob from http://forum.xda-developers.com/showthread.php?t=2105949 i download ◦Root_10.4.2.20_WW.zip
3.
Code:
E:\Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.000s
4. After the restart I could not access the internal storage only after the USB debugging was deaktivirt. Copy the Root_10.4.2.20_WW.zip to internal storage.
5. Holt power and vol.down the TF300 reboot... and the screen wihs 4 icon will show...
And now? i kann not select a .zip file
Sorry for ban eiglisch und wor my stupid question.
Hold power/volume down, Press up volume on rck which will take you to recovery you flashed once in recovery install zip file. Mine took a few times before root was enabled
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Hello and thanks for the answer.
I flash boot.blob from Root_10.4.2.20_WW.zip (fastboot -i 0x0B05 flash recovery boot.blob) bot the boot.blob hats not TWRP recovery...
by select rck icon show my tablet a dead andriod !...
i install openrecovery-twrp-2.3.3.0-tf300t-JB.blob and now i kan use RCK Icon.
Oh my apologies read quickly and replied didn't realise that wasn't a recovery. Hope you managed to flash the zip file now you have twrp recovery
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Im trying to install KatKiss ROM via recovery.
Its just that my recovery is a older version of TWRP and i have no boot on the TABLET..
Is there any way i can update TWRP to a new version in the twrp recovery? >_>
Ive also tried a few other older roms, but seems like all i get is "Error executing updater binary.....:"
elandriel said:
Im trying to install KatKiss ROM via recovery.
Its just that my recovery is a older version of TWRP and i have no boot on the TABLET..
Is there any way i can update TWRP to a new version in the twrp recovery? >_>
Ive also tried a few other older roms, but seems like all i get is "Error executing updater binary.....:"
Click to expand...
Click to collapse
We need your bootloader version and recovery version ...
You can find the bootloader on the fastboot/bootloader menu ....
It will start with something like "WW" "US" "TN"
Thx Josh
lj50036 said:
We need your bootloader version and recovery version ...
You can find the bootloader on the fastboot/bootloader menu ....
It will start with something like "WW" "US" "TN"
Thx Josh
Click to expand...
Click to collapse
BOOTLOADER : WW_epad-10.6.1.27.5-20130902
TWRP: v2.5.0.0
I just tried :
ADB commands in TWRP works.
fastboot -i 0x0b05 flash staging twrp.img
(having twrp.img on in c:\ together with the fastboot adb executables)
--- 'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Also tried:
fastboot flash recovery *.img
sending 'recovery' (4520 KB)...
OKAY [ 2.227s]
writing 'recovery' ...
OKAY [ 2.444s ]
finished. total time: 4.672s
-- then nothing happends when its restarted ^^
fastboot devices:
015d262e0d480e11 fastboot
elandriel said:
BOOTLOADER : WW_epad-10.6.1.27.5-20130902
TWRP: v2.5.0.0
I just tried :
ADB commands in TWRP works.
fastboot -i 0x0b05 flash staging twrp.img
(having twrp.img on in c:\ together with the fastboot adb executables)
--- 'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Also tried:
fastboot flash recovery *.img
sending 'recovery' (4520 KB)...
OKAY [ 2.227s]
writing 'recovery' ...
OKAY [ 2.444s ]
finished. total time: 4.672s
-- then nothing happends when its restarted ^^
fastboot devices:
015d262e0d480e11 fastboot
Click to expand...
Click to collapse
Yes you need to update TWRP to 2.8.x.x
You can find a thread its my kang version of TWRP .....
Once you have flashed TWRP from fastboot run this command ...
Code:
fastboot reboot-bootloader
Once back in bootloader go directly into recovery ....
Thx Josh
I found your version and that worked..
So atm i got your TWRP version
Ty so much