[SOLVED] Help! Can't pass through ASUS and TEGRA logo screen, did I brick it?

[mizifih]

FIXED IT! CLICK HERE TO READ THE SOLUTION.

I'm crazy here. I tried flashing ROMs, even the .30 ASUS provide on their site and got nothing, can't make it boot into system. One thing though, I can boot into fastboot mode. Actually that's pretty much what I can do. Help me, please!

Oh! The device is already unlocked.

The ASUS logo I see is the static white one, that appears before the animated, shiny ASUS logo.

UPDATE 1: Got ClockWorkMod Touch to work! So far, that's it, I'll try now flash a ROM.
UPDATE 2: Tried flashing the official .30 firmware but I got signature fail problem.
UPDATE 3: For my surprise ADB is working, adb push cm-9.0.0-tf300t.zip /sdcard/
UPDATE 4: Flashed CyanogenMod, it flashed ok (according to CWM), but on the first reboot, it showed that progress bar (I think it's supposed to perform the install of CM9 at this point), that went from 0 to 100% in less then one second, it rebooted right after that and now I'm stuck on the ASUS logo again.

You guys think this super wipe thing could work?

Thank you

[Ads]

[janner43]

Moved to development.
Please post in the correct section

Transformer Pad 300 Development
All hacking and rooting discussions regarding the Transformer Pad 300 belong in this section

[Frederuco]

Did you try a hard reset after you flashed? I have had to do that on some ROMs to get them to boot after seeing the progress indicator and then a boot loop.

You could try the superwipe. I have used it before when I flashed ARHD on my TF101. It is not going to hurt, and maybe the stock will work after you do it too.

[mizifih]

Did you try a hard reset after you flashed? I have had to do that on some ROMs to get them to boot after seeing the progress indicator and then a boot loop.

You could try the superwipe. I have used it before when I flashed ARHD on my TF101. It is not going to hurt, and maybe the stock will work after you do it too.

Hard reset? How do I do that?

- Sent from my Galaxy Nexus using Tapatalk 2
- Enviado de meu Galaxy Nexus usando o Tapatalk 2

[janner43]

Hard reset = cold boot = http://www.transformerforums.com/for...inks-help.html

[mizifih]

You could try the superwipe. I have used it before when I flashed ARHD on my TF101. It is not going to hurt, and maybe the stock will work after you do it too.

Even though I reflashed with CM9, the stock would work?

I can see the message on the screen and I proceeded with cold boot (by doing nothing and waiting the 10 seconds)
OS will code boot in 10 seconds if no input is detected.
Cold-booting Linux

And that's that, when I do that I get stuck on the Cold-boot/Hard Reset.
Hard Reset / Cold Boot didn't work neither.

Proceeded with Superwipe script.

Here's what I did

1) get into ADB and mount your SD card as your Data partition:

ADB Shell
mount /dev/block/mmcblk1p1 /data

This will make your SD card readable

2) download superwipe http://xda3.androidrevolution.nl/db_...ull_EeePad.zip

3) push superwipe to your sd card

adb push superwipe.zip /data/media/superwipe.zip

4) run superwipe from your CWM - it should be able to access your SD card now

5) push a CM9 to your SD using the adb push method above. Flash said rom

