Database Info

[Q] Transformer TF101G unable to boot to recovery.

Hi all,
This may sound like an old problem but believe me, it's not. Let me explain.
I've rooted my Transformer TF101G (B90) last year sometime on 3.2.1. This works fine with no issues. I've flashed ClockworkMod after installing ROM Manager. This worked fine, I can boot normally, I can boot to recovery, no problem.
With the latest update available from ASUS via the web, I decided to to allow the annoying icon complaining about upgrading to download and run the upgrade. After downloading the update the Pad rebooted so if to install the new update. This landed me on the CWM with an error message that stated the verification (or something failed). After this, the Transformer wouldn't boot directly to Android, but ended up booting to the recovery partition every time. I had to use the fastboot option to "cold boot" into Android.
This was annoying, so I googled and found the solution on this forum to fix the issue with 5.5.0.4 that kept rebooting to recovery. This solved that problem and I was still able to boot to recovery whenever required.
I decided to update CWM to version 5.8.2.1 via ROM Manager. This seemed to work via ROM Manager, but restarting the transformer and going to recovery showed version 5.5.0.4 still. So I went back to ROM Manager and it showed that it was upgraded to 5.8.2.1. I decided to update this to ClockworkMod Touch by purchasing it via Google market to support the guys that do development on it. This claimed to install also. "Reboot into Recovery" from ROM Manager still showed version 5.5.0.4.
I was now very confused.
So I decided to downgrade CWM from the 5.8.2.1 version it stated was installed to version 5.8.1.9. This worked according to ROM Manager, but rebooting into recovery still showed 5.5.0.4. I mean, WTF!
In the meanwhile the freeken update icon on the task tray still complained about updating Android. I allowed it again to try and update. At the point it rebooted it left me stuck on the "EEE Pad" screen.
Booting up with Vol - and Power takes me to the screen that gives you an option to press Vol + to boot to RCK. Doing so the Pad freezes at "Booting Recovery Kernel Image". My PC then detects USB ADB interface but any adb commands respond with "error: device offline" or "error: device not found".
Booting up with Vol + and Power leaves the screen blank. My PC then detects an USB APX interface. Using "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img" only responds with "waiting for device".
The only way to boot my tablet at the moment is to use the "cold boot" option.
I would like to think I've tried everything out there and would appreciated anybody that could point me to maybe something else I could try.
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.

PeekNPoke said:
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
Click to expand...
Click to collapse
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.

PeekNPoke said:
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
Click to expand...
Click to collapse
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.

dragon_76 said:
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
Click to expand...
Click to collapse
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?

PeekNPoke said:
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
Click to expand...
Click to collapse
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?

recovery
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60

mmarco80 said:
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
Click to expand...
Click to collapse
I've solved The problem whit the gnufabio toolsto install recovery. Then Used "reboot to recovery"
Now i've manually installed official ics ....work fine!

Thomas Cardif said:
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
Click to expand...
Click to collapse
I tried this combined with the instructions on android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active because I'd never used nvflash before.
I managed to boot my TF101 in APX-mode, but as soon as I do any nvflash-command (e.g. nvflash --sync) the connection to the TF is lost:
C:\Program Files (x86)\nvflash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
After that I have to reboot the TF and shut it down again to be able to go into APX-mode again.
What do I miss? Mine is a B80.

hans_zelf said:
What do I miss? Mine is a B80.
Click to expand...
Click to collapse
You can't use nvflash with a B80

baseballfanz said:
You can't use nvflash with a B80
Click to expand...
Click to collapse
Oops. Fastbook doesn't seem to work either. Any ideas?

Yeah, I can't get fastboot to work either. I still have root access on the device. Is it not possible to flash the recovery from to root prompt on the device?

I tried using ADB. That way I actually can access the device and copy the recovery.img to the device using:
adb push recovery.img /data/local/recovery.img
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Works out until the last step. Then I get a message sh: flash_image: not found. Am I missing some files I have to flash first or have I forgotten something else?

Success!
Finally I succeeded!
Flashed recovery using Gnufabio's RecoveryInstaller. (After that the TF101 rebooted itself but still got stuck at the splashscreen. Did a cold Linux-boot).
Opened an ADB-session:
C:\Program Files\...\platform-tools>adb shell
/ # su
/ # echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes transferred in 0.039 secs (128 bytes/sec)​/ # exit
Click to expand...
Click to collapse
Finally, using ROM-manager I downgraded to CWM 5.5.0.4.
After that I was able to boot into recovery, but not from ROM-manager. I had to hold Vol- but at least I have a working recovery and was able to upgrade to ICS.
I'm not sure if the first step was really necessary but this is how I did it.

Hey hans_zelf,
Wow, I'm glad you got it going. I'll give it a go aswell and give feedback here. By the way, where did you get the recovery.img file you originally tried to flash?

Not really sure. I did a search within the forum and found several img's and zips.
But in the end I didn't need it because both RecoveryInstaller and ROM-manager download their own.

Ok,
I did the following:
adb shell
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
exit
Used ROM Manager v5.0.0.6, selected "Erase Recovery" in the settings menu, then flashed ClockworkMod 5.5.0.4, and powered down.
I then tried to start with Vol + and Power, just a blank screen but the 0955:7820 usb driver loaded. Then I used Vol - and Power, it booted to the Eee screen with the blue progress bar, after this is booted normally to the OS.
I powered it down again, and this time booted with Vol - and Power. Got to the screen that says use Vol + to load Recovery. I did that, and Bobs-Your-Uncle !!!!! IT WORKS !!!
Thanks hans_zelf, I'd still be stuck if it wasn't for you !
PS: I think the trick might have been to flash the 5.5.0.4 back, I'm not sure, and I'm not trying this again

You're welcome, but all I really did was combine some very helpfull tips from this forum
In the meantime I flashed my recovery to repacked Touch CWM v5.8.1.8 by Roach2010. Works like a charm. Not only touch support but also keyboard!

Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again

Yep. Mine was also barked after I upgraded CWM from ROM-Manager.

mike0122 said:
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Click to expand...
Click to collapse
me too, i've solved whit gnufabio recovery

[Q] ROM manager clockworkmod update bricked tf700

Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.

shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.

Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!

shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?

shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.

No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!

shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.

MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T

MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.

I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?

shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.

OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards

ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.

[q] help please!!!!!

I just got my new asus transformer tf300t-bl and wanted to root and install either twrp or cwm on it,I unlocked it and when i went to reboot it i hit the volume up on the RCK and now its stuck on RCK and it didnt boot into the usb like it says it will on the forums. Now when i reboot it,it says " key driver not found.. booting os android cardhu-user bootloader < 1.00 e> released by "us_epad-10.6.1.8-20130225" a03 starting Fastboot usb download protocol. does anyone know what i can do? i would greatly appreciate ANYONES HELP THAT KNOWS IF THEY'VE DONE THIS TO THEIRS AND IF THIS IS FIXABLE. I USE THIS FOR COLLEGE AND JUST PAID $ 400 and cant afford to buy another one. Somebody please tell me i havent screwed the pooch and that it still can be flashed into recovery and rooted. Thanks you guys. As i rooted and flashed my transform ultra perfectly because of you guys and used the megatron 6 and love it.

No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.

flashing recovery/ ref: help me
sevenalive said:
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
Click to expand...
Click to collapse
im a lil new to doing this so would you please give me a detailed list of exactly what to do. and what firmware do i need to download from asus. And can all of this be done using a mac? and how do i flash it all to my comp. or from it to the tablet.

It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856

need your help plz
Hazard17 said:
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
Click to expand...
Click to collapse
i did everything it stated to do and when i get to the last steps to root my tf300t, it says adb cannot run as root in production builds. Im at a loss as to what to do at all. IM a noob, and i follow each command on terminal perfectly and everything executes till the last or itll say permission denied. What do i do or am i doing wrong. Im following the instructions of post forum.xda-developers.com/showthread.php?t=1720980

Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?

re: help me
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware

