Hi All,
I really hope you can help me out. I am a fairly unexperienced user who was actually quite proud that I succesfully managed to install Katkiss 7.1 a few month back (just to give you the impression what a noob i am in this field). All worked fine until yesterday when i wanted to startup my tablet again. It got stuck at the ASUS screen right at the start.
I've tried to hardboot it via the little hole as well as to use the pwr+volume down option to boot. Both end up at the ASUS screen.
I could get into the fastboot screen but when I enter RCK and can see the different options there, the screen becomes unresponsive so I cannot select anything there. I can also not move the 'swipe to unlock' feature, so I cannot use any of the options there.
The following information is shown when i use the pwr+volume down option:
Key driver not found......booting OS
Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" A03
Starting fastboot USB download protocol
I've tried to connect it to my W7 PC. Via explorer the internal and external memory can be seen and entered. I've also connected it to ADB and enter the command Fastboot Devices. This came back with a response of letters and digits. Then i tried to Fastboot –i 0x0B05 flash recovery boot.blob. That also worked. When I rebooted the device via Fastboot reboot, I got stuck in the ASUS screen again. (my best guess was to repeat the steps i've taken to flash it the first time, but perhaps I made the situation only worse...)
I've browsed many topics but since none of the issues I could find exactly match my issue (my biggest problem is i guess not being able to manouvre in the TWRP menu on the tablet), i'm a bit 'scared' to just try out the given answers there as it might do more harm than it will help.
I would be very grateful if you could guide me in how I can get my Tablet to work again (if at all possible)...
Thank you very much in advance,
Paul
You did not do anything terribly wrong - I think - so let's try to fix it.
To help you understand what you are doing I am going to dissect the fastboot command for you:
fastboot - doh, name of the protocol or program you are using, starts the exe
-i 0X0B05 - Asus vendor code, not strictly necessary
flash recovery - what to do, in this case flash something to the recovery partition
boot.blob - name of the file you want to flash to the partition specified above
So in this case you flashed a file called boot.blob to the recovery partition. Since you did not specify the file path to boot.blob (C:\myuser\fastboot\boot.blob) the file has to be in the same directory or file folder as your fastboot executable.
Now, the question is: What's in boot.blob? Is that a compatible recovery? A kernel? Who knows? Fastboot relies on you flashing the correct files, it has no way of checking if the file you specified is a compatible recovery or your utility bill accidentally renamed to boot.blob. The result suggests boot.blob was not exactly a working recovery.....
So check your fastboot directory for a file called boot.blob. Get rid of it.
Then download a fresh copy of TWRP 3.1 or whatever version you prefer as long as it is 2.8.7 or newer.
Place that file in your fastboot directory, unzip it if necessary. It should have .img extension
You can leave the file name as is or change it to something easier to type - that's up to you
Then flash it to your tablet:
fastboot flash recovery <exact file name>
Reboot and check if you can enter recovery
If you can, wipe /data, cache and Dalvik and reboot
If it still does not boot, format data, reflash the rom and gapps and reboot.
If one of the steps don't work come back here and we'll troubleshoot
Good luck
Hi Berndblb,
First of all thank you very much for your ample response! I will try to answer your questions to my best ability.
So in this case you flashed a file called boot.blob to the recovery partition. Since you did not specify the file path to boot.blob (C:\myuser\fastboot\boot.blob) the file has to be in the same directory or file folder as your fastboot executable.
Click to expand...
Click to collapse
Yes, I've located this file in the same directory on my PC as the ADB software is located. This i've read in one of the instructions.
The boot.blob file i fetched from this location: http://forum.xda-developers.com/tran...rea51-t3049395
it was part of this package: twrp_tf700t_kang_2.8.7.4-signed
It was the same file I used serveral month ago when i loaded the Katkiss Rom. I see now that it was actually written by you!!
https://forum.xda-developers.com/showthread.php?t=2688891
Then download a fresh copy of TWRP 3.1 or whatever version you prefer as long as it is 2.8.7 or newer.
Click to expand...
Click to collapse
The version I currently have is 2.8.7.4 so this should be OK if I read your description, however it does not have the .img extention, it contains this boot.blob file + a META-INF directory. Since this file worked the last time, i renewed it and send it to the tablet via the flash recovery command which indeed renewed my TWRP!
However, the screen is still inresponsive so I cannot move the Slider to accept to continue or keep 'read only' settings. When the screen is locked after some minutes I cannot unlock it due to the same issue. I've tried to place the tablet in the dock with keyboard and mousepad but with no luck....
Based on this, should i try to download a newer version of TWRP (3.1 as you suggested)?
If so, i browsed the forum but could find a download link to install in on my PC, only via the appstore to send it to my Tablet(https://forum.xda-developers.com/showthread.php?t=1797692)
Sorry for being such a pain....
That sliding button can be very sticky. Try holding it for a few seconds and then sliding or just fool around with it until it releases. Could be as easy as that
berndblb said:
That sliding button can be very sticky. Try holding it for a few seconds and then sliding or just fool around with it until it releases. Could be as easy as that
Click to expand...
Click to collapse
I'm afraid it's not in this case...even if the screen is unlocked (when i first enter TWRP), i cannot select any of the tabs as my touch is not recognized....
Btw, i upgraded TWRP to the latest version i could find for the TF700 (3.2.1.0) but still the screen is inresponsive to my touch so I cannot select anything.
Do yo have the keyboard dock for your 700? - NP
Hi Nektopoli,
Yes i do have a keyboarddock, but unfortunately this does not work either. There is no mouse cursor visible and the lock/unlock button does not work either.
Thanks for your help.
012380 said:
Hi Nektopoli,
Yes i do have a keyboarddock, but unfortunately this does not work either. There is no mouse cursor visible and the lock/unlock button does not work either.
Thanks for your help.
Click to expand...
Click to collapse
Can you try the a mouse with the keyboard to see if it will bring up the cursor. - NP
No, there is no support for the dock or any of its functions in either TWRP or fastboot.
This is very strange and I almost suspect a hardware failure. Maybe your touchscreen died...
Last thing I can think of on the software side is flashing the stock blob in fastboot. That would replace all the original drivers. If the screen is still unresponsive on stock it's gotta be a hardware issue.
Let me find a link on that...
Here are the instructions: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
Link to the Asus website is broken again. Get the Asus firmware here: https://www.androidfilehost.com/?fid=817550096634791660
Thanks again for your suggestions!
I do hope it"s a driver failure indeed...I will try this solution as soon as I am back home from my short business trip. I will of course let you know if it worked.
Thanks again,
berndblb said:
No, there is no support for the dock or any of its functions in either TWRP or fastboot.
This is very strange and I almost suspect a hardware failure. Maybe your touchscreen died...
Last thing I can think of on the software side is flashing the stock blob in fastboot. That would replace all the original drivers. If the screen is still unresponsive on stock it's gotta be a hardware issue.
Let me find a link on that...
Here are the instructions: https://forum.xda-developers.com/showpost.php?p=72801448&postcount=8
Link to the Asus website is broken again. Get the Asus firmware here: https://www.androidfilehost.com/?fid=817550096634791660
Click to expand...
Click to collapse
I use the dock so I have mouse functions in TWRP, on my TF201 I have the reverse X-Axis with the touch screen so having a working mouse, but that is the only way. Like you said no touch-pad in TWRP. - NP
Hi Berndblb,
Get the Asus firmware here: https://www.androidfilehost.com/?fid=817550096634791660
Click to expand...
Click to collapse
I've downloaded the drivers from this link but on all three mirrors the BLOB file is corrupt according to WinRar. I receive an error message that there is an error in the 'control number' (freely translated from Dutch) and 'the archive is unrecoverable'.
Do you happen to know any other source I can find these files?
Thanks in advance!
012380 said:
Hi Berndblb,
I've downloaded the drivers from this link but on all three mirrors the BLOB file is corrupt according to WinRar. I receive an error message that there is an error in the 'control number' (freely translated from Dutch) and 'the archive is unrecoverable'.
Do you happen to know any other source I can find these files?
Thanks in advance!
Click to expand...
Click to collapse
Are you erasing the recovery partition with the fastboot command [fastboot erase recovery] before you try to flash the TWRP blob with [fastboot -i 0x0B05 flash recovery c:TWRP LOCATION HERE]? - NP
Did you check the md5 of the zip you downloaded? This file has been downloaded multiple times and always was OK. Winrar does not have any business touching the blob. Why is it reporting it corrupted? You are not trying to extract it or something are you?
But you can try searching for "Asus TF700 Firmware" and see if you can find the Asus repository
Nektopoli said:
Are you erasing the recovery partition with the fastboot command [fastboot erase recovery] before you try to flash the TWRP blob with [fastboot -i 0x0B05 flash recovery c:TWRP LOCATION HERE]? - NP
Click to expand...
Click to collapse
No, i did not use this command so far.
I assume I should do so before uploading the blob file i used a few months back?(which the first post was based on; finding a solution for the tablet not being able to boot past the ASUS start screen)
This topic evolved into the screen not being responsive in TWRP but perhaps solving the issue mentioned above might resolve this latter issue as well.
Thanks,
012380 said:
No, i did not use this command so far.
I assume I should do so before uploading the blob file i used a few months back?(which the first post was based on; finding a solution for the tablet not being able to boot past the ASUS start screen)
This topic evolved into the screen not being responsive in TWRP but perhaps solving the issue mentioned above might resolve this latter issue as well.
Thanks,
Click to expand...
Click to collapse
1st you need a working TWRP [recovery console] which is what erasing and flashing the recovery partition should give you, once you get a working TWRP you can wipe the rest of the tablet and flash the ROM, SuperSU and GApps. - NP
I use the dock so I have mouse functions in TWRP, on my TF201 I have the reverse X-Axis with the touch screen so having a working mouse, but that is the only way. Like you said no touch-pad in TWRP. - NP
Click to expand...
Click to collapse
I've tried an USB mouse, but this also did not work unfortunately
But you can try searching for "Asus TF700 Firmware" and see if you can find the Asus repository
Click to expand...
Click to collapse
I've found drivers here: http://drivers.softpedia.com/get/JO...r-Pad-Infinity-TF700T-Firmware-94522-WW.shtml
Next I've executed these commands
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
Click to expand...
Click to collapse
But the tablet still hangs on the ASUS start screen.
Then i've uploaded the latest version of TWRP again, but still I cannot use the touchscreen....
I'm afraid this is all that can be done and i need to accept my tablet died, or do you have some final remedy i can try?
Thanks,
You have to flash the TWRC recovery console, not the system. But if you don't have a working touch screen your tablet might be bricked. - NP
012380 said:
I've tried an USB mouse, but this also did not work unfortunately
I've found drivers here: http://drivers.softpedia.com/get/JO...r-Pad-Infinity-TF700T-Firmware-94522-WW.shtml
Next I've executed these commands
But the tablet still hangs on the ASUS start screen.
Then i've uploaded the latest version of TWRP again, but still I cannot use the touchscreen....
I'm afraid this is all that can be done and i need to accept my tablet died, or do you have some final remedy i can try?
Thanks,
Click to expand...
Click to collapse
The tablet is not bricked if you have fastboot. You may have a hardware problem, but we don't know that yet and the only way to find out is to flash the Asus firmware blob in fastboot.
I just downloaded the firmware zip from my Android File Host site and checked the md5 - the file is fine. But here is the link to the Asus repository, took about 30 seconds on Google to find it: https://www.asus.com/us/supportonly/ASUS Transformer Pad Infinity TF700T/HelpDesk_BIOS/
I don't know what you are doing, but you are not following my instructions, so I really do not know how else to help you. There no "drivers' to download or install. You need to flash the stock blob as I described before
One last time:
Download the 10.6.1.14.10 firmware
check the md5 sum to make sure you do not have a corrupt download. If you do not know how to do that, google it. Plenty of instructions out for that
Unzip the file you downloaded
Copy the file called "blob" into your fastboot directory
run the commands I posted one by one
When done your tablet should boot into a JB 4.2 rom. If the touchscreen still does not work you need to replace the LCD/digitizer combo or give it up for dead.
I don't know what you are doing, but you are not following my instructions, so I really do not know how else to help you. There no "drivers' to download or install. You need to flash the stock blob as I described before
Click to expand...
Click to collapse
I'm sorry Berndblb, I was really trying to do exactly that what I understood you told me, however i am really a noob on this so have sometimes a hard time to understand.
Since I do not know how to check the md5 sum, i tried your other suggestion which was to google on firmware. However i see now that you meant a ASUS repository (i dit not know what this word repository meant) so i just took the first decription which seemed to match my search query. The result was a ZIP file containing a META INF folder and a blob file, so I thought i got what i needed. I should not have used the word drivers, I meant just firmware.
Again my appologies. I really did not mean to annoy you.
berndblb said:
I just downloaded the firmware zip from my Android File Host site and checked the md5 - the file is fine.
Click to expand...
Click to collapse
I have tried again, the download from the primary link is for me really slow (>5 minutes) and is often interrupted. After completion I checked the MD5 (this time taking your advice to google on how to do it) of the zip file i downloaded US_epad-user-10.6.1.14.10. For me the result was that the MD5 did not match the code given on the site. I received this: 8b9553195579ac5958a4a65141009c92 while the site reported this b407002737b48fb76d04b6542b828634
But here is the link to the Asus repository, took about 30 seconds on Google to find it: https://www.asus.com/us/supportonly/ASUS Transformer Pad Infinity TF700T/HelpDesk_BIOS/
Click to expand...
Click to collapse
Thank you for the link. This file i could download without any difficulties. However I could not find where the MD5 was stated on this site for the file which i downloaded, nor did i find any .chksum file or anything. I also tried so read the source code of the site, but this is way over my head and could not find anything that matched the MD5 I found of the downloaded file itself.
I would be interested to learn though where I can find the MD5 for this particular file/site when it's not stated like on your own site (I mean https://www.androidfilehost.com/?fid=817550096634791660). Anyway, the MD5 i got for the WW SKU 10.6.1.14.10 download (2nd from above) is a368c6096db38d375dc799273376d804 (I took the ww SKU because that is what my tablet showes when i use power+volume down: ww_epad-10.6.1.14.10-20130801" A03)
One last time:
1)Download the 10.6.1.14.10 firmware
2)check the md5 sum to make sure you do not have a corrupt download. If you do not know how to do that, google it. Plenty of instructions out for that
3)Unzip the file you downloaded
4)Copy the file called "blob" into your fastboot directory
5)run the commands I posted one by one
When done your tablet should boot into a JB 4.2 rom.
Click to expand...
Click to collapse
I took step 1, 3, and 4 and used the commands you posted in this threat https://forum.xda-developers.com/sho...48&postcount=8 to take step 5.
(step 2 I did not do because I could not find the MD5 stated on the website itself so have nothing to verify the MD5 I found in the file with)
Although I could see on my tablet that the blob file was installed (it displayed a blue progress bar) , the end result is still the same, the tablet does not boot but hangs on the ASUS screen you see directly after you power it on. I've waited for approx 30 minutes, but it does not come past it.
If the touchscreen still does not work you need to replace the LCD/digitizer combo or give it up for dead.
Click to expand...
Click to collapse
This I could not check as I could not boot up the tablet
I hope I did everything right this time.
Thank you again for your support, i really do appriciate it!!!
Related
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
stedrocklp said:
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
Click to expand...
Click to collapse
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Thank you Thank you Thank you!
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
That was definitely the problem and I had been trying everything for the past two days. I appreciate you taking the time to reply.
asus tf300 help
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Did I brick it?
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
solution
mizifih said:
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
Click to expand...
Click to collapse
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
jijitax4 said:
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
Click to expand...
Click to collapse
What if you can only boot to APX mode? I only have the option of using that because my unlocked bootloader got erased in the process of updating to JB. Is there a way to install a bootloader using fastboot? Or will it only work with an existing bootloader?
In other words, when I issue the fastboot command
fastboot -i 0x0B05 flash system blob
I get "waiting on device" and nothing happens after that.
Thank you, this worked !!!!!!
You can revert to the ICS bootloader with the .30 firmware following instructions below only using .30 firmware instead of the JB Firmware.
Thanks goes to saltxyz for this find.
I think we've taken this thread about as far as it can go information wise. Please join me in my new thread here: http://forum.xda-developers.com/showthread.php?t=1886877
Thank you everyone for taking the plunge with me, the Thanks, guidance, and making this a newsworthy thread!
You can download my custom kernel here or below: https://www.dropbox.com/sh/ay9iolwcfbxu0wm/_vpRpSQ6nK/kernel.zip
STOP
1. I am not responsible for any issues this may cause your device and won't be held for any soft-bricks, hard-bricks, boot loops, exploding pets or Resonance Cascades.
2. Go ahead and download ADB/Fastboot to make your life easier: http://developer.android.com/sdk/index.html
What Works/Doesn't Work
What Works:
Almost everything!
What Doesn't Work:
Changing Brightness Settings without the use of a Third-Party App
Resolution (DPI is set to 160 by default and changing it through an App or directly with build.prop makes no changes) - FIXED
You WILL lose Root and Custom Recovery with these methods
Drivers
I used the ASUS Android USB Drivers from the following post for ABD/Fastboot: http://forum.xda-developers.com/showthread.php?t=1706588
Installation
Method 1 for Locked/Unlocked Bootloader with Stock Recovery and/or Root
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad TF300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Rename the extracted .ZIP to "EP201_768_SDUPDATE" (without the " ") and copy it to your MicroSD card
5. Insert the MicroSD card in your tablet
6. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
8. At this point the device will go in recovery and should start updating your firmware
Method 2 for Unlocked Bootloader with Custom Recovery and/or Root
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad TF300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Copy the extracted .ZIP (XX_epad-user-10.4.2.9.zip) to your MicroSD card
5. Insert the MicroSD card in your tablet
6. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
8. From your recovery menu press Install and select the .ZIP file (XX_epad-user-10.4.2.9.zip)
9. Wait until the install process ends and then restart your device
Method 3 Advanced using Fastboot
1. Power off your tablet
2. Download the latest TF300T firmware (XX_epaduser_10_4_2_9_UpdateLauncher.zip) from Asus site based on your SKU location (eg. ww, US, etc): http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad TF300T&p=20&s=16
3. Right click and extract the downloaded .ZIP file (XX_epaduser_10_4_2_9_UpdateLauncher.zip) onto your desktop
4. Right click and extract the new .ZIP file (XX_epad-user-10.4.2.9.zip) onto your desktop; you should now have the blob binary and META-INF folder on your desktop
5. Copy the blob binary to your platform-tools folder (C:\Program Files\Android\android-sdk\platform-tools or C:\Program Files (x86)\Android\android-sdk\platform-tools)
6. Plug tablet into your computer
7. Boot your tablet into Fastboot by pressing and holding Volume Down AND Power for 5 seconds
8. A message will inform you that you have 5 seconds to enter Recovery; press Volume Down twice to select Fastboot and then Volume Up before the 5 seconds expire
9. Open a command prompt and cd into your platform-tools folder; or press right-Shift on your keyboard and right-click the platform-tools folder and click "Open command window here"
10. Enter the following command in the command prompt: "fastboot -i 0x0B05 flash system blob" (without the " ")
11. Once the previous command completes enter: "fastboot -i 0x0B05 reboot" (without the " ")
RECOMMENDED but Optional Steps:
If you are using Stock Recovery it is advised to Factory Data Reset or Wipe Data both BEFORE and AFTER the Firmware Upgrade
If you are using Custom Recovery it is advised to wipe ALL partitions
Unlocking the Bootloader
You can use the ASUS Unlock Tool from the ASUS Support site to unlock your bootloader. Despite ASUS saying it's for ICS it works fine on JB. Detailed instructions to come.
Recovery (TWRP) **Requires Unlocked Bootloader**
1. Turn your tablet off
2. Download the latest TWRP blob: http://teamw.in/project/twrp2/105
3. Rename the blob binary (openrecovery-twrp-X.X.X.X-tf700t.blob) to "twrp.blob" (without the " ")
4. Copy the twrp.blob binary to your platform-tools folder (C:\Program Files\Android\android-sdk\platform-tools or C:\Program Files (x86)\Android\android-sdk\platform-tools)
5. Plug tablet into your computer
6. Boot your tablet into Fastboot by pressing and holding Volume Down AND Power for 5 seconds
7. A message will inform you that you have 5 seconds to enter Recovery; press Volume Down twice to select Fastboot and then Volume Up before the 5 seconds expire
8. Open a command prompt and cd into your platform-tools folder; or press right-Shift on your keyboard and right-click the platform-tools folder and click "Open command window here"
9. Enter the following command in the command prompt: "fastboot -i 0x0B05 flash recovery twrp.blob" (without the " ")
10. Once the previous command completes enter: "fastboot -i 0x0B05 reboot" (without the " ")
Root **Requires Unlocked Bootloader AND Custom Recovery**
1. Download the latest Custom Recovery installable SuperSU .ZIP (CWM-SuperSU-vX.XX.zip): http://forum.xda-developers.com/showthread.php?t=1538053
2. Plug tablet into your computer
3. Copy the SuperSU .ZIP (CWM-SuperSU-vX.XX.zip) to Internal Storage
4. Turn your tablet off
5. Boot your tablet into Recovery by pressing and holding Volume Down AND Power for 5 seconds
6. A message will inform you that you have 5 seconds to enter Recovery; press Volume Up before the 5 seconds expire
7. From your recovery menu press Install and select the SuperSU .ZIP (CWM-SuperSU-vX.XX.zip)
8. Wait until the install process ends and then restart your device
9. Now your tablet should be rooted
F.A.Q.
JB seems to be laggy. Any suggestions?
Yes, Wipe!! Even if you've performed a Factory Data Reset or Wipe Data I HIGHLY recommend unlocking your bootloader, installing a Custom Recovery, wiping EVERYTHING and installing the firmware again; preferably using Method 3.
Is there any way to change the Brightness settings?
Yes, through Third Party Apps. The most popular seem to be Lux and Custom Brightness Settings
Are we "SOL" having the TF300 Bootloader when the Tf700 JB Firmware comes out?
Personally I'm not too worried about the bootloader.
Either the official JB for TF700 will have the same bootloader as for the TF300, or it will be a newer version that we'll be able to flash.
The bootloader doesn't seem to be looking for a device check or else the 300 loader wouldn't have installed on the 700.
It really only seems to be doing a sig check for OLDER firmwares, not NEWER.
Why don't we have an Official TF700 JB Firmware yet?
I don't know, ask ASUS. I'm as flabbergasted as you are. We've only found two issues so far!!
UPDATE UPDATE: Kernel configs are also amazingly identical. Most new options available in the JB 3.X kernel aren't even set. Only things that stick out are that CONFIG_SENSORS_ISL29028 (Light Sensor driver) went from yes to not set. Also I keep seeing NFC code EVERYWHERE which is disabled in JB stuff. Does the TF700 have NFC or is ASUS pulling from one base? <-(Hmmm...) CONFIG_NTFS_FS has also been set to yes in JB so we should check out NTFS formatted SDCARDs. Also fun fact; CONFIG_ISO9660_FS (CD/DVD Filesystems) was set to yes in the ICS kernel. LOL. Everything we need is there, somethings just stopping it. It's funny looking through the code you can tell it was written by two different teams as most times configs contain the same info, only in a different order. Makes it hard to compare code though; jerks. No wonder it's not officially out yet.
UPDATE: I just finished comparing /system between the TF300 JB blob and the TF700 ICS blob. 98% of the config files are similar or are only off by a line or two. Issues with screen resolution and brightness seem to be stemming from kernel. I'm gonna see if I can rip the ICS kernel out and transplant it in JB or recompile the TF300 kernel using the config from ICS. They jumped from 2.6.X to 3.X so who knows...
Is there a reason you need to name it recovery.zip? I just named it 300jb.zip, been installing for almost 30 mins here!
Unlocked bootloader, custom recovery and complete wipe.
Sent from my GT-I9300 using xda premium
fordwolden said:
Is there a reason you need to name it recovery.zip? I just named it 300jb.zip, been installing for almost 30 mins here!
Unlocked bootloader, custom recovery and complete wipe.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Nope, just going off what most people named it.
To get root back, its failrly easy.
1. Install TWRP using fastboot. Just check their site for the how to do. Make sure you have fastboot and the drivers on your PC
2. Download SuperSU-CWM pack from the SuperSU topic on XDA.
3. put the SuperSU pack on your SDcard internal or external.
4. Flash that pack.
5. Boot up and open up SuperSU.
6. Update binary and done
Maybe nice to note what is broke if you use this flashing methode.
- Brightness controll is broken. Its on full all the time
- Everything is a little bigger then usual, Or I am a little blind
For the rest I added the tweaks to the build.prob from the tips topic and I am running super smooth.
And I just downloaded that update for the TF300 from the asus site. Extracted it so I got the update zip thingy. Placed that on my SDcard. Wiped all and just installed. Did not rename a thing. And it worked just fine.
Then I did the steps from above and thats it.
Rooted and unlocked with TWRP running JB Me is very happy
Has anyone tested if the lag still exists with a bluetooth headset while viewing a video?
anyone know what causes a data transfer failure with the error "too many links" when using fastboot to flash?
i was able to get the boot blob to flash, but when i try flashing the system blob it crashes with that error. btw i'm flashing things separately because i don't want to have my bootloader updated.
urrlyx said:
anyone know what causes a data transfer failure with the error "too many links" when using fastboot to flash?
i was able to get the boot blob to flash, but when i try flashing the system blob it crashes with that error. btw i'm flashing things separately because i don't want to have my bootloader updated.
Click to expand...
Click to collapse
I think you answered your own question.
lafester said:
I think you answered your own question.
Click to expand...
Click to collapse
Actually I didn't, or I wouldn't have asked it. If the answer is "you can't flash this system blob with the old bootloader", then saying so would be an appropriate response.
Also, since it could be caused by something else like an inability of fastboot to flash extracted system blobs without the header file, or maybe corruption in the blob caused by using a windows binary of blobunpack, I feel my question is quite valid.
edit: I ended up doing more research and it appears that even if I did get the system blob flashed, it probably wouldn't boot without the updated bootloader due to the 3.x kernel. Even the custom JB roms for the 300 make you update the bootloader on that tablet first.
So, I'm going to put this on the backburner until there's an official bootloader update for the 700 or until someone already on the new 300 bootloader successfully flashes back to the current one.
rdejager said:
For the rest I added the tweaks to the build.prob from the tips topic and I am running super smooth.
Rooted and unlocked with TWRP running JB Me is very happy
Click to expand...
Click to collapse
I added the build.props tweaks and it bricked my tablet at ASUS bootsplash? which ones did you add? can you upload your build.prop?
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Keion said:
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Click to expand...
Click to collapse
I thought somebody said they flashed a custom jb rom from the tf300
Edit found who said it...
http://forum.xda-developers.com/showthread.php?p=31214220
Sent from my SPH-D710 using Tapatalk 2
Keion said:
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Click to expand...
Click to collapse
One guy said it flashed ok, another said no.
Sent from my EVO using xda premium
I'm pretty sure you need to be on the new bootloader for the stock rom / stock-based roms to work. I've been reading through the tf300 forums and so far I haven't found any posts about anyone being able to revert back to the ICS bootloader. One guy suggested this is due to signature checking, different permissions, and possibly an altogether different partition table.
urrlyx said:
One guy suggested this is due to signature checking, different permissions, and possibly an altogether different partition table.
Click to expand...
Click to collapse
AFAIK, the bootloader can't alter the partition table on Tegra units. In fact, the bootloader is itself a partition. Only way to change the partition table is with nvflash.
Hopefully the TF700 JB Update would be able to flash over the TF300 JB Bootloader, otherwise we will stuck at this "not so perfect"-build for a very long time!
I miss the DPI changing I'm not blind and everything is so ****ing big on the screen.
Guys, did someone else see that the Battery is going low pretty much faster?
Keion said:
I would much prefer it if we could install a custom ROM from our bros over at the TF300 forums.
Do those work as well or is it just the ASUS stock stuff?
Click to expand...
Click to collapse
If you change the updater-script (attached in zip) with the one in this ROM: http://forum.xda-developers.com/showthread.php?t=1854212
in the subfolder: Asu-JellyBean-HyDRO-R1.zip\META-INF\com\google\android\
You can Install it on your TF700T
I'm running it right now, but I will go back to stock JB because ASUS Settings bring a force close.
All other things are still the same, backlight doesn't work, anything else is fine.
Hopefully someone sees something helpful from this and can make a safe stock tf700 update.
Seems devs here work as hard as asus does.
Thanks guys for all you do
Sent from my ASUS Transformer Pad TF700T using xda premium
kabauterman said:
Hopefully the TF700 JB Update would be able to flash over the TF300 JB Bootloader, otherwise we will stuck at this "not so perfect"-build for a very long time!
I miss the DPI changing I'm not blind and everything is so ****ing big on the screen.
Guys, did someone else see that the Battery is going low pretty much faster?
Click to expand...
Click to collapse
Personally I'm not too worried about the bootloader. Either the official JB for TF700 will have the same bootloader as for the TF300, or it will be a newer version that we'll be able to flash.
The bootloader doesn't seem to be looking for a device check or else the 300 loader wouldn't have installed on the 700. It really only seems to be doing a sig check for OLDER firmwares, not NEWER.
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'd like to know how to update my TWRP from v 2.4.4.0 to a later version. This version doesn't seem to allow flashing of an img file on external sd card. I have tried without success on 2 computers to get windows to recognise this android, so I'm hoping there is another way. Eventually I'd like to install Katkiss,Gapps and SU on this android. At present it has no rom.
Secondly, I tried to install Cromi X and all goes well up until I reboot and it continually spools on the opening screen so I don't know what that is about but hoping with a later TWRP I may be able to set the partitioning better which may or may not be part of the cause.
Reboot recovery twrp.
Go to install.
Click on install image.
Search downloaded recovery.
Select recovery.
And install.
Done
sent from moto g2014 with cm13
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
Ot use flashify app.
It requires root.
sent from moto g2014 with cm13
There is no 'install image' on v2.4.4.0 and that version of TWRP does not seem to recognise .img files on the external sd card. On a later version of TWRP your solution would work.
If you want to flash the recovery in recovery it has to be inside a flashable zip (except for the latest versions).
You can use the Kang TWRP 2.8.x from post 2 here: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
You can flash Katkiss with it no problem, and it supports the dock SD which the official TWRP does not do.
Somewhere there's also a thread where some dude keeps posting TWRP 3.x in a flashable zip, but I can't think of where right now.
That CROMi-X does not boot can have a number of reasons:
You did not format data before flashing the rom
You are on an outdated bootloader
Something is physically wrong with your emmc.
Your problem to get the tablet recognized in Windows is almost certainly a driver problem an you should get that fixed. At minimum it sucks not to have fastboot access to the tablet. And it easily could be lethal. For the tablet - not for you
Could also be a problem with a cheap knock-off replacement USB cable. If you are not using the original Asus cable that's worth investigating. And if you are using the original it may become worn. Mine is starting to allow a connection only in certain positions... Age....
Make sure the device drivers are installed and try the Google Universal Naked drivers. Minimal ADB and fastboot is an excellent tool that shimp208 still keeps current after all this time, and if none of those work try the 15 second adb installer if you are on Win 7 or earlier (just google it).
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
This is not the same device you helped me with earlier...it now purrs beautifully.... this is a new challenge.
plato2 said:
Hello my old friend. Well I have finally managed to get an adb connection and am going over to old posts of previous help you gave me with this device. Although the device is now recognised I can't get any commands to work e.g. fastboot devices simply returns me to the c:/adb prompt and adb reboot bootloader just takes the flashing underline symbol to the next line and nothing happens. I have hope that I will be able to get this working OK now I have adb access. How do I know if I am on an outdated bootloader? thanks
Click to expand...
Click to collapse
Thought you looked familiar..... :cyclops:
Time to re-read this I think http://forum.xda-developers.com/showthread.php?t=2688891
Boot into the bootloader and read the small script. The last bootloader for this tablet is 10.6.1.14.10.
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
plato2 said:
Yes, that is the bootloader I have. Typing fastboot devices takes me back to the/adb prompt and then typing
fastboot -i 0x0B05 flash recovery <name-of-file>
I get a <waiting for device> but nothing happens.
Click to expand...
Click to collapse
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
berndblb said:
Yeah, so you have a driver problem. This is nothing you have to do now. Just download the flashable zip of Kang TWRP and flash it in your current recovery.
But when you have some time to kill open Device Manager and connect and disconnect the cable to the tablet. It should give you SOME change in device manager. If it doesn't, reboot both tablet and PC and try again.
Then try a different cable.
Still nothing? This could take longer. Driver problems suck in Windows....
So - you got yourself another TF700? Had just too much fun getting Katkiss to work on the last one, eh?
Click to expand...
Click to collapse
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
plato2 said:
Just download the flashable zip of Kand TWRP and flash it in your current recovery.
I don't know what you mean here.... how do I 'flash it in my current recovery' I have v 2.4.4.0 and it doesn't see img files on external sd.
Click to expand...
Click to collapse
If you downloaded from the second link, the flashable zip, you will see a zip file, not an img file.
Just hit Install, select the zip and swipe the button. Reboot when the flash is finished
All good so far. Up to the wiping data bit before converting to f2fs but this guide is missing, not sure why. I recall it was only a short set of instructions: Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tran...p-2-8-t3073471. Can you recall that part? thanks
Got it, found it or rather another post of yours here: tf700/help/how-to-update-twrp-withoput-adb-t3437702/post68163144#post68163144 so did that and successfully installed Katkis, Gapps pico and SU....another beautiful TF700T purring...many thanks yet again...
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?