[Q] TWRP 2.4.4.0-JB killed my Tablet? - Transformer TF300T Q&A, Help & Troubleshooting

I found multiple development threads that are close to this, but here's the deal...
I took Asus 4.2.1 OTA update and used that for a while.
The device was already unlocked and I decided to try TWRP 2.4.4.0 for recovery before trying any custom ROMs
I followed the big bold red instructions that said:
If you have taken the official Asus Jellybean OTA then be sure to install the '-JB' version of the recovery for your device - and only flash roms that are based on the Asus OTA.
I downloaded the -JB version (at that time, -ICS was the only other choice), and installed it via fastboot.
Upon rebooting, it will only boot into recovery and TWRP can't see any partitions. More importantly, I've spent almost a month now reading the threads that are related to this trying various suggestions in trying to break out of this, and during this time, I've realized that I can't flash anything. ADB works, but the devices says "123456789ABCDEF recovery". I can run "adb reboot bootloader" and I will get my 3-icon 4.2.1 bootloader screen with a blinking green square on RCK. Fastboot devices shows my S/N, and it acts like it is flashing (tried flashing the -4.2 version of TWRP 2.4.4.0 and a new copy of the JB 4.2.1 OTA ROM), but all the tablet does is lock-up. The green square stops blinking and, even though fastboot says it's working, the tablet is no longer responding and requires a reset to reboot, upon which it boots right back into TWRP.
I'm just asking if there is a way out of this yet that doesn't involve replacing the main logic board.
I suppose what bothers me more, is that Teamwin's website for TWRP still has the same instructions in big bold red letters, without acknowledging that there are TWO official Asus Jellybean OTA releases. One will work just fine with the -JB version they specify to download, the other will do what mine did. Anyone current with Asus releases is gonna follow these instructions and brick their pads unless they already know about the -4.2 version of TWRP.

Yo!
Have you tried flashing asus stock 4.2.1 system blob using adb?

Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

klownin5643 said:
Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This is the link to the instructions i followed. http://forum.xda-developers.com/showthread.php?t=2187982
Here is the main point.
- Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash system blob
, hit enter and wait until it completes
Write this to reboot your tablet:
Code:
fastboot reboot
or hold the power button for 10 seconds if the code doesn't work
You are now updated to Android 4.2

There are 3 things keeping this from working:
1) fastboot -i 0x0B05 flash system blob
This locks the tablet up. Fastboot thinks it's still working, but the blinking RCK has stopped blinking and...
2) fastboot reboot
... doesn't work because the tablet has locked up from the flash attempt. You have to...
3) hold the power button for 10 seconds if the code doesn't work
Which does reboot the tablet, but it goes right back into TWRP, and you have NOT been updated to anything.
Now, in my particular case, I can get it to "adb reboot bootloader" and tell it to cold boot Linux to get into my OS, but that never happens either. It's likely been wiped from one of my multiple attempts at trying others' suggestions for getting out of this.

I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...

joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I did the same thing as the OP. I'm not new at this, I've rooted and run custom ROMs for years on dozens of devices. I always do lots of research before starting the process. What the OP and I are saying is that the Team Win site doesn't state anything about the 421 patch and if you look at the file list, the patch only exists in the 2.4.4.0 version. With those two things in mind, a reasonable person would conclude that 2.5.5.0 is patched for both...as long as you use the -JB version. Obviously wrong as I now know, but certainly not clearly wrong before bricking the device.
I would never assume to blame the Dev's, but I (we) are asking that they be a bit more blatant with the fact JB v4.2 MUST USE TWRP version 2.4.4.0-4.2 and not anything else.
Now, for good or bad, so many people have now bricked their TF300's that there are many threads like this one. Any research at this point will reveal this issue. Still, Team Win should post the warning.

joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I wish it was as simple as reading the wrong post... When I downloaded TWRP 2.4.4.0, there were only -ICS and -JB files listed (much like TWRP 2.5.0.0 is now)... Wouldn't you have picked -JB?
Even now, Teamwin's directions tell you that, if you took the Asus JB OTA, that you need the -JB version. They don't differentiate WHICH JB OTA, and they don't mention that a -4.2 version specifically for the 4.2.1 OTA exists. Never mind mentioning that using the -JB version on the latest Asus JB OTA update will BRICK THE TABLET.
There are 192 people that have downloaded the 2.5.0.0-JB blob file as of now. How many of these folks do you suppose have taken the Asus 4.2.1 OTA update and are about to permabrick their tablets?

It sickens me to know of the 192, likely most are on 4.2.1. I only hope they catch it before pushing the ROM.

When you flash recovery its flash ix505blah recovery recovery.blob is it flash ix5o5blah system system.blob? If that makes sense? Or no.?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