Super Wipe didn't work neither. It ran like it was supposed to, I saw it saying that partitions were EXT4 formatted, but didn't solved my problem ;(

I'll try flashing the Official ASUS Transformer Pad TF300T Firmware: V10.4.2.9 Only for US SKU (Android 4.1).

[Frederuco]

After you ran the superwipe, did you flash a ROM again?

Superwipe will wipe the partitions (except the Recovery and possibly the /data/media/ depending on which superwipe was used).

Then flash your favorite ROM again.

Also, if the ROM you download has a checksum listed, be sure to verify the checksum (ES File Explorer - Long press the file, properties, checksum) and verify the file was downloaded and does not have any lost bits. The Asus files do not have a checksum to compare, but if it is not working then you will want to try to download it again and try the new file.

[mizifih]

After you ran the superwipe, did you flash a ROM again?

Yes, I flashed CM9.

Superwipe will wipe the partitions (except the Recovery and possibly the /data/media/ depending on which superwipe was used).

But if I flash a ROM I'm (supposedly) good to go, right?

Also, if the ROM you download has a checksum listed, be sure to verify the checksum (ES File Explorer - Long press the file, properties, checksum) and verify the file was downloaded and does not have any lost bits. The Asus files do not have a checksum to compare, but if it is not working then you will want to try to download it again and try the new file.

Can I do that with the Official ASUS Transformer Pad TF300T Firmware: V10.4.2.9 Only for US SKU (Android 4.1) - 438,56 (MBytes)?

Do I flash it like any other ROM, using "install zip from sdcard" function in ClockWork? The rom.zip file came inside a download.zip file, if unrar don't bitch about it when I extract, chances are the rom.zip file is ok, right?

Before I do that, I ran SuperWipe again, here's what I got:

Do you noticed that "Can't open /cache/last_install" message on the first image? That bothered me. Anyways, I proceeded with untrusted zip, when I restarted after flashing I got the red signature mismatch red warning, tablet rebooted by itself and got me back to the logo screen, where it got stuck.

root@android:/ # ls -p -e
ls -p -e
drwxr-xr-x    2 root     root             0 Thu Aug 23 16:58:04 2012 btmac/
drwxrwx---    3 system   cache         4096 Thu Jan  1 00:00:00 1970 cache/
drwxrwx--x    3 system   system        4096 Thu Jan  1 00:00:00 1970 data/
-rw-r--r--    1 root     root          2088 Wed Aug 22 15:12:06 2012 default.prop
drwxr-xr-x   10 root     root          2120 Thu Aug 23 16:58:04 2012 dev/
-rw-rw-rw-    1 root     root       2224936 Thu Aug 23 17:02:19 2012 dir.txt
drwxr-xr-x    2 root     root             0 Thu Aug 23 16:58:06 2012 etc/
-rw-r-----    1 root     root           616 Wed Aug 22 01:03:12 2012 fstab.cardhu
-rwxr-x---    1 root     root         98724 Thu Aug 23 02:13:33 2012 init
-rwxr-x---    1 root     root          1789 Wed Aug 22 01:06:50 2012 init.rc
-rw-rw-rw-    1 root     root       2224855 Thu Aug 23 17:01:49 2012 ls.txt
dr-xr-xr-x   97 root     root             0 Thu Jan  1 00:00:06 1970 proc/
drwxr-xr-x    3 root     root             0 Wed Aug 22 01:01:29 2012 res/
drwx------    2 root     root             0 Thu Aug  9 07:58:27 2012 root/
drwxr-x---    2 root     root             0 Thu Aug 23 02:39:33 2012 sbin/
drwxrwxrwx    3 root     root         16384 Thu Jan  1 00:00:00 1970 sdcard/
drwxrwx---    3 system   root          4096 Thu Jan  1 00:00:00 1970 staging/
drwxr-xr-x   13 root     root             0 Thu Aug 23 16:58:04 2012 sys/
drwxr-xr-x   15 root     root          4096 Thu Aug 23 16:55:56 2012 system/
drwxrwxr-x    2 root     shell            0 Thu Aug 23 16:58:04 2012 tmp/
-rw-r--r--    1 root     root          2237 Wed Aug 22 01:03:12 2012 ueventd.cardhu.rc
-rw-r--r--    1 root     root           272 Wed Aug 22 01:03:12 2012 ueventd.goldfish.rc
-rw-r--r--    1 root     root          3879 Wed Aug 22 01:03:12 2012 ueventd.rc
root@android:/ #

root@android:/system # ls -p -e
ls -p -e
drwxr-xr-x    2 root     root          4096 Thu Aug 23 16:55:29 2012 addon.d/
drwxr-xr-x    2 root     root          4096 Thu Aug 23 16:55:34 2012 app/
drwxr-xr-x    2 root     shell         4096 Thu Aug 23 16:56:12 2012 bin/
-rw-r--r--    1 root     root          2265 Fri Aug  1 12:00:00 2008 build.prop
drwxr-xr-x   13 root     root          4096 Thu Aug 23 16:55:34 2012 etc/
drwxr-xr-x    2 root     root          4096 Thu Aug 23 16:55:56 2012 fonts/
drwxr-xr-x    2 root     root          4096 Thu Aug 23 16:55:37 2012 framework/
drwxr-xr-x    8 root     root          8192 Thu Aug 23 16:55:50 2012 lib/
drwxr-xr-x    2 root     root          4096 Thu Jan  1 00:00:00 1970 lost+found/
drwxr-xr-x    4 root     root          4096 Thu Aug 23 16:55:52 2012 media/
drwxr-xr-x    3 root     root          4096 Thu Aug 23 16:55:55 2012 tts/
drwxr-xr-x    8 root     root          4096 Thu Aug 23 16:55:56 2012 usr/
drwxr-xr-x    4 root     shell         4096 Thu Aug 23 16:55:56 2012 vendor/
drwxr-xr-x    2 root     shell         4096 Thu Aug 23 16:55:56 2012 xbin/
root@android:/system #

root@android:/cache # ls -p -e
ls -p -e
drwx------    2 root     root          4096 Thu Jan  1 00:00:00 1970 lost+found/
root@android:/cache #

root@android:/sdcard # ls -p -e
ls -p -e
-rwxrwxrwx    1 root     root     449085869 Thu Aug  9 19:28:46 2012 US_epad-user-10.4.2.9.zip
-rwxrwxrwx    1 root     root     334806342 Mon Jun  4 16:50:12 2012 US_epad-user-9.4.3.30.zip
-rwxrwxrwx    1 root     root     139222714 Wed Aug 22 23:38:16 2012 cm-9.0.0-tf300t.zip
-rwxrwxrwx    1 root     root            34 Sun Jul 29 16:18:06 2012 command
-rwxrwxrwx    1 root     root     239166013 Tue Aug 21 20:15:12 2012 dlpkgfile
-rwxrwxrwx    1 root     root           129 Thu Aug 23 13:50:10 2012 fix_permissions.log
-rwxrwxrwx    1 root     root      52048746 Wed Aug 22 20:41:24 2012 gapps-ics-20120429-signed.zip
drwxrwxrwx    2 root     root         32768 Thu Aug 23 15:16:12 2012 media/
-rwxrwxrwx    1 root     root          6604 Thu Aug 23 16:22:32 2012 superwipe.log
root@android:/sdcard #

This is superwipe.log

Starting recovery on Thu Aug 23 16:19:08 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v6.0.1.2
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null) 0
  1 /system ext4 /dev/block/mmcblk0p1 (null) 0
  2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
  3 /misc emmc /dev/block/mmcblk0p3 (null) 0
  4 /boot emmc boot (null) 0
  5 /recovery emmc recovery (null) 0
  6 /staging emmc /dev/block/mmcblk0p4 (null) 0
  7 /data ext4 /dev/block/mmcblk0p8 (null) -32768
  8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
