Page 3 of 4 FirstFirst 1 2 3 4 LastLast
Results 21 to 30 of 38
Like Tree13Likes

Thread: Restore to Stock Firmware - Bricked my Me301T

  1. #21
    Super Moderator
    Supporting Member

    Member #
    53776
    Join Date
    Feb 2013
    Location
    Calgary AB
    Tablet
    TF Book T100TA
    Posts
    1,923
    Liked
    484 times
    Quote Originally Posted by ivonnep View Post
    Hi,

    I messed up my me301t... I wanted to install Custom Rom for the second time, my tablet was rooted, with TWRP and CROMI-Deodex.... but I wanted a fresh install. but in the boot menu by mistake selected the option to the right, the one that says WIPE DATA, and after that I don't remember what happened, I mean, I have been trying to revive this tablet like 32 hours ago that I can't remember things clearly... sorry :'(
    The thing is that I tried several times to install Custom Rom without success and now I think my tablet is bricked... if I shut it down with PWR+Vol.Up and then turn it up with PWR+Vol.Down until I see the ASUS logo, the boot menu never comes again, I think I deleted it... the only thing that shows up is the ASUS logo, and in the upper left corner it says "The Device is Unlocked". If I put a formatted microSD with the renamed blob firmware zip file, it doesn't do anything since I can't boot it to any RCK menu.... and I opened it to try to see if there was a hdd I could remove but I guess it is soldered... so I don't know how to transfer the software image to the internal memory....

    The pin clip thing doesn't do anything neither :S

    Sorry... I feel so stupid right now :'( never thought this could happen to me and is so frustrating to have a hardware thing win over you
    I'm so sorry to hear this. We do get a lot of cases like this and most of them cannot be repaired. You see, the boot menu is proprietary to Asus. Once you have lost it, you have usually corrupted everything. That being said, we have had some users succeed in unbricking other models but I can't remember exactly what their method was.
    Users Droidbound and Letmeknow will be able to tell for sure if there is any possibility of repair.
    *I apologize for any spelng mistakes. I frequently answer questions on my phone. The content is (usually) good, but the words may not be intelligible. If you cant understand my post... check back later or call me out on it.
    Tf300 Root and Custom ROM Guide!!_________Clean Install Windows 10 and Drivers______Tf700 Root and Custom ROM Guide!!

    Android Master Help Guide
    ______
    T100 Master Help Guide_____ T100 FAQ Thread

    Devices: Asus TF300t [Deceased], Asus t100TA -64GB, Google Nexus 6P

  2. #22
    Chief Customizer & Super Moderator
    Supporting Member

    Member #
    47492
    Join Date
    Oct 2012
    Tablet
    TF700
    Posts
    2,724
    Liked
    711 times
    Quote Originally Posted by ivonnep View Post
    Hi,

    I messed up my me301t... I wanted to install Custom Rom for the second time, my tablet was rooted, with TWRP and CROMI-Deodex.... but I wanted a fresh install. but in the boot menu by mistake selected the option to the right, the one that says WIPE DATA, and after that I don't remember what happened, I mean, I have been trying to revive this tablet like 32 hours ago that I can't remember things clearly... sorry :'(
    The thing is that I tried several times to install Custom Rom without success and now I think my tablet is bricked... if I shut it down with PWR+Vol.Up and then turn it up with PWR+Vol.Down until I see the ASUS logo, the boot menu never comes again, I think I deleted it... the only thing that shows up is the ASUS logo, and in the upper left corner it says "The Device is Unlocked". If I put a formatted microSD with the renamed blob firmware zip file, it doesn't do anything since I can't boot it to any RCK menu.... and I opened it to try to see if there was a hdd I could remove but I guess it is soldered... so I don't know how to transfer the software image to the internal memory....

    The pin clip thing doesn't do anything neither :S

    Sorry... I feel so stupid right now :'( never thought this could happen to me and is so frustrating to have a hardware thing win over you
    I wish you had come here a little earlier... Not to add insult to injury, but the 'wipe data' mistake would have been recoverable.
    Do I guess correctly that you were only able to boot to recovery and then you wiped the system, recovery or boot partitions?
    Now it really depends on if you can get far enough in the boot process to have access via adb.
    Since you were running CROMI-X I assume you have adb/fastboot set up on your PC?

  3. #23
    Soundwave
    Member #
    72515
    Join Date
    Aug 2014
    Location
    Spain
    Tablet
    MeMO Pad Smart
    Posts
    8
    Liked
    3 times
    Hi again!
    Thanks for the replies

    Well, I guess the more I tried to resolve the problem, the more I *edit* things up... but after posting my first message, I found that if I keep pressing PWR+Vol.Down a looooong time, with the microSD card removed, and the tablet disconnected from the PC, it goes to a blue TEAMWIN logo screen, and then goes to a TWRP V2.5.0.0 screen that asks me for a password, and the problem I am facing on this TWRP screen is that the touch screen doesn't work, I mean, I cannot hit "Cancel", I cannot write any password, I cannot select any menu option, NOTHING :S The only buttons that work are the PWR and Vol.UP and Vol.Down, so I am stuck on that TWRP screen and then it gets "locked", and says "Swipe to unlock", but I can't swipe anything.... I tried to connect an external mini keyboard, external mouse, extenal normal sized keyboard, and nothing... the only option left that I haven't tried is to get a "OTG cable" for external power supply to the mouse/keyboard... but I don't know if the issue could be driver related.

    On this TWRP screen, ADB commands show the next replies (sorry but my ADB knowledge is very basic, and I have BLUESTACKS installed on this Windows PC, so I don't know if that is the device showing...):

    C:\>cd fastboot
    C:\Fastboot>adb devices
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    List of devices attached
    0123456789ABCDEF recovery
    C:\Fastboot>fastboot devices

    And I don't know what the #$% this did but I ran the following to see what happened:
    C:\Fastboot>adb pull / c:\adbpullsystem

    This copied 2 folders inside c:\adbpullsystem, tmp and sys. Inside tmp was a recovery.log file with the following information:
    Starting TWRP 2.5.0.0 on Sat Jan 1 00:00:10 2000
    BOARD_HAS_NO_REAL_SDCARD := true
    I:Internal path defined: '/data/media'
    I:External path defined: '/external_sdcard'
    I:Mount: Unable to find partition for path '/data'
    TW_NO_REBOOT_RECOVERY := true
    TW_NO_REBOOT_BOOTLOADER := true
    RECOVERY_SDCARD_ON_DATA := true
    TW_NO_USB_STORAGE := true
    TW_INCLUDE_CRYPTO := true
    Starting the UI...Pixel format: 1280x800 @ 32bpp
    Pixel format: BGR_565
    framebuffer: fd 3 (1280 x 800)
    => Linking mtab
    => Processing recovery.fstab
    I:Processing '/system'
    I:Processing '/cache'
    I:Unable to mount '/cache'
    I:Actual block device: '', current file system: 'ext4'
    I:Processing '/misc'
    E:Unable to find parition size for '/misc'
    I:Processing '/staging'
    E:Unable to find parition size for '/staging'
    I:Processing '/data'
    I:Unable to mount '/data'
    I:Actual block device: '', current file system: 'ext4'
    I:Unable to mount '/data'
    I:Actual block device: '', current file system: 'ext4'
    E:Unable to find parition size for '/data'
    I:Backup folder set to '/data/media/TWRP/BACKUPS/015d46d949100a16'
    I:Settings storage is '/data/media'
    I:Processing '/recovery'
    E:Unable to find parition size for '/recovery'
    I:Processing '/boot'
    E:Unable to find parition size for '/boot'
    I:Processing '/external_sdcard'
    I:Created '/external_sdcard' folder.
    I:Processing '/sd-ext'
    I:Created '/sd-ext' folder.
    Updating partition details...
    E:Unable to mount '/system'
    I:Actual block device: '', current file system: 'ext4'
    E:Unable to mount '/cache'
    I:Actual block device: '', current file system: 'ext4'
    I:Unable to mount '/external_sdcard'
    I:Actual block device: '', current file system: 'vfat'
    I:Unable to mount '/sd-ext'
    I:Actual block device: '', current file system: 'ext4'
    I:Unmounting main partitions...


    Partition Logs:
    /system | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
    Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI
    Primary_Block_Device: /dev/block/mmcblk0p1
    Display_Name: System
    Storage_Name: System
    Backup_Path: /system
    Backup_Name: system
    Backup_Display_Name: System
    Storage_Path: /system
    Current_File_System: ext4
    Fstab_File_System: ext4
    Backup_Method: files

    /cache | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
    Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI
    Primary_Block_Device: /dev/block/mmcblk0p2
    Display_Name: Cache
    Storage_Name: Cache
    Backup_Path: /cache
    Backup_Name: cache
    Backup_Display_Name: Cache
    Storage_Path: /cache
    Current_File_System: ext4
    Fstab_File_System: ext4
    Backup_Method: files

    /misc | | Size: 0MB
    Flags:
    Primary_Block_Device: /dev/block/mmcblk0p3
    Display_Name: misc
    Storage_Name: misc
    Backup_Path: /misc
    Backup_Name: misc
    Backup_Display_Name: misc
    Storage_Path: /misc
    Current_File_System: emmc
    Fstab_File_System: emmc
    Backup_Method: dd

    /staging | | Size: 0MB
    Flags:
    Primary_Block_Device: /dev/block/mmcblk0p4
    Display_Name: staging
    Storage_Name: staging
    Backup_Path: /staging
    Backup_Name: staging
    Backup_Display_Name: staging
    Storage_Path: /staging
    Current_File_System: emmc
    Fstab_File_System: emmc
    Backup_Method: dd

    /data | | Size: 0MB
    Flags: Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI Can_Be_Encrypted Is_Encrypted Has_Data_Media Is_Storage Is_Settings_Storage Ignore_Blkid
    Symlink_Path: /data/media
    Symlink_Mount_Point: /sdcard
    Primary_Block_Device: /dev/block/mmcblk0p8
    Length: -16384
    Display_Name: data
    Storage_Name: Internal Storage
    Backup_Path: /data
    Backup_Name: data
    Backup_Display_Name: Data
    Storage_Path: /data/media
    Current_File_System: emmc
    Fstab_File_System: ext4
    Backup_Method: dd

    /recovery | | Size: 0MB
    Flags: Can_Be_Backed_Up
    Primary_Block_Device: /dev/block/mmcblk0p9
    Display_Name: Recovery
    Storage_Name: recovery
    Backup_Path: /recovery
    Backup_Name: recovery
    Backup_Display_Name: Recovery
    Storage_Path: /recovery
    Current_File_System: emmc
    Fstab_File_System: emmc
    Backup_Method: dd

    /boot | | Size: 0MB
    Flags: Can_Be_Backed_Up
    Primary_Block_Device: /dev/block/mmcblk0p10
    Display_Name: Boot
    Storage_Name: boot
    Backup_Path: /boot
    Backup_Name: boot
    Backup_Display_Name: Boot
    Storage_Path: /boot
    Current_File_System: emmc
    Fstab_File_System: emmc
    Backup_Method: dd

    /external_sdcard | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
    Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
    Primary_Block_Device: /dev/block/mmcblk1p1
    Alternate_Block_Device: /dev/block/mmcblk1
    Display_Name: Micro SDcard
    Storage_Name: Micro SDcard
    Backup_Path: /external_sdcard
    Backup_Name: external_sdcard
    Backup_Display_Name: Micro SDcard
    Storage_Path: /external_sdcard
    Current_File_System: vfat
    Fstab_File_System: vfat
    Backup_Method: files

    /sd-ext | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
    Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI Removable
    Primary_Block_Device: /dev/block/mmcblk1p2
    Display_Name: SD-Ext
    Storage_Name: SD-Ext
    Backup_Path: /sd-ext
    Backup_Name: sd-ext
    Backup_Display_Name: SD-Ext
    Storage_Path: /sd-ext
    Current_File_System: ext4
    Fstab_File_System: ext4
    Backup_Method: files

    I:Loading package: TWRP (/res/ui.xml)
    I:Loading resources...
    I:Loading variables...
    I:Loading pages...
    I:Loading page main
    I:Loading page main2
    I:Loading page install
    I:Loading page flash_confirm
    I:Loading page flash_zip
    I:Loading page flash_done
    I:Loading page clear_vars
    I:Loading page confirm_action
    I:Loading page action_page
    I:Loading page singleaction_page
    I:Loading page action_complete
    I:Loading page filecheck
    I:Loading page rebootcheck
    I:Loading page reboot
    I:Loading page selectstorage
    I:Loading page mount
    I:Loading page usb_mount
    I:Loading page usb_umount
    I:Loading page wipe
    I:Loading page advancedwipe
    I:Loading page formatdata
    I:Loading page formatdata_confirm
    I:Loading page backup
    I:Loading page backupname1
    I:Loading page backupname2
    I:Loading page backup_run
    I:Loading page restore
    I:Unable to open '/data/media/TWRP/BACKUPS/015d46d949100a16'
    I:Loading page restore_select
    I:Loading page renamebackup
    I:Loading page restore_run
    I:Loading page settings
    I:Loading page timezone
    I:Loading page screen
    I:Loading page advanced
    I:Loading page partsdcard
    I:Loading page htcdumlock
    I:Loading page lock
    I:Loading page filemanagerlist
    I:Loading page filemanageroptions
    I:Loading page choosedestinationfolder
    I:Loading page filemanagerrenamefile
    I:Loading page filemanagerrenamefolder
    I:Loading page filemanagerchmod
    I:Loading page filemanagerconfirm
    I:Loading page filemanageracction
    I:Loading page decrypt
    I:Loading page trydecrypt
    I:Loading page terminalfolder
    I:Loading page terminalcommand
    I:Loading page sideload
    I:Loading page installsu
    I:Loading page fixsu
    I:Switching packages (TWRP)
    E:Unable to mount '/cache'
    I:Actual block device: '', current file system: 'ext4'
    E:Cannot load volume /misc!
    E:Cannot load volume /misc!
    Startup Commands: ro.secure=0
    ro.allow.mock.location=1
    ro.debuggable=1
    persist.sys.usb.config=mtp,adb
    ro.build.id=IMM76L
    ro.build.display.id=cm_tf300t-eng 4.0.4 IMM76L eng.dees_troy.20130408.213443 test-keys
    ro.build.version.incremental=eng.dees_troy.2013040 8.213443
    ro.build.version.sdk=15
    ro.build.version.codename=REL
    ro.build.version.release=4.0.4
    ro.build.date=Mon Apr 8 21:34:53 UTC 2013
    ro.build.date.utc=0
    ro.build.type=eng
    ro.build.user=dees_troy
    ro.build.host=ded1.ktechnology.net
    ro.build.tags=test-keys
    ro.product.model=Transformer Prime TF300T
    ro.product.brand=asus
    ro.product.name=EeePad
    ro.product.device=tf300t
    ro.product.board=cardhu
    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=tf300t
    ro.build.description=WW_epad-user 4.0.3 IML74K WW_epad-9.4.3.29-20120511 release-keys
    ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.3.29-20120511:user/release-keys
    ro.build.characteristics=tablet
    ro.cm.device=tf300t
    ro.carrier=wifi-only
    ro.com.android.dateformat=MM-dd-yyyy
    wifi.interface=wlan0
    wifi.supplicant_scan_interval=15
    ro.opengles.version=131072
    persist.tegra.nvmmlite=1
    ro.epad.model=TF300T
    dalvik.vm.heapstartsize=5m
    dalvik.vm.heapgrowthlimit=48m
    dalvik.vm.heapsize=256m
    ro.rommanager.developerid=cyanogenmod
    keyguard.no_require_sim=true
    ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
    ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
    ro.com.google.clientidbase=android-google
    ro.com.android.wifi-watchlist=GoogleGuest
    ro.setupwizard.enterprise_mode=1
    ro.com.android.dataroaming=false
    ro.cm.version=9.0.0-RC0-tf300t-UNOFFICIAL
    ro.modversion=9.0.0-RC0-tf300t-UNOFFICIAL
    ro.config.ringtone=CyanTone.ogg
    ro.config.notification_sound=CyanMessage.ogg
    ro.config.alarm_alert=CyanAlarm.ogg
    ro.kernel.android.checkjni=1
    ro.setupwizard.mode=OPTIONAL
    dalvik.vm.dexopt-flags=m=y
    net.bt.name=Android
    net.change=net.bt.name
    dalvik.vm.stack-trace-file=/data/anr/traces.txt
    ro.factorytest=0
    ro.serialno=015d46d949100a16
    ro.bootmode=unknown
    ro.baseband=unknown
    ro.bootloader=unknown
    ro.hardware=cardhu
    ro.revision=0
    ro.emmc=0
    init.svc.recovery=running
    init.svc.mischelp=restarting
    init.svc.adbd=running
    service.adb.root=1

    E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
    I:Copying file /cache/recovery/log to /cache/recovery/last_log
    stat try 1: No such file or directory
    stat try 2: No such file or directory
    stat try 3: No such file or directory
    stat try 4: No such file or directory
    stat try 5: No such file or directory
    stat try 6: No such file or directory
    stat try 7: No such file or directory
    stat try 8: No such file or directory
    stat try 9: No such file or directory
    stat try 10: No such file or directory
    failed to stat
    Can't open
    (No such file or directory)
    E:Unable to set emmc bootloader message.
    E:Unable to mount '/cache'
    I:Actual block device: '', current file system: 'ext4'
    I:Can't unlink /cache/recovery/command
    I:Is encrypted, do decrypt page first
    I:Switching packages (TWRP)
    I:Set page: 'decrypt'
    I:Cannot find file /nobrightness


    If the Adb pull really extracted files from my tablet, I guess I can do "Adb push" to send files to it with the correct folders/files.... right?


    On the other hand, if I do the following commands in an UBUNTU system, I get:

    root@laptopcita:/home/ivonne/adt-bundle-linux-x86_64-20140321/sdk/platform-tools# ./adb shell
    error: insufficient permissions for device
    root@laptopcita:/home/ivonne/adt-bundle-linux-x86_64-20140321/sdk/platform-tools# ./adb root
    error: insufficient permissions for device
    root@laptopcita:/home/ivonne/adt-bundle-linux-x86_64-20140321/sdk/platform-tools# ./adb devices
    List of devices attached
    ???????????? no permissions

    root@laptopcita:/home/ivonne/adt-bundle-linux-x86_64-20140321/sdk/platform-tools# ./adb pull . /mnt/TABLEt/ADBPULL
    error: insufficient permissions for device
    root@laptopcita:/home/ivonne/adt-bundle-linux-x86_64-20140321/sdk/platform-tools# lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 002: ID 1bcf:2c17 Sunplus Innovation Technology Inc.
    Bus 001 Device 007: ID 0b05:4c83 ASUSTek Computer, Inc.
    Bus 003 Device 003: ID 046d:c52f Logitech, Inc. Wireless Mouse M305

    root@laptopcita:/home/ivonne/adt-bundle-linux-x86_64-20140321/sdk/platform-tools#


    Last edited by Swipe; 09-03-2014 at 12:15 AM. Reason: language guidelines

  4. #24
    Chief Customizer & Super Moderator
    Supporting Member

    Member #
    47492
    Join Date
    Oct 2012
    Tablet
    TF700
    Posts
    2,724
    Liked
    711 times
    Considering the circumstances you did really well.
    The recovery log helps, although the time stamp doesn't match, but it often doesn't.....

    Now - you will have to be patient. I am working all day and have very limited time in the evenings, so that's the pace I can help you at...

    You're device is pretty hosed. Recovery doesn't recognize any of your partitions, but you seem to have adb access and that is great!
    We will have to try to kick it into fastboot, then possibly you can flash the Asus system blob to get it back.
    In recovery run this command (and please post the output of your cmd window).
    Code:
    adb devices
    You sould get the numbers/letters + "recovery" again
    Then
    Code:
     adb shell cat /proc/partitions > partitions.txt
    That you should give you a text file with your partition table or, if that does not work
    Code:
    adb shell ls -l /dev/block/mmc*
    That should return a list of your partitions which we may need to clear the wipe data command you inadvertantly wrote to misc.

    If you get the partition table or not, then try this command
    Code:
    adb reboot-bootloader
    Let's see what that gets you.

  5. #25
    Soundwave
    Member #
    72515
    Join Date
    Aug 2014
    Location
    Spain
    Tablet
    MeMO Pad Smart
    Posts
    8
    Liked
    3 times
    Quote Originally Posted by droidbound View Post
    Considering the circumstances you did really well.
    The recovery log helps, although the time stamp doesn't match, but it often doesn't.....

    Now - you will have to be patient. I am working all day and have very limited time in the evenings, so that's the pace I can help you at...

    You're device is pretty hosed. Recovery doesn't recognize any of your partitions, but you seem to have adb access and that is great!
    We will have to try to kick it into fastboot, then possibly you can flash the Asus system blob to get it back.
    In recovery run this command (and please post the output of your cmd window).
    Code:
    adb devices
    You sould get the numbers/letters + "recovery" again
    Then
    Code:
     adb shell cat /proc/partitions > partitions.txt
    That you should give you a text file with your partition table or, if that does not work
    Code:
    adb shell ls -l /dev/block/mmc*
    That should return a list of your partitions which we may need to clear the wipe data command you inadvertantly wrote to misc.

    If you get the partition table or not, then try this command
    Code:
    adb reboot-bootloader
    Let's see what that gets you.

    Hi!

    As directed, I ran:

    C:\Fastboot>adb devices
    List of devices attached
    0123456789ABCDEF recovery
    C:\Fastboot>adb shell cat /proc/partitions > partitions.txt
    C:\Fastboot>

    Then I open the partitions.txt file and it contains only one line as follows:

    major minor #blocks name



    Then I ran:


    C:\Fastboot>adb shell ls -l /dev/block/mmc*
    ls: /dev/block/mmc*: No such file or directory

    C:\Fastboot>adb reboot-bootloader


    And nothing happens. It stays there without giving any reply back.


    If I do the ls command modified:
    C:\Fastboot>adb shell ls -l /dev/block/*
    brw------- 1 root root 7, 0 Jan 1 00:00 /dev/block/loop0
    brw------- 1 root root 7, 1 Jan 1 00:00 /dev/block/loop1
    brw------- 1 root root 7, 2 Jan 1 00:00 /dev/block/loop2
    brw------- 1 root root 7, 3 Jan 1 00:00 /dev/block/loop3
    brw------- 1 root root 7, 4 Jan 1 00:00 /dev/block/loop4
    brw------- 1 root root 7, 5 Jan 1 00:00 /dev/block/loop5
    brw------- 1 root root 7, 6 Jan 1 00:00 /dev/block/loop6
    brw------- 1 root root 7, 7 Jan 1 00:00 /dev/block/loop7
    brw------- 1 root root 179, 0 Jan 1 00:38 /dev/block/mmcblk0
    brw------- 1 root root 179, 1 Jan 1 00:38 /dev/block/mmcblk0p1

    /dev/block/platform:
    drwxr-xr-x 3 root root 100 Jan 1 00:38 sdhci-tegra.0



    In about 1hr I have to go out, and I will try to get an OTG cable to try to connect an external keyboard/mouse to see if I can choose "Cancel" on that TWRP screen that is asking for a password, since I read in another forum that if you choose cancel, then you have an option to restore some image...

    Thank you and see you later
    Last edited by ivonnep; 08-24-2014 at 09:00 AM. Reason: more info

  6. #26
    Super Moderator
    Supporting Member

    Member #
    53776
    Join Date
    Feb 2013
    Location
    Calgary AB
    Tablet
    TF Book T100TA
    Posts
    1,923
    Liked
    484 times
    Ivonep. Please do not try this without confirmation from someone else (Droidbound or Letmeknow) I found this guide which may be exactly what you need to do to get the partitions working again. http://forum.xda-developers.com/show....php?t=2854495

    Again PLEASE DO NOT RUSH AHEAD there is a very good chance given your skill level with adb that we can assist you.
    Last edited by Gtanner00; 08-24-2014 at 10:52 AM.
    droidbound and ivonnep like this.
    *I apologize for any spelng mistakes. I frequently answer questions on my phone. The content is (usually) good, but the words may not be intelligible. If you cant understand my post... check back later or call me out on it.
    Tf300 Root and Custom ROM Guide!!_________Clean Install Windows 10 and Drivers______Tf700 Root and Custom ROM Guide!!

    Android Master Help Guide
    ______
    T100 Master Help Guide_____ T100 FAQ Thread

    Devices: Asus TF300t [Deceased], Asus t100TA -64GB, Google Nexus 6P

  7. #27
    Chief Customizer & Super Moderator
    Supporting Member

    Member #
    47492
    Join Date
    Oct 2012
    Tablet
    TF700
    Posts
    2,724
    Liked
    711 times
    Quote Originally Posted by Gtanner00 View Post
    Ivonep. Please do not try this without confirmation from someone else (Droidbound or Letmeknow) I found this guide which may be exactly what you need to do to get the partitions working again. http://forum.xda-developers.com/show....php?t=2854495

    Again PLEASE DO NOT RUSH AHEAD there is a very too chance given your skill level with adb that we can assist you.
    Good find Gtanner!
    I pestered lj long enough it seems to put his guide together. That's exactly the method I was thinking of.
    @ivonep you can follow that guide. I know of no other method to revive your tablet from its current state.

  8. #28
    Soundwave
    Member #
    72515
    Join Date
    Aug 2014
    Location
    Spain
    Tablet
    MeMO Pad Smart
    Posts
    8
    Liked
    3 times
    OMG!

    I'm still not there but I got my bootloader menu back!!

    SAM_3762.jpg

    But now, when I run "fastboot devices", or even if I run again "adb devices", nothing shows up:

    SAM_3763.jpg


    Should I go ahead and continue with the instructions, and erase misc, cache, system, recovery, etc???


  9. #29
    Soundwave
    Member #
    72515
    Join Date
    Aug 2014
    Location
    Spain
    Tablet
    MeMO Pad Smart
    Posts
    8
    Liked
    3 times
    Updating information....

    On my previous post I was working on a Windows PC... and getting no devices with adb or fastboot commands, I decided to try in my Ubuntu laptop to see what happened... and it was detected!!!

    Captura de pantalla de 2014-08-24 20:00:03.png

    So I am going to continue with the erase commands

    Hope to return with good news!

  10. #30
    Soundwave
    Member #
    72515
    Join Date
    Aug 2014
    Location
    Spain
    Tablet
    MeMO Pad Smart
    Posts
    8
    Liked
    3 times

    Red face

    Wooooohoooooooo!!!!!!!!!!!

    SAM_3765.jpg

    Everything is OK now!!! though I still have to install the Custom ROM and all that, but I learned that NEVER, NEVERRRR have to choose the option "Wipe Data" from the bootloader menu again... and yes, I must admit that last night I went to sleep and some tears escaped my eyes while thinking that my tablet was completely dead but thankfully I found you guys!!!

    Kisses and hugs and many many thanks!

 

 
Page 3 of 4 FirstFirst 1 2 3 4 LastLast

Remove Ads

Sponsored Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. NVflash restore your sbk1 TF101 to rooted stock ICS
    By sharpe351 in forum Asus Transformer (TF101) Development
    Replies: 20
    Last Post: 08-09-2013, 10:30 AM
  2. MeMo ME301T firmware update - 4.2.1 is here - build 10.6.1.15-20130329
    By shlemik in forum Asus MeMO Pad Smart (10") General Discussion
    Replies: 30
    Last Post: 06-28-2013, 08:46 PM
  3. Restore to Stock Firmware
    By xavieredouard in forum Asus MeMO Pad Smart (10") Help
    Replies: 0
    Last Post: 04-20-2013, 01:35 PM
  4. Bricked TF101, CWM unable to load any (even stock) roms
    By teegunn in forum Asus Transformer (TF101) Help
    Replies: 9
    Last Post: 10-14-2012, 03:02 PM
  5. UK Firmware update 20\02\2012 just bricked my Prime !
    By Boothy in forum Transformer Prime General Discussions
    Replies: 8
    Last Post: 02-20-2012, 07:40 AM

Search tags for this page

,

asus me301t bricked

,

asus me301t factory reset

,

asus me301t stock rom

,
asus me301t stock rom download
,

asus memo pad 7 k013 stock recovery rom

,

asus memo pad bricked

,

downgrade asus memo pad me172v firmware

,

factory reset me301t

,

how to reset asus me301t

,

me301t restore default

,

me301t stock recovery

Click on a term to search for related topics.
Powered by vBulletin® Version 4.2.3
Copyright © 2020 vBulletin Solutions, Inc. All rights reserved.
Search Engine Optimization by vBSEO 3.6.1
All times are GMT -6. The time now is 10:07 AM.