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.
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.
I have a B70 model Transformer. I figured I had one of the versions that still allowed you to root it, as mine was rootable. I have Prime installed on it and also did the eMMC Ubuntu installation. However, due to many reasons I abandoned using it/trying to get it to work more functional. Whenever I reboot the tablet now, though, it auto boots into Ubuntu. To get into Prime I have to hold vol down + power, wait for the rck screen, then hit vol down again to cancel full data wipe (it says it is "cold booting linux" yet boots into Prime. It's as if prime and ubuntu switched places between recovery). Recently it switched back, then reverted once again.
Now, since I have a B70 transformer it appears the bootloader is locked despite my ability to root it before. NVflash gives the failed to usb write error, so I cannot use the stock....sh file to remove Ubuntu, get CWM back, and be able to update or even change my ROM again. Is there anything I can do without any recovery available to me?
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?
So I made the mistake of installing Clockwork recovery mod when I installed Rom Manager on accident. Stupid mistake. I tried getting into recovery after that and it would hang right after pressing volume up at 5 secs. I did a normal restart of the tablet and decided to do a factory reset and see if i could restart with with and install TWRP. I ran the factory reset and restarted my tablet when prompted. This is when the issue started and now I'm stuck at the boot screen, the first screen you see when you start up. So i tried to start it up into recovery and it still wont budge. whats weird is it doesn't ask to press vol up it just says "Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03. Checking for android ota recovery. Booting recovery kernal image." Yet nothing happens. So am I bricked... is there any way out of this. My bootloader is unlocked and i am rooted... am i screwed? I read somewhere I might be able to fastboot, but is that possible if i cant get into recovery?
UPDATE: After doing some research I discovered that it might be possible using the NVflash method using site below but unfortunately NVflash is not compatible with the tf700 atm. Meanwhile I have submitting a ticket to asus but i do think NVflash would be my only hope if it actually worked for me.
androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
NVFlash will *not* work on the TF700 - others have tried - it will probably make your situation even worse.
I don't know the answer to your question off-hand, but I'm sure someone will be able to provide a method to get you back up - just stay away from NVFlash on the TF700...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Reading through different forums I have read problems similar to mine but nothing exactly the same. I followed each fix anyway but I have not been successful.
The last thing I remember I did before the brick, I flashed CWM touch then CyanogenMod 9. I am unsure what occurred but I tried to flash back to my JB backup and the problem started.
Now my tablet comes on and just hangs on the Asus splash screen. If I turn the tablet off, it automatically comes back on.
I have tried to turn the tablet off and boot into recovery but it just boots back up to the splash screen and hangs; I have no option to go into recovery, android or fastboot.
I can get into what I think may be USB mode by pressing power and volume up through a couple of cycles; my computer detects a device but I cannot load drivers.
I have downloaded the Android USBPCdrivers but each time I try to navigate to the folder to install the device manager fails.
If anyone has any thoughts I would appreciate any assistance, thanks for your time!
UPDATE TO ORIGINAL POST
I as able to finally get my computer to recognize the tf300t in device manager by wiping all the usb drivers and installing "Universal Naked Driver 0.7" posted by 1wayjonny from XDA's website http://forum.xda-developers.com/show....php?t=1766220, not sure if it matters my computer "sees it" as a ASUS transformer prime rather than tf300t.
Now I am reviewing an ASUS unbrick called Wheelie http://forum.xda-developers.com/show....php?t=1687285, I believe this is geared towards the tf101. Anyone have any thoughts based on my status at this point? Thanks
If you are on JB stock, there is no way to flash a booting Cyanogen 9 ot 10 Rom.
Only Hydro JB is running!!!! And JB Stock.
1st of all you have to download a special Recovery. I highly recommend TWRP. You have to dl the JB version!!!!!
Flash it through fastboot. Then flash the Stock JB via TWRP recovery
Then flash TWRP again via fastboot.
Than flash The Hydro JB rom
Then reboot
Then go back to recovery
Then flash the latest Hydro update and reboot
You are like me stuck on the f...... new JB Bootloader and Kernel. All other roms are for the ICS Bootloader and Kernel, so no way of getting them running until the Cyanogen devs finding a solution.
Fastboot not an option
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
mfsmith said:
Thanks for getting back with me.
Fastboot is not an option for me; the tablet hangs on the splash screen.
I can get into the usb mode but I am unable to locate any APX codes to push anything over. The only codes I can find are for tf100 & 200 moddels.
Any thoughts?
Click to expand...
Click to collapse
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
喔喔兒 said:
i have the same problem, and only APX mode is accessible, (no fashboot, recovery..) can get chip ID from APX mode, that is all,
should i wait for the nvflash rom(about 3-4 weeks, is that right?), or paid for this? (replace the motherboard)
Click to expand...
Click to collapse
Waiting for nvflash won't do you any good since you needed to have it BEFORE bricking your tablet. If your tablet is already bricked, APX/nvflash will not help you.
krhainos said:
You're hosed.
The developers that worked on the prior TF units' nvflash said the development isn't done on the TF300 yet. And, even if it was, you needed to perform some steps prior to bricking the device to make APX accessible after a brick. If your device is bricked already, your only recourse is to send it to Asus and eat the $197 fee to have your motherboard replaced.
Click to expand...
Click to collapse
He could still try sending it for RMA. Mine got repaired for free for some reason.
An unusual Asus TF300T brick
Yeah, I'm having problems with my TF300T, too. I had CWM installed, but when I tried to flash a new ROM, I bricked it. No problem, I had figured it out before. But when I was in the bootloader, I inadvertantly erased instead of selecting the USB. Now, All I get when I try to boot up is the white ASUS screen with;
The Device is Unlocked
Android cardhu-user bootloader <2.0 e> released by "ww_epad-9.4.3.26-20120416" A03
Checking for android ota recovery
Booting recovery kernel image
My computer sees the tablet. The Device Manager shows: Asus Transformer Prime APX Interface
But it only shows up when I reset. As soon as I try to boot the tablet, it no longer sees it. I can't access the bootloader and Fastboot doesn't do anything except "waiting for device".
SO! If anyone can give me some help, I'd appreciate it. It's a puzzle for ya, anyway.
Thanx
As your last resort, this worked for me
Link to my thread---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, feel free to ask anything.