ro.build.id=JRO03C
ro.build.display.id=JRO03C.US_epad-10.4.2.9-20120809
ro.build.version.incremental=US_epad-10.4.2.9-20120809
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Thu Aug  9 15:49:39 CST 2012
ro.build.date.utc=1344498579
ro.build.type=user
ro.build.user=
ro.build.host=Uranus
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=tf300t
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=US_epad-user 4.1.1 JRO03C US_epad-10.4.2.9-20120809 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.9-20120809:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.24
gps.version.driver=V7.9.9
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.31
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r1
ril.disable.fastdormancy=1
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.factorytest=0
ro.serialno=015d15b51c040001
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.emmc=0
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/dev/block/mmcblk0p8
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_flags=0x00000006
ro.crypto.state=unencrypted
init.svc.recovery=running
init.svc.adbd=running
service.adb.root=1

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
    Size: 29618569216
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label: 
    Blocks: 7231096
    Block groups: 221
    Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231096 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware

Formatting /cache...
Creating filesystem with parameters:
    Size: 448790528
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 6848
    Inode size: 256
    Journal blocks: 1712
    Label: 
    Blocks: 109568
    Block groups: 4
    Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware

Formatting /sd-ext...
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.

-- Installing: /sdcard/media/superwipe.zip
Finding update package...
I:Update location: /sdcard/media/superwipe.zip
Opening update package...
Installing update...
about to run program [/sbin/sleep] with 2 args


