Database Info

Bootloop, Fastboot and the Broken Power Button - Help!!

Hey all
I was in the midst of an update via clockwork recovery (to get back to stock rom and lock the bootloader...warranty purposes to repair the power button that does not work...)
Well, I am now in a bootloop, and cannot get fastboot to work.
What is interesting is that though the power button doesn't work, I can still get into the bootloader screen, but my volume up/down buttons don't work (and they work a-okay usually) I can't even choose to boot into recovery...sigh.
In fastboot, it just get "wating for device"
Kind of stuck and now paranoid....
Need this beast resurrected...any help is appreciated!
Thanks gang!

I have literally the exact same problem, took it to a repair shop, but the guy tried to tell me my power button was working fine and that it was a software issue. Yeah but not really sure what we can do if our phones aren't even being recognised by fastboot etc.?

After playing around with it, I can execute adb commands during the bootloop, like adb reboot recovery (hoping that CWM was there) so I can just use the soft keys to navigate to a nandroid backup...but nope...it was the triangle exclamation mark. I really just want to fastboot CWM, but still, it's just waiting for device.\
Help?!

I also had the same Problem and yes its a Software problem taht comes with ics 4.0.3 update, well it was my luck that my power button started working on its own and i went in recovery mode and formatted all partitions and reinstalled 2.3.6 and beeen working fine now...

Well, I have sent it in under a warranty claim through Rogers here in Canada.
I expect a Christmas Miracle, I've been good! I promise!
It is definitely a software issue.

try installing a fresh cwm recovery image from adb if adb works

I have the exact same problem and adb isnt detecting a device. Am i screwed?

Great news. Samsung replaced my nexus. We are now good to go
Sent from my Nexus S using Tapatalk

I brick my asus tf300t please help me

Hello guys,before with the rom hidro ponic 4.4 all was well.After i want change my rom and i've brick my asus after flash rom unofficial cm10..because the camera apk not found, and dispay is total green..I suppose the problem is the rom but after another flash rom the problem is same.On again the display is lock on the logo Asus and upstar on the little: the device unlock..stop.My asus there's no way to get it to recognize at pc and the driver installed not found..are't fastboot logo in Controll Pannel.I've not possilìbility to choce android--usb--wipe data.Help me please thank you sorry for my English

