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.
Hi,
I have a BB0 eeepad. So, I've tryied to change kernel, After doing that, my eeepad continue rebooting, stucking on the Eeepad first screen (before the asus logo). CWM is not accessible, if I try to power on in apx mode, the tablet does that correctly. I have installed the correct driver using your tutorial (video) but i get the following error:
rcm version 0X4
Command send failed (usb write failed)
If I try to get into CWM, i get the double icon screen, wipe data or android. If i choose wipe, it works, but the tf101 won't boot. If i choose android, the screen show me "cold booting android" and it get freezed...
Could you help me ?
Thank you
Boot into recovery, you have to press Volume UP before the option to 'wipe' or 'cold boot' comes up to get into recovery. I have a feeling you aren't doing that.
Nope, i did it, but in this case, it continues to reboot in loop... (Same as wipe data)
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
baseballfanz said:
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
Click to expand...
Click to collapse
Yep, Immediately Reboot over and over again...
can you or not acces to cwm? if you can your device is not fully bricked
wich version of cwm recovery do you have?
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
If you have no recovery, and you cannot get into your ROM, and you are SBK2..hang it up, you FUBARed your tab..sell it to someone who needs some hardware maybe? Try to RMA it to Asus, who knows- and then go sign the petition to release the SBK2 and this problem would not inconvenience you or Asus any longer when this happens..
Sorry guys
magnumrt562 said:
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
Click to expand...
Click to collapse
You need to put working adb. try with a linux livecd or whatever you can, with that version of cwm recovery you will need some commands to be able to acces a microsd card and reflash the device
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Antjac said:
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Click to expand...
Click to collapse
You more than likely voided your warranty by flashing or rooting your device BTW..so good luck getting Asus to cooperate (fooling them)
Unfortunatlly, i've not other choice... (except if NvFlash's team find a solution for B70+)...
Wait and see...
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
magnumrt562 said:
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
Click to expand...
Click to collapse
That is supposed to happen, you need to execute adb shell to get a shell or adb push file /sdcard/ to push a file to the sdcard
I have the exact same thing, upgraded to ics, all worked ok, rooted, all ok for 2 day then nothing after a reboot, cant nvflash vol+ & power doesnt find any options bar stock if i recover goes to dead android with ! then asus logo and nothing. So it seems the issue is with the upgrade but as most of us rooted we may have a problem, mind you i did the wipe and recovery so it may have erased evidence.
If anyone is selling a TF101 I would love to buy one...
I forgot my TF101 on top of the car and ran it over, still works but the housing and lcd digitizer are dead >.<
Please email or pm me if interested
Well, good news...
As I said, I've sent my TF101 to Asus (to Czech Republic). I said my Tablet was bricked by updating to the ICS rom (That's not wrong in fact...).
So no problem, they flashed my tablet and sent it back. I've received it yesterday, everything is OK
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?
I have an Asus tf700t that i rooted a long time ago and was running Cromi-x 5.something. I also have TWRP recovery installed.
I can't even remember the details now but at one point about 12 months ago, i when to do a wipe & flash (which i did many times and I felt very confident doing with TWRP) and something went wrong.
All my tablet does now is turn on and flash at the TeamWin screen, that's it. I've allowed for the battery to drain, I've attempted holding the volume key in to boot into recovery, I've removed the SD card...nothing seems to get me un stuck.
I attached my tablet to my pc (which now is windows 8.1 x64) and all I get is an Unknown Transformer device. I have attempted to download and install the google SDK kit along with the original items i used to root my device, none of them seem to "click in".
Am I looking at a dead unit here?
cheers,
Dave
Did you use Wipe Data from the bootloader menu?
If yes, you may be in a forced reboot to recovery loop.
First thing to try is to connect the tablet to power and leave it in TWRP. If you're lucky it'll sort it out and eventually execute the wipe data command. I would leave it for 8 hours or so....
Can you get into the bootloader = fastboot mode?
When in TWRP do you get it recognized with
Code:
adb devices
?