Related
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
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
grimsonfart said:
Hi. I'm trying to flash my TF300T to the latest stock ROM. I'm currently on 4.2.1 and bootloader 10.6.1.15.3. Reason being i can't flash TWRP 2.8+ to install lollipop because i get splitscreen issue, so i'm trying to get the latest bootloader by getting the official one...
Ok, now to the problem. Fastboot is setup and working properly. ADB commands work, fastboot commands work.
Problem is, when i try and flash using this command "fastboot -i 0x0B05 flash system blob" (i have placed the blob file in the fastboot directory), it renders my computer practically useless, in other words everything is super slow. In CMD after entering the command nothing happens. It's almost like it's working insanely hard, yet nothing is happening. The first time i let it go on for about 30 mins because i didn't want to interrupt it if it was flashing, but i decided to hard shutdown my computer. Nothing had been done and the tablet turned back on as normal
Any help would be great...
Click to expand...
Click to collapse
Wrong command!
You can't flash whole ROM blob on 'system' (i.e. OS) partition because ROM blob contains bootloader, partition table, recovery, kernel, system and userdata, which are to be flashed to other partitions.
Therefore our Transformers have a 'ramp-up' partition called 'staging'. On reboot bootloader flashes the 'sub'-blobs of blob (blob.EBT, blob.SOS, blob.LNX, blob.PT, blob.USR) to their respective partition.
Use:
Code:
fastboot -i 0x0b05 flash [b]staging[/b] blob[enter]
fastboot -i 0x0b05 reboot [enter]
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
grimsonfart said:
Really?? you see, i have been following a few tutroials on doing this on this tablet, and all of them gave me that command. Thanks a lot anyways, will try
Click to expand...
Click to collapse
This should work! However it will last along time. When tab reboots, you will see a blue progression bar, which sometimes seems to freeze. Let tab restart by itself.
If you don't succed, you might have a corrupt blob, either by downloading or by unzipping with an outdated winrar (suffered that myself).
Well, no luck first time. Exactly the same thing happened when using that command in CMD. Not sure if it's a problem with my PC or what... Going to re-download the files from ASUS.
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
I am doing this one a really old computer though (no access to mine atm). It's windows XP SP3, 1gb ram and intel celeron 1.8ghz i think. Not sure if it has anything to do with this but anyways.
grimsonfart said:
Not sure what you mean with that blue progression bar? (really long time since i have messed around with my tablet) You mean on the tablet? When i'm in fastboot and trying to flash nothing happens, i see the same rck, android, whipe data and all the writings on top left is the same.
Click to expand...
Click to collapse
When you flash to staging, bootloader copies blobs to their partitions after reboot, while this happens, a blue progression bar is visible on ASUS Screen not on bootloader screen.
As you report it, you are probably not in fastboot mode.
Try to follow:
1. Press power + vol down -> bootloader screen appears with icon RCK blinking. Now you are in fasboot mode.
2. Connect tb to pc; tab should show up in Win's device manager as ASUS fastboot device(o.s.). If warning sign appears or 'unknown device' label, install proper drivers.
3. Open terminal window with admin permissions in fastboot folder.
4. Type
Code:
fastboot devices [enter]
-> device should be shown; if not: type
Code:
fastboot -i 0x0b05 reboot [enter]
tab should now reboot into OS; if not, fastboot doesn't work.
5. Try procedures 1. to 4. with every single USB port available. If no success try different pc (normally WINXP is no deal breaker, Win 8.1 sometimes might be).
6. Report.
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
grimsonfart said:
It worked now . I just had to wait for about 20 minutes then it started sending "staging". Aftr that it all went fine. I guess it was just the computer being a ****.
Succesfully booted into android too. Everything working fine. +1 for your help anyways man. Cheers
Click to expand...
Click to collapse
Glad to be of any help.
You might add to your OP tag [Solved]
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Terry_Tsang said:
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Ok I was dumb and figured out the first half of my problem. I thought it had to boot into recovery mode to get the fast loader to work. Anyways now it lists my device when I type fastload device but when I try to flash twrp it gives me an error saying
Sending 'Recovery" <6800 KB> ...
Failed (command write failed(No such device or address))
Can someone please help? thanks
I guess you forgot "-i 0x0b05" in the command
it should look like this:
fastboot -i 0x0b05 flash recovery twrp.blob
if fastboot devices detects tablet then this should work.
AFAIK Asus is the only one brand that needs "-i [hex_ID]" even when it is the only fastboot device detected by "fastboot devices" command
Sent from my TF300T using XDA Free mobile app
th3cr0w said:
I guess you forgot "-i 0x0b05" in the command
it should look like this:
fastboot -i 0x0b05 flash recovery twrp.blob
if fastboot devices detects tablet then this should work.
AFAIK Asus is the only one brand that needs "-i [hex_ID]" even when it is the only fastboot device detected by "fastboot devices" command
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
That id string is a vendor code and all android vendors have one ....
It is not need to flash from fastboot, it is only for safety that you need to use the vendor id ....
Thx Josh
I remembered reading about that while performing nvflash backup - https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
and then I remembered it didn't work for me without that vendor ID specified manually,
later on I rooted my cousin's Sony phone and that one did fastboot without -i option, so I concluded it must be asus specific "issue" - not to detect ID automatically or sth ....
Anyway @Terry_Tsang - If you have not tried like that, it is always worth a shot ;]
I have tried it with and without the -i tag and get the same error. I have a feeling my recovery file is corrupt as I get an error when I try to boot into that mode. I also now have a new error instead of unable to write, it says invalid argument.
Since I was able to root it with kingo, I tried the TWRP app but it also crashes when I try to do an install of TWRP through the app. I have no idea how to proceed.
I have tried, rooting with kingo and the commands. I have tried unrooting it. I have tried rooting then using ROM Manager and TWRP apps. I have no idea how to continue. I definately think something is wrong tho lol.
th3cr0w said:
I remembered reading about that while performing nvflash backup - https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
and then I remembered it didn't work for me without that vendor ID specified manually,
later on I rooted my cousin's Sony phone and that one did fastboot without -i option, so I concluded it must be asus specific "issue" - not to detect ID automatically or sth ....
Anyway @Terry_Tsang - If you have not tried like that, it is always worth a shot ;]
Click to expand...
Click to collapse
Well its all good not a point of being right a point in giving good info ...
Here are the most use vendor codes not just an Asus thing ?
https://gist.github.com/lj50036/3b30ecc420b5838646be
Thx Josh
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
Terry_Tsang said:
Hello everyone. I am trying to root and flash my TF300T for the first time, and I am running into some problems.
I downloaded the unlocking tool from asus and that seemingly worked fine.
Now however when I try to boot into recovery mode, the android just falls down and gives me an error message. I am able to boot into the standard android mode without an issue. I tried to root with kingo which seemed to work as I can access the SuperSM.
I downloaded Minimal ADB and Fastboot to try and flash a ROM but I cant see the device in flashboot but I can in adb. (Saw on a different thread that I need to be in recovery mode to see this?)
I downloaded the naked universal drivers and put on everything that said asus but that didnt help at all.
My main goal is to get lollipop on my tablet but I cant seem to make any headway. Can someone help point me in the right direction on what I am doing wrong or what I should do next? Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
You do not have to root to flash a recovery anyway ...
If you would like to look into this more shoot me an email at [email protected]
Thx Josh
Terry_Tsang said:
I have a feeling my recovery file is corrupt as I get an error when I try to boot into that mode. I also now have a new error instead of unable to write, it says invalid argument.
Click to expand...
Click to collapse
You did check the checksum of your download right?
Hi everyone.
I´ve decided today that I want to re-lock my bootloader on Lenovo P11 tablet and I discovered no fastboot commands work on that.
I installed clean version of ROM from Lenovo Rescue and Smart Assistant (TB_J606L_S120217_210805_ROW) but still nothing works.
Normally i reboot to Fastboot and try "fastboot flashing lock" but i recieve:
< waiting for any device >
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
When i try others like "fastboot oem lock" i recieve:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Does anyone has any advice what can I do to relock bootloader?
1. enable developer option
2. enable oem unlock in developer option
3. boot to fastboot mode and run
fastboot flashing lock
Thanks @ong14 for your reply but as you can see above I already tried that...
If you're on chinese firmware, try "fastboot oem unlock-go".
Sadly I get this response for this command:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Is it possibly because of version of my ADB and Fastboot tools? I downloaded many versions (lastly directly from Android Studio) but it didn´t fix anything. @ong14, could you possibly upload the tools you are using?
Sorry for my last reply, it should be "fastboot oem lock-go".
AFAIK, if you're on global rom, use this "fastboot flashing lock".
And if you're on chinese rom, use this "fastboot oem lock-go"
I'm using an old minimal adb and fastboot.
It is totally OK, I am grateful that you are trying to help me at all.
I will try your old adb and fastboot tools and see what happens.
Sadly I don´t have much hope. I am on global rom and command "fastboot flashing lock" resulted only in:
"
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
"
I will keep you posted about my progress and what else I tried.
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
My guy, you are brilliant. I wonder why the change from oem to flashing was done and were you getting sent to that fastbootd menu too? This worked for my 2020 Moto Edge and I don't know how much longer I would have needed without you.
Thanks.
kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
Install RSA from Lenovo also works, and you can run rescue if you want to go back to 100% bone stock
kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
Where and how do you get the drivers for this tablet? For some reason I'm stuck in (what I think) is the exact same screen on my tablet. It says fastboot... in the lower left hand corner and you can hear the disconnect chime come from my laptop every few seconds. I punch in fastboot devices and it's stuck in limbo, no error codes or anything.
BakedinRC said:
Where and how do you get the drivers for this tablet? For some reason I'm stuck in (what I think) is the exact same screen on my tablet. It says fastboot... in the lower left hand corner and you can hear the disconnect chime come from my laptop every few seconds. I punch in fastboot devices and it's stuck in limbo, no error codes or anything.
Click to expand...
Click to collapse
Did you check device manager?
I didn't think I had to, when I plug in the tablet it pops up with the name and everything.
I'll try the Motorola drivers, is that going to solve the fastboot stuck screen?
Where do I go about getting the Motorola drivers?
hey mate. i had problem. now my Xiaoxin Tablet Pro 2021 having widevine L3 even i already lock the BootLoader and Stock Rom. how do i get Widevine L1 ?
kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
what did u do after installing the usb drivers?...can u pls explain in detail?....actually im facing the same problem again and again
me too can't figure it out, very sad
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.