Database Info

[Q] Fastboot Linux

Ive been trying to get TWRP loaded on to my TF300T on 4.2.1 using this guide but on the fastboot its stuck on waiting for device. The device is recognised in the Terminal but have no luck flashing the recovery. Is there any other methods for flashing a recovery I can use on linux or advice.
Im running Xubuntu 13.04

mackay508 said:
Ive been trying to get TWRP loaded on to my TF300T on 4.2.1 using this guide but on the fastboot its stuck on waiting for device. The device is recognised in the Terminal but have no luck flashing the recovery. Is there any other methods for flashing a recovery I can use on linux or advice.
Im running Xubuntu 13.04
Click to expand...
Click to collapse
Is your OS 32 or 64-bit? If it's 64, you may need to have both ia32-libs and ia32-libs-dev installed for fastboot to work properly. Also, did you get the android-tools packages from the repos? I'm not sure about the *buntus, but on Debian, they're in the unstable repos. Make sure you have the newest versions (trust me; it matters).
If you want to do it via ADB, you could do this:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
Make sure the recovery image is on your internal storage if you do it that way.
I recommend trying to get fastboot working, and use ADB as a last resort.

Its 32-bit, I used fastboot for my N4 so unsure why its not working just now. I tried the method you said but think i may ahve done it wrong it completed the operation but got the Android on its back with the red triangle :/
First time i got :-
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
12896+0 records in
12896+0 records out
6602752 bytes transferred in 5.185 secs (1273433 bytes/sec)
Then after that i got :-
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
ry.img’: No such file or directory <
/system/bin/sh: dd:: not found
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
1|[email protected]:/ $