The two things here centers around the fact that TWRP is the only thing that will boot, other than the bootloader (but you have to boot TWRP first).
1) If you are in TWRP, there are no partitions mounted. In fact, there are no mmcblk devices at all, which is why there are no partitions mounted. As a result, there is nothing to flash to from here (even if fastboot worked). Adb works from here, but the device serial says "123456789ABCDEF recovery". Fastboot detects no devices at all from here.
2) If you reboot bootloader from adb, you can get access to fastboot. However, any flashing from here locks up the tablet, even though the command looks like it's running and completing the first time. Adb does NOT work from here, sees no devices. Fastboot looks like it sees the right device until you try to flash something with it. Once you try to flash anything, no fastboot command completes, furthering the notion that the tablet is frozen. A reset reboots the tablet back into TWRP, and nothing has changed. Repeat the cycle ad nauseum.
Basically, you can't do squat from TWRP, and fastboot flash from the bootloader locks up the tablet so you can't flash anything. I'm pretty sure it will take a logic board replacement to fix it at this point unless someone comes up with something better.

I'm having the exact same issue as you... I had flashed the TWRP JB blob and it couldn't recognize anything so I tried to flash CWM. Now...My fastboot doesn't do a thing since the blue progress bar doesn't show up and just freezes when trying to flash the stock firmware. I don't think I can send it to Asus for warranty either since my device is unlocked.

Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.

splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
You can't flash a recovery? And what about the stock Rom?
Sent from my WT19i using xda app-developers app

splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
Lol did that too...I don't know if there is anything left to try. Did you try putting stock rom on an external SD card and running RCK?

Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.

splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
I did the same thing and got the same result. This i very interesting because the
Code:
fastboot -i 0x0b05 flash <partition> <filename>
command which tries to write/edit something on the partition fails (maybe is due to some encryption introduced in 421) but the
Code:
fastboot -i 0x0b05 erase <partition>
which also does the write/edit, succeeds. What I'm trying to say is that either both should fail or succeed because both are trying to do some editing to the storage.

steveb05 said:
Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.
Click to expand...
Click to collapse
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.

splashg said:
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.
Click to expand...
Click to collapse
Just got my TF300 back for Asus service center. They said that they had to replace the motherboard @ a cost of $186.00 total, parts and labor. Told them to just send it back. I'll buy a Nexus 7 instead for the same price almost.

Got my broken TF300 ebay win today. Digitizer and LCD were toast. But, the main board went right in to my bricked TF300. I'm unlocked, rooted, and running 4.1.1 and life is good!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Related

[Q] Please help - ASUS Transformer Infinity TF700 Brick

Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
I am having the same issue. Just rooted today. Please help!
dpadaddict said:
I am having the same issue. Just rooted today. Please help!
Click to expand...
Click to collapse
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
http://teamw.in/project/twrp2/105
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
fordwolden said:
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
Click to expand...
Click to collapse
I wish I could... The message I receive is as follows when I do that:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image
And nothing ever shows up. Just the ASUS logo.
Did you solve your problem? I'm having the same issue and tried to install custom ROMs without solving the problem
reboot the device! (power and vol down for 5 sec)
hold vol down at the ASUS screen, but don't go to recovery, just wait until you see a 3 different logos on your screen.
An Android, a Wipe and a USB Icon
go between theese logos with vol down choose USB Icon with vol up!
Now you are in Fastboot mode and with your PC you can flash another recovery image.
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
kabauterman said:
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
Click to expand...
Click to collapse
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I never said I was new to Android. I was new to the ASUS stock tablet recovery orientation (its landscape as I found out). Hence, hit up twice, wiped data. I am by no means new in general. I did not fix the problem. I requested an RMA with Newegg and it was approved I said the issue with it was bad screen bleeding (no lie but it is normal for this tablet but bad was exaggerated) In any case! RMA approved should be getting my new unit Tuesday!
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
fix
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
Just follow this method and you will be fine
http://forum.xda-developers.com/showthread.php?t=1755576
kabauterman said:
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
Click to expand...
Click to collapse
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
GRIM1337 said:
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
Click to expand...
Click to collapse
Any resolution to this other than the RMA?
HelgesenJ said:
Any resolution to this other than the RMA?
Click to expand...
Click to collapse
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
MartyHulskemper said:
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
Click to expand...
Click to collapse
One more who used ROM manager recently and now I have a nice tray for serving beers :crying:
I'm having the same issue with APX available by powering on the transformer holding volume+up but with no nvflash backup.
I don't understand why people keep using ROM manager to install recovery, this is a death wish to your device. If they read all the "How to" posts, none of them instructed to use rom manager to install recovery, so I don't know where they got this idea from???? beat me!!!
GRIM1337, you need RMA to send out for repair. Sorry but there's no hope to recovery this.
Didn't use ROM Manager
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
3c said:
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
Click to expand...
Click to collapse
How did you get into fastboot mode for your device??
buhohitr said:
How did you get into fastboot mode for your device??
Click to expand...
Click to collapse
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
3c said:
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
Click to expand...
Click to collapse
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Re: Help needed i will try
OK WHAT YOU HAVE DONE IS WIPED THE OS FROM THE UNIT...AND LEFT THE BOOTLOADER FILES...SO THERE ISNT
ANYTHING TO BOOT TO AT THE MOMENT... I DID THIS LAST WEEK... IT WAS A BIT SCARY AND FRUSTRATING UNTIL
I FIGURED OUT HOW TO FIX IT.. ITS NOT HARD. ILL PUT DOWN HERE WHAT I DID...
1. DOWNLOAD THE GOOGLE NEXUS 7 TOOL KIT... ( this is a very good rescue tool )
2. RUN IT... INSTALL THE DRIVERS... REBOOT IT ALL AND START THE TOOL KIT AGIAN WITH YOUR TRANSFORMER
CONNECTED TO USB...
3. YOU SHOULD SEE THE SERIAL NUMBER OF YOUR TABLET AT THE TOP OF THE PAGE IN THE TOOLKIT...
IF SO..YOUR ALMOST DONE !
4. THERE ARE MANY CHOICES..SOME WORK SOME DONT ON THE TRANSFORMER...
5. I CHOOSE THE ROOT OPTION...
6. NOW..WHEN IT GETS TO THE PART WHERE IT SAYS ARE U IN FASTBOOT MODE.. SAY NO !!! THAT WILL ACTUALLY
PUT IT IN FASTBOOT AND THEN PROCEED AS DIRECTED ON THE SCREEN TO ROOT...
THATS WHAT I DID...CAUSE I NEEDED ROOT AND I HAD A STUCK BOOT LOOP JUST LIKE YOU.....
BASICALLY YOU NEED TO ROOT IT AGIAN AN THEN REBOOT AND TRY TO GET INTO CWM..OR HAVE IT REINSTALL CWM...TO FLASH A ROM...THAT WORKS..

