[Q] Asus TF700 Bootloop

Search This thread

Nahakiole

Member
Jul 7, 2012
26
6
Hey everybody

After applying the Changes in the Build.prop in this thread http://xdaforums.com/showthread.php?t=1758160 and restarted the transformer, I got a Bootloop.

I tried to cold boot it up (holding both volume buttons), but it just shows me an opened Android Figure with a red warning sign.
EDIT: https://www.dropbox.com/s/ryoee7a6irjtn76/2012-07-09 14.19.38.jpg

What can I do now to boot up my Tablet.

Thank you for any helping advice.

Here is my build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.WW_epad-9.4.5.21-20120601
ro.build.version.incremental=WW_epad-9.4.5.21-20120601
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun  1 16:39:06 CST 2012
ro.build.date.utc=1338539946
ro.build.type=user
ro.build.user=
ro.build.host=Mars
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
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 is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=WW_epad-user 4.0.3 IML74K WW_epad-9.4.5.21-20120601 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.5.21-20120601:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1

#NFC
debug.nfc.fw_download=false
debug.nfc.se=false

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=300
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r1
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=v,o=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y

#Added Lines
debug.sf.hw=1
persist.sys.ui.hw=1
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
debug.performance.tuning=1
video.accelerate.hw=1
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
ro.config.nocheckin=1
persist.adb.notify=0
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.HOME_APP_ADJ=1
 
Last edited:

Nahakiole

Member
Jul 7, 2012
26
6
Thanks for your answer.

I managed it now to use adb to connect to my device.

But I can't change the /system to r/w.

Here's the console log of the commands su and mount.

Code:
shell@android:/system $ chmod 777 build.prop
chmod 777 build.prop
Unable to chmod build.prop: Read-only file system
10|shell@android:/system $  mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /
system
ffs2 /dev/block/mtdblock3 /system                                             <
mount: Operation not permitted
255|shell@android:/system $ su
su
Segmentation fault
139|shell@android:/system $  mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
/system
affs2 /dev/block/mtdblock3 /system                                            <
mount: Operation not permitted
255|shell@android:/system $

EDIT: I just found out with the adb that my build.prop was empty.
Now I try to Download via adb my data and afterwards I will try to factory reset the device.

EDIT2: I heard with busybox I can use my root rights with adb. Could I just install the busybox app?
Or can I use the Bootloader unlock tool for the asus transformer prime to unlock my root rights on the adb?
 
Last edited:

d14b0ll0s

Senior Member
Sep 4, 2011
1,213
448
Perhaps you missed something while replacing the files? It shouldn't be empty even if something didn't work.

The unlocking tool probably won't work.

I'm not sure why remounting it R/W didn't work either. Try again any of these:

adb shell mount -o remount,rw /system
or
mount -o rw,remount /dev/block/mmcblk0p1 /system

(I'm not sure why you've inserted /dev/block/mtdblock3 there? adb guide for a different device maybe?)

and then push your desired build.prop
 
  • Like
Reactions: Nahakiole

Nahakiole

Member
Jul 7, 2012
26
6
How can I do that?
I don't find anything when searching for a hard reset for the infinity.
Is it as the same, as on the prime? (Holding the Power on and Low Audio Button)?

Somehow I do experience problems with turning the infinity on, sometimes it doesn't turns on after pushing the power button.
 

d14b0ll0s

Senior Member
Sep 4, 2011
1,213
448
How can I do that?
I don't find anything when searching for a hard reset for the infinity.
Is it as the same, as on the prime? (Holding the Power on and Low Audio Button)?

Somehow I do experience problems with turning the infinity on, sometimes it doesn't turns on after pushing the power button.

1. Hold volume down & power button.
2. Release power button after it starts booting.
3. Release power down and press volume up after seeing some white text in the top left corner of the screen.
4. Press power button and you'll have the options you can navigate through by pressing volume buttons (volume down x2 + power button = factory reset).

