Related
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
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
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
ericsundiu said:
My infinity just passes its warranty and it is in newest stock firmware and not rooted. I think it is too slow and laggy and i would like to make some change by flashing new rom. As i know, the newest firmware .10 can not be unlocked and flash rom? So do i have to downgrade to .8 to make it work?
Click to expand...
Click to collapse
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
ericsundiu said:
do you mean i can still unlock with the 10.6.1.14.10 firmware? using the official unlock tool?
Click to expand...
Click to collapse
Unlocking and rooting are two different things. There is no known root method at this time for the 10.6.1.14.10 firmware. The Unlock Tool should still work.
I don't think it's a question which firmware you have - sometimes it works like a charm and other users cannot unlock at all due to incorrect or incomplete S/N database on Asus servers. At least I have not heard anything that people have trouble unlocking after the last update.
Just download the latest version, v8 I think, install and run it. The worst that can happen is it fails.
Do yourself a huge favor and educate yourself thoroughly before you try to flash custom software to the tablet.
There is little risk in flashing a custom rom IF you do it right. But yesterday night I tried to help someone who did it wrong and hard bricked his tablet. Read 3 times, ask twice, flash once!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot
Click to expand...
Click to collapse
For flashing via adb and the staging partition, Android must be rooted. Fastboot works without root.
I did a clean wipe of my tablet and installed 10.6.1.14.10 onto my tablet.
I have unlocked the bootloader, but when booting up I then have the default recovery and rom supplied by Asus with no root.
I tried motochopper and debugfs method, and as described above neither work, the cmd prompt windows just record failures.
Read this forum regarding what is what (fastboot, root, unlocked etc.) and why you do them
http://forum.xda-developers.com/showthread.php?t=1833212
The way I gave root to the stock rom was by loading into fastboot mode and pushing a twrp image to my tablet off CHROMI rom site. I then used that to root the system. To be honest I did not need to root as I could have just then flashed the CHROMI custom rom which comes with SU anyway....
Get fastboot into a folder and also copy the TWRP recovery img inside the fastboot folder
Attach your device to the PC
Start fastboot mode by switching off your tablet then switching on in bootloader by holding down power on and volumn down
Connect tablet to PC (need approperiate drivers)
Open cmd prompt as admininstrator and goto directory with recovery image in the fastboot folder
Type the following commands:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot -i 0x0B05 reboot (though I don't think i typed this if honest, struggling to remember)
Unplug tablet from the PC and reboot into recovery mode
If you got the image of twrp from CHROMI site which includes bootloader also, i think it includes SU, therefore just exit and close recovery and it should ask to install SU. Select yes
Reboot the device
Your device is now rooted, though think you need to run SU in the tablet to get it fully setup.
Sorry this is not 100% perfect, I will recall what I did tonight when at home in front of PC with files.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Click to expand...
Click to collapse
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
M1ster1 said:
Hello Berndblb (and everybody else ),
I'm quite a Noob around here as you can see and I've the same problem.
My TF700 has the build : US_epad-10.6.1.14.10 and the Android version : 4.2.1
I followed the instructions from this thread and now my tablet is unlocked.
I want to flash it to run under the last version of Cromi and I've read the instructions :
"- Step 1 - Coming from Stock Asus 10.6.1.x – INSTALLING TWRP 2.5 on 10.6.1.14.4/8"
Okay, so now I need to install TWRP, so I followed the guidelines : to do so, the easiest way is to install goomanager on the playstore.
Okay let's do this, I go to the playstore and I read the first line : This app is for ROOTED USERS ONLY!
Okay, so now before doing anything, I need to root my TF700, so I go back to this thread and I see that the easiest way to do it is by using motochopper but motochopper doesn't seem to work on 10.6.1.14.10.
As you said yourself previously before, I need to downgrade to 0.8 before using motochopper to root my tablet.
Okay let's do this, I search many threads and I've finally used this method :
1/ Download the previous firmware from asus website for my tablet (us version) and unzip it to get another .zip : US_epad-user-10.6.1.14.8.zip
2/ Put it into the root of my internal sd card
3/ Boot with "power + vol down" then after the splash screen put "vol up".
4/ Android start to work to add the downgrade version.... then I get the sick droid !
So, now I'm quite stuck here, I can't downgrade this way... any advices ?
Click to expand...
Click to collapse
You can try to install from your system, not stock recovery. You need to boot your system normally and look in the lower right corner at your notification. It should notify you that their is an update for you. When you click on it, it will walk you through the update process. You need to make sure that you have only one zip file in your directory which is the Asus firmware that you want to update.
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
LetMeKnow said:
You can also use fastboot to install the TWRP. I don't think you need to root to install a custom recovery by using fastboot if you already unlocked your bootloader. IMO, I think fastboot is easier and faster than motochopper because of rooting process...
Click to expand...
Click to collapse
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (right click on your device, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your phone.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
Good job! Congrats!
And thank you for putting this guide together. That's what I call sharing! :victory:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
M1ster1 said:
Thanks LetMeKnow !
It was the right way to do it (Berndblb advised this also here).
It worked and I've now TWRP installed ! :victory:
But it wasn't so easy, fortunately there's plenty of help around here
I'll write here quickly how I did it, it could help someone, who knows, sharing doesn't hurt, even if I'm sure there's plenty of different methods to do it.
I found some help in this guide because the explanation under "Download - Recovery Image / Fastboot Method:" from the TWRP page is a bit rough for a beginner like me.
First I need to mention that I've Windows XP on my computer.
As you can read here there's 3 different ways to install TWRP on the TF700, the first one is the easiest one, but you need to be root, if you're unrooted like me and you want to skip rooting, let's install TWRP via fastboot.
Requirements :
- Bootloader must be unlocked. Very easy following this thread.
- ADB and Fastboot must be installed on your computer. You can follow this guide, this way you'll install them from the latest version of Android SDK and avoid any trouble.
- You should have the USB driver for your TF700 installed on your computer. I've read multiple times that that the official drivers could create some trouble, and indeed it happened to me. So you can give a try, and if this doesn't work, let's go for the Universal Naked Driver.
- Download the last version of TWRP (the newest .blob file) from here. Rename it to twrp.blob and place it under C:/Android (or C:/Android-adb, depending how you've rename your folder containing adb and fastboot.exe).
Fastboot method :
- Before starting, you want to be sure that your computer recognize well your tablet, otherwise, you'll follow a tutoriel like me, enter the final command, press enter and watch... nothing ! just a prompt command blinking in front of you, because if the script don't find any device, it will just write nothing.
To be sure of that, turn on your TF700, Plug it to your computer via a USB cable, then enable USB debugging (Tap the Build Number 7 times under Settings, About Tablet and it will show up under Dev Settings).
Now, if you're under WinXP like me, it may be possible that the pc doesn't recognize well your tablet, and you'll probably have to play with your device manager (to go into your device manager right-click on My Computer and click Properties, In the System Properties window click the Hardware tab, In the Hardware tab click the Device Manager button then look for your device, click on it, uninstall drivers, then reinstall the naked driver mentioned before for example). You may find some help here or around here in the forum.
Once you think your tablet with USB debugging enabled is well recognized by your computer, try to open a command prompt (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box) and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed. If your device shows up, let's continue to next step, otherwise, you should continue to play with uninstalling drivers, reboot, installing others drivers...
- Turn off & Unplug your device.
- Enter fastboot mode : Keep pressing the Power button while holding the Volume down button till the screen responds then
1) If you have an old bootloader select USB icon, press Volume up button.
2) If you have the new 4.2.1 boot loader it automatically boot into usb mode, it should be written in the upper left corner something like this :
The Device is UnLocked.
key driver not found...booting os
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14-20130329" A03
Starting Fastboot USB download Protocol
I didn't know that and I found some answer here and here.
- Plug the TF700 to your computer via a USB cable. (and make sure no other android devices is connected to the computer)
- Open a command prompt in your computer (First, press Win + R to launch the Run dialog, then enter “cmd” in the dialog box).
Just to be sure (one more time) that your device is well recognized by the computer type “fastboot devices” (without quotes).
You should see at least one line with some numbers written.
Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
- Normally the TWRP recovery is now installed on your device !
To check that enter recovery mode : Boot with "power + vol down" then after the splash screen put "vol up". You should see that image, cool right ?
I don't take any credit for this quick explanation because I took all the informations from this forum (and from different other websites) and gathered them together for my own case, but I think this may help others.
A big Thanks to all the guys here who take the time to write, explain and help, that's great, keep it up the good work :good:
Click to expand...
Click to collapse
It is a nice written How to do list, good job... :good:
You can add these command for fastboot to your list instead of using the power button and volume down..
> fastboot reboot-bootloader # Exit fastboot and reboot into bootloader.
> fastboot reboot # Exit fastboot and reboot to your system
Good job.. :good:
FAILED (InvalidSize)
I am attempting to install a ROM on my Transformer Infinity as it pretty much sucks these days but am a complete NOOB. Have never attempted this with any of my phones or tablets, but figure I would try since these directions are so detailed. After following most the steps you have listed, I get the error below in the command prompt. Can someone please help, I tried searching XDA and Google to no avail. If possible please be as basic and speak in layman's terms b/c all this technical jargon goes right over my head. Thank you in advance!!!
Step followed:
- Then, change the working directory of the command window to the directory where you had placed the TWRP recovery file (twrp.blob) using the command “cd directorylocation” without quotes (probably, “cd c:\android“).
Then, in the command prompt, enter the command: fastboot -i 0x0B05 flash recovery twrp.blob
After the process finishes, You can unplug and reboot your tablet.
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
epps720 said:
Error:
c:\Android-ADB>fastboot -i 0x0B05 flash recovery twrp.blop
sending 'recovery' <8218 KB>...
OKAY [ 2.938s]
writing 'recovery'...
FAILED <remote: <InvalidSize>>
finished. total time: 6.633s
Click to expand...
Click to collapse
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Don't know if you cut and paste the error message or typed it up. But what I notice is that you named the recovery file .blop
It should be .blob
Another step to avoid simple errors: Place the recovery.blob file into the same directory with your fastboot file.
Right click in that directory to open a command prompt and then execute the command
fastboot -i 0x0B05 flash reccovery twrp.blob
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
epps720 said:
Thanks for the help but I'm still getting the same error. I did move the recovery file to the same folder and open the command prompt right from that folder but no luck. Any other ideas?
Thanks again.
Click to expand...
Click to collapse
Actually yes.
Just read in another thread about someone having the same problem as you, getting the incorrect file size error.
Download the TWRP 2.5 blob and try it with that file. I have no idea why, but TWRP 2.6 may cause this error.
At least that bloke got the recovery installed that way. Once you have TWRP, it's easy to upgrade to the latest version.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
I have no idea why, but TWRP 2.6 may cause this error.
Click to expand...
Click to collapse
The blob for TWRP 2.6.3 is bigger than the recovery partition. 2.6.1 should work.
berndblb said:
You don't have to downgrade.
After you unlocked your tablet, you can push a custom recovery through ADB or fastboot and use that custom recovery to flash a custom rom.
If you use this method you bypass rooting the stock rom altogether. Every custom rom is rooted already.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Ive had the same question as the OP, i also have a .10 version, i have a US sku, and i downlaoded said associating item but when I went but when i go to either do it with sd, or intewrnal sd, or how ever. through manual or through android, either method both resulted in error when trying to downgrade, i dont know if its because its a downgrade or what.
Ive some linux experience over the years, and have rooted and run custom roms in the past. im trying to achieve the same as the OP, fix my lag, and more options and tweaks.
I have the .zip of the rom i want whitch i found I liked the xcromi rom, so I downloaded it. so, i can put that in and name it what and how do i do the update than through the volume down + pwr combo into that menu? (not sure what its called) but i can't do sideloads because i can't havbe the ultity to sideload without rooting and i can't root with .10, so i have been trying to get past this single step all night and this morning now.
@M1ster1
Thanks for posting this guide. It doesn't do a perfect job however on the TF700t running Android build 10.6.1.14.10. Tried to use the "fix permissions" option in ROM Manager but failed due to insufficient permissions. I installed CWM Superuser and cleaned up the version of SuperSU (prefer Superuser anyhow)... updated the binaries and still no love when trying to correct the permissions, despite all tests showing the device fully rooted.
After a day of pulling my hair out I finally came across vRoot and after even longer found a guide in English. Ran that, again swapped out the Superuser that went with vRoot and again reinstalled Superuser. Used Ti to install as system app. After reboot ROM Manager was finally able to correct permissions and all is golden again.
Hi ,
My Transformer has 10.6.1.14.10 and I am trying to install TWRP thru fastboot as per "M1ster" instructions.
these are the results I see from my command prompt.
C:\Users\Ken>fastboot devices
015d2bbce7041e07 fastboot
C:\Users\Ken>cd c:\Android-adb
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
OKAY [ 0.066s]
writing 'recovery'...
OKAY [ 3.374s]
finished. total time: 3.441s
c:\Android-adb>
after I reboot and select RDK , i get the sick droid error,
I feel like I have missed something, hopefully somebody can point me in the right direction
Thanks
helihaole said:
c:\Android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (4 KB)...
Click to expand...
Click to collapse
Your "twrp.blob" apparently doesn't contain a recovery - it should be around 6 to 8 MB.
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
grimsonfart said:
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
Click to expand...
Click to collapse
Wrong command!
You can't flash whole ROM blob on 'system' (i.e. OS) partition because ROM blob contains bootloader, partition table, recovery, kernel, system and userdata, which are to be flashed to other partitions.
Therefore our Transformers have a 'ramp-up' partition called 'staging'. On reboot bootloader flashes the 'sub'-blobs of blob (blob.EBT, blob.SOS, blob.LNX, blob.PT, blob.USR) to their respective partition.
Use:
Code:
fastboot -i 0x0b05 flash [b]staging[/b] blob[enter]
fastboot -i 0x0b05 reboot [enter]
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
grimsonfart said:
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
Click to expand...
Click to collapse
This should work! However it will last along time. When tab reboots, you will see a blue progression bar, which sometimes seems to freeze. Let tab restart by itself.
If you don't succed, you might have a corrupt blob, either by downloading or by unzipping with an outdated winrar (suffered that myself).
Well, no luck first time. Exactly the same thing happened when using that command in CMD. Not sure if it's a problem with my PC or what... Going to re-download the files from ASUS.
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
I am doing this one a really old computer though (no access to mine atm). It's windows XP SP3, 1gb ram and intel celeron 1.8ghz i think. Not sure if it has anything to do with this but anyways.
grimsonfart said:
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
Click to expand...
Click to collapse
When you flash to staging, bootloader copies blobs to their partitions after reboot, while this happens, a blue progression bar is visible on ASUS Screen not on bootloader screen.
As you report it, you are probably not in fastboot mode.
Try to follow:
1. Press power + vol down -> bootloader screen appears with icon RCK blinking. Now you are in fasboot mode.
2. Connect tb to pc; tab should show up in Win's device manager as ASUS fastboot device(o.s.). If warning sign appears or 'unknown device' label, install proper drivers.
3. Open terminal window with admin permissions in fastboot folder.
4. Type
Code:
fastboot devices [enter]
-> device should be shown; if not: type
Code:
fastboot -i 0x0b05 reboot [enter]
tab should now reboot into OS; if not, fastboot doesn't work.
5. Try procedures 1. to 4. with every single USB port available. If no success try different pc (normally WINXP is no deal breaker, Win 8.1 sometimes might be).
6. Report.
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
grimsonfart said:
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
Click to expand...
Click to collapse
Glad to be of any help.
You might add to your OP tag [Solved]
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?