Database Info

[Q] Enrcyption Support for ClockWorkMod Recovery

Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg

Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out

Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.

Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.

Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...

mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S

small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...

I didn't read anything about encryption so did not upgraded to the touch recovery yet

you should lock the bootloader if someone is nagging you

jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva

rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S

DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva

Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S

The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse

rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.

Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...

What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse

Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards

orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)

thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.

[Q] Rooted? I can't flash any roms though.

TF101. 16GB
As far as I know I am rooted. When I boot into recovery it is using ClockworkMod Recovery v3.0.2.8
Android version 3.1
Build Number
HMJ37.US_epad-8.4.4.5-20110527
Anytime I try to flash any rom I get an error 7.
What am I doing wrong? Anymore information needed to help?

ls3mach said:
TF101. 16GB
As far as I know I am rooted. When I boot into recovery it is using ClockworkMod Recovery v3.0.2.8
Android version 3.1
Build Number
HMJ37.US_epad-8.4.4.5-20110527
Anytime I try to flash any rom I get an error 7.
What am I doing wrong? Anymore information needed to help?
Click to expand...
Click to collapse
are you verifying the MD5SUM of the OS post pushing it to the SdCard.

neidlinger said:
are you verifying the MD5SUM of the OS post pushing it to the SdCard.
Click to expand...
Click to collapse
I have not. I have tried multiple sources and roms (stock and modded). I can't get any to flash.

Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.

ls3mach said:
Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.
Click to expand...
Click to collapse
are you extracting the OS are leaving it in a .zip

neidlinger said:
are you extracting the OS are leaving it in a .zip
Click to expand...
Click to collapse
It is in a zip format. When I insert my SD card into my TF101 it recognizes that it has a system file on the card.

ls3mach said:
It is in a zip format. When I insert my SD card into my TF101 it recognizes that it has a system file on the card.
Click to expand...
Click to collapse
If it's the stock ROM, you actually have to unzip it after download to get to another zip file inside.

ls3mach said:
Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.
Click to expand...
Click to collapse
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision

gee one said:
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?

baseballfanz said:
If it's the stock ROM, you actually have to unzip it after download to get to another zip file inside.
Click to expand...
Click to collapse
I am pretty sure I have done that. It is recognizing that their is a system file when the card is inserted.

ls3mach said:
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?
Click to expand...
Click to collapse
You could try the Team Rouge recovery but I don't know if it will help or not

ls3mach said:
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?
Click to expand...
Click to collapse
You can mount via adb or extract the ramdisk from cwm and add staging partition to the etc/recovery.fstab
I'm not sure which versions of cwm have staging. As I said, I think roach's 3.2.0.1 has it. I'm actually using a modded version of his, but I won't post it because it will probably cause more bootloops and headaches.
sent from my cyanogen(mod) vision

You could also flash a rom that doesn't use the staging partition.
sent from my cyanogen(mod) vision

gee one said:
You could also flash a rom that doesn't use the staging partition.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I tried to flash the new ICS rom, but it wouldn't load for me either. Are you sure this is a staging issue? Also, why can't I flash the stock ROMs? After I get a new one loaded is this going to be a continuing issue?

gee one said:
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I have the SDK installed and updated. How do I make those ADB commands work? I am in PROMPT and the correct folder. Sorry, I don't use this program often and haven't since I installed the mod originally and I have had my TF101 since they were new.

ls3mach said:
I have the SDK installed and updated. How do I make those ADB commands work? I am in PROMPT and the correct folder. Sorry, I don't use this program often and haven't since I installed the mod originally and I have had my TF101 since they were new.
Click to expand...
Click to collapse
The stock roms usually use the staging partition, the custom roms are hit or miss, so this could potentially be a recurring issue.
rom the command line prompt, type:
adb devices - if all is well, you'll see you tf's serial number
adb shell
su
mkdir /staging - you'll get an error if it already exists, which is fine
mount /dev/block/mmcblk0p4 /staging
exit
Then mount system in cwm and flash your rom.
Good luck
sent from my cyanogen(mod) vision

baseballfanz said:
You could try the Team Rouge recovery but I don't know if it will help or not
Click to expand...
Click to collapse
Well, that worked to flash, but now I get the Android goon when I try to get into recovery.

It sounds like it worked- if you were flashing the 86521 stock rom, it has a stock recovery on it.
You should receive the ICS update now. There is an ICS root exploit in the dev section by rhcp012345, if you want to root.
sent from my cyanogen(mod) vision