Good luck! And hope you'll be able to do these tweaks next time.
Tell us how it went.
 
Last edited:
  • Like
Reactions: Nahakiole

Nahakiole

Member
Jul 7, 2012
26
6
I did now the Factory reset, but my transformer still won't boot up.
Any other chance of recovery?

Or do I have to send it in?

EDIT: Could I somehow flash the Original Firmware? Or something alike that?
Do I still have root rights after doing a factory reset?
When I connect to the transformer via adb and try to use su or sudo it doesn't work?
Code:
255|shell@android:/system $ su
su
Segmentation fault

EDIT2:
Now I can't even connect via adb to the transformer.
My Windows 7 64 Bit PC tries to install the drivers and gives me "error 10 can't start the device".
 
Last edited:

d14b0ll0s

Senior Member
Sep 4, 2011
1,213
448
I am no specialist in adb, so not sure about the su results there (try to Google it @xda), but after doing the factory reset you should not have root anymore, so sending it back should be safer than before the reset.

I don't think there's already original firmware out there to download, apart from the source code being available at ASUS's website.

Sorry it didn't work for you, I'm not sure why. You can try sending it to ASUS.

If adb did work, I would consider installing an update from a zip file consisting of the old build.prop, but it will be safer for you to send it back I guess (we can't even be sure this was the original reason it didn't boot).
 
  • Like
Reactions: Nahakiole

Nahakiole

Member
Jul 7, 2012
26
6
Okay thanks for your Help. I will go today to the shop where I bought it and will try to get a new one or a refound.

I will update this post as soon as I will be back from the Shop.

EDIT: I will get a new one without the Dock in about two Days and the Dock will be shipped in mid july.

Thank you for your Help d14b0ll0s.

EDIT2: For the next time, how could I make use of root on adb? Is there a Programm within I could activate this? So I could simply put in my Backup from my Computer?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Sorry to hear that, the tweaks worked fine for me. You can try pushing files through adb, try getting your old build.prop to work. If not, factory reset the device.

    This might be helpful (follow carefully): http://droidmodderx.com/prime/?page_id=74
    1
    Perhaps you missed something while replacing the files? It shouldn't be empty even if something didn't work.

    The unlocking tool probably won't work.

    I'm not sure why remounting it R/W didn't work either. Try again any of these:

    adb shell mount -o remount,rw /system
    or
    mount -o rw,remount /dev/block/mmcblk0p1 /system

    (I'm not sure why you've inserted /dev/block/mtdblock3 there? adb guide for a different device maybe?)

    and then push your desired build.prop
    1
    I tried both, but it showed me "Operation not permitted"

    Any other Ideas?

    None. Hard reset it and be sure not to place an empty or faulty build.prop directly on /system partition next time! Now you know what it leads to ;)
    1
    How can I do that?
    I don't find anything when searching for a hard reset for the infinity.
    Is it as the same, as on the prime? (Holding the Power on and Low Audio Button)?

    Somehow I do experience problems with turning the infinity on, sometimes it doesn't turns on after pushing the power button.

    1. Hold volume down & power button.
    2. Release power button after it starts booting.
    3. Release power down and press volume up after seeing some white text in the top left corner of the screen.
    4. Press power button and you'll have the options you can navigate through by pressing volume buttons (volume down x2 + power button = factory reset).

    Good luck! And hope you'll be able to do these tweaks next time.
    Tell us how it went.
    1
    I am no specialist in adb, so not sure about the su results there (try to Google it @xda), but after doing the factory reset you should not have root anymore, so sending it back should be safer than before the reset.

    I don't think there's already original firmware out there to download, apart from the source code being available at ASUS's website.

    Sorry it didn't work for you, I'm not sure why. You can try sending it to ASUS.

    If adb did work, I would consider installing an update from a zip file consisting of the old build.prop, but it will be safer for you to send it back I guess (we can't even be sure this was the original reason it didn't boot).