[Q] another TF300T brick thread

[JaZz0n]

I just simply smashed my TF300T (nonliterally) into a wall.

what I had:
official PACman 4.2.2 milestone with oc kernel
old bootloader with RCK, Android, USB (fastboot), wipe data
TWRP 2.5.0.0
what I did:
1 wiped data/cache/dalvik/system in TWRP after backup
2 flashed V10.6.1.27.1 WW SKU from XDA INDEX.
what I wanted:
well, stock Asus FW and then flashing CromiX for stability and battery ... :silly:
what I got:
bootloop on second Asus logo (metallic one)
new 4.2 bootloader with RCK, Android, wipe data

Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.1-20130711" A03

Starting Fastboot USB download protocol

no TWRP
adb and fastboot don't seem to work, commands "adb devices" and "fastboot devices" display pure nothingness
what I tried:
I did NOT try to update adb drivers as they worked perfectly berfore
installed minimal adb and fastboot, used commands "adb kill-server" & "~ start server", still no adb/fastboot devices
flash exact same rom via ext SD, worked! (that's good, right?)
--> I am not sure wether I should try an older stock rom, i.e. V10.6.1.15.3 or V10.6.1.8 OR even 4.1 rom
I don't want to damage my system even further - so please be kind and help ... IF there is a possible solution :fingers-crossed:
maybe I should just move on to the new shiny nexus7 ...


what doesn't seem to work:
How to Unbrick Your Tf300t and any other fastboot methods, naturally

 

[graphdarnell]

I just simply smashed my TF300T (nonliterally) into a wall.

what I had:
official PACman 4.2.2 milestone with oc kernel
old bootloader with RCK, Android, USB (fastboot), wipe data
TWRP 2.5.0.0
what I did:
1 wiped data/cache/dalvik/system in TWRP after backup
2 flashed V10.6.1.27.1 WW SKU from XDA INDEX.
what I wanted:
well, stock Asus FW and then flashing CromiX for stability and battery ... :silly:
what I got:
bootloop on second Asus logo (metallic one)
new 4.2 bootloader with RCK, Android, wipe data

no TWRP
adb and fastboot don't seem to work, commands "adb devices" and "fastboot devices" display pure nothingness
what I tried:
I did NOT try to update adb drivers as they worked perfectly berfore
installed minimal adb and fastboot, used commands "adb kill-server" & "~ start server", still no adb/fastboot devices
flash exact same rom via ext SD, worked! (that's good, right?)
--> I am not sure wether I should try an older stock rom, i.e. V10.6.1.15.3 or V10.6.1.8 OR even 4.1 rom
I don't want to damage my system even further - so please be kind and help ... IF there is a possible solution :fingers-crossed:
maybe I should just move on to the new shiny nexus7 ...


what doesn't seem to work:
How to Unbrick Your Tf300t and any other fastboot methods, naturally

Your system don't sound damaged to me at all. You, on the other hand, might be, judging from the changes in fonts in your text (lol). To me, it's obvious your tab is working, the only snag being the connectivity between it and the PC. This could be software or hardware-related, but not too hard to find out, except if it's the cable and you don't happen to have a spare one. Now if you can still charge the tab via that cable, I would rule it out. Which leaves the USB ports on your PC, and the drivers. Use another PC, and update the damn drivers to see what happens.

 

[sbdags]

Agreed - sounds like a bootloop.

Why would TWRP be erased?

 

[kaos420]

adb device isnt going to show a device follow this
http://forum.xda-developers.com/showthread.php?t=2187982

 

[JaZz0n]

You, on the other hand, might be, judging from the changes in fonts in your text (lol).

Just wanted a shiny and flashy post as bait. Seems like it worked

Now if you can still charge the tab via that cable, I would rule it out. Which leaves the USB ports on your PC, and the drivers. Use another PC, and update the damn drivers to see what happens.

Well, everything worked just fine until I flashed with fastboot, don't know why any hardware would break that fast :/ (I will test it regardless, thanks a lot)

Agreed - sounds like a bootloop.

Why would TWRP be erased?

Don't know, when I open RCK via bootloader the dead android appears ... Maybe I should have mentioned that sooner?

adb device isnt going to show a device follow this
http://forum.xda-developers.com/showthread.php?t=2187982

aaah, I see, there is a chance, that the new fw has driver issues in general ... Or need new drivers or whatever. I wanted to avoid installing Asus bloatware, but ...

...
Time for some testing
...

Sent from my GT-I9100 using Tapatalk 4

 

[JaZz0n]

Well, now I feel kind of retarded.
Installing Asus sync worked well - fastboot works again (adb does not but hey, who needs that, right?:silly

Thanks :highfive:

Don't know why, but flashing with the tf300t makes me feel uneasy and like a noob.
i9100 is waaaaay easier to both understand and use!

 

[pyraxiate]

Well, now I feel kind of retarded.
Installing Asus sync worked well - fastboot works again (adb does not but hey, who needs that, right?:silly

Thanks :highfive:

Don't know why, but flashing with the tf300t makes me feel uneasy and like a noob.
i9100 is waaaaay easier to both understand and use!

Its dangerous. Be very very very and I stress VERY call flashing roms. Make sure your recovery and bootloader match our your will wind up with a permanent brick.

Sent from my SGH-T889 using xda app-developers app

 

[JaZz0n]

Yep, that's why I always check 3 times beforehand what I'm flashing and in which way (for this device). Well, to sum things up: fastboot and adb did not find anything on "~ devices" in cmd, but flashing twrp 2.5.0.0 via fastboot worked, unexpectedly.
I installed cromiX 4.7 via sd through twrp, works now :good:
Thanks, again. Case closed

Gesendet von meinem GT-I9100 mit Tapatalk 4