gee one said:
It sounds like it worked- if you were flashing the 86521 stock rom, it has a stock recovery on it.
You should receive the ICS update now. There is an ICS root exploit in the dev section by rhcp012345, if you want to root.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
It did. I appreciate the help everyone. Now to get my HBoot1.5 EVO3d working. My previous one gave up the ghost

gee one said:
The stock roms usually use the staging partition, the custom roms are hit or miss, so this could potentially be a recurring issue.
rom the command line prompt, type:
adb devices - if all is well, you'll see you tf's serial number
adb shell
su
mkdir /staging - you'll get an error if it already exists, which is fine
mount /dev/block/mmcblk0p4 /staging
exit
Then mount system in cwm and flash your rom.
Good luck
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I tried....but.....
N:\3\3>adb shell
~ # mkdir /staging
mkdir /staging
mkdir: can't create directory '/staging': File exists
~ # mount /dev/block/mmcblk0p4 /staging
mount /dev/block/mmcblk0p4 /staging
mount: mounting /dev/block/mmcblk0p4 on /staging failed: Invalid argument
~ #
Ivalid argument...any idea?

Only CWM on my TF101G B90...

Hi all,
I'm here because I need your help...
Days ago I installed on my TF101G the recovery CWM 5.8.1.8...
now I can just go into recovery mode and if I try to mount /data I receive the message "no location found"...
how can I push a Rom on my TF to try to install it?
thanks in advance for your help

how to flash a ROM
The ROM to be flashed must be cwm flashable, you cannot flash official firmware unless it is repacked to be cwm flashable.
Your ROM must be a zip file, do not unzip it.
Copy (or adb push) the ROM to /sdcard/
Reboot tab into recovery.
Follow cwm flash instructions. There are many such a manual available on-line, one of them is:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
You can just jump to section "apply update from sdcard", which tells you how to use cwm recovery to flash a ROM
One thing you should pay attention is:
if the ROM to be flashed is only a update to your current ROM, do not do any wipe work.
If it is a new ROM, you must do the wipe.

You can also try this....
hi Fenice82,
read this forum
http://forum.xda-developers.com/showthread.php?t=1213723
and read message 1 and 313 for mounting and the adb commands for sending cmw flash file to your internal card of your TF.
Make sure you have the cwm flashable rom file on you computer in the adb dir.
good luck.

I'm hege again...
thk nlheiz for your post...
I push the rom in my TF... I tried different location...
data/media
or
data
or
system
or
sdcard
or
sdcard/rom
if I go in adb shell and I use command mkdir to make a new folder like system,data,sdcard I see the the file already exist...
but my tf "can't mount /sdcard/" and at the same time if i try to mount /data from recovery I see the message
"Error mounting /data!"
what can I do now?
edit... maybe this can help you...
via ADB shell
mount data
mount: mounting /dev/block/mmcblk0p7 on /data failed: Invalid argument

How about restore stock recovery and ROM? Here is a recent guide for root/unroot/downgrading:
http://forum.xda-developers.com/showthread.php?t=1622628

I don't have experience with cwm 5.8.1.8, I stayed on 3.2.0.1 because it is possible to flash from external sdcards.
cold you try this:
put our tablet into cwm (volume - plus power and when asked volume +) and connect it to usb on pc.
then on your pc:
adb devices
this should give you a serial number back.....
then try this:
to mount the internal sdcard so that you can push a new rom- use
adb shell
mount /dev/block/mmcblk0p7 /data/
ls /sdcard/
exit
then from your pc, type:
adb push /path/to/your/rom.zip /data/media
I found this here http://forum.xda-developers.com/showthread.php?p=23256536 in post 3......
let me know if this works

e154037 said:
How about restore stock recovery and ROM? Here is a recent guide for root/unroot/downgrading:
http://forum.xda-developers.com/showthread.php?t=1622628
Click to expand...
Click to collapse
thk man... with method 3 I installed new recovery and with it I installed the official update, from external storage, that recovery my tablet...pdate
before official update I tried to install other custom rom but I incurred in encryption problem... with official after the fist boot it automatically resolved the problem
I'm very happy
thk again

[Q] Can't format Sd Card

I was recently downloading clockwork for my Infuse I just flashed back to stock. No problems at all, the phone booted up and had CWM installed. The phone randomly shut off, and everytime we put the battery in it started back up. We cleaned the power button and had it working again, but when I tried to boot up, I got stuck in a boot loop. So I reflashed it using UCKD5 in odin with repartions. Pass, and the phone still stopped at the at&t screen. I went in to recovery, and no longer had CWM but 3E recovery. After deleting the cache and factory resetting, and then trying to format the sd card it says can't mount sd card. Can't mount /dev/block/mmcblk0p1. I not a noob, i've successfully flashed 5 infuses and my current one is running 4.2.1 slim. I believe what happened is the partitions got messed up some how and I need to repartition the phone to format my Sd Card. But not quite sure.
Any help would be appreciated. Thanks
Tank

