Database Info

stuck in cwm, adb wont work

hi guys
I've been searching and trying around some days but I cant get it fixed.
My Transformer TF101 is stuck in a CWM bootloop and cant get anything done.
Cant access my rom anymore, cold boot wont work and my pc wont reconize my tablet anymore.
Adb wont work any way, tried many things.
Maybe anyone got a solution for this?
Greetings,

My suggestions:
1- Try a different PC. Quick solution - use a Live Linux CD/DVD to boot linux and on your current PC and see if that works.
2 - Does APX mode work? If your PC detects it in APX mode (not linux, but Windows) then you can use NVFlash/Wheelie or EasyFlasher to flash a working recovery.
3 - Do you need a new charging cable? It IS possible that your cable still charges but does not work for ADB/APX. I had this happen to me.

It's kinda weird, adb did work 1 time and then the tablet went off because it was out of battery and now I can't get it back anyway..
APX mode is with power + volume down right?
I got the black screen but thats all.. computer(s) will still not see the tablet connected.
USBDeview doesnt even reconize my tablet connecting anymore.. probably my usb cable, what u mentioned.

Kryptonice said:
It's kinda weird, adb did work 1 time and then the tablet went off because it was out of battery and now I can't get it back anyway..
APX mode is with power + volume down right?
I got the black screen but thats all.. computer(s) will still not see the tablet connected.
USBDeview doesnt even reconize my tablet connecting anymore.. probably my usb cable, what u mentioned.
Click to expand...
Click to collapse
APX mode is Power & Volume Up, you'll see nothing on the tablet screen, but if you have it connected to USB, the PC should see it when it enters APX

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.

[Q] Bricked TF101?

Hello everyone,
some days ago I flashed Android Revolution HD but shortly I've found out that the TF101 wasn't recognized anymore by my PCs. When I've inserted the stock cable the tablet turned on but nor win 8.1 64bit nor windows 7 64bit recognized it. It even hasn't appeared between the unknown devices in the related window, so I couldn't install any drivers. Then I've decided to clean cache and system on TWRP recovery and after reboot the TF101 was stuck on logo screen, the boot one, not the next one with the ASUS logo.
Now the stock cable and the stock charger still work, they charge the tablet but the charging screen doesn't appear, if I turn on the device, it shows only the first android logo with the green bar, if I try to enter recovery with volume down button, it says 'entering the recovering' but it doesn't go any further. Last chance is the APX mode, with the volume up and turn on button: I've tried it but I can't recognize if it enters APX or not, I only know that in the devices list doesn't appear any unknown device, and I'm sure that the TF101 has never been connected before to this PC. At least, if I was able to connected it in APX I would use Easyflasher and flash stock rom.
Basically now it's a bricked tablet, any help please? Someon can tell me specifically how to enter APX mode, or is it a cable issue? Is this thing called 'governor' related to this?

[Q] (Q) (A700) Bricked? Help!

I received an Acer A700 from friend and here is the story;
He started getting the boot loop issue, Acer logo and reboot, etc...
He got into factory reset mode, and attempted a factory reset, during the process, it froze on "formating" and he attempted to shutdown the tablet. After he shut down, the tablet no longer does anything! Power LED only comes on during charging, and no beeps, no vibrate, no screen, just black. I have tried to use the usb connector to connect to my PC, but the device shows up as an APX device, but drivers fail to load, and then the device disappears. I have tried to install the latest usb driver from Acer, but no luck. I have the same tablet and I use CM and would like to get him moved over to that if possible! Any one has any suggestions, or is he bricked?
Thanks

Zoltair said:
I received an Acer A700 from friend and here is the story;
He started getting the boot loop issue, Acer logo and reboot, etc...
He got into factory reset mode, and attempted a factory reset, during the process, it froze on "formating" and he attempted to shutdown the tablet. After he shut down, the tablet no longer does anything! Power LED only comes on during charging, and no beeps, no vibrate, no screen, just black. I have tried to use the usb connector to connect to my PC, but the device shows up as an APX device, but drivers fail to load, and then the device disappears. I have tried to install the latest usb driver from Acer, but no luck. I have the same tablet and I use CM and would like to get him moved over to that if possible! Any one has any suggestions, or is he bricked?
Thanks
Click to expand...
Click to collapse
Again and Again "When Reset Factory Default within Setting than it will always bootlop".
Similar Problem About This Thread.
http://forum.xda-developers.com/iconia-a700-a510/help/a700-stuck-boot-loop-factory-reset-t2869270
http://forum.xda-developers.com/showthread.php?t=2778230
http://forum.xda-developers.com/iconia-a700-a510/help/acer-iconia-tab-a700-bootloop-help-t2878799

