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.
Related
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?
Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh
Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans
Sorry all for those who read my last post in my other thread - "can't root- twrp not working" which makes this post redundant but I'm feeling a little desperate and I'm also new to this stuff. Since I was unable to install TWRP for some reason it was advised I use the old fashioned NV flash method with prime rom, however 'how to' video from the following thread- http://www.tabletroms.com/forums/tr...ment/976-nvflash-unbricking-forever-root.html
has been removed and now I'm stuck with this message on my tablet :
entering nv flash recovery mode/nv3p server
chip vid ----
I hope this doesn't mean I bricked "permanently mt tf101. I've completed the following 3 steps to get this far:
downloaded nvflash zip and prime 1.4.
1 Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
2 (Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
3 Run download.sh (linux) or download.bat (windows)
In step 2 - driver wouldn't take I presume since I already updated driver when using frederuco's guide. Shouild I have uninstalled APX and reinstalled this version?
Anyhow, after step 3 allot of messages about partioning came up on tablet and now there is the entering nvf flash recovery mode message stuck on tablet screen. Is this right? Am I supposed to flash prime 104 now? If so how? I was advised to install this way as a back door if you will so as I can later install a better rom once I've successfully rooted.
The tablet will reboot when NVFlash is finished, you should be able to follow its progress on the PC screen / CMD window
NVFlash can take a while
There is no cmd window open. I cant remember if there even was one or if i closed it. What do i do now? Do i re-run bat program as shown in step 3?
leif2 said:
There is no cmd window open. I cant remember if there even was one or if i closed it. What do i do now? Do i re-run bat program as shown in step 3?
Click to expand...
Click to collapse
Basically the entire procedure for NVFlash is this
1: Connect TF101 to PC USB
2. Power Off TF101
3. Put TF101 into APX mode (Power & Volume Up)
4. Run download.bat as Administrator (Right click > Run as Admin)
5. Keep an eye on the CMD window as it will say things like "Deleting partitions > Creating partitions > Sending System / Boot / etc"
6. TF101 should reboot when done
----
If you didn't see the above, just start again from No.1
Yeah, i remember seeing a bunch of messages on tf101 about partioning ect.. . I dont think tf 101 rebooted though. Or maybe it did. This was some hrs ago now since tablet has been stuck with entering recovery mode on screen so i cant remember. I also dont remember if i ran bat with admin privilages. Shall i restart the entire nv flash procedure then? Should i first uninstall and reinstall the apx driver as i sugguested since the one i installed came with a different download pack?
leif2 said:
Yeah, i remember seeing a bunch of messages on tf101 about partioning ect.. . I dont think tf 101 rebooted though. Or maybe it did. This was some hrs ago now since tablet has been stuck with entering recovery mode on screen so i cant remember. I also dont remember if i ran bat with admin privilages. Shall i restart the entire nv flash procedure then? Should i first uninstall and reinstall the apx driver as i sugguested since the one i installed came with a different download pack?
Click to expand...
Click to collapse
It doesn't take hours to complete, not even an hour, you're looking at somewhere around the 15-30 minute mark, been a long time since I used it
Yea just cancel it, you can't break NVFlash, it is hard coded into the TF itself, its the lowest level communication between TF and PC that will still work even if you messed up your firmware, so long as hardware is fine
Drivers come with the NVFlash ROMs, uninstall the one you have running at the minute and install the one from the NVFlash zip
You'd be better off getting the new drivers ready and uninstalling the old ones while the TF is still connected in APX mode or they will disappear from device manager
These are the ones I use
http://www.xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
EDIT - Is your TF101 SBK1 ? (Serial number below B7O)
I went into device manager and uninstalled apx driver like you said but after that I didn't see a way to update apx driver. Holding down vol up/ power didn't seem to be doing anything so I rebooted my PC with asus still attached. That caused the asus screen to go dark which had previously been stuck with the entering nv flash recovery mode/nv3p message for the last 3 hrs. tf101 wouldnt seem to turn on so I plugged it into wall thinking battery may have died but now it still wont turn on. Have I killed my tf101? If not what do I do now? I can feel the charger heating up so pherhaps I better leave it plugged into wall until charger cools down again letting me know it's charged?
Its likely still in APX mode, you'll need to hold power for about 20-30 seconds, then power it on again normally
To install the new APX drivers, you'll need to power it into APX mode while it is attached to the PC USB, then once the PC sees it, point the driver install to the new driver location and install them that way
I plugged back into pc and in device manager it wont let me change apx. It says it already has the best version. This even though i had uninstalled it just before. At this point since i cant see my battery leval im going ro leave plugged into wall for a while and then try running bat file again with current apx drivers and come back here to post my results. Thx for assistance. By the way before plugging back into pc i tried holding power button down for 30 seconds and nothing happened.
You'll need to check the "Delete driver software" box when you uninstall the APX driver or it will just install it again automatically
Likely that driver is fine anyway if it can see the TF
Holding the power button down for 30 seconds just powers the TF off, you won't see anything until you power it back on again
APX mode is 99% black screen on the TF until you power it off and back on normally again
Before i run the bat file- did you say to do it in a cmd prompt? Cause i dont remember reading directions to do it that way. I think before i just double clicked the bat file that was extracted on my PC. By the way i held rhe power button for at least 30 seconds more than once im pretty sure, and there was no activity on my screen
The .bat file will open CMD itself
you were right, when i checked the box "delete driver software" I was able to uninstall. Then after rebooting W8 in advanced settings I was able to disable driver certification which let me update my APX to that of the same folder in which I downloaded the nvflash im currently using. Unfortunately all this had the same result. That is the cmd ran successfully formatting/ partioning ect.. and then like before the cmd said something quickly about being successful and then self closed. Now like before my tf101 is stuck showing entering nvflash recovery message on screen. It never rebooted. Could this be that my tf101 is too new for this method to work? My serial bar sticker came off so I can't check it but my sales invoice is dated june 8 2011 if that helps. Please advise what I should do now
leif2 said:
you were right, when i checked the box "delete driver software" I was able to uninstall. Then after rebooting W8 in advanced settings I was able to disable driver certification which let me update my APX to that of the same folder in which I downloaded the nvflash im currently using. Unfortunately all this had the same result. That is the cmd ran successfully formatting/ partioning ect.. and then like before the cmd said something quickly about being successful and then self closed. Now like before my tf101 is stuck showing entering nvflash recovery message on screen. It never rebooted. Could this be that my tf101 is too new for this method to work? My serial bar sticker came off so I can't check it but my sales invoice is dated june 8 2011 if that helps. Please advise what I should do now
Click to expand...
Click to collapse
Normally it tells you that it can't find the tablet or fails sending the data if your TF is SBK2, it sounds like something else is wrong somewhere
You could try using Easyflasher, that works on SBK1 and SBK2 TF101s
http://forum.xda-developers.com/showthread.php?t=1688012
That should install TWRP Recovery, and from there you can flash any ROM you like from MicroSD Card
Make sure you choose TWRP recovery though
I was having trouble rooting. Started a couple threads here about a couple different methods I tried. It seems the nvflash method may have worked but it seems the instructions for this were removed and I didn't know I had to put the rom inside the nv flash folder. My failed nvflash showed a bunch of formatting/partioning info on pc screen in a cmd prompt before saying successful and force closing. This left tablet with a entering recovery message stuck on screen. I then went into device manager to update my apx. I had previously gone into w8 advanced settings to uninstall a apx to apply a different one but when I went into device manager my android wan't there. I notice when I hold down power/ down i get a usb sound of dissconecting followed quickly by a sound of connecting but still no sign of device on device manager. In view under device manager I clicked show hidden items. There I saw the android. I then uninstalled them but I don't see a way to install new APX and ever since my fail nvflash tf101 wont boot. Please tell me I didn't brick! And I dont have system restore on my PC. I was thinking to bring back driver:crying:
Best not to keep making new threads for the same issue, keep everything in one thread or people will stop replying / mods will close duplicate threads
well even though I didn't see apx in device manager I was able to run easy flasher and flash stock android so I'm very relieved to have a working tf101. transformer rebooted successfully
Good stuff, so long as you don't try to mess with TWRP recovery again, you shouldn't run into any more issues, you can flash customs ROMs from recovery from now on, just make sure you keep TWRP as your recovery and not CWM
Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!
You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go
I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.
It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back
I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.
It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck