[TF300TG] For all who had received a brick after updating on the last firmware

Garfield3333

Senior Member
May 10, 2012
228
218
63
Maybe i have the answer ?!?

Sorry for my bad English but i have Asus Transformer 300T.

I was flashing the wrong bootloader for my Tablet TWRP 2.5.0.0
but the right was TWRP 2.5.0.0 - 4.2 so i have a soft brick.

So i reboot my bootloader with PDX, then i was in fastboot, when i was in Fastboot i erased my recovery- image.!(only the Recovery, nothing else)!

The Tablet boot normally into Android, when i was in the Android System, i was made the "CWM permissions" then it was fixed the
partitions, so reboot my Tablet into Fastboot, flash the Stock ROM from ASUS and everthing was fine.


Sorry for my bad English, but maybe i can help with it.........http://forum.xda-developers.com/images/icons/icon12.gif
 

clutz2516

Member
Nov 7, 2007
36
6
0
Biddeford
Sorry for my bad English but i have Asus Transformer 300T.

I was flashing the wrong bootloader for my Tablet TWRP 2.5.0.0
but the right was TWRP 2.5.0.0 - 4.2 so i have a soft brick.

So i reboot my bootloader with PDX, then i was in fastboot, when i was in Fastboot i erased my recovery- image.!(only the Recovery, nothing else)!

The Tablet boot normally into Android, when i was in the Android System, i was made the "CWM permissions" then it was fixed the
partitions, so reboot my Tablet into Fastboot, flash the Stock ROM from ASUS and everthing was fine.


Sorry for my bad English, but maybe i can help with it.........http://forum.xda-developers.com/images/icons/icon12.gif

sorry but what does "i was made the "CWM permissions" then it was fixed the
partitions" mean exactly?
 

Garfield3333

Senior Member
May 10, 2012
228
218
63
Android 4.1 have another partition to Android 4.2 (mounting the partitions)

Sorry i forgot when you are in Android you must root your device with motochopp, and then you fix the permissions with CMW
(Rom Manager - fix permissions)
Then you reboot your device and boot into fastboot mode flash the offical ASUS Stock and everthings fine.

I hope i can help.....
Sorry for the bad English.....
 

jaffer707

Senior Member
Mar 11, 2009
129
3
38
Dear Senior Members,,,,, One of the local Android developer here in Pakistan told after diagnosing my Tf300tg that the upgrade of 10.6.2.3 has corrupted the Partition table.....that is why ADB and fast boot is not working. Though that is latest JB version produced by ASUS......Solution we may get from ASUS or XDA developers only.......according to him changing of motherboard is foolish advice.!!!!!!!!!!!

So please ........do something ..there are lots of hopes from senior member of XDA to save TF300TG :crying:
 

matt95

Senior Member
Aug 8, 2010
5,963
2,372
0
Milan
Dear Senior Members,,,,, One of the local Android developer here in Pakistan told after diagnosing my Tf300tg that the upgrade of 10.6.2.3 has corrupted the Partition table.....that is why ADB and fast boot is not working. Though that is latest JB version produced by ASUS......Solution we may get from ASUS or XDA developers only.......according to him changing of motherboard is foolish advice.!!!!!!!!!!!

So please ........do something ..there are lots of hopes from senior member of XDA to save TF300TG :crying:
I'm working on a solution but I don't come up with nothing :(
 

XtriFe

Senior Member
May 17, 2010
230
17
0
Santo Domingo
Everything goes well except for the fact that my tablet freezes everytime i use the flash command on fastboot. It does say sending [OKAY] and writing too (see screenshot) but the tablet remains frozen and does not even get to show any progress bar. If I try the 'fastboot devices' command afterwards, it just shows :

????????? fastboot

and the fastboot reboot command doesnt really restarts the tablet. Same thing happens with the recovery flashing process. So basically I cant really flash anything because it says it sends and writes ok but nothing shows up in the tablet as it freezes.
 

crimson12

Senior Member
Jun 7, 2010
467
60
0
Metro Detroit, MI
See there's the problem that I was expecting. Let me guess, your tablet says it's unlocked when you turn it on right? Around the bottom of that Window you'll see where it says "unlocked: no". My tablet said the same thing. Basically there's some miscommunication going on where it displays the unlocked splash screen, but it's actually not unlocked. My guess (and seriously it's just a guess) is that it's not letting us run commands in fastboot (that don't hang) because of this miscommunication. I'm currently trying to show customer support that my tablet is not unlocked (same output as yours), but they aren't really listening.
As for a solution, I'm sorry I don't have one. I'd send it to support and hope they fix it. Or keep it and wait for a dev fix.

Sent from my Galaxy Nexus using Tapatalk 4 Beta
 
  • Like
Reactions: XtriFe

XtriFe

Senior Member
May 17, 2010
230
17
0
Santo Domingo
See there's the problem that I was expecting. Let me guess, your tablet says it's unlocked when you turn it on right? Around the bottom of that Window you'll see where it says "unlocked: no". My tablet said the same thing. Basically there's some miscommunication going on where it displays the unlocked splash screen, but it's actually not unlocked. My guess (and seriously it's just a guess) is that it's not letting us run commands in fastboot (that don't hang) because of this miscommunication. I'm currently trying to show customer support that my tablet is not unlocked (same output as yours), but they aren't really listening.
As for a solution, I'm sorry I don't have one. I'd send it to support and hope they fix it. Or keep it and wait for a dev fix.

Sent from my Galaxy Nexus using Tapatalk 4 Beta
Exactly. Im not sure but i think the communication issue is because the data partitions are wrong, so nothing is where is where its supposed to be.
 

crimson12

Senior Member
Jun 7, 2010
467
60
0
Metro Detroit, MI
I was informed by Asus tech support that merely entering fastboot mode voids my warranty. What the f*ck. Their technicians asked if I was able to enter recovery and fastboot.

Sent from my Galaxy Nexus using Tapatalk 4 Beta
 

jaffer707

Senior Member
Mar 11, 2009
129
3
38
I was informed by Asus tech support that merely entering fastboot mode voids my warranty. What the f*ck. Their technicians asked if I was able to enter recovery and fastboot.

Sent from my Galaxy Nexus using Tapatalk 4 Beta

It means there is no solution for those who have bricked their TF300TG :mad:
Replacement of motherboard is a painfull thing.

---------- Post added at 12:33 PM ---------- Previous post was at 12:31 PM ----------

It means there is no solution for those who have bricked their TF300TG :mad:
Replacement of motherboard is a painfull thing.
Even NVflash is useless for JB devices.....this is kind of annoying thing by NVIDIA and ASUS
 

cmouapilou

Member
Dec 26, 2007
8
1
0
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back

i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.

Here how i restored my TF300T JB

download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file

install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)

Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot

(the folowing i did at least 10 times already but didn't erase misc)

fastboot -i 0x0B05 erase system
fastboot -i 0x0B05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 erase misc
fastboot -i 0x0B05 erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot


* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s

im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )


hope i could help you out!

cheers
-Buster
originaly posted in this thread http://forum.xda-developers.com/showthread.php?t=2179759&page=2

i use this method and all work fine for me.
thankx buster99 and thankx to everyone here
 
  • Like
Reactions: axllent