Zoltair said:
I received an Acer A700 from friend and here is the story;
He started getting the boot loop issue, Acer logo and reboot, etc...
He got into factory reset mode, and attempted a factory reset, during the process, it froze on "formating" and he attempted to shutdown the tablet. After he shut down, the tablet no longer does anything! Power LED only comes on during charging, and no beeps, no vibrate, no screen, just black. I have tried to use the usb connector to connect to my PC, but the device shows up as an APX device, but drivers fail to load, and then the device disappears. I have tried to install the latest usb driver from Acer, but no luck. I have the same tablet and I use CM and would like to get him moved over to that if possible! Any one has any suggestions, or is he bricked?
Thanks
Click to expand...
Click to collapse
If he's booting in APX mode, (black screen, PWR lite on, and seeing it shows up as an APX device), he's pretty well bricked. Problem is, it takes NVFlash to flash the proper files in that mode, and unfortunately also and SBK (Secure Bootloader Key) which Acer refuses to give us.
He can try doing a manual data erase (there's a post sticky on key combinations in the forums that explain how. )
If he can get it into fastboot somehow, it's possible to erase some of the partitions. Might help.
Heres the link for some manual modes. Note that some of them changed from ICS to JB, so might help to read all the posts. If he can get to fastboot, it would help a little.

[Q] Unable to unbrick my transformer

I've had my eee Pad Transformer TF101 for a few years now. I've had it rooted for most of the time, I've installed several roms before. But a few months ago I hard bricked (Pretty sure it's a hard brick) my tablet installing a new rom.
It will turn on, but it well stay on the ASUS logo for 5 minutes then turn off and start back at the ASUS logo until it turns off again. I use the power and down key to somewhat access recovery. I attempt to access recovery but all I get is a screen with an android on it's back with the red explanation point signal. The blue bar under the android acts like it loading, but I never get past this screen, and after a few minutes it will reboot to the ASUS logo again.
Also when I plug my tablet into my computer it will recognize that something is plugged in but is unable to install the driver. I've attempted to install other drivers but my computer wont allow me to, it keeps telling me the driver I have installed is the best driver, even though its not working.
I've looked all over xda, and I've tried easyflasher and peri. but I'm unable to connect to my computer successfully in order to get either to work.
Does anyone have any advice?

You need to get the Universal Naked Drivers installed
If you are running 64bit Windows, disable driver signing from safemode options - or use Win 7 32bit
Win 8.x needs driver signing disabled for both flavours
--
You need to stick the TF into APX mode (Power off then Vol up & power till the PC recognises it and tries to install the drivers) then install the above drivers and try Easyflasher again

I got the Universal Drivers working a few hours ago. I was able to boot into APX and have my transformer recognized by my computer. I ran Easyflasher several times trying to flash a recovery and using the stock/unbrick option, but it hadn't ran all the way through or told me on the tablet that it was successful until a few minutes ago. I tried again a few minutes ago and Easyflasher went all the way through and the tablet stated on screen that it was successful, excpet now I can't boot at all or even attempt to pull up recovery, it now doesn't boot into anything but APX.

Did you use the correct SBK on Easyflasher?
B6O serials and earlier are SBK1, some B7Os too, the rest above are SBK2
Wont do any harm using the wrong one, it just wont work
And to get out of APX mode, hold power for 30 seconds~, then power on normally
--
Did you try flashing it back to stock using the stock firmware instructions on the Easyflasher page ?
If you only flashed TWRP recovery, you will need to power on normally (not recovery) at least once and hopefully see the blue update progress bar under the ASUS logo for a few seconds while it updates RCK - then you should be able to power off and press VOL DOWN & POWER till you see the white text at the top of the TF screen - then release all buttons and within 5 seconds, hit POWER UP once to enter recovery