420Misfit said:
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
Click to expand...
Click to collapse
well, I am using a win xp machine for fastboot. so I don't have the same issues. fastboot works fine, so that I use the normal fastboot process to flash the system and the recovery kernel.
I finally got it to work again by flashing the newest TWRP instead of CWM. It seems CWM does not yet work on the latest firmware.
I followed this guide for flashing TWRP with fastboot. This version actually also just asked me, if I want to root the device, I clicked yes and it was rooted. Perfect.
http://forum.xda-developers.com/showthread.php?t=2187982

philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
I am in EXACTLY the same boat as you. The only difference is that I flashed TWRP instead of CWM. I finally decided that it was time to root my tablet...got tired of the lag. IIRC I've gotten the "key driver not found.. booting OS" error message since doing the OTA update to 4.2 (I did this prior to rooting.) Everything SEEMS to be working okay, but this bugs the heck outta me, and I'm sure it can't be a good thing. Hoping somebody will chime in with a fix for this. I've searched and searched to no avail.

TF300T soft-bricked, please help!

Hi
I was trying to update from CM10 stable to the latest CM10.1 nightly. All went well until I got to reboot, when it got stuck on the "This device is unlocked / Asus logo" screen.
OK, I thought, I'll give this up as a bad job and restore my nandroid backup. But I got to the same point again, i.e. the stuck screen!
Now I'm starting to worry. I can boot into recovery OK, and also to the 3 icons menu. But I don't want to do anything else precipitous until I've got some good advice.
Thanks
Rob

If you can access fastboot, download stock Asus FW from their support site, extract it and flash blob into your system.

spenat said:
If you can access fastboot
Click to expand...
Click to collapse
I can get to "Starting Fastboot USB download protocol". PC recognises the device as "Asus Android Bootloader Interface" but nothing showing up with "fastboot devices" from a command box.

Well It worked for me plenty of times even when "fastboot devices" didn't showed up, so try just skipping this step. Also be sure to install Android SDK for drivers and official Asus drivers for it.
Also try different computers, fastboot just didn't worked on 4 computers I've tried, and the fifth worked even without installing drivers (both from Android SDK and official Asus drivers).

OK, thanks, that was a good tip to ignore fastboot devices. Was able to fastboot OK. But then...
I ran "fastboot -i 0x0B05 flash system blob", got an OKAY for sending but a failed for WRITING. Command box error was "FAILED <remote: <>", and the error message on the Asus was "Failed to process command flash:system error(0x170003)".

Well I don't know what's happened, but I thought I'd try and reflash my old CM10 ROM (which I'd fortunately left on the SD card) and this time it worked! No idea why it wouldn't work yesterday, but at least I now have a working device
Spenat, many thanks for your help.
Rob

You are welcome, glad to see another unbricked device

Asus tf300t(g) boot loop and stuck in TWRP wont mount, not recognized. - briked

hello
I have an asus tf300tg and I did update to 4.2.1 JB. bootloader was unlocked before the update. Tablets started ok then I put TWRP 2.5.0 but it seemed like something was not working well because I could not see external sd card when I tried to give you wipe from TWRP, but said faild. I rebooted the tablet I entered fastboot and in this mode shows, three icons. RTK, android, and wipe again. And naturally I did wipe once, then never turned on.
Now bootloader is unlocked and starts straight into TWRP.
At first my pc (win7 64bit) Recognize that "transformes" then I searched and found "Naked drivers 0.72" in the idea of ​​connecting the tablet in fastboot and write something-anything but I DON'T HAVE SUCCES.
I installed in various ways (asus adb, google adb) of naked driver but I could not communicate via fastboot. Maybe I don't chose the right way
Does anyone else have a procedure that can be repaired?
And that since the corect connection mode that allows me to write on tablet via fastboot ?
I saw that the problem occurs in many places and forums (like here: http://www.teamw.in/project/twrp2/97 Note the comments) but I dont found a solutions.
BR
Mihnea
I wait with many interes your sugestions.

Wrong forum, this needs to be in Q&A!
You need to find the 4.2.2 patched version of twrp and flash it via fastboot.

JoinTheRealms said:
Wrong forum, this needs to be in Q&A!
You need to find the 4.2.2 patched version of twrp and flash it via fastboot.
Click to expand...
Click to collapse
Thx for answer.. OK I WIILL WAIT until apear 4.2.2.pached version of twrp.
BR
MIhnea