mackay508 said:
Its 32-bit, I used fastboot for my N4 so unsure why its not working just now. I tried the method you said but think i may ahve done it wrong it completed the operation but got the Android on its back with the red triangle :/
First time i got :-
1|[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
12896+0 records in
12896+0 records out
6602752 bytes transferred in 5.185 secs (1273433 bytes/sec)
Then after that i got :-
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
ry.img’: No such file or directory <
/system/bin/sh: dd:: not found
127|[email protected]:/ $ dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
1|[email protected]:/ $
Click to expand...
Click to collapse
Stupid question probably, but is your tablet unlocked?
Also, for the second one, you weren't logged in as root. You need to be root to write the image.
Linux 101:
- If you see a dollar sign ($) in the terminal, you're a normal, unprivileged user
- If it's a pound sign (#), you're root.
Also, like I said before, the version of Fastboot matters. Way back in August, I soft-bricked my tablet, and fastboot gave me the same problem it's giving you, even though I had used fastboot on my tablet before that. Months later, I found the fastboot in the Debian repos. I'm not sure what the difference was between the versions, but the new one from the repos worked perfectly, and I was able to get my tablet working again.

EndlessDissent said:
Stupid question probably, but is your tablet unlocked?
Also, for the second one, you weren't logged in as root. You need to be root to write the image.
Linux 101:
- If you see a dollar sign ($) in the terminal, you're a normal, unprivileged user
- If it's a pound sign (#), you're root.
Also, like I said before, the version of Fastboot matters. Way back in August, I soft-bricked my tablet, and fastboot gave me the same problem it's giving you, even though I had used fastboot on my tablet before that. Months later, I found the fastboot in the Debian repos. I'm not sure what the difference was between the versions, but the new one from the repos worked perfectly, and I was able to get my tablet working again.
Click to expand...
Click to collapse
Yeah I unlocked it using the unlocker app and have the this device is unlocked at the boot screen. Forgot the su part :/ what i get for using the up button haha. Yeah it came up with grant superuser access on my tablet, I deleted and reinstalled fastboot the other day to see if it would help but it didnt. Might have to wait until i can access a Windows laptop :/

Sorry I couldn't help. Those are the most common problems/solutions I've seen and personally experienced. And I have no idea why dd didn't work in ADB Shell. I would check the recovery image and try again. Check out adb --help to see if there are any other options available. I'm not overly familiar with ADB.
You could also flash the recovery while booted into Android using Terminal Emulator. That's how I usually flash recoveries. Just use the dd method from the ADB Shell instructions. Just skip the first command, starting ADB Shell, and start at su.
Oh, and I completely missed it earlier, but make sure that the recovery you're using ends in -42.img or - 42.blob. If you use one with -JB, you could brick your tablet. I don't know why the guy giving instructions in your link said to use -JB, but there have literally been dozens of bricked tablet threads here because people flashed a -JB recovery on a 4.2 bootloader. -JB recoveries should only be used with the 4.1 bootloader.

EndlessDissent said:
Sorry I couldn't help. Those are the most common problems/solutions I've seen and personally experienced. And I have no idea why dd didn't work in ADB Shell. I would check the recovery image and try again. Check out adb --help to see if there are any other options available. I'm not overly familiar with ADB.
You could also flash the recovery while booted into Android using Terminal Emulator. That's how I usually flash recoveries. Just use the dd method from the ADB Shell instructions. Just skip the first command, starting ADB Shell, and start at su.
Oh, and I completely missed it earlier, but make sure that the recovery you're using ends in -42.img or - 42.blob. If you use one with -JB, you could brick your tablet. I don't know why the guy giving instructions in your link said to use -JB, but there have literally been dozens of bricked tablet threads here because people flashed a -JB recovery on a 4.2 bootloader. -JB recoveries should only be used with the 4.1 bootloader.
Click to expand...
Click to collapse
Thanks for the help anyway, yeah just glad i read up on the recoveries before hand incase it worked and i got bricked. Ill try using the terminal and see if that works

[Q] CWM Recovery loading at startup and infinite boot animation issue

Hello,
I have nerve-breaking issue with CWM Recovery wich loads up every time i turn on my tablet. So if i wish to restart or to go to CWM i have to hold volume down button to get to bootloader and then select Android to get back to CWM.
So my first question is how do i resolve this problem with constant booting into CWM Recovery? so it would go to recovery only when i select reboot to recovery option in CWM
My next issue is that i have tried to install Ubuntu Touch for TF101 (from ubuntu touch wiki). And in installation guide it says you have to download cm-10.1-20130404-UNOFFICIAL-tf101.zip, and then quantal-preinstalled-phablet-armhf.zip. The fist zip i got successfully but the second link did not exist, so i checked their repository and found similar zip named saucy-preinstalled-phablet-armhf.zip (i tought it's a newer version) well, then i made data wipe and installed both as stated in guide, i also deleted cache and now when i try to boot my tablet i get to blue spinning CWM logo and it stays there for eternity.
So my second question is how to put some other rom on SD card so i can install another rom? or what i have to do to make Ubuntu Touch work?
My third thing that i noticed (for me it seems wrong) is that with every data wipe it makes new 0/ folder and it keeps everything before wipe in it. I made couple of data wipes and now my data structure looks something like this:
Code:
0/
0/
0/
0/
ASUS/
Alarms/
Albums/
AndroZip/
...other folders (apps and data from stock rom)
Alarms/
Android/
Autodesk/
DCIM/
...other folders (probably from first wipe)
Alarms/
Android/
DCIM/
Downloads/
...other folders (probably from second or third wipe)
legacy/
obb/
obb/
So my third question is if this is the correct data structure because it seems wrong for me? And how to resolve that issue?
My un-educated guess is that all three problems are connected, but my android experience and knowdlege is far to small to have a clue how to begin resolving this twisted problem.
I did some researching and as far it goes with second question i think i have soft-bricked tablet (maybe there is still hope?). So i would like to make it back to original rom or 4.2 jelly bean as i had till now without CWM Recovery issue, if possible of course
(Using ClockworkMod Recovery v5.8.3.4 now, and i think at beginning there was ROM Manager used, i bought used tablet)
Please help, thx

The issues are somewhat intertwined, and run back to using CWM 5.8.X.X
The first thing you MUST do is stop the CWM bootloop or you will not be able to install any other ROM or recovery.
If you can boot to a ROM, run a terminal window with SU permissions. If you cannot boot to a ROM, you will need to run from an ADB Shell from a computer when booted to recovery:
Code:
echo boot | dd of/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally and your bootloop to CWM should be fixed.
Next, I HIGHLY HIGHLY recommend upgrading to TWRP 2.3.2.3 or higher. The /0/0/0/0 issue has to do with the new directory structure of Android 4.2 for multi-users. CWM 5.8.X.X cannot handle multi-users properly.
TWRP 2.3.2.3 can be updated using the GooManager app (tap the menu key in the top right and choose Install OpenRecovery Script).
IMO, TWRP is far superior to CWM as it has a file manager and terminal emulator.
I am running SidneyK's TWRP 2.6.3.0. He has a zip that can be flashed from CWM to update, however you have to have the boot loop issue resolved or it will not flash.

Ok, as you said i cannot boot to ROM so i tried with ADB Shell but it says
error: device not found
I have device connected on keyboard dock and cable from dock to pc
Any advices how to reslove that issue? Am i missing some drivers?
In device manager i can see that there is a Transformer device with yellow exclamation. I tried to install drivers from asus webpage but it wont install.
Should i get copy of live linux and try from there?
EDIT:
I got the connection working with ADB Shell but i got this response from code you provided
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee image there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?

boonz said:
Maybe i should type?
Code:
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
Damn, yeah, it should be ...of=dev/block/...
D'OH!

I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx

boonz said:
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
Click to expand...
Click to collapse
There are a few ways.
You can use ADB to push the TWRP.zip from sidneyk's thread in the dev section, install that from the internal storage.
If you have a TF101 (non 3G) you can use one of my repacked EasyFlasher in APX mode to push TWRP: http://forum.xda-developers.com/showpost.php?p=43986513
Another option is to use the .blob file (extracted from the zip) and use adb to install when in CWM recovery.
Push the blob file to the /sdcard/ (called twrp.blob for this example)
Use adb shell and execute:
Code:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (you need to see the progress indicator complete before rebooting to recovery). What I do is just hold the power button for 10 seconds, once the progress bar completes and it flashes black, hold VOL DOWN until you see the RCK message then tap VOL UP to boot to recovery. With any luck you will see TWRP.

Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard

boonz said:
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
Click to expand...
Click to collapse
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.

frederuco said:
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
Click to expand...
Click to collapse
Ok superb, i have TWRP it says v2.3.2.3
How do i perform something like format or delete everything (so there will be no 0/0/0/ folders or whatsoever) and make my tablet usefull again. I would like to run jellybean again because i'm pretty used to it and delete that Ubunto Touch mess i made. Maybe little help here, so i don't mess anything up?
Thx

Go to the Wipe section.
Wipe the system, davlik and also the cache.
Choose the FORMAT DATA option to completely wipe the /data/ partition (this deletes everything in the /data/media/ aka /sdcard/ directory)
Then I would reboot back to recovery (suggested after a format data) and then install your ROM, applicable GAPPS and kernel if necessary.

[Q] Stuck in TWRP 2.1.1 with no Sideloader

Hi All,
I wanted to change the stock ROM on my tf700t so I downgraded to V10.6.1.14.8 from V10.6.1.14.10 installed unlocker and installed GooManager. Now when GooManager went to InstallOpenRecovery Script it got stuck on the 'download has started' screen. I looked for alternative options and found out that you could install via the ADT/SDK options using latest twrp.blob file. So I went to the twrp site and got latest blob file but rather stupidly they list the oldest at the top and the newest at the bottom?. So I ended up installing the 2.1.1 version using adb terminal via these instructions:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
Now I did this but I didn't put the Roms that I wanted into the default SD Card first and this version of TWRP doesn't support microSD or ADB Sideload. It now just keeps rebooting into TWRP and when I connect to PC in TWRP the PC just recognizes the driver as Transformer but none of the ASUS drivers work. I have no idea where to go from here, backup doesn't seem to work....?
I've been looking around but seems perhaps I've hit a unique issue.
Any help on how I can progress from here to get the latest version of TWRP or indeed any decent ROM - I was originally going for cm-10.2-20131112-NIGHTLY-tf700t.zip and googleapps.
Help would be most appreciated.
Thanks,
Kavster

also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide - cannot get boot recovery now just boots into TWRP...
android.sc/update-asus-transformer-pad-tf700t-to-cm-10-2-android-4-3-jelly-bean-rom
am I screwed..???

Kavster76 said:
also worth mentioning i did a wipe data via the switch on with volume down and the 3rd icon of wipe as I was following this guide
Click to expand...
Click to collapse
This option causes the bootloader to force starting the recovery until the wipe is done. The problem: The ancient recovery that you flashed cannot access the eMMC due to bootloader incompatibilities.
So your only chance to unbrick now is to get adb shell access working, then try "adb reboot bootloader" and see if you can get back to the bootloader menu. Then choose Android and run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1

The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.

Kavster76 said:
The problem is that the TF700T is only recognized just as 'transformer' in Windows 7 device manager and I don't have a driver that will allow me to see the device via adb. Any ideas on how I can get the right driver so that I can see it again in the adb devices:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Then I can the adb shell.....
Thanks.
Click to expand...
Click to collapse
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502

flumpster said:
Have you tried the Universal Naked Drivers?
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.? Can I also install new version of TWRP..??
Cheers...

Kavster76 said:
Yes the Naked Drivers worked and device is now recognised. But it wont boot back into bootloader using the "adb reboot bootloader". It reboots but goes back to TWRP so how can I rebuild the bootloader from here.?
Click to expand...
Click to collapse
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974

_that said:
Hmmm, OK, try this:
Download and extract this to your computer:
http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132
then run:
Code:
adb push bootit.ko /
adb shell insmod /bootit.ko
If you are lucky, this reboots into the bootloader menu from which you can use fastboot to flash a working recovery. At least it helped this user: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?

Kavster76 said:
Excellent stuff !!!! - that worked I now am back to the original bootloader screen. Now I have RCK / ANDROID / WIPE-DATA what should I now do to get the stock rom (I'm too nervous now)..?
Click to expand...
Click to collapse
I'd use fastboot to flash a proper version of TWRP now.

OK So clicking Android has taken me back to 4.2.1. Think I'll do some more reading before messing about with it again - Thanks for all your help - Much Appreciated !!!!!

Trying to get back to the latest TWRP I have renamed openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob I then put it in /sdcard root copied it over and ran the following:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
12212+1 records in
12212+1 records out
6252648 bytes transferred in 3.658 secs (1709307 bytes/sec)
[email protected]:/ #
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.

Kavster76 said:
everytime I reboot it is still in 2.1.1 TWRP and not the 2.6.3.1 version..?
and I have to run bootit.ko to get back again.
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer.
Click to expand...
Click to collapse
Meaning he has to flash TWRP in fastboot not in adb shell - correct?
If yes - how is it different?

So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1:
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6106 KB)...
OKAY [ 2.605s]
writing 'recovery'...
OKAY [ 1.482s]
finished. total time: 4.087s
C:\Users\Kavster\Documents\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Surely that should of worked..?

Kavster76 said:
So I did the following - copied openrecovery-twrp-2.6.3.1-tf700t.blob to twrp.blob and then put it in same directory as fastboot.exe but still same issue after reboot - still on twrp 2.2.1
Click to expand...
Click to collapse
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.

_that said:
You have to clean the misc partition (mmcblk0p3) before the bootloader will cooperate again, see my previous answer. In post #3.
Click to expand...
Click to collapse
OK Cheers (sorry wasn't sure what post you were on about), all sorted now phew...
Backing up system now and I'm ready to install latest CyanogenMod...

_that said:
run the following in Terminal or via adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=32 count=1
Click to expand...
Click to collapse
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Thanks!

berndblb said:
Just out of curiosity: Is this command equivalent to
Code:
fastboot erase misc
to wipe the misc partition?
Click to expand...
Click to collapse
In theory, yes. However, when asking the bootloader for supported partitions (fastboot getvar all), "misc" is not among them, so I don't know if it really works.

Latest CyanogenMod all installed and looking good....
Thanks for all the help (I have added thanks) !!!
Kavster.

about qoute #8
hi friend.I have this problem too but my phone is samsung i9001.as you said,I downloaded the file and extracted it and then conected my phone to the pc and went to this path {start*accessories*command prompt} and entered the command "adb push bootit.ko" ,but responsed " adb is not recognised as an internal or external command, operable program or batch file" . I m too unhappy now,because my phone just boot to TWRP and like Kavster I have used TWRP 2.2.1 without adb sideload option.please help to rescue my phone.tanks dear friend

[Q] How to upgrade from CM10 Nightly

I have had this on the tablet for a while. It is very laggy and too slow to be useful. I tried to install the TWRP recovery (from CWM) and it does not take. I always come back to CWM. I tried using dd to write the TWRP recovery (copy to root of SD card, dd if=/dev/zero of=/dev/block/mmcblk0p3 then dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 (after I had extracted the twrp.blob to the sd cadr)) no luck. So, I wiped it and tried to install KattKiss. It gets stuck booting. I get the 4 dots that go round and round and the logo, but it never boots. So, I went back through the CM10 instructions (http://wiki.cyanogenmod.org/w/Install_CM_for_tf101) and I have 'joy' (definition: it boots and runs), but am wondering what is 'wrong' that I cannot load another ROM image. This is an old machine and there are a lot of meandering threads on XDA and none seem to work for me. I am not averse to 'starting over', but would like some guidance. I have rooted and rom-ed an atrix 4g, sgs2 and sgs3, but this is a bit different. I read that there is a bootloader unlocker for some tf101s, but those links are dead. I see lots of references to goo manager to assist with recoveries and such, but those links are dead as well.
Any help appreciated.
Keith

so I finally figured out how to stop it from recovery looping.
Cold booted it then 1) changed to su (sudo su), I'm running Linux 2) adbshell, 3) echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0 4)
reboot and voila, it will reboot to cm10.
Code:
sudo su
adb shell
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
Now to get kitkat installed. Is there anything else I am doing wrong before I try it again?
Keith

Can't flash latest TWRP, and lost my old install of it. Help?

Hi all,
I was running LineageOS 14.1 on my H830 with TWRP 3.2.1.0. Installed the newest nightly release via the OTA updater, which screwed up. System wouldn't boot, but I could get into TWRP. I ended up having to install it via the TWRP install option, and then had to run this code in TWRP's terminal:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
to get out of the boot loop that I had.
Now I have the latest LineageOS, but I cannot boot into TWRP recovery. I have the TWRP app and have root from Magisk. I tried flashing via the app, and it gives me a success message, but when I try to boot into recovery either via the app or using power + volume, it takes me to fastboot mode. I tried flashing via adb, but this still didn't work (was getting Failed: remote: unknown command). Really need TWRP back, as I want to switch to XenonHD. Any help?
Update:
Solved thanks to @autoprime
Method (flash via dd):
dl latest twrp from h830 page on twrp.me
rename to twrp.img
place in same folder as install location for adb client (i use Minimal ADB + Fastboot)
push to /sdcard using adb client (adb push twrp.img /sdcard/twrp.img)
open adb shell (type adb shell)
type su
type appropriate dd command found on install guide on device page on twrp.me (in this case: dd if=/sdcard/twrp.img of=/dev/block/platform/soc/624000.ufshc/by-name/recovery)
if permissions denied even if you have root:
go to developer settings
enable local terminal app
open and type su
grant super user permissions
type dd if=/sdcard/twrp.img of=/dev/block/platform/soc/624000.ufshc/by-name/recovery
reboot into recovery via adb (adb reboot recovery) or via key combo (turn off, then hold power + volume down till lg logo, then let go of power for a second and then hold again until twrp appears)
and you're good to go!