Related
Hi all!
I'm an andoird newbie and I've a big problem with my tab!
I was using the NX Manager by my PC to unlockink my android table and installing CWM.
All was going all right but, while I'm using CWM I was entring in the Format/Mount section to mount "system" but I've click the wrong botton in the wrong line and I've format my system dir.
Now I've my nexus block on the main page, where ther is the "Google" string on black screen.
I thinks there's no problem because I'll can install an new Rom (like cm 10) but, when I connect my device to my PC, the PC don't recognise my tablet! And I can't reboot the tablet or entre in recovery mod! Is block!
What can I do!?
The Rootkit don't go, the NX manager don't go (because I was hoping thet they reboot my tablet in fastboot).
Rox666 said:
Hi all!
I'm an andoird newbie and I've a big problem with my tab!
I was using the NX Manager by my PC to unlockink my android table and installing CWM.
All was going all right but, while I'm using CWM I was entring in the Format/Mount section to mount "system" but I've click the wrong botton in the wrong line and I've format my system dir.
Now I've my nexus block on the main page, where ther is the "Google" string on black screen.
I thinks there's no problem because I'll can install an new Rom (like cm 10) but, when I connect my device to my PC, the PC don't recognise my tablet! And I can't reboot the tablet or entre in recovery mod! Is block!
What can I do!?
The Rootkit don't go, the NX manager don't go (because I was hoping thet they reboot my tablet in fastboot).
Click to expand...
Click to collapse
So what's the issue, you don't have a recovery installed any longer?
RMarkwald said:
So what's the issue, you don't have a recovery installed any longer?
Click to expand...
Click to collapse
No because I've done a mess!
I' ve formatted the "system" folder, and now my tablet is freezed on the startup screen, with the Google logo, and if I try to reboot it/shut it down, the tablet doesn't work. So i'm locked in this situation.
I've downloaded two roms: CM 10 and the orignial google roms.
The very big problem is that:
Windows doesn't recognises my tablet! It says that I've connected an USB MTP but don't open anything! So I can't do aything...Is there any flasher program that can help me?
A good way to reboot it may be to turn off the battery opening the back dock, but i'm not good in hardware-hacking so I wonder in any other solution.
Thanks
Just now I turned it off holding the Powerbutton+Volumeup ( but now doesn't reboot in any way) and Windows recognises it as an APX device
Another edit:
I just rebooted in the bootloader, but when I start the Recovery Mode, the tablet freezes on an "android" icon with a red "error" icon
Thanks
You can either do one of two things:
1. Start over from scratch going back to complete stock. This will erase your internal sd card, so anything there will be gone. Hopefully you have a backup if anything important is there.
LINK: http://forum.xda-developers.com/showthread.php?t=1907796
NOTE: Assuming you unlocked your bootloader already, start reading under the heading Flashing Factory Image, start at Step 3.
2. You can boot into the Bootloader, connect the tablet to your computer, use fastboot to flash a custom recovery, then use adb to push the CM10 zip file to your device, flash it in recovery and reboot.
There's a few steps involved in each, both use fastboot commands, so it's really up to you. I can explain either.
EDIT: The methods I'll describe do not use any sort of toolkit, which is also known as the "manual" way of doing things.
Problem solved!
Ok, I MADE IT!! :victory:
I forced the shutdown pressing PowerButton+Volume UP, then i Rebooted the device pressing PowerButton+Volume DOWN ( Fast Boot).
Then...
First of all I downloaded the Nexus7 Toolkit of XDA Developers,
- I downloaded the flash stock (Google/Nexus) ( Step 9 of the toolkit actions)
- and flashed the device from the Nexus7Toolkit (Step 9 of the toolkit actions again)
Then the device returned in "factory status", including the Bootloader version ( Removing the old Recovery Mode).
Problem Solved! :laugh:
Thank you very much for the instant support.
I was misunderstanding some things about installing the ROMS ( I've tried to Push the factory stock into the tab - Step 13 of the Toolkit) , so I thought I came in trouble, but following step by step the Toolkit commands, I made it.
Thank you so much.
Rox666 said:
Ok, I MADE IT!! :victory:
I forced the shutdown pressing PowerButton+Volume UP, then i Rebooted the device pressing PowerButton+Volume DOWN ( Fast Boot).
Then...
First of all I downloaded the Nexus7 Toolkit of XDA Developers,
- I downloaded the flash stock (Google/Nexus) ( Step 9 of the toolkit actions)
- and flashed the device from the Nexus7Toolkit (Step 9 of the toolkit actions again)
Then the device returned in "factory status", including the Bootloader version ( Removing the old Recovery Mode).
Problem Solved! :laugh:
Thank you very much for the instant support.
I was misunderstanding some things about installing the ROMS ( I've tried to Push the factory stock into the tab - Step 13 of the Toolkit) , so I thought I came in trouble, but following step by step the Toolkit commands, I made it.
Thank you so much.
Click to expand...
Click to collapse
You're welcome, glad I could help!
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Two options:
1. Flash a custom recovery using "fastboot flash recovery recovery.img", then boot into it and flash a ROM
2. Download the stock android images from the Google dev site and flash them using fastboot
nikonjunkie said:
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Click to expand...
Click to collapse
Download the 4.3 image HERE
Then, plug in your phone into your computer, boot into fastboot mode, extract the zip and run the flash-all.bat file (Or the .sh if your on a *nix/OSX computer). This will flash 4.3. If you don't want to loose your data, delete the userdata.img in the zip file before running the .bat/.sh file. Wipe cache in recovery, and it should boot.
Go into fastboot and download the stock image from Google.
Run the batch file it comes with and bam, you should be good to go
Sent from my Nexus 4 using xda app-developers app
nikonjunkie said:
The OTA update hit my phone this afternoon. I'm using the 16GB N4, rooted but running stock ROM. Install looked to be going fine, and then it restarted itself and hung up at the glowing X for about 20 minutes.
Possibly stupid, but at that point I held the power button down to restart it. Now I can't get past the X.
Booted into fastboot mode. Recovery Mode gives me the open Android belly icon and says "No command". Start hangs up at the X.
At this point I'm at a loss to what I should even try. I was on 4.2.2 before--no custom ROM or anything like that. Just unlocked bootloader and rooted.
Click to expand...
Click to collapse
Once you see the Android laying on its back with a red triangle, press and hold power button and then press volume up once. That'll take you to the recovery options. At this point you must decide if you want to wipe data/factory reset (which will let you go past the X logo) because that'll wipe your device, all your data will be gone.
lopezk38 said:
Download the 4.3 image HERE
Then, plug in your phone into your computer, boot into fastboot mode, extract the zip and run the flash-all.bat file (Or the .sh if your on a *nix/OSX computer). This will flash 4.3. If you don't want to loose your data, delete the userdata.img in the zip file before running the .bat/.sh file. Wipe cache in recovery, and it should boot.
Click to expand...
Click to collapse
Do I need ADB installed? Have never needed it for any reason on this computer
The flash-all.bat file is giving me the error "fastboot is not recognized as an internal or external command" (am on Win 8)
Not sure if it's relevant, but I don't believe I have USB debugging enabled right now. It is 99% of the time, but of course right now I'm almost sure it's not. Am I screwed? My phone isn't showing up as a drive on my computer like it normally would. Thanks in advance!
nikonjunkie said:
Do I need ADB installed? Have never needed it for any reason on this computer
The flash-all.bat file is giving me the error "fastboot is not recognized as an internal or external command" (am on Win 8)
Not sure if it's relevant, but I don't believe I have USB debugging enabled right now. It is 99% of the time, but of course right now I'm almost sure it's not. Am I screwed? My phone isn't showing up as a drive on my computer like it normally would.
Click to expand...
Click to collapse
Yeah, you need fastboot.exe. I attached a copy from my Windows partition. Download it, extract it, and put the fastboot.exe in the same folder that you have the flash-all.bat
lopezk38 said:
Yeah, you need fastboot.exe. I attached a copy from my Windows partition. Download it, extract it, and put the fastboot.exe in the same folder that you have the flash-all.bat
Click to expand...
Click to collapse
Thanks. I downloaded the file from your link, extracted it, moved to the same folder I have the BAT file. Ran the BAT file, got this error:
The program can't start becayse AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
nikonjunkie said:
Thanks. I downloaded the file from your link, extracted it, moved to the same folder I have the BAT file. Ran the BAT file, got this error:
The program can't start becayse AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
Click to expand...
Click to collapse
Same thing that you did with the fastboot.zip with the attached ADB.zip
lopezk38 said:
Same thing that you did with the fastboot.zip with the attached ADB.zip
Click to expand...
Click to collapse
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
nikonjunkie said:
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
Click to expand...
Click to collapse
Your welcome
nikonjunkie said:
IT'S ALIVE! Thank you thank you!
I had deleted that userdata.img file prior to all this, so let's see what data I keep. I just ran the initial setup and it's currently downloading my apps. WHEW.
Of course I did loads of icon customization last night before all this mess. I'm mystified what couldn't caused this OTA update to crap out. It looked to be going fine, little green line proceeding to the right as expected, then once it rebooted, it just stayed on that X forever.
Click to expand...
Click to collapse
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
nikonjunkie said:
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
Click to expand...
Click to collapse
I have the similar problem here - OTA 4.3 finished ok, but I've lost my root. When I try to boot into recovery, I got "No command" (probably in english, it's in fact translated) and Android laying with open belly.
After rebooting, system itself works as normal.
Thanks for any help.
nikonjunkie said:
I spoke too soon. So I expected to lose root, but now I still can't boot into Recovery mode even after installing the 4.3 image. Open Android belly. So I'm up and running but facing the same issue. Have been unable to flash custom recovery. Any ideas?
Click to expand...
Click to collapse
That's the stock recovery, press and hold power and then press volume up to get the stock menu
EddyOS said:
That's the stock recovery, press and hold power and then press volume up to get the stock menu
Click to expand...
Click to collapse
The open Android belly is *supposed* to show up? Wow, then I guess I've had a custom recovery so long I can't recall ever seeing this.
If I do that sequence, then I get the options:
- reboot system now
- apply update from ADB
- wipe data/factory reset
- wipe cash partition
If this is the stock recovery, then how do I go about getting a custom recovery on here? So far have been unsuccessful with sideloading anything via the toolkits. I'm now on 4.3, unrooted, but unlocked bootloader. I guess I was expecting the menu that permits you to flash a zip on the phone FROM the phone.
Thanks!
nikonjunkie said:
The open Android belly is *supposed* to show up? Wow, then I guess I've had a custom recovery so long I can't recall ever seeing this.
If I do that sequence, then I get the options:
- reboot system now
- apply update from ADB
- wipe data/factory reset
- wipe cash partition
If this is the stock recovery, then how do I go about getting a custom recovery on here? So far have been unsuccessful with sideloading anything via the toolkits. I'm now on 4.3, unrooted, but unlocked bootloader. I guess I was expecting the menu that permits you to flash a zip on the phone FROM the phone.
Thanks!
Click to expand...
Click to collapse
Download the latest TWRP version for Mako. Boot to bootloader. Open a CMD window and type:
fastboot flash recovery yourrecoveryname.img
Mercado_Negro said:
Download the latest TWRP version for Mako. Boot to bootloader. Open a CMD window and type:
fastboot flash recovery yourrecoveryname.img
Click to expand...
Click to collapse
J*sus C******. Now I can't even get the phone to be recognized as an ADB device. What happened since last night, I have no idea. The toolkits don't help, by any method. Have rebooted computer, phone, unchecked and rechecked USB debugging about a zillion times, uninstalled and reinstalled drivers. It's like the phone is invisible. Four more hours, and I am throwing this Nexus off the 23rd floor balcony.
Thanks, though!
nikonjunkie said:
J*sus C******. Now I can't even get the phone to be recognized as an ADB device. What happened since last night, I have no idea. The toolkits don't help, by any method. Have rebooted computer, phone, unchecked and rechecked USB debugging about a zillion times, uninstalled and reinstalled drivers. It's like the phone is invisible. Four more hours, and I am throwing this Nexus off the 23rd floor balcony.
Thanks, though!
Click to expand...
Click to collapse
When you connect your device via USB, does the computer recognize it and open up a window where you can see your files/folders?
Mercado_Negro said:
When you connect your device via USB, does the computer recognize it and open up a window where you can see your files/folders?
Click to expand...
Click to collapse
Sometimes it does, sometimes it doesn't. I can't figure out the inconsistency. Same things are checked. I've changed USB ports (tried all three), tried a new cable, quadruple-checked the settings. Rebooted the phone and the computer, and still it's inconsistent. I can hear the little chime on the computer indicating it's recognizing the device, but only half the time does it open the folder to view files. The other half of the time, the phone doesn't show up as a drive under My Computer at all--even after a refresh.
In a strange new dvelopment, in Wug's Nexus Root Toolkit, the phone is recognized in bootloader mode, but nothing on this green earth can make it show up as an ADB device when powered up and booted into Android. I've tried going at it from every angle. Didn't have this problem last night. Other than setting up email and moving icons around, I didn't do much to it, so I'm mystified and annoyed.
Thanks for any ideas.
Yeah, that's happened here as well. Sometimes I have to unplug and plug it back in to make it show folders and files. It's inconsistent as you say (though to be honest, I can't remember if it's happened again since I flashed 4.3 a week ago). Anyways, you say that adb can't see it when you type "adb devices", right? If you turn off your device (unplugged), then press and hold power and volume down buttons for a few seconds to go to Bootloader and then plug it back in, can you run any adb command? Like push, pull, etc.? That would rule out any faulty file in your platform-tools folder (where fastboot.exe is).
This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.:good:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link ---> http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 because that's the guy that wrote this procedure from above (credits to him) :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This part was me now -ozkrtech <--- (credits to me)
In addition to that, if you simply can't see your device using the command "adb devices" go check on device manager if you see a device called just "Transformer" with a yellow icon indicating it needs a driver, and manually update driver, select "browse my computer for drivers" and then select let me pick from a list of device drivers on my computer" there you will see a list of like 3 different drivers, one of them says "bootloader" and one of the others says "adb" (i think they self explain) but just in case try with each one of them you can keep on switching drivers until you get your device recognized by the command "adb devices".
You should be asking yourself... whats the right moment to do an "adb devices" command? well my tablet same as -Buster's tablet had the wrong recovery menu flashed (wrong bootloader version) and it just kept booting into the corrupted recovery (in my case TWRP) with the "can't mount anything" and "what's the password" issue. When you get to password screen just hit cancel and try the "adb devices" commando and you'll see it gets recognized with your device serial number.
Once your device gets recognized by "adb devices" command you will proceed to use "adb reboot-bootloader" command and the tablet will reboot into the menu that had 4 options but now have 3 options and its missing the fastboot option (don't panic) in the last bootloader it is auto-fastboot mode when you reach that screen with just 3 options in it now (yeah is the screen with the RCK option) at this point try "fastboot devices" command to see if your device gets recognized same as "adb devices" procedure, it should get recognized with a different serial number (don't know why, maybe that number isn't a serial number), at this time you are SO LUCKY! now you will follow what I posted at the beginning from that other dude ---> (-Buster) or follow his link --- > http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
And you'll have an unbricked tf300t in no time =) (I personally used the stock but newest Asus ROM) 4.2.1 (10.6.1.27.1) and it worked flawlessly.
**NOTE** don't turn off nor reset your device once you have formatted the partitions, no need for that (don't know what happends but it might get really hard bricked) just proceed to flash the stock rom after erasing the partitions.
I'm 100% positive this will work if your device is in same state as ours. (had TWRP for JB) then updated bootloader to version 4.2 and forgot to update twrp to version 4.2 or installed twrp version JB by mistake and lost fastboot and TWRP is asking password.
Hope it helps. Let me know your status and if it worked for you.
So I am in the same boat as I flashed the wrong twrp. My device shows up under adb devices and I can boot into the bootloader using adb reboot-bootloader. However, once there, I can not get the device recognized with fastboot. I have tried messing with the drivers like you suggested but nothing will get it to show up with fastboot. Anybody have advice on where to go from here?
So extra info. The device bootloops into twrp 2.6. The only way I can boot into fastboot mode is with adb reboot-bootloader and I can get into APX. I can also boot directly into my current ROM (Slim beta 3) by selecting android in the bootloader menu. I have tried flashing proper recovery through flashify, which is says was successful, but the wrong twrp never gets overwritten. Rebooting the device will send it back to twrp.
Thanks if anyone can help
Thanks, man! It took a while to find this thread, but this was exactly my problem. The adb driver in windows was the pre-solution to help get back to the fastboot server in the bootloader. Awesome information. Thanks again!
I have tried "adb reboot-bootloader" and then adb devices and fastboot devices and neither will show the tab listed while the tab reaches that screen with just 3 options. I have uninstalled reinstalled drivers, it does show in device manager as Asus Android Composite ADB Interface but when running the command it will not list the tablet. Any suggestions?
Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Remember please I cannot go in fastboot recovery menu, only apx. Thank you in advance!
I can not thank you enough!!! my tablet is now working I honestly though it was done for aha THANK YOU!!!
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following the OP's guide I was successfully able to reflash stock firmware and the device runs fine now.
However, upon reflashing said firmware, it became apparent to me (from reading various threads in the development subforum), that I would need to downgrade to an older firmware version to reflash TWRP. So I did that successfully, but now I am having a problem similar, or perhaps identical, to that of Bionicbowtieguy, in that ADB appears to be broken for my tablet. I have tried uninstalling and reinstalling the Asus usb drivers, in addition to reinstalling/updating all of the ADB software. Fastboot still works fine, but as such I'm unable to root using Motochop's rooting kit (I know there are other methods out there), nor am I able to flash a new recovery. I have also tried repeatedly reflashing the older stock in the hopes that ADB would magically start working again to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Kombatant said:
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Click to expand...
Click to collapse
Same here!
Thank you OP for making this a topic even if you didn't come up with it you made it a thread that has saved a few people like myself money and headaches. Literally I just stumbled on this thread 10 minutes after I told my wife is be Tablet shipping Black Friday. Thank you sir.
Thank you.
I did this on a hackintosh running OSX since on Win 8.1 fastboot kept crashing.
March of this year I bricked my tablet during that 1 week period where nobody knew that TWRP was broken + fastboot freezing.
I must have tried everything, Maybe that erase misc was the key factor for success.
I was about to sell this for what I could get or send it to asus, now I can use it again!
How are you guys getting your tablet into fastboot mode? I've tried power on with volume down, the reset hole with volume down, and letting the battery die then recharge, then power on with volume down... Nothing. What am I doing wrong?
Sent from my Galaxy Nexus using Tapatalk
Best thread ever!! You are a life saver !!! thank you!!
leris2 said:
Best thread ever!! You are a life saver !!! thank you!!
Click to expand...
Click to collapse
Indeed. You are a god among men. Thank you so much
This worked! I thought I was out of luck. Thanks a lot.
I accidentally flashed an incomparable version of twrp. It would only boot straight into recovery and I couldn't get into recovery. TWRP kept asking for a password even though I never set one up and it wouldn't mount the internal storage or sd card.
I had to follow the instructions at the bottom to intall the drivers so adb and fastboot to work. After that I followed the instructions at the top.
The only thing different I did was skip the "fastboot erase boot" step. I was afraid that would really brick my device if I screwed up (Does this really erase the bootaloader leaving the device with no bootloader?).
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Fastboot
Bolandk said:
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Click to expand...
Click to collapse
They do not sit at all they will go right to it. You must not have the right combination yet. Keep trying.
Took me awhile to get the link.
norm883
FIXED!
BY GOD, I have no words for how incredible grateful I am right now! You not only saved my TF300T's life but also a lot of money for me and gave me another lesson of Android insight.
Thanks so much for this!
Let me know if I can return the favor somehow!
Regards,
(a very happy) philleicht
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
same problem reboot back to twrp
well i may be stupid because i can't understand why i have tried a couple of commands and i still get the same problem reset volume down still goes back to twrp and ask for a password can someone please explain this in alittle more detail and what commands i also get the waiting for device in my commands is there another way to push these files into this device tf201 please help is there a way to do something in the twrp recovery like terminal command
I was a fool for flashing wrong recovery!
DrPhant0m said:
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
Click to expand...
Click to collapse
I have exactly this! I hope someone knows the answer for this issue. Else the tablet will learn how to fly!
I tried to push the reset button as described earlier but nothing changes. Not able to go into recovery Just stuck at ASUS in the middle NVidia in the bottomright corner en upperleft corner 'this device is unlocked'
As the title indicates, I soft-bricked my G2 via bad rom flash (wrong version of CM)
This post will be my outline of how I got my phone out of this mess and operating perfectly.
I foolishly made the mistake of not making a backup so as a result, I have scoured numerous forums and pushed my google-fu to it's limits. Biggest tip I can advise (as if it needs to be said again) is to backup before you do any flashing. If things go south though, here's what happened to me and how I fixed it all.
I rooted and installed TWRP 2.6.3.2 then did full wipe and flashed the wrong G2 version of CM from the internal storage. Rebooted and got the "udc_start()" message of sadness.
Hard reset the device by doing the power button/volume down thing which involves the following:
fully black screen except for tiny little message saying something like UDC_Start() and some other jibberish. Basically it doesn't do anything.
Hold down the power button for about 12~15 seconds. After 10 seconds the phone display will shut off and the LG logo will pop back up. KEEP HOLDING THE POWER BUTTON DOWN.
The screen will shut off again.
Now holding the volume down button, press and hold it and the power button together until the LG logo comes up again.
Release the buttons and then quickly hold down the power button again until you get a device reset screen.
hit the power button to confirm and it will load up TWRP.
I was relieved to be back in recovery but it dawned on me that the wrong version of CM is the only rom I had on my phone. Performing a factory reset does not fix the issue.. just kicks me back to that UDC error.
Next level googling engaged. I had the CORRECT ROM and a couple others for my device downloaded but I had to somehow get them onto the internal storage so that I could flash them.
HOWEVER, I also discovered in the hellfire rom thread, there are issues with TWRP version 2.6.3.2 flashing roms and that flashing the PHILZ recovery from within TWRP (just like flashing a new rom) to replace TWRP would work. I didn't want to take any chances so I got that zip file from here.
http://forum.xda-developers.com/showthread.php?t=2201860
To get these zip files onto the device, ADB push command was the trick.
I grabbed this (if the link is broken, google search for ADB fast boot zip)
http://d-h.st/iqA
And extracted the files to a folder on the desktop.
Next, after reading through some ADB push threads, I copied the zip files into the ADB folder on the desktop and then in windows explorer, hover the mouse over that ADB folder and then shift + right click the folder and in the pop up menu, select "Open command prompt window here"
it's efficiency - not laziness
then with the phone connected via usb cable to the computer, in that prompt type this
adb push ROMNAME.zip /sdcard/
After a short wait, it showed a couple hundred megs worth of a file was transferred. I repeated the command again with the PHILZ recovery zip name and again, it showed completing the transfer.
Time to get to work.
From TWRP, I went to flash a zip, pointed to the PHILZ zip file and successfully flashed that, went back to the main menu and then told it to reboot back into recovery.
I was greeted with the snazzy PHILZ recovery interface.
I then told it to do a wipe for a new ROM install and then after that completed, went to flash a zip, pointed it to the correct version of CM this time and flash was successful.
Crossed my fingers and rebooted the device and SUCCESS! Up and running perfectly.
hopefully this helps those who find themselves in the unfortunate soft brick scenario or something similar that I was in.
Great stuff. I'm sure this saved a couple of lives. Comment bump for ya.
Sent from my LG-D802 using Tapatalk
Hello, going to put this here if it helps anyone else out. Couldn't find a post that helped (there may be I might have not looked hard enough lol)
So after leaving it for a week today I let my Nexus 9 WiFi only do the latest OTA security update, halfway through it came up with an error and on reboot got stuck booting with the little Android fella on his back with a message saying it was corrupted.
First thing I went to do was install the factory stock image, but this would not let me as I had not unlocked the bootloader (and couldn't as I couldn't access the Dev menu in android previously). Tried a few other things including factory wipe/fastboot/etc and this is what fixed it for me
Note: you need ADB installed (plenty of ways to do that on XDA)
- Download latest OTA here
- Connect tablet to PC with USB
- On the recovery screen bring up the menu (Power button + up)
- Select 'Apply update from ADB'
- [Windows] Bring up CMD and navigate to the update location (Hold shift + right click brings up the option to open CMD in that folder location)
- Type 'adb sideload (ota file.zip)' in brackets is the file name of the download (Copy the file name and right click into CMD/Paste)
- Tablet should update and be working after that
I also wiped Cache after installing the image, whether you need to do that I don't know. Tablet is now back up and running. I had factory reset the unit before trying this, so I don't know if it will keep data. I assume it would do as OTA don't normally wipe data.
Hopefully this helps someone
This issue pops up every month with corrupted OTA process.
Numerous threads with this solution posted in it.
Thanks for sharing.