Click This
See qkster's reply.
XDA - Aug. 7

Pony Express said:
Click This
See qkster's reply.
XDA - Aug. 7
Click to expand...
Click to collapse
Thanks, but no help I need to format the internal sd card.

Tank Weston said:
I was recently downloading clockwork for my Infuse I just flashed back to stock. No problems at all, the phone booted up and had CWM installed. The phone randomly shut off, and everytime we put the battery in it started back up. We cleaned the power button and had it working again, but when I tried to boot up, I got stuck in a boot loop. So I reflashed it using UCKD5 in odin with repartions. Pass, and the phone still stopped at the at&t screen. I went in to recovery, and no longer had CWM but 3E recovery. After deleting the cache and factory resetting, and then trying to format the sd card it says can't mount sd card. Can't mount /dev/block/mmcblk0p1. I not a noob, i've successfully flashed 5 infuses and my current one is running 4.2.1 slim. I believe what happened is the partitions got messed up some how and I need to repartition the phone to format my Sd Card. But not quite sure.
Any help would be appreciated. Thanks
Tank
Click to expand...
Click to collapse
3e recovery after an odin flash back to stock means you're in stock recovery. you can only wipe cache or factory reset in STOCK recovery.
you need to have cwm recovery back...
you'll need to figure this part out.
will have to debate the noob issue later

I know this, the only way I know of how to do this is using adb to push a copy of cwm through. But im not to sure on how to use adb. And we could debate that now, both my infuse's work flawlessly with 4.2.1

can anybody guide me through this, I know there is people who have resolved this issue using adb. I'm just not that familiar with it all yet.

tank,
you should look over this a few times.
http://forum.xda-developers.com/showthread.php?t=1437548
Secure stock kernels don't like stuff pushed onto them. it doesnt sound like you're even rooted
you need to flash and unsecure kernel via odin or heimdall to proceed.
if you are on froyo uckd5, you can root it with soc and use sgs kernel flasher to flash your insecure kernel

1 - can you boot into the phone OS? If so, format "USB Storage" or in froyo whichever of the cards is 13GB .. if that doesn't work:
2a - flash a UCLB3 GB Heimdall or Odin package with PIT:
http://forum.xda-developers.com/showthread.php?t=1524081
http://forum.xda-developers.com/showthread.php?t=1705260
2b - then flash a CWM kernel (the infuse toolkit includes any you might need - see my sig)
2c - then flash a custom or rooted stock GB rom that has busybox installed (most or all do). Then....
From CWM recovery you will have the option to unmount and format the internal sd card but not the external sd card. Or you can go back to step one to try format the card.
If none of this works, we're back to your original question: If you want to try the reformat via adb option you will need to be running a working rooted, busyboxed rom... Once you get yourself an unsecure kernel, and have installed the Android SDK on your PC (for ADB), and the device drivers for the Infuse on your PC (your search mission if you choose to accept it), you can do the following:
adb shell
umount /sdcard -or- umount /mnt/sdcard {probably not needed, just in case}
then one of the following commands should work:
mkfs.vfat /dev/block/mmcblk0p1
-or-
mkfs.vfat /dev/block/vold/179:1
you may need to preface with "busybox<space>" or "/system/xbin/" but this should not be necessary from one of the GB kernels with CWM.
Once done, you can try mounting from the CWM menu on the phone and then typing the "mount" command from the adb shell command line to see if /sdcard is mounted. This is one option to accomplish this goal. There are others that involve using other tools that you copy over to your phone - if none of this works, here's a primer which covers most or all of what is needed in general terms.. some searching and testing should net you what you need:
http://forum.xda-developers.com/showthread.php?t=907436
Just for fun, here's a half-assed xref of the mmc storage devices on the infuse:
(device / vold / mount)
mmcblk0p1 - 179:1 /sdcard
mmcblk0p2 - 179:2 /data
mmcblk1p1 - 179:9 /sdcard/external_sd
(full device path / literal mount)
/dev/block/mmcblk0p2 /data
/dev/block/vold/179:1 /mnt/sdcard
/dev/block/vold/179:9 /mnt/sdcard/external_sd

...thus saith the Zen.

