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
Hi everyone,
I was hoping someone might have some advise for me to try. I did the following and now I can't seem to boot the ROM I installed and/or load the partitions to wipe them. TWRP is asking for a password (which I just cancel) and then it can't mount the partitions. Here is what I did.
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Any advise would be appreciated. Thank you. The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file. Thanks so much for your time. Someone is helping me on the side via PM, if I get anywhere with that, I'll post the resolution here.
-Tony
qzmicro said:
The custom ROM I installed has a filename of cm-4.4.2-20131226-cmb4. I think it's a CM mod file.
Click to expand...
Click to collapse
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Any suggestions?
manhart said:
The file cm-4.4.2-20131226-cmb4 is for Verizon HTC One only and not for the ASUS TF700T.
You must download the CM from this site: Link
I run my TF700T with CM11 (nightly build) and with TWRP 2.6.3.2.
Regards
Matthias
Click to expand...
Click to collapse
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
qzmicro said:
Thanks for the reply but the ROM I used is indeed for the TF700T mode. The exact filename is cm-4.4.2-20131226-cmb4.4-tf700t-rc3.zip. As you can see my device model is in the filename. I also only downloaded ROMS that are form this forum (TF700.) Any suggestions?
-Tony
Click to expand...
Click to collapse
That is a rom based on CM11 kitkat. Did you read the requirements (which the cmb creators unfortunately just touch upon in their op) before you flashed it?
The CM11 OP states that you have to be on 10.16.1.14.x bootloader and CWM 6.0.4.4 as a recovery.
It also clearly states that TWRP has problems with KitKat. Supposedly the latest TWRP version works, but to my knowledge that is not confirmed. Don't know what TWRP version you initially flashed, but then you flashed one that's totally outdated and possibly not even compatible with your bootloader.....
I hope you still have access to fastboot.... download CWM 6.0.4.4. and flash it. Then try to flash the rom again.
But check your bootloader version first!
Read this: http://forum.xda-developers.com/showthread.php?t=1957660
Now I can't seem to erase certain partitions or write to system...
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
qzmicro said:
Hi everyone,
So, I tried to erase all partitions using fastboot and then install the asus firmware blob back on my system to see if I can get it back to where it was. At this point I can't seem to write to the system partition. I get a failed error on fastboot and a failed command error on my tablet. Any suggestions? Is there any way to install a bootloader with fastboot? I suspect it's the bootloader as it is still ASUS's stock bootloader. I would like to change it to something that may be able to write and wipe the partitions properly using CWM or something similar. Please advise, I'm running out of options here. I'd hate to think I bricked my first device ever... thanks so much for your time. Cheers.
-Tony
Click to expand...
Click to collapse
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
It's been a single ? since I started using fastboot.
berndblb said:
You do have fastboot access? If you enter
Code:
fastboot devices
in the cmd prompt, does it return the serial number of your device.
If not, you may have a driver problem on your PC.
The only method I know of to get a bootloader via fastboot is to flash the system blob, but you seem to have tried that already. The question is: How?
Please post the commands you used and the output you get back.
You also may want to look at buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
qzmicro said:
I've installed fastboot on two separate systems (both windows 8.1 64-bit) and both have drivers installed (device manager shows it installed fine.) Since I started using fastboot it simply shows a ? instead of my device's serial number. Could this be the issue from the start? I was able to install TWRP with it, so I assumed it worked. * Sigh * I should know better. (I kept moving forward once I saw TWRP installed) Would it surprise you to know I'm a network engineer?
I put up a windows 7 system at this point to see if I have a better time with fastboot and the drivers simply aren't recognized, even when I install the asus software that has the drivers (Asus pad pc suite.)
How can I get just the raw drivers for my system to use with fastboot? Either for Windows 8 or 7. Any help would be appreciated, thank you for your time.
-Q
Click to expand...
Click to collapse
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Drivers are installed now and stilll ? for fastboot devices.
berndblb said:
Ain't computers great? If you are a network engineer you should be used to this! LOL!
On Win 8 there's some nasty stuff where you have to turn off "windows driver verification" or some such in system settings - just google "Windows 8 fastboot" and you should find the necessary steps.
The attached drivers work fine for me with Win 7 (forgot which one's I installed). Try the Universal Naked Drivers first and uninstall the ones you have now prior to installing these.
But one thing is for sure: ? is not an acceptable return for "fastboot devices"
Edit: XDA won't let me upload the Google Universal Naked Drivers, so download them from here:
http://forum.xda-developers.com/showthread.php?t=2263822
I would try these first, then the adb recovery driver I attached as a zip
Click to expand...
Click to collapse
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
qzmicro said:
Hi, so I installed the naked drivers and they seemed to work. Once that was done, I used fastboot devices and got a questionmark again. Please keep in mind that since the tablet was out of the box, I have only seen a ?. I don't believe that this issue is related to the other only because it's been consistently ? the whole time, across 3 workstations. I can now erase the system partition but can't seem to write to it. I guess it would help to resolve the drivers issue but I am not sure how. Naked drivers are installed. commands like erase and reboot tend to work properly. write worked the first time as well but since then I cannot write to certain partitions. Any ideas how I might resolve the ? issue in fastboot devices?
-Tony
Click to expand...
Click to collapse
I have never heard of this issue.....
Please post the fastboot commands you are using.
Liunx Mint 32 bit
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
I will document what I have done so far, step by step.
berndblb said:
I have never heard of this issue.....
Please post the fastboot commands you are using.
Click to expand...
Click to collapse
I'll post shortly what I have done and how it went down. Specifically the commands used in fastboot as that is the ONLY tool I've used so far besides the ASUS Unlock Tool. Standbye...
-Tony
I'll be installing linux mint 32 on a VM....
lj50036 said:
You need Linux Mint 32 bit, to have a fighting chance of solving this issue...Let me know if I can help... Thx, the cmb team, and lj50036
Click to expand...
Click to collapse
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
UPDATE: Here is all the commands I've tried on my Tablet...
Originally I did this:
unpacked the tablet and started it up. Put my Wi-Fi and google account on it and updated the firmware.
I then downloaded the ASUS unlock application and unlocked my bootloader. It shows as unlocked now when starting up.
I installed TWRP (Latest version) via fastboot.
I created a backup with TWRP.
I installed a custom ROM.
Restarted
System not booting. I attempted to recover from backup and/or wipe the partitions and it won't mount them. also TWRP asks for a password and I just cancel out of it. I believe you know the symptoms.
I then read that maybe an older version of TWRP would work. I tried 2.3.3.0 I believe and it had the exact same affect. I installed it via fastboot as well.
Since then I've tried this:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob (blob was in same directory as fastboot and I got it form the latest asus firmware zip file) <-- Failed It sends the data okay but fails to write to the disc. Error on ASUS tablet in red also confirms the command write:system failed and gives a memory address.
fastboot -i 0x0B05 reboot
Please note that some of the erase commands simply hung. I had to restart the tablet to go back into fastboot mode. When I restart it sometimes they erase successfully. Not sure why. I know I couldn't erase userdata at all, and recently tried again and it worked.
I now have a copy of Mint Linux 32-bit ready to go. What should I try?
-Tony
VM Mint
qzmicro said:
@lj50036:
I would love to try anything... even if it's just for educational purposes.
Can I install Linux Mint on a VM? If so, I'll have this done soon and get back to you. If not, please let me know and I can put up a physical machine with it. Thanks. Cheers.
At this point it seems by biggest problem is that I can't write to the damn system partition... Fastboot is all I have used to modify the tablet but it has never shown my serial number. Is this what we are trying to address with mint? Would you mind giving me some more info while I get this done is possible. Thank you.
-Tony
Click to expand...
Click to collapse
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
lj50036 said:
I can not say about VM. I have not done that because I have lots of hard drives, so I cant give any feedback about VM and if that will work. I would say to stay away from VM but thats just me... So really what we need is like a 80 gig or bigger hard drive you can just slap mint 32 bit on... If you need any help with this just let me know.. Just to clarify, have enable nvflash?? you can send me a email at [email protected]
Click to expand...
Click to collapse
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
P.s. I do not believe I have NVFLASH. I had firmware that didn't alow for it, so I just did the Asus Unlock Tool. Please refer to my previous message about anything/everything I've done so far. Cheers.
qzmicro said:
Done. I have mint installed on an x86 system. No VM. I figured why risk it. What can I do from here? Install fastboot and try again from this platform? Do I need to install drivers for my tablet? If so, manufactureres website best ones to use? I'm ready to do this... and praying...
-Tony
Click to expand...
Click to collapse
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
lj50036 said:
Open a terminal window and type fastboot, it will not be installed but it will prompt you how to get it...do the same for adb just type adb and will prompt..... Than boot your tablet into fastboot.... Connect it to your mint pc and type fastboot devices see what it says......
Just to clarify you do have a unlocked bootloader, yes??
EDIT TYPE----- sudo fastboot devices
Click to expand...
Click to collapse
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Great
qzmicro said:
Roger that. ... and yes, I do have an unlocked boot loader. It's the factory ICS from what I understand. Unlocked with the ASUS Unlocker Tool. it completed successfuly. It states it is unlocked when I boot the device. I'll let you know what happenes in an hour or two. I have to finish some work. Thank you, I'll post shortly.
-Tony
Click to expand...
Click to collapse
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Linux Mint still shows ?????? as my serial.
lj50036 said:
Sounds great!!! No worries on a time.. Just let me know... Thx lj
Click to expand...
Click to collapse
So, I installed fastboot and ADB and installed all updates on the OS for kicks. Then tried the fastboot devices command and I recieved:
Code:
[email protected] ~ $ fastboot devices
no permissions fastboot
[email protected] ~ $ sudo fastboot devices
[sudo] password for amascolo:
???????????? fastboot
[email protected] ~ $
...? Still no serial number. I've seen this since I took it out of the box. Not sure what that is all about, I have found no one else with this issue. I'm going to try to flsh and I'll let you know what happens.
-Tony
UPDATE: I have tried to re-flash the damn thing and it still fails. Here is what I see...
Code:
[email protected] / $ sudo fastboot -i 0x0B05 flash staging /home/amascolo/Desktop/blob
sending 'staging' (800927 KB)...
OKAY [135.763s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 136.934s
[email protected] / $
Any ideas fellas? Seems I simply am not able to write to the system partition again.
-Tony
* SIGH *
Anyone have any ideas as to why I can't write to my device? Any ideas as to what I may try? Please advise, I'm not looking forward to throwing this thing away. Cheers.
-Tony
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...
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone. Reason is I want to try it out and also tweek som files but not necessarily rooting it.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot I get the fast boot menu with the options but when I connect it to the computer it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried this from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such. It's basically in the fastboot menu that it doesn't seem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Ps: Posted this a few days ago in the general Q&A as a suspect it's not necessarily a specific One Vision problem but it didn't get any replies so I'll try here. Sorry if it's a bit of a double post. ds-
I've made some headway and manage to reboot and connect but when I try to ./fastboot boot IMAGE I get the message Validation image failed.
If I understood it correct it's not possible to boot an image in this way which is of an earlier version than the one installed. Is this correct?
I''ve got 4.4 installed, and the image is 3.4.
/Magnus
Cardinal_Vice said:
I've made some headway and manage to reboot and connect but when I try to ./fastboot boot IMAGE I get the message Validation image failed.
If I understood it correct it's not possible to boot an image in this way which is of an earlier version than the one installed. Is this correct?
I''ve got 4.4 installed, and the image is 3.4.
/Magnus
Click to expand...
Click to collapse
Did you flash the patched vbmeta image?
ttomovcik said:
Did you flash the patched vbmeta image?
Click to expand...
Click to collapse
No, I can't get that to work. I'm not sure if I understand where I should place it.
Appreciate that you pitch in.
I have a One Vision x1907-1 variant and recently it bricked. The device can't be recognized and don't works with the motorola drivers . So it's similar issue maybe
mjraogr said:
I have a One Vision x1907-1 variant and recently it bricked. The device can't be recognized and don't works with the motorola drivers . So it's similar issue maybe
Click to expand...
Click to collapse
No, my phone works perfectly fine. I just can't flash the vbmeta image and I can't run the .bat file.
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
jwoegerbauer said:
The only command to verify whether an ADB / Fastboot connection got successfully established is
Code:
adb devices OR fastboot devices
The command
Code:
adb reboot
simply in Android's system file called build.prop (re-)sets flag ro.bootmode to normal what is read by bootloader when Android boots up.
Click to expand...
Click to collapse
As it turns out, I had already stumbled upon your your "ADB-FASTBOOT-Installer" during a trip down one of the many rabbit holes trying to get this tablet working again.
adb devices returns:
List of devices attached0123456789ABCDEF recovery
adb reboot restarts the tablet, which I assume means the ASUS tablet driver is working.
I can't seem to do anything else with adb, however, such as push a new TWRP version, etc. This may be a key point, as it seems likely the version I have of TWRP may be too old to support upgrade using something like Chrombi-KK.
Is this a likely theory?
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
NotTheLips said:
Hello folks.
In my months-long quest to avoid turning an ASUS TF201 tablet into e-waste ...
I've searched, searched again, searched some more, and while I've found answers (none of which have worked), a lot of them seem to be dated, or depend on files that are no longer available for download, so I turn to you for suggestions.
Current state:
The tablet will not boot Android.
TWRP works fine.
The problem(s):
I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails.
I have tried Chrombi-KK, following the directions step by step, but a few strange things occur:
1. When flashing through TWRP (.zip images sitting on an SD card), everything completes with no errors, but on reboot, the tablet displays its ASUS logo, but does not boot into Android. I let it sit there for three hours today, and it just sat there, displaying the logo.
2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine.
Now, I'm at a loss. The hardware seems fine, but I'm stuck ... and this is after months of trying, giving up, trying again etc.
Is this a lost cause?
Any help at all would be much appreciated. I've tried so many things, so many online "solutions," to no avail. So I turn to the experts as my Hail Mary pass before sending this to the eco centre.
Thanks for reading, and hopefully ... just maybe ... someone will have the magical set of instructions to get this thing working again.
Click to expand...
Click to collapse
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
jwoegerbauer said:
I would re-flash phone's Stock ROM to get rid off of all mofications applied so far to check for phone is working as expected.
Click to expand...
Click to collapse
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
[email protected] said:
ok, so good thing is twrp boots, now again if you have box with wich the tablet come try to get correct model number and search for official frimware to flash through adb using flashall.cmd
again, if official rom is not installing don't worry flash THIS custom rom using TWRP make sure to wipe all before flashing.
Click to expand...
Click to collapse
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
NotTheLips said:
As I mentioned: "I am unable to flash the device with ASUS' official firmware. TWRP returns an error when the ASUS firmware runs its "checks," then fails."
This is exactly what I'm trying to find a solution on how to do.
Click to expand...
Click to collapse
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
NotTheLips said:
Yes, thank goodness it's not completely bricked, haha.
I think the version of TWRP that's on there may be too old, and I'm having trouble pushing a newer version through ADB ... so this is the current hurdle I'm trying to overcome.
Might you happen to have a link to the ASUS TF201 drivers known to work in Windows 10, so I can rule that out? If I can't get ADB to push a newer TWRP version from Windows, I may give it a go in Linux too ... but I'm trying not to open up new avenues of complexity, so I've restricted all my efforts to Windows as that's where most of the online help I can find tends to take place.
Thanks!
Edit: Unfortunately, the download link to [ROM][N 7.1] KatKiss Nougat [TF201] no longer works:
404 Not Found
This has been another constant obstacle, i.e., recommended files to download are no longer available.
Click to expand...
Click to collapse
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
jwoegerbauer said:
Nobody needs TWRP to re-flash a device's Stock ROM.
It's typically done via ADB Sideload method.
Click to expand...
Click to collapse
As I mentioned before, "2. When trying to flash from ADB (TWRP update for example), it sits there endlessly at "< waiting for any device >". This is odd, because ADB's "reboot" commands works fine."
[email protected] said:
how you tried to flash stock rom, i mean do you boot into fastboot after booting into twrp or not?
Click to expand...
Click to collapse
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
NotTheLips said:
I've tried two methods.
The first is to try to flash it from TWRP, but this fails with an error. The stock ROM appears to be checking for dependencies, and it fails this check.
The second is to use ADB (fastboot) while the tablet is sitting in TRWP. It stalls at "< waiting for any device >".
So this the problem. Neither of those two methods work for the stock ROM.
With a third party ROM, TWRP appears to flash the device successfully (no errors or stalls). When I reboot the device, it will not boot Android, and gets stuck at the ASUS boot logo indefinitely.
I'm not sure what do next to get past these two problems.
Click to expand...
Click to collapse
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
[email protected] said:
here is the problem, ok so follow the steps carefully,
boot into twrp
then connect your phone to your pc
type "adb devices",
if some thing like 1234567890 -recovery shows up proceed else start-over,
after successfully detected by adb typed "adb reboot bootloader"
then after booting into fastboot mode type "fastboot device"
if something shows up proceed else tell me
make sure you have installed adb and fastboot properly,
after all this run the cmd file in stock rom, to automatically flash it.
Click to expand...
Click to collapse
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
the problem is your pc does not have adb and fastboot properly installed
try this one https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
also, use this official driver https://www.asus.com/SupportOnly/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
if your pc is 64 bit use win764bit version
NotTheLips said:
Here's what happened:
C:\Windows\system32>adb devicesList of devices attached0123456789ABCDEF recoveryC:\Windows\system32>adb reboot bootloaderC:\Windows\system32>fastboot device< waiting for any device >It sits at < waiting for any device > indefinitely, until I reboot the device.
Click to expand...
Click to collapse
This "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in Fastboot mode, so you can easily have permission to it in ADB but not in Fastboot.
Each manufacturer implements Fastboot differently. So, if not already done yet, download and install the suitable "Android USB Driver" provided by ASUS. Then Fastboot should work.
BTW: Your device actually stucks in recovery mode.
Is OEM Unlock got enabled in Android settings? If not, Fastboot never will work.