Dear all,
If you haven't updated it, don't do it.
My situation now is:
1. It stucks at the red dual core logo; (I think it shouldn't be called a boot loop)
2. It can't be powered down; (even I press and hold the power button forever!)
3. If I reboot it, I can still press the -vol button to choose between modes, but there are only 3: NvFlash; RSD; and fastboot. No "android recovery" option.
As of now, I put it into Nvflash mode so that the screen will not keep shining with the red logo.
May anyone suggest how I could unbrick it, or the worst case, reinstall everthing to stock?
Thanks very much for your help!
204 and 205 don't work...
If you had read a few posts back on the thread you would know this.
203 however is great...just clear caches and flash...all will be fine.
ionSeven said:
204 and 205 don't work...
If you had read a few posts back on the thread you would know this.
203 however is great...just clear caches and flash...all will be fine.
Click to expand...
Click to collapse
I have known that already, didn't u notice?
I know 203 is great, too.
My problem now is I am stocked, and couldns't get into the recovery. Any suggestion to fix it?
I have tried some brick fixing method in the forum, but a strange thing is even though I can control and even flash files to my xoom, but if I typed "adb devices", it shows that the xoom is actually not connected. And thus, the work I have done didn't help at all.
Waiting for someone who is Almighty to help me!
Hi, I think you can try flashing the recovery again with the fastboot. Do the following:
Plug your Xoom to your PC
Open a cmd (if you're on Linux tell me)
Go to your fastboot folder with it
Download a recovery and rename it to recovery.img
Type:
Code:
fastboot flash recovery recovery.img
It may do the work, if it doesn't work, please quote this post and I'll tell you how to factory reset .
great fix, back working
XxLordxX said:
Hi, I think you can try flashing the recovery again with the fastboot. Do the following:
Plug your Xoom to your PC
Open a cmd (if you're on Linux tell me)
Go to your fastboot folder with it
Download a recovery and rename it to recovery.img
Type:
Code:
fastboot flash recovery recovery.img
It may do the work, if it doesn't work, please quote this post and I'll tell you how to factory reset .
Click to expand...
Click to collapse
I am a long time reader but this is my first time writing a comment.
the most recent update locked up my xoom but this brillient reply saved me, I flashed twrp and recovered to a older rom flash i still had in goo manager. Thank you very much.
diamondvsn said:
I am a long time reader but this is my first time writing a comment.
the most recent update locked up my xoom but this brillient reply saved me, I flashed twrp and recovered to a older rom flash i still had in goo manager. Thank you very much.[/QUOT
Congrats! U r so lucky.
As of me, I tried, no luck. I flash the recovery, the computer told me it's successful, and the tab showed the same. But when I reboot it, I still got only 3 options: nvflash,RSD and fastboot.
And I think one of the important point is, when I connected it in the fastboot mode, I type "adb devices", my devices didn't show up. However,I can still flash the recovery with fastboot commands. Strange.
Click to expand...
Click to collapse
XxLordxX said:
Hi, I think you can try flashing the recovery again with the fastboot. Do the following:
Plug your Xoom to your PC
Open a cmd (if you're on Linux tell me)
Go to your fastboot folder with it
Download a recovery and rename it to recovery.img
Type:
Code:
fastboot flash recovery recovery.img
It may do the work, if it doesn't work, please quote this post and I'll tell you how to factory reset .
Click to expand...
Click to collapse
Thanks so much for your help. I tried this. But still no luck. I have mentioned the situation in the above post. Pls give suggestions. Thanks.
tech.arthur said:
Thanks so much for your help. I tried this. But still no luck. I have mentioned the situation in the above post. Pls give suggestions. Thanks.
Click to expand...
Click to collapse
Okay, so your case seems worse than I expected... Somehow it seems your recovery partition for screwed . I will think a little, if I don't come off with anything I will send you a guide on how to restore to stock (unless you want it now I can send it). Gimme some time and I hope to find an answer for you
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
tech.arthur said:
Thanks so much for your help. I tried this. But still no luck. I have mentioned the situation in the above post. Pls give suggestions. Thanks.
Click to expand...
Click to collapse
So, I did a little research and it seems that NVFlash is a thing back from HC LOL! I dunno how you got there, but I'll help you getting out! Remember the following will completely wipe your device, if you want to take some more time I can see if I can find a way to get you out without wiping. So here we go:
Download the Stock ROM from here: http://forum.xda-developers.com/showpost.php?p=13178555&postcount=2
Extract it to a folder which cointains fastboot protocol
Boot your tablet in fastboot and plug it to your PC
Open a cmd and go to the fastboot folder
Type:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Hope this saves your device .
Dear friend,
I am so glad there is a person who cares so much to others.
I would like to wait for u, for a way that needn’t wipe everything. For there are some photos in the internal memory.
Or a way that I could back up everything first. Wait for your good news.
Thanks in advance!
QUOTE=XxLordxX;43575614]So, I did a little research and it seems that NVFlash is a thing back from HC LOL! I dunno how you got there, but I'll help you getting out! Remember the following will completely wipe your device, if you want to take some more time I can see if I can find a way to get you out without wiping. So here we go:
Download the Stock ROM from here: http://forum.xda-developers.com/showpost.php?p=13178555&postcount=2
Extract it to a folder which cointains fastboot protocol
Boot your tablet in fastboot and plug it to your PC
Open a cmd and go to the fastboot folder
Type:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Hope this saves your device .[/QUOTE]
tech.arthur said:
Dear friend,
I am so glad there is a person who cares so much to others.
I would like to wait for u, for a way that needn’t wipe everything. For there are some photos in the internal memory.
Or a way that I could back up everything first. Wait for your good news.
Thanks in advance!
XxLordxX said:
So, I did a little research and it seems that NVFlash is a thing back from HC LOL! I dunno how you got there, but I'll help you getting out! Remember the following will completely wipe your device, if you want to take some more time I can see if I can find a way to get you out without wiping. So here we go:
Download the Stock ROM from here: http://forum.xda-developers.com/showpost.php?p=13178555&postcount=2
Extract it to a folder which cointains fastboot protocol
Boot your tablet in fastboot and plug it to your PC
Open a cmd and go to the fastboot folder
Type:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Hope this saves your device .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't think this wipes internal memory. Just application data.
ChillyChan said:
I don't think this wipes internal memory. Just application data.
Click to expand...
Click to collapse
Yes, it will wipe your internal data, when I first did the command I thought the same as you, resulted in a loss of 13-14GB of storage . So now you know and will never do this without warning . About the case now, can someone make me and the OP a favor?
Get the stable EOS 4 ROM, install it, go to adb shell and type:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/sdcard/recovery.img
Then upload those three files
So the OP will be able to fastboot flash the files and it will probably boot, as it's the same ROM he was using before, prolly it will require only a 'fastboot erase cache' command.
Hope you can help with it .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
XxLordxX said:
Yes, it will wipe your internal data, when I first did the command I thought the same as you, resulted in a loss of 13-14GB of storage . So now you know and will never do this without warning . About the case now, can someone make me and the OP a favor?
Get the stable EOS 4 ROM, install it, go to adb shell and type:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/sdcard/recovery.img
Then upload those three files
So the OP will be able to fastboot flash the files and it will probably boot, as it's the same ROM he was using before, prolly it will require only a 'fastboot erase cache' command.
Hope you can help with it .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
So let me see if I get it right:
The method u suggest now, is useable even I can only control the device in fastboot mode?
I need to boot it in fastboot mode, and then type the commands u posted.
Now, could I just download a 203 zip and unzip it to do so?
XxLordxX said:
Yes, it will wipe your internal data, when I first did the command I thought the same as you, resulted in a loss of 13-14GB of storage . So now you know and will never do this without warning . About the case now, can someone make me and the OP a favor?
Get the stable EOS 4 ROM, install it, go to adb shell and type:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/sdcard/recovery.img
Then upload those three files
So the OP will be able to fastboot flash the files and it will probably boot, as it's the same ROM he was using before, prolly it will require only a 'fastboot erase cache' command.
Hope you can help with it .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
I learned it the hard way ha ha. Followed your directions and I was able to boot the tab (my brother's) to stock but all data is gone like you said. Too bad I didn't check the thread before that.
Now it's running EOS 203 with no problems. I'd help you upload the images but my upload speeds are terrible so if you/he can wait till tomorrow, I can upload it overnight.
Btw, can he just flash the stable EOS 203 zip using "fastboot flash zip"? I could do it on HTC One X so I'm just wondering if Xoom supports it too. The recovery is just CWM Touch from clockworkmod.com and the boot.img is in the ROM zip.
tech.arthur said:
So let me see if I get it right:
The method u suggest now, is useable even I can only control the device in fastboot mode?
I need to boot it in fastboot mode, and then type the commands u posted.
Now, could I just download a 203 zip and unzip it to do so?
Click to expand...
Click to collapse
ChillyChan said:
I learned it the hard way ha ha. Followed your directions and I was able to boot the tab (my brother's) to stock but all data is gone like you said. Too bad I didn't check the thread before that.
Now it's running EOS 203 with no problems. I'd help you upload the images but my upload speeds are terrible so if you/he can wait till tomorrow, I can upload it overnight.
Btw, can he just flash the stable EOS 203 zip using "fastboot flash zip"? I could do it on HTC One X so I'm just wondering if Xoom supports it too. The recovery is just CWM Touch from clockworkmod.com and the boot.img is in the ROM zip.
Click to expand...
Click to collapse
Hehe, the hard is way is the worse (but at least you never forget lol). About the update.zip, what happens is the following:
When you do an update.zip file, you write something like a "install script", which the recovery reads and apply, that's what the update.zip does while the fastboot simply flashes the partition itself. That's the difference, what I think you used on your HTC One X is adb sideload, which I used some times already, which basically sends the zip to a tmp folder and install it. The thing is, fastboot is very different from adb, so you can't simply do it. On new devices (with unlockable bootloaders) the fastboot has already some new cool features, I tried to use on my Xoom to see of worked, but no luck, the command was "fastboot boot recovery.img" which could prolly work on OP case, however Xoom's bootloader is old and doesn't support this command. I don't mind waiting and am very grateful for your help . Hope we cab fix Arthur's tablet soon !
~Lord
PS.: regarding your other question @tech.arthur, that command should be used by someone with a Xoom booting, so we can get the EOS4 system.img and boot.img, this way you can boot your tablet after flashing the new imgs with fastboot .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
XxLordxX said:
Hehe, the hard is way is the worse (but at least you never forget lol). About the update.zip, what happens is the following:
When you do an update.zip file, you write something like a "install script", which the recovery reads and apply, that's what the update.zip does while the fastboot simply flashes the partition itself. That's the difference, what I think you used on your HTC One X is adb sideload, which I used some times already, which basically sends the zip to a tmp folder and install it. The thing is, fastboot is very different from adb, so you can't simply do it. On new devices (with unlockable bootloaders) the fastboot has already some new cool features, I tried to use on my Xoom to see of worked, but no luck, the command was "fastboot boot recovery.img" which could prolly work on OP case, however Xoom's bootloader is old and doesn't support this command. I don't mind waiting and am very grateful for your help . Hope we cab fix Arthur's tablet soon !
~Lord
PS.: regarding your other question @tech.arthur, that command should be used by someone with a Xoom booting, so we can get the EOS4 system.img and boot.img, this way you can boot your tablet after flashing the new imgs with fastboot .
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
So, I can't download the 203 nightilies .zip to unzip it to use those .img files?
I have to wait for the uploads, right?
A bit confuse to me. Sorry.
tech.arthur said:
So, I can't download the 203 nightilies .zip to unzip it to use those .img files?
I have to wait for the uploads, right?
A bit confuse to me. Sorry.
Click to expand...
Click to collapse
Unfortunately yes you'll have to wait, the zip has no imgs.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Oh, I re-read everything, I understand now.
So dear friend ChillyChan, I will wait for your upload, and I am pretty sure you will get a lot of thanks Cox I believe a lot of noobs like me out there is stucked too! Haha!
XxLordxX said:
Unfortunately yes you'll have to wait, the zip has no imgs.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
Yes, I will wait patiently.
You guys are awesome! Thanks thanks thanks!
XxLordxX said:
Unfortunately yes you'll have to wait, the zip has no imgs.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Galaxy S4
Click to expand...
Click to collapse
Wanna clarify: if I leung wait for the.img files, I wouldn't need to wipe my tab to save it, right?
Related
Like a complete prat, I have lost my boot and recovery img!!!
I was trying to get clockwork recovery as the recovery img and then accidentally did:
fastboot flash boot recovery.img
instead of
fastboot flash recovery recovery.img
I have found an unlocked bootloader from here (third one down) http://forum.xda-developers.com/showpost.php?p=9869067&postcount=38
I have saved this to the AndroidSDK\tools file as bootloader.img and tried the below whilst in fastboot mode:
fastboot flash boot bootloader.img
but the phone only reboots to the fastboot screen.
I now have no phone and I need it for work, can anyone help me, im desperate?
Thank you
Why not just flash cwm recovery then flash a ROM?
There's a sticky in this forum section with almost all full ROMs (stock Android, no need to flash cwm recovery for the signed ones, can use stock recovery) or head over to dev forums and look for a custom ROM you like (need cwm recovery).
Be sure to pick the right ROM for your device.
you don't need a bootloader! you need a boot.img! a kernel with ramdisk! ^^
Sent from my Nexus S using XDA Premium App
If the following command was executed successfully:
Code:
fastboot flash recovery recovery.img
Next step is to download a ROM of your choice and flash it via ClockWorkMod recovery and you're good.
FYI, the command
Code:
fastboot flash boot ...
does not flash your "bootloader". It is used to flash the kernel, which will already be included in the ROM you downloaded.
meso100 said:
...instead of
fastboot flash recovery recovery.img
I have saved this to the AndroidSDK\tools file as bootloader.img and tried the below whilst in fastboot mode:
...but the phone only reboots to the fastboot screen.
Click to expand...
Click to collapse
No problem. Flash your recovery using the correct command (above).
If you have access to fastboot, use your volume keys as up and down, and navigate to the "Recovery" option. When your phone boots into recovery, you can mount your USB and copy a ROM to your device.
Then go back, do a factory/data wipe, and flash the zip you copied. This should restore your phone.
Recovery images:
http://forum.xda-developers.com/showthread.php?t=988686
ROMS:
http://forum.xda-developers.com/showpost.php?p=13556812&postcount=2
Thank you all for your replies and help and apologies for the late delay.
I have been away for a few days and with your help and a bit of playing about I managed to sort out the problem. I was probably a bit hasty to ask for help but actually felt that I had bricked my phone!
This happened because I was following two different fastboot flash guides on the net...lesson being just keep to one!
Also, when I lost cwm I didnt know how to get it back...but again you can only learn from your mistakes and I did.
I managed to get cmw reinstalled and cm7 flashed.
Now I am running the latest MIUI and it is pretty good.
Thanks all for your help, see you the next time I panic!
meso100 said:
Thank you all for your replies and help and apologies for the late delay.
I have been away for a few days and with your help and a bit of playing about I managed to sort out the problem. I was probably a bit hasty to ask for help but actually felt that I had bricked my phone!
This happened because I was following two different fastboot flash guides on the net...lesson being just keep to one!
Also, when I lost cwm I didnt know how to get it back...but again you can only learn from your mistakes and I did.
I managed to get cmw reinstalled and cm7 flashed.
Now I am running the latest MIUI and it is pretty good.
Thanks all for your help, see you the next time I panic!
Click to expand...
Click to collapse
Thanks for using your brain and figuring it out. Congrats on getting it up and running.
Sent from my PC36100 using XDA Premium App
I know this is not a new subject. but i feel i wont get a response in another thread that is pretty outdated. so im trying to flash cwm recovery thru fastboot but i get an error. I've tried typing the directory path c:\android-sdk\platform-tools\recovery.img. i get "cannot load recovery.img". this is what im typing
fastboot flash recovery c:\android-sdk\platform-tools\recovery.img
and i still get the error. I've even tried moving the recovery.img to c:\recovery.img
but no matter where or how i call it. it wont load. please help guys. I had android sdk install before but i had to wipe my pc clean and i just recieved a replacement nexus s 4g.
Have you tried navigating to the folder where recovery.img is located and typing "fastboot flash recovery recovery.img"
Sent from my Nexus S using XDA App
What do mean navigating? Typing the directory path?
Sent from my Nexus S 4G using Tapatalk
I think he means typing this first:
cd c:\android-sdk\platform-tools\
So how would I type this? I don't I am... please elaborate. Thank
Sent from my Nexus S 4G using Tapatalk
What operating system are you using? Windows?
Sent from my Nexus S using XDA App
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Harbb said:
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
wow. i did everything mentioned. i even redownloaded the recovery image. and i still get cannot load error. i even did it where i renamed it and left it alone the way it was typed
Is your bootloader unlocked? Also, fastboot devices shows a serial number right?
Harbb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
yup its unlocked.
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
let me give this a tried
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow this did it for me... i dont understand bc i typed
fastboot flash recovery rec(tab)
fastboot flash recovery recovery.img.img and i hit enter and it flashed. weird. but thanks dude i greatly appreciate it for sticking it out with me.
Wonderful. You probably have "hide file extensions for known file types" checked. So when you downloaded the original, it ACTUALLY had a .img on the end of it already (which windows hid from you). Windows, unlike unix, cannot differentiate files based on their header, but instead relies on a useless extension in the file name of all places (ie, .img, .mp3 and .jpg at the end of the filename).
And noo problem mate, happy to help.
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Techno Droid said:
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Click to expand...
Click to collapse
weird. i downloaded superuser from the their website and flashed. it didnt show. so i downloaded it from the market and tried running an app that requires su permission and it worked. am i missing something here? why did this work that way?
Flash this su.zip file. There was an older su version that automatically accepted any su access because it wasn't compatible with ICS yet.
thanks. it feels good to finally be rooted. i was stock for 2 days.. lol thanks
cannot load recovery.img
Thanks. the TAB autocomplete worked. I had forgotten about the additional file extension. gotta change that setting. Thanks again
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow, thanks man, you made my day, was about to throw the phone from anger. thanks a million man thank you.
hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
iostu said:
hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
Click to expand...
Click to collapse
Unless you can go into fastboot (Power + volume down) there isn't much to do but to sign a petition & wait...
XDA member HAZARD17 has been running a petition
Sign NVflash petition for Transformer TF300T, Prime & Infinity!
https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash
vconceicao said:
Unless you can go into fastboot (Power + volume down) there isn't much to doo but to wait...
Click to expand...
Click to collapse
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
iostu said:
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
Click to expand...
Click to collapse
For someone to come up with a solution, Like a NVflash utility for Tf300...
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Hazard17 said:
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Click to expand...
Click to collapse
i can't flash anything :| in adb it sais <waiting for device> i've tried everything and i can't get it to work.. can you pleeeeeease help me ?
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
The USB icon is gone. I sugguest downloading the correct firmware and flashing it with fastboot.
fastboot flash system blob
Download the correct system firmware, open the zip, open the zip, extract the blob to the same directory as fast boot.
iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
4.2 bootloader does not have USB icon, just plug in USB..
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
Sounds like you're in the same boat as the rest of us...
http://forum.xda-developers.com/showthread.php?t=2179874
iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
OK. The bootloader menu you now are seeing is the new 4.2 version. RCK - Android - Wipe Data(do not use wipe data).
When you get into this menu if you leave everything alone your tablet should auto into fastboot - watch the screen - upper left.
With fastboot flash the latest (proper) JB blob for your unit.
Good Luck!
iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
hgoldner said:
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
Click to expand...
Click to collapse
Here is an example of an adb command that does work to flash twrp with slight modification it will flash stock blob as well.
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I don't know where you are getting your information but you need a new source.
No one said type adb fastboot they are two different things and each has a specific structure to follow.
If the op can get either fastboot or adb to work I'll gladly provide the proper commands.
then you have the same problem as me and a bunch of other people. The bootloader freezes on the flash command, even though it will show success and stuff. It never flashes.
I can push files with ADB and on reboot the files on gone. Since we can't flash with fastboot. We have to send it in to asus at this point. I got quoted $87 + shipping.
sorry, i meant to say just fastboot. i didn't write adb fastboot.. i've tried everything you guys said, but with no success my last resort is to send it to asus for re-softing. It costs about $80 + shipping. It doesn't sound like a lot of money, but it's a price to pay for stupidness or noobness i just hope they can repair it or otherwise i'll have a very expensive thing on whch to chop onions
thanks again guys for helping me
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
zenkix said:
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
Click to expand...
Click to collapse
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
RollTribe said:
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
Click to expand...
Click to collapse
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
zenkix said:
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
Click to expand...
Click to collapse
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
RollTribe said:
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
Click to expand...
Click to collapse
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
zenkix said:
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
Click to expand...
Click to collapse
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
RollTribe said:
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
Click to expand...
Click to collapse
Quick update...I flashed boot.img of the first link (CynogenMod) and my phone got passed the "HTC Quietly Brilliant" screen! But now it seems stuck on HTC One (Beats Audio at the bottom) screen. I'll give it a few minutes...
I'm really worried that I did major damage to my phone in the bootloader and clockwork recovery menus. I literally tried every single option there trying to get my phone to boot earlier.
Oh man...it seems stuck. Maybe I should just flash the completely stock boot.img file. If that works, I will factory reset my phone just to make sure everything is back to how it was before.
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
timmaaa said:
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your help man. If what you're saying is correct, does that mean my phone is hopeless? I deleted/wiped everything using the ClocworkMod Recovery menu. When I choose "install zip from sdcard" I get "E: Can't mount /sdcard/" and when I try to mount an sdcard I get "Error mounting /sdcard". I don't think I can flash any ROMs right now unless install zip from sideload is an option (I don't know how sideloading works).
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
timmaaa said:
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
Click to expand...
Click to collapse
This sounds like a good plan. I will give it a try tomorrow after work. Thank you guys for your help!
I couldn't sleep...so I followed your steps and my phone is now alive! Thank you!
I think now I need to flash GApps, right? I have this ---> gapps-jb-20130301-signed.zip
Any chance that's the wrong zip file? Do I need a special one for CM10.1?
That's the right gapps zip, it's the most recent one so yeah you're good to flash it.
And no problems, you're welcome
Sent from my Evita
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?