================================================
|           !!! Wiping Script !!!              |
|   This operation will remove all your data   |
|  You have 15 seconds to turn OFF the device  |
|           to cancel this procedure           |
================================================


Creating filesystem with parameters:
    Size: 448790528
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 6848
    Inode size: 256
    Journal blocks: 1712
    Label: 
    Blocks: 109568
    Block groups: 4
    Reserved block group size: 0
Created filesystem with 11/27392 inodes and 3440/109568 blocks
1. Erasing & formatting EXT4 *CACHE* partition

about to run program [/sbin/sleep] with 2 args

2. Erasing & formatting EXT4 *SYSTEM* partition
Creating filesystem with parameters:
    Size: 805306368
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 3072
    Label: 
    Blocks: 196608
    Block groups: 6
    Reserved block group size: 0
Created filesystem with 11/49152 inodes and 6166/196608 blocks

about to run program [/sbin/sleep] with 2 args

3. Erasing & formatting EXT4 *DATA* partition
Creating filesystem with parameters:
    Size: 5242880
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 320
    Inode size: 256
    Journal blocks: 1024
    Label: 
    Blocks: 1280
    Block groups: 1
    Reserved block group size: 0
Created filesystem with 11/320 inodes and 1050/1280 blocks

about to run program [/sbin/sleep] with 2 args

about to run program [/sbin/e2fsck] with 3 args
4. Now checking filesystems for errors/sbin/e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p2
Filesystem mounted or opened exclusively by another program?
run_program: child exited with status 8
about to run program [/sbin/e2fsck] with 3 args
/dev/block/mmcblk0p1: clean, 11/49152 files, 6166/196608 blocks
about to run program [/sbin/e2fsck] with 3 args
/dev/block/mmcblk0p7: clean, 11/320 files, 1050/1280 blocks
about to run program [/sbin/sleep] with 2 args



about to run program [/sbin/busybox] with 4 args
5. Creating log file on SD card

Is there anything else I can do to properly flash any ROM?

[Frederuco]

Try going into CWM - Advance - Fix Permissions.

The other suggestion I have is to try to flash a TWRP recovery and see if you have better luck on that. Looks like there may be an issue with your /system/ partition, but I am not 100%.

As far as what needs to flash, each ROM is different. I know that for the Team EOS JB ROM, you have to flash the ROM, GAPPS and then a custom kernel if you want it. Some ROMs have everything included. Best to check at the ROM thread at XDA or wherever to see what needs to be flashed.

[mizifih]

fix permissions log

/sbin/fix_permissions 2.04 started at 08-23-2012 13:50:10
/sbin/fix_permissions 2.04 ended at 08-23-2012 13:50:10 (Runtime:0m0s)
/sbin/fix_permissions 2.04 started at 08-23-2012 17:18:09
/sbin/fix_permissions 2.04 ended at 08-23-2012 17:18:09 (Runtime:0m0s)

I just noticed something, /sdcard is actually a SD Card I have inserted, it's not the internal memory. If I remove the /sdcard I can't mount it again.

Isn't /sdcard supposed to be mounted on the internal memory?