Zen Arcade said:
1 - can you boot into the phone OS? If so, format "USB Storage" or in froyo whichever of the cards is 13GB .. if that doesn't work:
2a - flash a UCLB3 GB Heimdall or Odin package with PIT:
http://forum.xda-developers.com/showthread.php?t=1524081
http://forum.xda-developers.com/showthread.php?t=1705260
2b - then flash a CWM kernel (the infuse toolkit includes any you might need - see my sig)
2c - then flash a custom or rooted stock GB rom that has busybox installed (most or all do). Then....
From CWM recovery you will have the option to unmount and format the internal sd card but not the external sd card. Or you can go back to step one to try format the card.
If none of this works, we're back to your original question: If you want to try the reformat via adb option you will need to be running a working rooted, busyboxed rom... Once you get yourself an unsecure kernel, and have installed the Android SDK on your PC (for ADB), and the device drivers for the Infuse on your PC (your search mission if you choose to accept it), you can do the following:
adb shell
umount /sdcard -or- umount /mnt/sdcard {probably not needed, just in case}
then one of the following commands should work:
mkfs.vfat /dev/block/mmcblk0p1
-or-
mkfs.vfat /dev/block/vold/179:1
you may need to preface with "busybox<space>" or "/system/xbin/" but this should not be necessary from one of the GB kernels with CWM.
Once done, you can try mounting from the CWM menu on the phone and then typing the "mount" command from the adb shell command line to see if /sdcard is mounted. This is one option to accomplish this goal. There are others that involve using other tools that you copy over to your phone - if none of this works, here's a primer which covers most or all of what is needed in general terms.. some searching and testing should net you what you need:
http://forum.xda-developers.com/showthread.php?t=907436
Just for fun, here's a half-assed xref of the mmc storage devices on the infuse:
(device / vold / mount)
mmcblk0p1 - 179:1 /sdcard
mmcblk0p2 - 179:2 /data
mmcblk1p1 - 179:9 /sdcard/external_sd
(full device path / literal mount)
/dev/block/mmcblk0p2 /data
/dev/block/vold/179:1 /mnt/sdcard
/dev/block/vold/179:9 /mnt/sdcard/external_sd
Click to expand...
Click to collapse
I can't boot the device up at all. I flashed UCLB3 with odin and heimdall no success. I installed adb, but that was the extent of that. I can't use your tools, because I can't access anything on my phone. So still no luck, if anything else comes up let me know.
Thanks a lot though for the help though.
Tank

Have you tried booting into recovery by holding down both volume buttons?
Or, if phone on, hold down both vol plus power button until Samsung logo, then release only power until recovery loads?
If that works you can flash a rooted stock package via Odin (choose the second package in jscott30's OP I linked above and then flash a custom kernel via Odin or Heimdall), boot recovery, and then follow the instructions from adb install on.
Sent from my SAMSUNG-SGH-I997 using xda premium

Zen Arcade said:
Have you tried booting into recovery by holding down both volume buttons?
Or, if phone on, hold down both vol plus power button until Samsung logo, then release only power until recovery loads?
If that works you can flash a rooted stock package via Odin (choose the second package in jscott30's OP I linked above and then flash a custom kernel via Odin or Heimdall), boot recovery, and then follow the instructions from adb install on.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I've tried all this, no luck. I just noticed the water damage circle thing was red.. So I think that might be my cause, though I can boot into recovery, and downloading mode..

[Q] Help i may have doomed my tablet.

So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.

supernova0 said:
So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.
Click to expand...
Click to collapse
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!

das chaos said:
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!
Click to expand...
Click to collapse
I was able to that, but the filesystem that I was using was f2fs so when I booted to the stockrom it said" encryption unsuccessful" so i had to format my data partition to a compatible format. so i flash twrp recovery, but I had the same problem, the screen flashes and then it stays at the twrp splash screen. then I thought it might be a problem with my data partition, so I erased my whole data partition using fastboot, with the command
fastboot format userdata
it worked and the recovery is working also, but my filesystem is on ext3 and I know ext 4 is better than ext 3, so using the twrp recovery I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.

supernova0 said:
..... I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.
Click to expand...
Click to collapse
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!

das chaos said:
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!
Click to expand...
Click to collapse
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.

supernova0 said:
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.
Click to expand...
Click to collapse
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.

das chaos said:
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.
Click to expand...
Click to collapse
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--

bretzke said:
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--
Click to expand...
Click to collapse
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh

lj50036 said:
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh
Click to expand...
Click to collapse
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1

bretzke said:
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1
Click to expand...
Click to collapse
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.

bretzke said:
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.
Click to expand...
Click to collapse
See you found your own answer and I like that ..... :good:
Thx Josh