[Q] How to unbrick my tf300

Hi there, Can anyone help me to unrick my tf300, its stuck on the logo screen.
I have try many things, some guys from hong kong tell me i have to use APX mode to sort the problems out, I manage so far.
Drivers I download the is Universal_Naked_Driver_0.7, also use nvflash drivers, both I try. i still get te samethings when I try to use the nvflash
I turn on tf300 with volume up, few seconds the screen went blank, and hear a beep from my pc, so is connect alright.
I type download.bat command, with prime 1.4 rom in the same folder. after few seconds I get
nvflash start
unknow usb found.
Can anyone tell me what i done wrong here.
can someone show me some step by step.
otherwise is a waste of money, the tf300 not working.
THankyou
acelaw said:
Hi there, Can anyone help me to unrick my tf300, its stuck on the logo screen.
I have try many things, some guys from hong kong tell me i have to use APX mode to sort the problems out, I manage so far.
Drivers I download the is Universal_Naked_Driver_0.7, also use nvflash drivers, both I try. i still get te samethings when I try to use the nvflash
I turn on tf300 with volume up, few seconds the screen went blank, and hear a beep from my pc, so is connect alright.
I type download.bat command, with prime 1.4 rom in the same folder. after few seconds I get
nvflash start
unknow usb found.
Can anyone tell me what i done wrong here.
can someone show me some step by step.
otherwise is a waste of money, the tf300 not working.
THankyou
Click to expand...
Click to collapse
You flashed a PRIME rom to your tf300?
First of all, we should know which firmware do you have before your tablet doesn't boot (Stock ICS, JB, Custom Rom).
Then, you can use fastboot to recover your tablet (i did it a lot of times). Try steps below:
1. Download latest oficial Asus firmware (V10.4.2.13). BE SURE to download your region (WW, US, etc...)
2. Extract downloaded zip and take blob file.
3. Download Android SDK and install them on C:\ (http://developer.android.com/sdk/index.html)
4. Execute SDK downloader and mark tools and platform-tool options for download.
5. OPTIONAL add tools and platform-tool folder to PATH, after that test if fastboot command runs on CMD.
6 Copy blob file on same SDK folder.
7. Connect TF300T with usb cable and put it in Download Mode (USB icon on recovery menu)
8. Wait until drivers are installed.
7. Open CMD, go to Android SDK folder and then type command below:
fastboot -i 0x0B05 flash system blob
wait 2 or 3 minutes and then you'll see a message that send and write was OK. Now type this command:
fastboot -i 0x0B05 reboot
And It should boot again.
ppmeis said:
First of all, we should know which firmware do you have before your tablet doesn't boot (Stock ICS, JB, Custom Rom).
Then, you can use fastboot to recover your tablet (i did it a lot of times). Try steps below:
1. Download latest oficial Asus firmware (V10.4.2.13). BE SURE to download your region (WW, US, etc...)
2. Extract downloaded zip and take blob file.
3. Download Android SDK and install them on C:\ (http://developer.android.com/sdk/index.html)
4. Execute SDK downloader and mark tools and platform-tool options for download.
5. OPTIONAL add tools and platform-tool folder to PATH, after that test if fastboot command runs on CMD.
6 Copy blob file on same SDK folder.
7. Connect TF300T with usb cable and put it in Download Mode (USB icon on recovery menu)
8. Wait until drivers are installed.
7. Open CMD, go to Android SDK folder and then type command below:
fastboot -i 0x0B05 flash system blob
wait 2 or 3 minutes and then you'll see a message that send and write was OK. Now type this command:
fastboot -i 0x0B05 reboot
And It should boot again.
Click to expand...
Click to collapse
but fastboot need a unlocked bootloader, no?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Yes, that's right, but I suppost if he tries to flash a custom rom he has already unlocked his device. You can't flash any rom without unlock bootloader.
I cant do anything apart from get on to apx mode, from apx mode how do I use command to flash back.
My tf300 is ics, unlock.
when i connect usb to pc. i press power and volume up. thats only things i can do.
so what do i do next?
thanks.
The same problem.
I only see: "device is unlocked" or something like that. And nothing go on.
Is it totaly bicked or is there any chance to restore it?
Please advice.
Did anybody ever figure this out. I'm in the same boat. Can't do vol down+power to get to recovery. But if i do volume up+power it shows in device manager as transformer prime apx interface (even though it's just a tf300)
bigworm82 said:
Did anybody ever figure this out. I'm in the same boat. Can't do vol down+power to get to recovery. But if i do volume up+power it shows in device manager as transformer prime apx interface (even though it's just a tf300)
Click to expand...
Click to collapse
Try this link.
http://forum.xda-developers.com/showthread.php?t=2034866
no way to unbrick tf300t
Funny, I bricked my tf300t without doing anything. One day it just got stuck in asus screen.
tried to recover, nothing happended.
tried hard reset. Nothing.
Wipe data: result: bricked tablet.
I'm looking for information it is defintely impossible to unbrick it.
Anybody else with the same situation can tell you that.
Nobody has even been able to do it.
If you send it to Asus they provide a new tablet.
Conclusion:
TF300T is a terrible product, as any other asus product i assume. Amazing that you can brick a tablet without even trying to flash it or without even being connected to a computer.
It bricks by itself. Hundreds of other users can confirm it.
My advice: dont by asus products
If you already have one, dont use wipe data as anybody who has done it has ended up with an expensive useless brick.
Odp: [Q] How to unbrick my tf300
I don't agree witch this, only think what you not should use is t the wipe data from bootloader menu - I already flashed many times not working kernel, get really often bootloop - the problem is - much users going to made stupid things when the get a soft bootloop - If you get this first try wipe data from recovery, if this won't help, try to format data from recovery - often happends that the ext4 filessystem get broken. Recovery should allowa us to run fsck on data - I fixed my bootloops many times with it without loosing my data.
Sent from my GALAXY Cooper
OP,
I think your anger is misdirected. The device, as it comes out of the box, works 100% without issues. YOU as a user decided to make changes that could potentially brick it. YOU chose to follow the steps with the full disclaimer that it can/may brick your device. So at the end of the day, its' not the fault of ASUS or the device for "bricking itself"; the responsibility of your actions lies on your own shoulders.
That being said, Asus will not provide warranty support for a tablet that has been unlocked. This is clearly stated in their unlocker app. So no, they won't "send you a new tablet" if you send it to them (unless you pay out of pocket for the repairs).
I've done just about as bad of a brick as I possibly can on my tablet and recovered just fine. It was just a matter of being CAREFUL, reading instructions three times before l followed them, and asking lots of questions. But what ultimately saved me was the NVFlash tool, and for that I am eternally grateful.
Just my two cents.
opethfan89 said:
OP,
I think your anger is misdirected. The device, as it comes out of the box, works 100% without issues. YOU as a user decided to make changes that could potentially brick it. YOU chose to follow the steps with the full disclaimer that it can/may brick your device. So at the end of the day, its' not the fault of ASUS or the device for "bricking itself"; the responsibility of your actions lies on your own shoulders.
That being said, Asus will not provide warranty support for a tablet that has been unlocked. This is clearly stated in their unlocker app. So no, they won't "send you a new tablet" if you send it to them (unless you pay out of pocket for the repairs).
I've done just about as bad of a brick as I possibly can on my tablet and recovered just fine. It was just a matter of being CAREFUL, reading instructions three times before l followed them, and asking lots of questions. But what ultimately saved me was the NVFlash tool, and for that I am eternally grateful.
Just my two cents.
Click to expand...
Click to collapse
I have problem that my partitions won't mount at all. I have access to fastboot, CWM, and adb but no matter what i cannot access my partitions and so i cannot install zip from CWM. When i try blob within fastboot my tablet just freezes.....
Hi, what happens if I have no access to fastboot? It loops in the ASUS logo and what ever I do, can't gain access to recovery because it doesn't get into fastboot. So how to solve it via APX? Thank you.
You wont solve the problem unless youve done a nvflash backup. If you tablet is recognised as APX while plugged in PC, then you have an unrecoverable brick. If nothing appears when you plug it, then try on another PC.
Sent from my TF300T using xda premium
unbrick tf300
ilyuha1108 said:
You wont solve the problem unless youve done a nvflash backup. If you tablet is recognised as APX while plugged in PC, then you have an unrecoverable brick. If nothing appears when you plug it, then try on another PC.
Sent from my TF300T using xda premium
Click to expand...
Click to collapse
Hi,
I am having a similar problem to the one described. I have unvblocked my TF300T and installed CWM recovery (v. 6.0.2.3), but it can't mount any filesystem, so I can not flash anything. The boot menu is gone (RCK, wipe tablet, android) and when I switch the tablet on It just goes to CWM. If I connect the tablet to a PC, I can send commands with adb from my win 7 PC (for instance "adb reboot" will reboot the tablet), but fastboot doesn't work (it keeps "waiting for device"). Prior to this my android version was JB 4.2. I didn't make any backup, so I am fearing the worst outcome. Did I brick my tablet for good?
Thanks a lot for any reply.
TF300T blocked on boot screen
hello everybody,
my name is jonathan, and i have a very big problem.
My Asus TF300t is blocked on boot screen after try to install a new rom on JB 4.2.2.
>My clockworkMod reconvery is v6.0.1.0.
I tried to install several roms, offical or not but the problem is the same, "The device is unlocked" on the boot screen Asus...
I read the previously posts and :
- i installed on my pc the sdk
- i dowload the "blob" file and i placed it on tools directory
- but, the actually problem is whis the lign "fastboot -i OxOBO5.... (i have copied and paste it on schell command) and enter
load_file: could not allocate 820157833 bytes
error: cannot load "blob": not enough space
can you help me please ?
i want to resolve this problem with you to install the best rom for this model.
Thank you very much and sorry for my english, i am french but i understand your paragraph.
See you soon
Jonathan
If you have mounting / PIT errors you could try my solution as described here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
no guarantee though but it basically wipes your device so that you should be able to flash the blob file back.
also if your tab still is ICS- check if you are using the correct recovery - also bear in mind that cm10.1 afaik uses the new 4.2 bootloader and probably wont work with ics based PIT devices.
gl
same problem of space
Buster99 said:
If you have mounting / PIT errors you could try my solution as described here:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
no guarantee though but it basically wipes your device so that you should be able to flash the blob file back.
also if your tab still is ICS- check if you are using the correct recovery - also bear in mind that cm10.1 afaik uses the new 4.2 bootloader and probably wont work with ics based PIT devices.
gl
Click to expand...
Click to collapse
Hello man,
I try your method but the problem is the same when i want to copy the blob file, "not enough space ..."
fastboot erase system OK
fastboot erase recovery OK
fastboot erase userdata OK
fastboot erase boot OK
fastboot erase misc OK
fastboot erase cache OK
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob PROBLEM
The message is the same like previously, always the problem of space.
I tries the method by copy the blob file on different directory on my computer and on a usb key too.
Always the same problem of space
I think the problem is the space on the tablet but i dont' understand. I erase system, recovery, userdata, boot, misc, cache, i think the tablet is empty.
Can you help me please ?
Thank you very much
Jonathan
which blob file did you use? Was the zip appropriate for your region? also what was the last stock rom version you ran - you said you wanted to update to 4.2.2 - what was the old version?
-Buster

flashed wrong recovery, now in boot loop- help!

I updated to the newest version from asus site Version WW_V10.6.1.8 and then by mistake flashed the latest version of TWRP recovery. now the tablet is in recovery boot loop. I tried the next command: "adb reboot bootloader" and managed ti get fastboot to work but adb shell does not work.
The weirdest thing is when I press the green android icon in boot loader screen, the system boots normally!!!! but!!! when i do restart it always boots into the twrp screen. the only way to boot the system is with your command. I tried to flash the patched recovery which works with the new firmware (the flash is ok) but i cant pass the recovery screen. How can I get rid of this recovery????
If fastboot is still working ok I would suggest re-flashing the stock 4.2.1 (10.6.1.8) system blob. After doing so you will be completely stock again, so you'll have stock recovery and no root. You can then root again & flash the patched twrp again.
Either of these two threads has the info & commands needed as well as links to the patched twrp for the 4.2.1 bootloader.
[GUIDE] Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
pjc21 said:
If fastboot is still working ok I would suggest re-flashing the stock 4.2.1 (10.6.1.8) system blob. After doing so you will be completely stock again, so you'll have stock recovery and no root. You can then root again & flash the patched twrp again.
Either of these two threads has the info & commands needed as well as links to the patched twrp for the 4.2.1 bootloader.
[GUIDE] Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Click to expand...
Click to collapse
i did it. it still does the same thing. goes into recovery each time i turn on the tablet. it flashes but does nothing in the same time. is there any way to flash a new recovery or a new rom from inside the system??
tainka said:
i did it. it still does the same thing. goes into recovery each time i turn on the tablet. it flashes but does nothing in the same time. is there any way to flash a new recovery or a new rom from inside the system??
Click to expand...
Click to collapse
If when you flash the system blob via fastboot & you do not get the blue progress bar on the tablet this means that your fastboot is dead with no known fix. This seems to be caused be flashing the incorrect recovery on 4.2.1 (10.6.1.8) bootloader.
To test:
after running the command "fastboot -i 0x0b05 flash system blob" on the command prompt on pc it will say complete but you will get no progress bar on the tablet, after this command run "fastboot reboot" if the tablet does not reboot to this command then you are in the below group sorry.
http://forum.xda-developers.com/showthread.php?t=2179874
pjc21 said:
If when you flash the system blob via fastboot & you do not get the blue progress bar on the tablet this means that your fastboot is dead with no known fix. This seems to be caused be flashing the incorrect recovery on 4.2.1 (10.6.1.8) bootloader.
To test:
after running the command "fastboot -i 0x0b05 flash system blob" on the command prompt on pc it will say complete but you will get no progress bar on the tablet, after this command run "fastboot reboot" if the tablet does not reboot to this command then you are in the below group sorry.
http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
there is no blue progress bar. so there is no solution for that?
tainka said:
there is no blue progress bar. so there is no solution for that?
Click to expand...
Click to collapse
Sorry to say but no.
The only solution is to replace the motherboard, replace the tablet or send to asus for repair which will cost about the same as a new tablet.
Replacing the motherboard looks like the cheapest way to go as you can pick up a second hand tablet with a broken screen but still has a good motherboard for just over $100 on ebay.
pjc21 said:
Sorry to say but no.
The only solution is to replace the motherboard, replace the tablet or send to asus for repair which will cost about the same as a new tablet.
Replacing the motherboard looks like the cheapest way to go as you can pick up a second hand tablet with a broken screen but still has a good motherboard for just over $100 on ebay.
Click to expand...
Click to collapse
the funny thing is that the tablet boots in cold boot and works perfect. I just cant reboot it of turn it off. is it worth the motherboard replacement?
tainka said:
the funny thing is that the tablet boots in cold boot and works perfect. I just cant reboot it of turn it off. is it worth the motherboard replacement?
Click to expand...
Click to collapse
Well that's the thing, you can leave as is but now don't have the option to flash anything else until there is a fix that may or may not come along.
Seeing that you still have a working os it really depends on what you want out of the tab.
It is a very weird issue & I don't believe that the motherboards are actually fried in any way but rather locked up somehow in a conflict between the recovery & bootloader but not sure on that & not sure if there will be a solution for this. So it's really up to you. Sorry I could not be of more help here.

[Q] Did I really hard brick my TF300T?

Today I felt ambitious and tried to install a new JB rom (AOSPA 4.2.2). The instructions said that if I had 3 icons I would be on JB bootloader and that I would need to upgrade to the latest TWRP 2.5.0.0 (I was on 2.4.4.0). Well, what I missed is the fact that there were two different versions of 2.5.0.0 (one specifically for JB 4.2) and of course I flashed to wrong one.
Now when the tablet boots it goes straight to recovery and asks for a PW (I don't know the password and never set one). I can select cancel which lets me into the main menu but none of the functions actually have write access. Nothing mounts or lets me gain access to the internal memory. When I try to reboot it immediately goes back to recovery, never letting me get back into fastboot to install the correct version.
Reading some forums and doing some other google search I don't find anyone with exactly the same problem, but it seems that I cannot get out of this mess. I know that nvflash is out of question since that is not working on JB yet.
If anyone has encountered a similar issue or knows how I could potentially get fastboot to trigger again so I can flash the correct version of recovery, that would be a great start.
Thanks !!
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
pjc21 said:
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
Click to expand...
Click to collapse
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
anosis said:
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
Click to expand...
Click to collapse
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
pjc21 said:
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
Click to expand...
Click to collapse
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
anosis said:
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
Click to expand...
Click to collapse
Miraculously the tablet will allow me now to cold boot into the previous rom. That at least makes it usable again, but it probably means that I am stuck on this. Also strange is that the tablet now no longer is recognized as a USB device. I cannot access the internal ram??
Under 'About Tablet' my build # shows 10.6.1.14.4/US DEODEX. Not sure if this might help in fixing the recovery issue?
Anyway I am glad I don't have to spend money to get a replacement, but sure hope I can fix the existing recovery image issue.
So tried to flash back the previous version of TWRP and it will not. Even though the fastboot command prompt shows a successful flash nothing appears to be changed, which refers to the original issue that states that I am stuck on whatever rom is on this tablet.
Is the reason I cannot flash back an older or correct version because there is a permission issue? Is there something I can do directly from within the rom after it boots up, like the shell emulator?

[Q] Custom ROM on TF300T

HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
robscar said:
HI all,
I am VERY new to this custom ROM stuff, and I am a bit confused. I have an ASUS TF300T Transformer Tablet. It has 4.2.1 loaded, build is JOP40D.US_epad-10.6.1.12.3-20130416. If more particulars are needed, I can provide.
I have rooted the tablet (I used motochopper to gain superuser access), thinking that would allow me to load a custom ROM. I was WRONG (as most of you probably know). I want to load a custom ROM (CyanogenMod), and also not use the ASUS preloaded software. I want something with less bloat, is faster, and something I can customize at will.
So....I have read a ton of posts on this, but I can't seem to find a step by step single, simple process to accomplish this daunting task. Simply put, I need step by step instructions that can get me where I want to be. At this point, I'm not so sure I could be more confused! LOL!
Anyone who has done this, or is experienced with this, I could use some major league assistance!
I want a faster, more "open" tablet. I also know I don't want to brick it. I definitely don't need a 300.00 paperweight!
Any help would be greatly appreciated.
Thanks!!
Scar!
Click to expand...
Click to collapse
You need a custom recovery! download twrp here: http://techerrata.com/browse/twrp2/tf300t
DOWNLOAD THE ONE THAT SAYS "openrecovery-twrp-2.5.0.0-4.2" and flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob" make sure you rename the blob to "twrp.blob"
*update your info your bootloader is "10.6.1.15.3" instead of "10.6.1.12.3"
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You can also follow this guide. It explains what you need to do pretty well. But you do need a custom recovery, which i prefer TWRP http://forum.xda-developers.com/showthread.php?t=2187982
I was confused at first too. I think they need to change the wording in the tutorials. They say "If you're on JB bootloader, this twrp, if you're on 4.2 BL, that TWRP" and i was just thinking... WTF, both of them, 4.1 and 4.2 are jellybean.... it should be changed to 4.1 BL and 4.2 BL, none referred to as JB.
Sent from my TF300T using Tapatalk 2
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
robscar said:
So...does my tablet need to be unlocked first? What do I do once TWRP is loaded on my tablet? When you say "flash it with fastboot in cmd " fastboot -i 0x0B05 flash recovery twrp.blob". What does this mean? This is where it gets very confusing.
Click to expand...
Click to collapse
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
I've a TF300TG but I think my question is associated to the title of this thread. Do I have to note the sku of my Pad or isn't that important when I flash a custom Rom?
In the threads of many custom Roms I've read nothing about the sku. So I'm not sure if I have to take care for this.
Sent from my HTC One X using xda app-developers app
noahvt said:
if you installed root on your device you should have adb and fastboot, right?
if you are on windows(pc) press the windows key + the R key and type cmd in the search box, then press enter now navigate to the adb/fastboot directory on your pc by typing "cd <the location of the file>" then plug in your tablet in fastboot and type " fastboot -i 0x0B05 flash recovery twrp.blob" what does this do? this command flashes twrp over the stock recovery, with twrp you can install custom roms! after you have done this download a rom you like (watch out for bootloader versions! if you are on stock 4.2.1 i would reccomend the latest unofficial AOKP or the latest official cm10.1) if you download a rom you can see it is a zip file, place this zip file on your sdcard and power up your tablet in bootloader by holding volume down + power button till icons pop up! now press the volume up key when the RCK icon is blinking! now twrp should start, now click on wipe and then advanced wipe and wipe system data cache(you don't need to wipe your data if you prefer to keep it!) now go back to the main menu of twrp by pressing the home button in the top right corner, now click install and navigate to the directory you have placed the rom in, after install reboot!
Click to expand...
Click to collapse
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
robscar said:
OK, first, I am on a MAC. I have "terminal" for CMD lines, so, it should find whatever files I need it to find just as the windows CMD block will.
I have "fastboot and ADB" in a folder on my desktop, I have named the folder "android". I also downloaded the TWRP for 4.2.1 (renamed to TWRP.BLOB). I think I have all the files I require, it's just a matter of what steps to take. I also have the CM 10.1. This is the ROM I would like to use.
I was also reading that using TWRP, I am not supposed to wipe. I guess, theoretically, I want to be able to boot to the original ASUS ROM in case anything goes wrong. Otherwise, I wouldn't have a ROM to boot from.
I'm not sure if everything I am saying is correct, again, I am very new to this and trying to undertand exactly what I am doing.
Click to expand...
Click to collapse
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
diesburg said:
The fast boot and adb you have are most likely windows files. Not sure if there is fast boot and adb for Mac.
Sent from my TF300T using Tapatalk 2
Click to expand...
Click to collapse
I got these files from the SDK download for MAC.
robscar said:
I got these files from the SDK download for MAC.
Click to expand...
Click to collapse
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
robscar said:
Any possibility of kicking this to the top and maybe getting this tablet accomplished tonight? I believe I have all the files I need (for MAC), and I am ready to go. I just need to know exactly what to do.
HELP!! LOL!!
Click to expand...
Click to collapse
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
diesburg said:
I can TRY to help. I have no mac, never used one, dont know the procedures for getting the drivers and stuff installed on mac. So, im going to assume you have the fastboot drivers installed properly.
NOTE: IF YOU'RE TABLET BREAKS, NEVER TURNS ON AGAIN, OR GOES UP IN SMOKE BECAUSE OF MY DIRECTIONS, IT'S ALL YOUR FAULT AND RESPONSIBILITY NOT MINE. GET OVER IT AND BUY A NEW ONE.....LMAO.... really though, i am helping as best as i can and you always run a risk flashing devices and thats your risk, not mine.... but if you follow my directions exactly, you will be jsut fine and not have a broken device...
First, make sure you're on the latest update from asus. Should be a bootloader ending in 15.3 and android 4.2.1 .
Second, unlock your bootloader. Unlocking the bootloader is quite simple. Download this: http://d-h.st/86c Install it on the tablet and open the app (its a RAR file so it needs extracted first) Follow the directions it gives you, if i remember correctly, you just click yes or something, tablet reboots, and the bootloaders unlocked. If it sucessfully unlocks, when you first turn the tablet on, in the top left corner of the screen, it will say unlocked.
After bootloaders unlocked, turn the tablet off. Power on the tablet by holding the power button and the volume down button at the same time. This will take you into bootloader mode. One quick thing to make sure you are on the latest bootloader. The bootloader screen should have 3 icons to choose from, if it has 4, you are on the old/wrong bootloader and need to go back and update your system before proceeding. If 3 icons, you're good to go, plug the usb cable in the tablet and in your computer.
Download TWRP recovery now. This is the part where you dont wanna screw up, downloading and flashing wrong recovery can equal a broken tablet. Download this exact TWRP recovery: http://diesburg.co/tf300t/twrp/openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Put that file in the folder where fastboot is.
Now in your terminal/command line, go to the directory where fastboot is. With tablet plugged in and in bootloader mode like mentioned above and terminal in the fastboot folder, type: fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob and press enter .... this will flash TWRP recovery to your tablet using fastboot.... if you get something like "waiting for device" in your terminal window after typing this and it never gets past that, thats where i cant help, drivers for fastboot or something isnt right.... if it works, hell yea, onto the next step....
Reboot the tablet, type: fastboot -i 0x0B05 reboot and press enter.... let android fully boot up, copy your ROM to your tablet and dont forget the gapps package for the rom..... now turn the tablet back off......
power the tablet back on like before holding power button and volume down.... once in here, RCK will already be highlighted, if its not, use your volume down key to get it highlighted... once highlighted, hit volume up and this will boot the twrp recovery you flashed......
Once in TWRP, (FIRST DONT FORGET CLICK BACKUP AND MAKE A BACKUP OF YOUR CURRENT ROM!!!) now, make sure you can see your cyanogenmod rom file and gapps by clicking install and going to the ocation where its at, if you see the 2 files, click the back button to the main screen.... on the main screen, click : Wipe, then click factory reset.....after that, go back to the wipe screen, and click system to wipe the system partition..... now go back to the main screen again....
Click install, then click to install the cyanogenmod rom.... after it installs, install the gapps package.... after that, you SHOULD be good to go, reboot the tablet by clicking reboot to system.....
I think that covers everything..... now in the future for flashing other roms, always wipe before flashing and flash the roms the same way you did this one.... just so you know, not ALL roms require gapps package.... most specify whether they do or not....
Any problems, let me know unless its the "waiting for device" thing, i cant help with mac drivers, someone else will have to
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
So, no matter what I do, the bootloader has to be unlocked, correct?
robscar said:
So, no matter what I do, the bootloader has to be unlocked, correct?
Click to expand...
Click to collapse
for a custom rom, as far as i know, yes
but for just root on stock rom i believe theres ways to root stock without unlocking the bootloader
Sent from my TF300T using Tapatalk 2
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
robscar said:
I simply cannot seem to get the MAC to do this. I just don't know what command lines to use in the "terminal". I am amazed that no one has flashed their tablet with a MAC.
Anyone who has done this with a MAC, please drop a line if you can. I would really like to get this done if at all possible.
I am unlocked, I get all the way to the "flash" commands, and then it seems to not want to cooperate.
HELP!
Click to expand...
Click to collapse
It's most likely drivers.
http://forum.xda-developers.com/showthread.php?t=1917237
Maybe that'll help?
Sent from my TF300T using Tapatalk 2
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
robscar said:
I wanted to close out this thread and thank everyone who jumped in to try to assist me. I was not able to flash my tablet, nor get the Cyanogen mod loaded. Not sure why, but, as I try to load TWRP, I get a "permission denied" error.
Eventually, I will get my hands on a windows computer and give this another shot. But, it should have worked on my MAC as easily as anything else. Not sure exactly what I am doing wrong, but, my tablet is working just fine so, I know I did not "mess" anything up (YAY).
If someone has been able to "flash" and put a custom rom on their ASUS Transformer using a MAC computer, please get with me and let's chat!
Again, thanks everyone for taking some time to walk me thru this! I learned a lot, so your efforts did not go to waste! I great appreciate it!
Scar!
Click to expand...
Click to collapse
not sure exactly how a mac works but i believe its some sort of linux. can you by chance start the terminal with "administrator" priveleges or type "su" in the terminal to get root priveleges? Just my thoughts with a "permission denied" error, you dont have administrator/root access.
In that link i shared above about mac and fastboot, it says to use " ./ " in front of every command. So try the fastboot commands i said above to flash the recovery but do it with ./ infront like this: ./fastboot flash commands
Sent from my TF300T using Tapatalk 2
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
robscar said:
Well, I used Motochopper to root my tablet, so, I'm not quite sure exactly what you mean. So, I am rooted, my BL is unlocked.
My tablets boots in "fastboot", I just can't seem to get the flash done. At this point, I am not so sure I could be more lost. LOL!
Click to expand...
Click to collapse
In the steps I told you above. The part where you do the fastboot commands in the terminal. "fastboot flash 0x(somenumber) recovery twrp.blob"
put a ./ in front of the fastboot command... so its "./fastboot flash 0x(thatnumber) recovery twrp.blob"
Sent from my TF300T using Tapatalk 2

Categories

Resources