Ok like an idiot I went to install the stock Asus rom over my AKOP rom using twrp. Now it just sits at the Asus logo screen and will not boot. How the hell do I fix that?
If you still have fastboot flash cwmand do it again
And if I don't have fastboot? I mean right now if I hold vol down and pwr all it does is turn the screen off. It will not boot into twrp
falcon26 said:
And if I don't have fastboot? I mean right now if I hold vol down and pwr all it does is turn the screen off. It will not boot into twrp
Click to expand...
Click to collapse
Turn the screen off? Screen shouldn't be on when you do it, shut it down, then hold Power+VolDown until it turns on and the white text comes up in the corner.
then you will see 3 icons choose the usb icon with Vol- and Proceed with Vol+. Then you are in fastboot.
I got it thanks! She's back up and running.
Hello,
I also have the problem to get stuck in the boot screen. I have a brand new TF300TG, only installed some apps (not unlocked, not rooted). I only made the automatic update to 9.4.4.40, after that it always stops at the boot screen.
What I already tried:
- cold boot
- wipe
- RCK (Android with rotating things shows up short, after that the Android with the warnings sign shows up)
I also downloaded the whole WW 9.4.4.40 package from ASUS and put it on a MicroSD. If I make RCK with this (if I rename the file to EP201_768_SDUPDATE.ZIP) the Android with the rotating thing shows up longer, but I still get stuck in the boot screen.
I already contacted ASUS support and will also return it to a service center, but I'm in China and expect a long process with some troubles, so I wanted to ask if anyone has another idea what I can try?
Ernst
Update:
I think it was now possible to update WW 9.4.4.40 again (renamed to EP201_768_SDUPDATE.ZIP). I now used a different MicroSD with only 2GB. The first time RCK it stopped in the middle of the update (after that the Android with the warning sign came), the second time I tried it, I think it finished, but the TF300TG still stops booting at the ASUS boot screen.
If I try now to update over MicroSD again, it doesn't work.
I have the same problem, only difference is that pressing vol down and power on makes no difference. When its on I also can't turn it off. I just have to wait until the battery is drained.
you have flashed ICS ROM in JB bootloader as far I see - hardbrick if you don't have nvflash files - only service.
Sent from my GALAXY Cooper
Its not me Its the Drivers!!!
So I have a TFT300T, unlocked and rooted, all was fine till i decided to try another ROM. So I installed CWM no problem. Once I installed the ROM problem. I seem to be stuck at the ASUS screen. I have tried loading boot loader to do a wipe and factory reset and that simply boots me to CWM, tried the same thing there but to no avail. So researched bricked Transformer and came across the Nvflash method as well as the Asus Transformer Kit (US ONLY). However I cant proceed cause of the APX driver issue. I tried the included drivers but Win7 wasn't interested. I tried 1 desktop and two laptops, same thing. I even tried my bench tester. Now Universal_Naked_Driver_0.72 seems to install but no communication between the PC and the tab with this driver.
I tried bootloader to try a fastboot command but then the Device manager demands a driver for "Transformer". Same issue. Tried downloading from Asus plus a couple on the web. It seems its the Tablet. I thought to try CWM and an sdcard but it doesn't give me the option to mount it. So if any one knows a fix I would be forever grateful.
gixermann said:
So I have a TFT300T, unlocked and rooted, all was fine till i decided to try another ROM. So I installed CWM no problem. Once I installed the ROM problem. I seem to be stuck at the ASUS screen. I have tried loading boot loader to do a wipe and factory reset and that simply boots me to CWM, tried the same thing there but to no avail. So researched bricked Transformer and came across the Nvflash method as well as the Asus Transformer Kit (US ONLY). However I cant proceed cause of the APX driver issue. I tried the included drivers but Win7 wasn't interested. I tried 1 desktop and two laptops, same thing. I even tried my bench tester. Now Universal_Naked_Driver_0.72 seems to install but no communication between the PC and the tab with this driver.
I tried bootloader to try a fastboot command but then the Device manager demands a driver for "Transformer". Same issue. Tried downloading from Asus plus a couple on the web. It seems its the Tablet. I thought to try CWM and an sdcard but it doesn't give me the option to mount it. So if any one knows a fix I would be forever grateful.
Click to expand...
Click to collapse
I also found the asus transformer kit(us only). But the same problem. I am able to connect my tablet with apx mode, in my device manager I see apx device. but in the tutorials it says that I have to force install de driver, but I don't know which driver to install. I tried the asus driver and every file in the asus transformer kit but nothing. I triend the universal_naked_driver but I can't get it to install can anyone tell me how to proper install that?
Related
I had rooted/cwm'd my tf101 when I first got it. It was running the 3.1 update at the time. I followed the pure root posts here on XDA.
Sadly I had never tested CWM, and perhaps since it went so easily I didn't really understand/read enough on CWM to understand what is happening. When I ran the 3.2 OTA (OK so I shouldn't have done that, I know now) the TF froze on the initial splash screen.
I've tried many things and read tons of posts here on XDA and other sites, and I'm not getting anywhere, but part of it is I don't know for sure what I'm trouble shooting.
I was using a dual boot laptop in Windows mode when I did the initial update. I had the drivers working and succesfully rooted my system.
What I am trying to do is restore a stock rom for now and I've tried several methods.
1) Asus download SOP - It detects the image on the SD card, checks validity of the firmware, shuts down and reboots and hangs at the first splash screen.
2) CWM recovery, if I understand this right, I Power+ vol_down. I hit the vol_up to enter The screen says
Checking for RCK. press key <Vol_Up> in 5 sec to enter RCK.
I do that and it hangs at:
Booting recovery kernel image
3) I've tried several nvflash posts out there. NVFlash does not seem to be working, I've now done this on two windows boxes. Both the one that used to work, and a clean windows XP machine I had lying around. In both cases, I can get the nvidia APX drivers loaded and the device is seen. However, adb doesn't show any devices, and from pulling apart the batch files and doing some reading, I tried nvflash -r --getpartitiontable myfile.txt and some other commands which always hang. Eventually if I disconnect the tablet - then I get a read error of some sort.
4) quick reboot - every option leads to reboot and freeze at first splash screen.
So questions that I can't seem to find an answer too.
1) If I'm connected in APX mode, should adb show a device? Like I said the PC recognizes it as the APX device and loads the nvidia drivers instead of the normal transformer MTP drivers when I do the power + vol_up.
2) Is there a simple test to use for nvflash? The device shows up, is there anyway I can confirm whether APX mode is working or not?
I'm only starting to piece together the boot process in my own head, and my guess is that niether the stock recovery image or the cwm recovery boot image is working. Would that be a reasonable assumption based on behavior? I will admit I really don't understand the boot loading process in android.
FYI, if I go through Power+Vol_down, wait for rck to skip and then boot without wiping, the TF is fine after that. Meaning as long as I don't try to update, it will work and reboot normally. Root also still seems to be working.
I tend not to suspect a driver issue, since one machine was confirmed working, it's how I got root - and 90% of the time that machine is run as linux. I almost never boot into windows. I'm pretty sure the last time I did was to root the TF.
What happened is you overwrote the cwm when you installed the new update. You can't just randomly install things once you're rooted.
If you have a B7O machine, you need to check that you have the old or new sbk. Go to the general transformer forum, and there's a thread about the new sbk locked bootloader. Follow the test to see if you have one that you can use nvflash with. If that is the case, then go to the dev forum, and look through the nvflash unbricking thread.
Thanks for the reply
First off, you're right and I should have known better. Almost nothing I own runs it's stock firmware, and I just got dumb and didn't do the full research excited for HC 3.2 goodness.
I have a B50 machine, or at least the my serial number indicates that.
I've already tried several nvflash debricking instructions, but it seems that nvflash is not working either. I have several copies of prime and the .11 release from asus. But since nvflash is not behaving as expected, all of those threads are not helping.
I do have the nvidia USB recovery device show up in device manager, but every nvflash command fails hangs at
nvflash started
[resume mode]
ADB devices shows a serial when I'm normally connected, but it doesn't show up when I'm in APX mode. I'm just not sure if the device is in a functional APX mode, since nothing actually runs, despite it showing up in device manager. I've tried googling that situation, but I can only find posts that tell me how to get it to show up in dev manager... It seems like when that happens everyone else has been fine.
WHILE GOOGLING FOR MORE INFO ON b70 - I managed to get NVFLASH working, and now I get what the first command and -r do.
3.2 Update Problem SOLVED
So look at the original post for the strange condition I had gotten into.
Somewhere along the line, the transformer had stopped responding to adb even not in APX mode.
I uninstalled PC Suite and Asus Sync. Then reinstalled only ASUS sync. ADB started working when TF was connected normally
I did not reboot my PC, win7 64 bit. Shutdown transformer, it hung at the splash screen. WHILE HUNG, I held power and vol_up until device manager showed nvidia USB recovery device
I used the stock rom replacement from tabletroms. Sorry I can't include the link as I am too new to XDA.
Got the transformer back up, set up my account, restored data. However OTA from there was not working.
So I went to ASUS, grabbed the .11 image and updates via SDCARD following the SOP instructions.
After reboot, checked for updates, and there was one. Let it do the OTA for 3.2 and now I'm back at having stock 3.2 updated TF.
I will probably root, but may not CMW this time.
Hi everyone,
i just bought a (not new) 16g Transformer Tablet (FW3.1) which has finally arrived today.
The pre-owner told me the transformer got a Custom ROM. (MoDaCo) Unfortunately the tablet isnt working correctly.
After turn-on, the Transformer shows up the Eee Pad Logo and Asus logo on the bottom, but doesnt boot up to anything else. The restore-Function (Power+Vol down - told from Asus) does not work for me.
If im trying to power off the device, the screen turns off for apx. 5 seconds and the device just reboot back to the asus / eee logo. So i cant even turn off the device. The USB Port seem to work, Windows 7/x64 gives a plugged-in-noise when the Transformer is connected, but theres not storage device shown.
Can somebody help? Maybe a hard-Reset or full-restore without asus software?
thanks for help!
Hi, got exactly the same problem, and I am not only the one... definitely an issue with the 3.2 HC update. Just trying to fix at the moment... will appreciate some help from the Phorum...
I had the same thing happen, although I had put my own cwm into the stock 3.1 rom.
However if you had a custom rom/boot loader and tried running the OTA update - you will have issues.
First, press vol_down with power button hold for a while, then you should eventually get a screen (If you're not even more hosed than I was) that says press vol_up to wipe, vol_down to cancel. do either, and then it will cold boot linux, and you should be working as long as you don't want to update again.
If you do want the update (I did) what I had to do was do a full nvflash (look for transformer unbricking threads) of a stock image - those are also available on xda threads.
Once you have done that, I personally had to then use microSD SOP update from ASUS, so that future OTA updates would be recognized. So do the standard ASUS offline microSD install of the latest 3.1 build.
Finally you can ota to 3.2 and then mod/root from there.
All of this changes if your serial number starts with b70 (Mine does not) but I do know b70 builds have other issues with the boot loader, that may cause issues.
Thanks pal, I am trying a factory reset (could access by button volume - power combination) but it's seems to be taking ages (40 minutes and accounting with the "it make take a few minutes" screen) Is it normal? How long does it take a cold reset?
Factory reset also fails at that point. If I understand correctly, using the power/vol down got you back into the OS, from the settings app, you did a factory wipe?
That also will not work. Once you're back up and running via power/vol_down - you need to do a NVFLASH of EVERYTHING. Even the factory wipe seems dependent on things that get overwritten when you try an OTA over a CWM'd device.
Once you have the stock back in place, then factory wipe etc will work, but using nvflash to replace everything will accomplish essentially the same thing.
Here is the link for the stock roms I used:
http://www.transformerforums.com/fo...nsformer-nvflash-stock-3-1-recovery-roms.html
@akameswaran -> Thanks for the Hint!
I´ve downloaded a Stock Rom 3.1 from Tabletroms.com with NVFlash included. So it was rather easy, after installing APX Drivers (nVidia Restore / Recovery Device USB Drivers) you can just use the prepared NVFlash to send the Boot, System and Kernel ROM Files automatically to the transformer.
All data on the tablet has been deleted, but its now back on 3.1 factory defaults and working fine. Theres also use a MoDaCo Custom ROM, put into the NVFlash Folder, to re-flash the device with modified roms.
However, thanks everyone!
What could it possibly mean if even NVflash back to stock doesn't work? I can't get to Honeycomb at all. :'(
It just turns off right after showing the Eee Pad logo for 1-2 seconds. I
Can you connect the tablet to the PC and get it recognised? Go to device manager and see if there is a device with exclamation mark.Load the drivers and flash via Nvflash.
APX mode works fine, as does the flashing process. It just still won't boot even with the stock ROM.
I've found that since the US 84411 rom having the wrong bootloader may cause the transformer not to boot with other roms.
I'd suggest trying to nvflash to 3.2 stock again but first replace bootloader.bin in your nvflash folder with the one in the attached zip file.
is or was your transformer also making a some sort of ticking sound?
because my transformer is also hanging on that eee pad logo, i'll think also after installing a new clockworkmod recovery.
I have a sl101. I only get eeepad screen. My son did something to the machine. I can get it to say booting recovery but nothing happens. I also can get a text that says cold booting Linux. Again nothing happens. Nvflash says USB write fail. But when I check adb the device is recognized. Is there a way for me to adb push a recovery in there for me to boot too, so I can reflash a rom. I have a little dilema here. I also was wondering if I can flash rom thru adb. I read once that's how they used to do it on g1. I don't know if I am speaking accurately though. Any kind of light shed on me will be greatly appriciated
Sent from my SAMSUNG-SGH-I997 using xda premium
not sure about the slider but i had a customer return yesterday with this exact issue on the tf101 and i couldnt get out of it. the tf just kept switching itself back on and getting stuck on the splash screen.
found this set of instructions but im not sure if its what you need or if it will work:
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
good luck
That is exactly what is going on with mine. The slider is basicly the same thing. I plug it in and I tries to boot. I thought you had to be booted into recovery or the rom for adb to work? That's why I believe this method you just revealed to me. Or some variation of it will work. I will be trying shortly.
Sent from my SAMSUNG-SGH-I997 using xda premium
not working transformer
i have asus tranfrormer 9.x.x.x, recovery 5.8.x.x, after i did superwipe , every thing is gone and i cant flash any rom through adb/nvflash saying cant write to sdcard (read only). any suggestions?
HELP : Same problem, no apx, recovery strange, no boot
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
densleonis said:
I still have access to clockwork but nothing seems to install, i tried update clockwork nothing worked, reboot gives me clockwork, APX don't work...
please HELP !!!!
Click to expand...
Click to collapse
nvflash if your TF101 is compatible model.. (must B60 and below).
Or read Wolf's thread HERE. It might helped everyone here..
Thanks but everything needs adb connexion and as apx is not working, i can't connect ADB..
I have a B50 model
Nobody have a clue ?
well, I have to send it back to my reseller that will change it but before that I need to delete clockwork mode or brick it, how can i do ?
I tried every thread here, update rom does nothing, looks like it does not write anything on the tablet
Thanks in advance
try to follow this procedure...
http://forum.xda-developers.com/showpost.php?p=25636698&postcount=5
let me know
Hello, thanks, but as I can't get to apx mode, I can't use nvflash, so still stuck with my recovery, I tried to modify super Wipe package to do things but can't get through...
If someone can make a package to delete recovery, then I can try it on my tablet, I really yneed it to be bricked cause now it load with Rogue's recovery on and on, so the reseller will new it has been modified and I will have to pay to get it back ...
Thanks in advance
with the procedure posted in the previous link you don't need APX mode and don't need NVflash...
Just boot your TF in recovery mode and plug it to your pc...
remove all previous drivers and install the new one that you can find in the post
ciao
ps... at the end of the procedure you will have your TF101 with stock rom and stock recovery
I will try but even when I am on recovery, nothing appears in Hardware management, no recognition from My computer, still strange... And when I power + vol down key, It never says to presse vol up in the text in the upper left corner, just says booting linux kernel...
When I try to boot pressing vol up + power, nothing happens, not even the clics that can be heard when it powers up...
I had a similar issue when I used SuperWipe and discovered my ROM on the external SD Card could not be accessed by CWM
I tried pushing the file with adb but kept receiving errors - protocol, etc. I suspected it was a driver issue along with the fact that 64 bit systems don't always play nicely with drivers. I actually dug up an old hard drive and did a very basic install of 32bit Win7. I booted the Transformer into CWM and when I connected it to my PC - I pointed it to the universal naked driver. I was then able to successfully push the rom to internal storage and used CWM to flash it
Hello,
I tried to connect my tablet to an old Windows 2000, but still nothing happens
Hello every one, I finally sendt back my transformer to my reseller, now I can buy a new one...
Thanks again
Ok, I swear I have read 100 pages of similar problems, but it looks like everyone else is able to get into apx mode at least to run nvflash or easy flasher.
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. Never shows up in device manager and it doesn't beep or anything like the ones in all the videos do.
I really just want to get up and running at the very least, as I handle all of my businesses billing through my xformer, but my ultimate goal is to get on the HD-ROM.
I have downloaded the newest firmware from asus, have all the drivers installed (I think), have tried booting into recovery with one, some or all of the new software on the sdcard.
Any more ideas I can try? Do you just have to hold your mouth right to get it into apx mode? I have held those buttons so much I think I'm getting Nintendo thumb!!!
Thanks all!
nobody?
Throw something at me! What update.zip file do I put on the sd card? I have tried putting the newest asus update.zip on there with both its original name and the update.zip name. still comes up with a dead android and an exclamation point.
Download a firmware from Asus, rename it to EP101_SDUPDATE.zip
Put it on the root of your sd card and boot into recovery, hopefully it will flash it and let you boot up.
As for NVFlash, make sure you install teh APX driver.
Still won't get past about a second or two of trying to boot with EP101_SDUPDATE.zip on the sd card. Think I'm stuck, or is there something else I need to try?
Thanks!!
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
scottyf79 said:
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
Click to expand...
Click to collapse
i am the same issue by flashed the touch CWM and window wont able to reconigzed my TF as a APX device
i tried many drivers it still not able to work.
how can i get back to normal CWM? i dont have havy roms or update.zip in internal roms.. and Touch CWM wont able to recongized Removerable sdcard
god~~
The root and backup option should flash you an external recovery.
While tablet reboots hold down volume up and power until reboot stops.
Then try brks tool again and select root and backup.......during the process it may ask if you want to back up but its not worth while as i dont think theres anything to backup. You should end up with ext micro sd recovery.
As i said id look for the prime rom thread and download the nv flash version and see if it works first.
If asus restore the wiped TF without question and everything goes ok il let you know as it may be worth wiping it with wheelie nv recovery and just RMA.
I just simply CAN'T get it into apx mode. I've installed, uninstalled and reinstalled the drivers. Trying to flash ep101_sdupdate.zip still just results in an error. crap.
Hold Volume-UP BEFORE holding power, then hold power for 5 secs (Still holding vol-up( doing this all while connected. It should show in device manager.
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
scottyf79 said:
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
Click to expand...
Click to collapse
same case for me~~~just cant install the driver
You all can try running Puppy or DSL (damn small linux) in a virtual box on your windows pc. Comes with drivers included and only is a 200/60 Mb download.
Got so frustrated with it I just went and bought a tf-300
c3poman said:
Got so frustrated with it I just went and bought a tf-300
Click to expand...
Click to collapse
no better way to fix it than that
nice one
Yea, I like it pretty good so far. Volume is WAY louder on the 300, even though there is only one speaker. The screen also gets darker, which is nice if you watch tv or browse the interwebs in the bed. Also, wifi reception is great. Haven't tried gps yet, but I'm sure it is improved.
It did get really laggy, but I did a factory reset and it seemed to clear out the cobwebs.
Thanks for y'all's help! I'm still going to try to unbrick that tf-101 and sell it or something. Hate to have a $400 paperweight...
People will buy bricked ones on Ebay for a reduced price, just clarify that it is in fact bricked.
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