What about booting into recovery? Or fastboot?
As far as I understand your post Android isn't booting, but what if you hold volume-down when you turn on the tab?
I have almost the same problem. I flashed a bad boot blob (vanilla linux, not android) and now I'm stuck at the first Asus logo if I boot normally. But I still have fastboot and CWM recovery so I'm confident I can get it back into shape (even though a restore in CWM didn't help)

I think there's no way to unbrick the device,because I have the same problem.
I flash my device to official 4.1 and I found I lost root of my device
So I try to downgrade my device,but I failed...
Then I try to enter recovery and I failed again...
At last I try to wipe data of my device but it had no respond...
Of course,I had to reboot my device...
The result is:It bricked...
The symptom is just like the thread starter
What should I do???
I tried to contact the customer service of ASUS,but they said the device which unlocked by yourself couldn't get any warranty,even I willing to pay for it
(I think the customer service of ASUS is too bad,especially their attitude)
(I'm also sorry for my poor English...)

this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me

seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
e...Thanks anyway
But my problem(the same as the thread starter) is:I couldn't enter either fastboot nor recovery
If I could enter one of it,I think I can fix it...
(Maybe I misunderstand what you mean?)

seanzscreams said:
this is simple
download the asus jelly bean launcher.zip
from their website
unzip the launcher so its just the eepad 10.blahblah.zip
if it says update launcher you still need to extract this
then flash the twrp jelly bean recovery
now add the official jb rom to an external sd card
and flash
reboot
and voila
reboot again to fastboot and reflash recovery afterwards
and then flash root
worked for me
Click to expand...
Click to collapse
Thanks guys Today i can try the guide..we ope in God:angel:

I try twrp jb recovery but not function because the teerminal it's impossible go in download mode (down+power)....The Jig Usb forf Asus exist?

Hello guys, but for this type of brick no one has an answer? Method with nvflash can 'operate according to you ..? But I'm trying to appear APX and install the drivers as a guide is a company because it makes them install it

As far as I can see nvflash is coming to TF300T, it has been developed for T201 (http://androidroot.mobi/t3_nvflash/). But at least for TF201 they have to have fastboot first, so that may not help you.
If I understand you correctly nothing is booting and you have neither ADB nor fastboot access. In that case I don't think there's anything to do except wait and hope for a working nvflash or to try to have Asus fix it, but since the tab is unlocked they probably won't do so for free.
It seems this tab bricks easily.

I have the same problem, and I hope nvflash too. But I don't know nvflash in dev or no. This my best device which die first. Cry

Having the same problem here also. Only had the tf300t for less than a week.
Here is a sticky to a thread I made. I'm just waiting for people to put in a bunch of ideas. Hopefully NVFLASH doesn't need fastboot.
http://forum.xda-developers.com/showthread.php?p=31465583#post31465583

Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:

surdu_petru said:
Hi !
...to force entry in recovery ...you need first to reset your device than go to recovery ;
- press for 10 sec. power button , release and quickly press volume down and power button at the same time ! -> normal the device should be entered in recovery ! Good luck ! :good:
Click to expand...
Click to collapse
...Tried it about 1000 times, not possible, but thanks anyway. No fastboot possible, NVFLASH won't be working either...
I asked our friends at androidroot.mobi if it would be possible to have this issue solved with NVFLASH, this is their response:
@AndroidRootMobi Is it worth waiting for NVFLASH on (very hard) softbricked TF300t? Or should I go to @Asus
‏@AndroidRootMobi
@Joanuz @ASUS Sorry. If/when we support TF300T, you will need device-specific files. So no brick recovery if you're already bricked.
It sucks, I know. I'll be sending mine back to ASUS tomorrow. No warranty. Hopefully a reflash will do the job (normally it should be around 75 euro), if the mainboard needs to be replaced, the total costs will be around 200... I will open a thread here once it's under repair. Good luck!

Same problem. Stucked at Asus Logo but i can go into recovery. What can I do? Help me please
My PC finds it as Fastboot.

Seem I'm no alone...
Seem I'm not the only one.
This morning I bricked my tablet, 5 minutes after I bought a wall charger on EBay... :crying:
As for now the only answers seem to be from people that don't read post good.
We can't get to use the recovery...
Again, if someone knows how reset the tablet prior booting...
I beleive that its the only other way.
The last possibility, buy a new one...
I believe the problem started before.
- I unlocked my tablet more that a month ago, at the Jelly Bean release.
- Rooted
- Installed the official release
- Everything went well, up to this morning
- I noticed that my Rom Manager Premium start to show adds
- Goo manager refused to install recovery script
- Then I tried to go in recovery, it fails.
- I said to myself that it was better to start from scratch
- I tried a Factory reset using setting menu.
- After this step the tablet started to show This device is unlocked
-After the last step the device wouldn't boot no other way...
I don't know what happened but it seem a bit strange that everything worked fine before this morning.
For sure I'll keep exploring ways to get out of this mess.
But if I have to buy another tablet, there's a chance that I'll go to a Nexus 7...
Good luck to all the other unfortunate that that are in the same boat.
Alain

Hi back,
After I bricked my device i sended back my tablet to canadian customer service.
At first the didn't wanna fix the proble and the service told me that he needed to change the motherboard.
I argue a while and after an email discussion whit the customer service agent, they told me that they would fix the problem for me THIS TIME.
This morning I received my tablet and everything seem to work fine, as it was reset to factory.
BUT, after I started to investigate, seem that in no time the cover removed.
And maybe the motherboard change is a trick to suck more money from the users.
In fact I can't understand why you'de have to change the motherboard after the tablet is bricked.
Maybe I'm wrong, but I find this way of doing thing awefull, and I consider lucker that I got outa this mess...
Good luck to the others unfortunates
Alain

No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.

Bricked TF300GT (please help)
Hello developers,
I have a bricked Transformer the goes in a loop flashing ASUS every 5 seconds or so. That was after having unlocked and then reset to factory default.
I have been reading a lot of articles at various forum for a solution. I have never seen something so confusing. Please is someone can point to me a page where the un-bricking is described step by step for that aparticular model?
Many thanks in advance
Yves
NB: I have tried the -volume and power button trick or the +volume power button that just make a USB connection on my PC
---------- Post added at 11:01 AM ---------- Previous post was at 10:53 AM ----------
tobdaryl said:
No need waiting for NVFlash, it is here (check developer section) but will not work on unit if already messed up.
I have used two things that aren't mentioned here; I don't recommend either but if you are ready to ship off it might work for you as it did for me.
Both times were caused from ota updates.
1. use of reset button while powered on, if that fails to help, poweroff and reset button again.
2. let battery run down, put ac charger on power strip which is turned off but plugged into ac. Hold foot over power strip button, hold power and down volume on unit; mash power button on power strip with foot while holding power and down volume on unit.
I should have said neither of these fixed my unit; they just allowed me to get into fastboot to fix my unit.
Click to expand...
Click to collapse
I have the same problem and done what you described without success. What must I flash with fastboot and where will I get fastboot. I believe my machine is in JB 4.0.. Many thanks,
Yves

i got my tf300t bricked to.
got my tablet this weekend wanted to install cyanogenmod.
just did a week early'er a other one (the one for my mother)
that went well
my tablet installed de orginal 4.2.1 from asus.
Today wanted to install cyanogenmod.
run first de unlocker v8
the installed fastboot twrp421.blob
when i went to the twrp menu the cyanogenmod wont install, but the orginal wont start also not, it want nothing to start.
tryed with external sd.
ok i thought i want cmw so i run the recovery-clockwork-5.5.0.4-tf300t.img
went wel also.
i can only go to cwm but they are no file rights and still can install a zip or mount a sd internal or external.
now fastboot is not working
when i turn the tablet on it is going to cwm
wat i can do?
edit:
cmw version = v6.0.2.3

Me too! asus ask 230$ for replace new mainboard. I think they want eat money, because they already have nvfash to fix. 230$ can buy new item from amazon. I hate asus and never buy any thing of asus. Very bad support.

[FIXED] TF101 won't boot

UPDATE: Tried with TWRP (Thanks to Lethe6) and installed Ray's Unofficial CM10 with Kat Kernel and now i've got a working tab on my hands. wiped my internal memory though, but still good
Hi, sorry for the unclear title. i searched the forum but the only problems i found were either recovery bootloops or softbricks after updating.
my problem is, however, that my TF101 keeps showing the spalsh screen, making a click noise and then turning off and repeating the same thing over and over unless i enter my Rogue team's recovery (based on CWM 6) and use the power off option there. it doesnt even cold-boot. i didnt install anything new that would cause this problem.
Also, today i decided to install a new rom (i was using the stock ICS rooted). But i'm unsure if i have enough battery power for that.
i'll be online so if you need any more info just ask below.
Thanks in advance, Dan

ok so i used EasyFlasher to flash the latest Stock rom, and not only did it not fix my problem, but apparently it wiped my recovery so now i cant power off the tablet or enter APX mode to flash a new recovery.
its stuck in this constant loop of powering on displaying EEEPad splash, click noise, rinse and repeat over and over again i cant stop it

after 5mins of mashing the Vol_Up button i got into APX by chance and flashed RogueXM Recovery
i now have access to APX mode and recovery installer again but the problem persists and i cant boot my tab ever still....

Try TWRP recovery. I know it's a long shot but it solved many issues for many people. You can flash it from easyflasher.

flash?
DemonDan said:
after 5mins of mashing the Vol_Up button i got into APX by chance and flashed RogueXM Recovery
i now have access to APX mode and recovery installer again but the problem persists and i cant boot my tab ever still....
Click to expand...
Click to collapse
Can you flash anything? And do all ROMs stick?
I am only guessing.....
scott (tf101 with EOS4 )

@wn1ytw i can flash now, and i think the roms stick but since it doesnt boot i cant really tell
@Lethe6 i'll try TWRP and update the post
Also, Another question, Does the TF101 charge when connected to a wall adapter but turned off?

[Q] Bricked TF300T (APX mode only, no nvflash) – any hope?

I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.

I think to only solution is to replace the main board OR buy a new tablet :'(
Sent from my ASUS Transformer Pad TF300T

jay-roc said:
I bricked a TF300T today, and I'd like to know if there is possibility that it might be repaired.
I was attempting to install CyanogenMod 10.1 on the tablet for my friends, which I offered to do since I have a bit of experience doing similar on other devices. It was running Android 4.2, and had the latest firmware (v10.6.1.15.3, WW). After researching the XDA forums, I unlocked and rooted the device, and installed the TWRP recovery (2.5.0.0). I used TWRP to flash CM 10.1 and the Google apps, but when I tried to boot I got stuck at the Asus logo. After some more research I realized that the official release of CM doesn't work with the 4.2 bootloader, and that if I wanted to install that ROM I would need to downgrade my bootloader (right?).
The trouble occurred during the downgrade. I downloaded the 10.4.2.20 firmware and used flashboot to flash it. The flash completely successfully and I was going to run "flashboot reboot." Thinking I'd save keystrokes on the command line, I hit the up arrow to call up my last command, and meant to delete the last half of it, but I managed to hit 'enter' instead, starting the flash over again. I cancelled the command (^C), which might not have been wise -- but then I made my dumbest move, and powered the device off. (I'm not really sure why; I guess I assumed I'd still be able to get into fastboot mode.)
Now the device will not boot at all, except into APX mode -- i.e., the screen is blank, but when plugged into the computer the device registers. From what I've read here, there isn't really anything useful I can do in APX mode, given that I never setup nvflash, and I can't figure out any way of getting the tablet to do anything else.
Is there anything I've missed? Is there anything I could accomplish by cracking open the tablet (popping out the battery)? I've seen references to replacing the logic board – would that work, and how should I go about this? I know most if not all of these questions have been answered in different places before, and I tried to do my homework, but I figured I'd ask in case anyone had new experience or expertise to share.
Click to expand...
Click to collapse
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
For future reference here is the way I see the recovery and rom matching issue.
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob

tobdaryl said:
APX mode is useless without nvflash installed and nvflash can only be installed while on ICS and once you leave ICS you can't go back.
Some Info: the vehicles to recover without nvflash are
1. recovery - stock or twrp
2. adb
3. fastboot
Do any of these work?
Try this link to find ways you may not have used yet -to get to the bootloader - thus recovery or fastboot
[GUIDE] Enter APX mode or Bootloader-recovery menu!
Click to expand...
Click to collapse
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.

jay-roc said:
Thanks for the response. I've already tried the relevant methods in the guide, except for disconnecting the battery. I can get into APX mode -- the tablet registers as an APX device when plugged into the computer -- but I can't get it to enter the bootloader, so recovery, adb, and fastboot do not work. At this point I don't have much hope that the device will ever boot again without replacing the motherboard.
Click to expand...
Click to collapse
I'm sorry, I hoped the guide would give you a chance of recovery.

I definitely appreciate the help, and the guide's a great resource.
tobdaryl said:
I'm sorry, I hoped the guide would give you a chance of recovery.
Click to expand...
Click to collapse

jay-roc said:
I definitely appreciate the help, and the guide's a great resource.
Click to expand...
Click to collapse
You are welcome!
I had wished for better results.
Good Luck!

noahvt said:
I think to only solution is to replace the main board OR buy a new tablet :'(
Click to expand...
Click to collapse
Is there any tips for buying mainboard? Should it be exactly the same as in my tablet (I mean the same region and, therefore, version of ROM installed), maybe serials.
I have a bricked TF300T, and the only way I have to resurrect it - MB replacement. So, please, ANY info will be useful. Thanks in advance.

try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster

Buster99 said:
try to get it into fastboot somehow - i was stuck in apx too but with a bit of trying i was able to get to fastboot (try resetbutton + vol-down, let it completly drain of power, charge it back and try again)
here is what i did after i regained fastboot:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
gl
-Buster
Click to expand...
Click to collapse
I'm so damn appreciated! Thank you so much)) I'd add this way to get to fastboot - adb reboot fastboot - just from faulty CWM. Other way it didn't worked.

I got mine working this way
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!

ozkrtech said:
Link to my thread --> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps. Try It!
Click to expand...
Click to collapse
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty

martyzzz said:
I have the same problem...
My TF300T got bricked and now i cant boot at all anymore, i just see the Asus logo.
Vol down and power doesnt work but i think i can boot it into APX mode, screen stays black but my pc recognises an APX device.
At first my pc didnt install the driver but than i found APX drivers in these forums.
I've downloaded the APX drivers from a thread and i can choose to install various drivers, i tried all of them.
The one i think i need is the Asus Transformer ADB interface driver but this one along with every other one i can choose from doesn't work.
After installing and trying fastboot devices and adb devices i never had a device name show up
im kinda stuck right now
Can anyone please give me some advice ?
Cheers, any help is appreciated
marty
Click to expand...
Click to collapse
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+

ozkrtech said:
Can you explain me step by step what you did to get bricked? Are you on bootloader 4.1 or 4.2+? 10.4.x.x is 4.1 and 10.6.x.x is 4.2+
Click to expand...
Click to collapse
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers

martyzzz said:
Bought the Asus tab a year back and kept it original and updated by Asus for a few months.
Begin this year i unlocked it through a guide here on XDA (i dont thin through the Asus APK but another way).
After it succesfully unlucked (you could see "your device is unlocked" in the left top of the Asus boot screen i installed CWM.
After CWM i installed Cyogenmod 10.1 and kept it updated for months
This was all in the beginning of this year...
In june after updating Cyogenmod 10.1 to a newer version it wouldnt boot up anymore (i still had acces to my CWM recovery at this time).
So i switched back to the last working Cyogenmod 10.1 version (think it was 15th or 16th june).
I left it again for 2 months, still everything was fine till i saw that Cyogenmod 10.2 was out on XDA.
The upcomming is all last week;
First i tried to install 10.2 through CWM but my tab wouldnt boot up.
Than i switched recovery through fastboot because i have read that 10.2 was only compatible with TWRP 2.5+ so i got the latest TWRP
(2.6.0.0 i think)
After booting into TWRP i fully wiped the tab (i might have wiped everything because i dont know TWRP so well), after the wipe i wanted to install 10.2 again.
My tab still didnt boot so i got anctious and wanted to switch back to my latest version 10.1 (june 2013 that did work) so i could at least use my tab again.
Installing 10.1 again didnt work through TWRP, after that i came to the conclusion that i couldt install any rom anymore, at every rom i got an error in TWRP so i thought i had the wrong TWRP installed. (see my other post for a link to the screenshot of the error msge, i just cant find it atm).
Last but not least i tried to load my old CWM again as recovery, after i did this i couldnt get into recovery anymore...
Thans basicly the whole story.
Hope some1 can help me out.
Thanks in advance !
Cheers
Click to expand...
Click to collapse
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.

is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app

ozkrtech said:
What happends when you press volume down+ power?
It jeeps rebooting or it goes to black screen? Have you tried pressing the reset button is below the micro sdcard slot.
You should be able to boot any recovery.
Click to expand...
Click to collapse
When i press vol down+power i get the asus boot screen for a minute or 2, the tab switches off and on again to the same boot screen.
I cant boot into recovery
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
Buster99 said:
is I recall correctly cm switched partition layout to 4.2 on tf300.
if you still have fastboot try my guide to flash stock and then flash recovery and cm10.2. since it sounds a lot like my error I had with cm it should work for you as well.
good luck
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
I dont have fastboot in any way.
I can only power on the device with volume up + power to enter APX mode, than only my pc sees a USB device.
I tried a lot of differtent drivers but for nome of them i can ADB of Fastboot to the device.
It would help if someone that has managed to unbrick through APX mode posted the right driver for a TF300T
Cheers

have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app

Buster99 said:
have you tried the apx drivers that come with the sdk?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)

martyzzz said:
Ive tried searching in the SDK forders but i cant find any.
If i try to install drivers automaticly and than point to the root SDK folder i get the windows msge the best drivers are already installed (no matter what driver is in stalled at that time)
Click to expand...
Click to collapse
don't just point at the folder
manually select the driver for the device from android-sdk\extras\google\usb_driver
gl

[Q] Soft bricked A200

Do not see a section for the A200..... Someone in A100 said I'd have better luck here.....
OK, so I soft bricked my A200 and need to USB connect to it, so I can use fastboot or some other recovery tool.
Problem is that when I plug the A200 into my computer, it grinds away for a bit then gives a driver failed to install red "X" message.
I've reloaded the Acer USB drivers a couple of time, but no joy there. I've tried two different computers, I've tried XP and W7, nothing seems to help. Looking in the device manager shows an error 10 (device can't start).
Since the PC at least recognizes the A200 when plugging in, I think if I can get the USB talking I can easily unbrick the A200.
When I power it on, it boots to the IconiaTab screen, but no further. It's been rooted and bootloader unlocked using HBWelch's Simple Tool. I can get into fastboot mode by using a convoluted (to me, at least) procedure, that takes 6 fingers to accomplish.
After rooting and UL'ing BL it worked fine for over 6 months. Tried to flash back to stock over the weekend, and that's when I bricked it.
I posted this same message over on Acertabletforums, but so far no response's. Moderator, if you don't mind, please merge my other thread over in the A100 section with this thread.
Help??
Boowho??

Do you know if CWM is available for your A200 ?
If your bootloader is unlocked, i think you can flash a boot or recovery via Fastboot

success anyThan
Shreps said:
Do you know if CWM is available for your A200 ?
If your bootloader is unlocked, i think you can flash a boot or recovery via Fastboot
Click to expand...
Click to collapse
Fastboot appears to need a working USB connection (thru drivers). When I run it on the PC, it hangs with the message "waiting for USB connection". This is with the tablet booted in "fastboot" mode.
I CAN get it to read from update.zip on the SD card. The update.zip I'm using is the completely stock firmware (ROM, recovery, etc).
It starts the update (Android with spinning wire frame ball), gets about 25% done and then the update fails with the "dead android" symbol.
Thanks
Boowho??

Problem solved..... Thanks. Was able to flash via update.zip on SD card.

One damn thing after another!!!
boowho said:
Problem solved..... Thanks. Was able to flash via update.zip on SD card.
Click to expand...
Click to collapse
Everything did work fine for a day. Now I cannot enter recovery using the hardware buttons.
Using an APK called "Quick Boot" I can easily boot into CWM from the home screen and everything is fine. Root is fine, bootloader unlocked properly, etc.
Everything acting as I would expect.... BUT....
Unfortunately, not being able to enter recovery from HARD boot pretty much makes any recovery worthless, right??
Anything besides hardware that could be causing this?? The volume rockers work just fine as volume controls.
Thanks
Boowho??

This problem solved too....... Brainfart!!!
Boowho??