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
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 Guys,
I have the TF101 tablet and anytime I try to reboot it just stays at the first boot screen with the "Eee...." screen. Forever. If I hold down power and vol-down then hit vol up, it just stays there saying its booting recovery image but never changes. If I hold down volume long enough it comes to the factory reset/cold boot screen, if I choose cold boot it will boot.
I have rooted the tablet and had no problems previously, was able to flash roms and whatever else I wanted to do. Also, when I plug the tablet into my Windows XP machine, it does not detect the tablet in any way.
Tablet info:
Android Version: 4.0.3
with 2.6.39.4 kernel
I don't remember what rom its running exactly but I know its a version of ICS
Did you use ROM manager to update your CWM version? This sounds exactly like that, you can try running the bootloop-fix in my PERI tool (link in my signature) to fix, or manually run roach2010's fix found in his latest recovery thread. You definitely need ADB working, otherwise you'll need to Nvflash. (Nvflash Wheelie link is in my signature as well)
You are probably right i very well could have done so in rom manager. Im on vacation and dont have access to a pc right now but am going to try ur tool when i get back. Thx for the info
Sent from my Transformer TF101 using xda premium
Wait. I just realized. My pc doesnt even respond when i plug my tab in. How do i run PERI?
Sent from my Transformer TF101 using xda premium
Cold boot and install the drivers.
Ok Thing o Doom, you've been great pointing me in the correct direction, however I need some more guidance.
I have installed ADB, and when I cold boot the device and run adb devices I get nothing.
HOWEVER, if I just reboot the tablet, when it's stuck on the EEE screen, I do adb devices and it shows 123456789ABCDEFG.....
My computer doesn't see the tablet when it's plugged in otherwise, nor does any other windows PC in the house. Do you have any guidance as to what I can do? Please help, I need to get this thing running right.
You just need to get to a state where adb is recognized, and 'adb shell' command works.
From that point PERI should work.
Reboot when it prompts you to if it doesn't automatically (Probably won't being stuck on logo)
I can't seem to get anywhere else. My pc recognizes the tablet at the first boot screen but adb shows it as inactive. When I cold-boot the tablet it boots and loads fine but ADB nor any PC recognizes that it's plugged in. I'm lost.
Is "Enable USB Debugging" Checked in Developer Options?
I'm trying to install CWM and I rooted my Asus TF101. I installed RecoveryInstaller.apk, but when I click "Click to flash Recovery" the large button highlights blue for a few seconds, then goes back to black and nothing happens, no reboot, no CMW installed. When I try to boot into recovery I get the Android guy laying on his back with a Warning symbol in his belly...any ideas? I wiped my TF completely and still does the same thing. When I tried running Razorclaw I get the message saying I'm already rooted. Originally I used Debugfs Root Generic v2.3 to root my TF101. The firmware version I am on is US_epad-9.2.1.27-20120615. I wiped my data this morning in an attempt to resolve this issue, but before the wipe I DID have the superuser app. Now after the wipe, there is no superuser app.
Any ideas? I'm also having an extremely hard time getting my TF101 to connect to ANY PC. Its really weird because sometimes it will work after hours of it not working...most of the time it just comes up as "Unknown Device" with an error.
If you are rooted, install GooManager, grant root and then tap the 3 buttons in the top right and Install OpenRecovery Script.
This installs TWRP which is much better than CWM in my opinion.
Also, check the Dev section for my guide to Root and ROM the TF101, including APX drivers to install recovery with EasyFlasher.
I suspect young not be rooted because AFAIK you need a custom recovery to root on the latest firmware.
frederuco said:
If you are rooted, install GooManager, grant root and then tap the 3 buttons in the top right and Install OpenRecovery Script.
This installs TWRP which is much better than CWM in my opinion.
Also, check the Dev section for my guide to Root and ROM the TF101, including APX drivers to install recovery with EasyFlasher.
I suspect young not be rooted because AFAIK you need a custom recovery to root on the latest firmware.
Click to expand...
Click to collapse
So I was able to install GooManager as suggested but when I tried to install OpenRecovery it would download successfully (and I can browse to the file) but it would not install the recovery. Any suggestions? Thanks in advance.
Sent from my MB865 using Tapatalk 2
polishfly said:
So I was able to install GooManager as suggested but when I tried to install OpenRecovery it would download successfully (and I can browse to the file) but it would not install the recovery. Any suggestions? Thanks in advance.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Are you really rooted?
I suspect you are NOT rooted, which is why these are not working.
When you opened GooManager, did it prompt you for Root Permissions from SuperUser or SuperSU?
If not, then you need to root again.
Check out PERI or EasyFlasher to root.
polishfly said:
I'm trying to install CWM and I rooted my Asus TF101. I installed RecoveryInstaller.apk, but when I click "Click to flash Recovery" the large button highlights blue for a few seconds, then goes back to black and nothing happens, no reboot, no CMW installed. When I try to boot into recovery I get the Android guy laying on his back with a Warning symbol in his belly...any ideas? I wiped my TF completely and still does the same thing. When I tried running Razorclaw I get the message saying I'm already rooted. Originally I used Debugfs Root Generic v2.3 to root my TF101. The firmware version I am on is US_epad-9.2.1.27-20120615. I wiped my data this morning in an attempt to resolve this issue, but before the wipe I DID have the superuser app. Now after the wipe, there is no superuser app.
Click to expand...
Click to collapse
Razorclaw doesn't work on that firmware. Do as frederuco suggested.
I think it may be my TF
I can't get it to connect to my PC properly. It comes up as "unknown device" and sometimes the sync app opens on the tablet but I still can't see the tablet on the PC with Asus sync or even windows explorer. I have looked everywhere online for a solution to this and tried every set of drivers I could find and I still have the same results...tried on 3 different PCs..2 win7 x64 and 1 win xp. Its out of warranty and I'm not sure what else to do. I may be stuck with the stock ROM. Any thoughts ideas or suggestions?
Sent from my MB865 using Tapatalk 2
polishfly said:
I think it may be my TF
I can't get it to connect to my PC properly. It comes up as "unknown device" and sometimes the sync app opens on the tablet but I still can't see the tablet on the PC with Asus sync or even windows explorer. I have looked everywhere online for a solution to this and tried every set of drivers I could find and I still have the same results...tried on 3 different PCs..2 win x64 and 1 win xp. Its out of warranty and I'm not sure what else to do. I may be stuck with the stock ROM. Any thoughts ideas or suggestions?
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
I used the Naked Drivers v0.72 on mine and it worked great (both ADB and APX). Did you try those?
There is also a chance it is your charging cable (it may still charge, but may not work for USB connections).
Where can I get the Naked drivers? I feel like I've already tried this and when I try to install them windows says they are not for my hardware. I will buy a new cable.
Sent from my MB865 using Tapatalk 2
polishfly said:
Where can I get the Naked drivers? I feel like I've already tried this and when I try to install them windows says they are not for my hardware. I will buy a new cable.
Click to expand...
Click to collapse
[ADB/FB/APX Driver] Universal Naked Driver 0.72
frederuco said:
[ADB/FB/APX Driver] Universal Naked Driver 0.72
Click to expand...
Click to collapse
Turns out I already tried these drivers. When I plug my TF in it shows up as 1 "unknown device" so I tried to install both the apx and win drivers which both showed the following error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
polishfly said:
Turns out I already tried these drivers. When I plug my TF in it shows up as 1 "unknown device" so I tried to install both the apx and win drivers which both showed the following error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
Strange, because I used those exact drivers here on a Win7 x64 system with no issues: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
frederuco said:
Strange, because I used those exact drivers here on a Win7 x64 system with no issues: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Click to expand...
Click to collapse
That's a bad ass guide you got there! Here is where I am getting stuck:
"Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds. You should hear the new hardware found sound. It will probably fail the driver installation. "
Nothing happens when I hold the VOL UP and POWER for 15, 20, 30 seconds...it doens't boot up or anything...it only responds when I hold the power button alone or the power button and vol down. Any thoughts?
New USB cable on its way...but from what I have read, there has not been 1 instance where a new USB cord had fixed the exact issues I am experiencing.
Not sure, some users had issues where their power button may not work for APX mode. Keep in mind, the screen will be black when in APX mode.
You could try holding VOL UP and the plug in the USB cable to your PC (continuing to hold VOL UP) and this will trigger the tablet to turn on and enter APX mode.
polishfly said:
That's a bad ass guide you got there! Here is where I am getting stuck:
"Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds. You should hear the new hardware found sound. It will probably fail the driver installation. "
Nothing happens when I hold the VOL UP and POWER for 15, 20, 30 seconds...it doens't boot up or anything...it only responds when I hold the power button alone or the power button and vol down. Any thoughts?
Click to expand...
Click to collapse
Nothing happens on the tablet, that is normal, screen stays black in apx mode.
The computer should see the a usb device though. Vendor ID is 0955 (nvidia). On linux 'lspci' shows it. On windows you should see it in the device manager, maybe even tagged with a yellow exclamation mark due to drivers not being installed. If you see it there try installing the drivers using device manager.
frederuco said:
Not sure, some users had issues where their power button may not work for APX mode. Keep in mind, the screen will be black when in APX mode.
You could try holding VOL UP and the plug in the USB cable to your PC (continuing to hold VOL UP) and this will trigger the tablet to turn on and enter APX mode.
Click to expand...
Click to collapse
I tried what you suggested, but I still get no APX device to show up in Device Manager. It shows up as "unknown device" and when I try to install the APX and/or Win drivers, I get the error stating that I do not have the hardware for the drivers.
I dunno, I used the naked drivers on mine with a Win7 x64 system and x86 with no issues.
frederuco said:
I dunno, I used the naked drivers on mine with a Win7 x64 system and x86 with no issues.
Click to expand...
Click to collapse
At this point I think it could be one of 2 things...a faulty USB cable (ordered) or a TF hardware issue (its out of warranty so I'm SOL if that's the case)...worst case scenario, I'm stuck with stock since I can still boot and charge. I would love to run CyanogenMod though =(
Try a linux CD and use ADB to install TWRP to the TF.
I would use an Ubuntu Live CD and install ADB on the live session (don't reboot or you will have to start over)
Then you should be able to follow the directions from the link below...
http://www.teamw.in/project/twrp2/109
The reason I say to use a Linux live CD is because you won't have to worry about drivers or be in APX mode. You just have to make sure you have the checkbox for android debugging mode enabled in settings on your TF.
bfmetcalf said:
Try a linux CD and use ADB to install TWRP to the TF.
I would use an Ubuntu Live CD and install ADB on the live session (don't reboot or you will have to start over)
Then you should be able to follow the directions from the link below...
http://www.teamw.in/project/twrp2/109
The reason I say to use a Linux live CD is because you won't have to worry about drivers or be in APX mode. You just have to make sure you have the checkbox for android debugging mode enabled in settings on your TF.
Click to expand...
Click to collapse
This, if that doesnt work id go for hardware issue(although even that is highly unlikly due to it being dectect at all) ive had various issues relating to these drivers, you really need to install the naked drivers before trying to install asus sync software as i think asus software causes issues. Best option would be to install windows in a virtual machine and install the naked drivers and try again.
Right, I searched on numerous pages on these wonderful forums, but couldn't quite find what I was looking for. So I'll try my luck here. I'll describe my problem.
My TF101 was rooted using the CWM recovery. After doing more research I found out I shouldn't be doing this. But, unfortunately the damage has already been done. After several succesful ROM installations I wasn't quite happy with, I tried one last CM10 install. That's when it all went to ****. My TF101 has been stuck on the Eee Pad splash screen for nearly 2 months now.
Normally when going into the recovery mode I can simply select install from SD card and install a new rom. Now it can't seem to mount and displays E:Can't mount \SD card or whatever.
Further on, I tried using the ADB tools to manually restore system files. Without luck. After which I tried to install the naked USB drivers using http://forum.xda-developers.com/showthread.php?t=1426502. Without luck as well. I simply ran out of ideas.
The thing is, in Device manager I do see a device called Android. But, for some reason I can't seem to install any drivers for it. I guesse this would be the first step towards getting it back to work? Or perhaps I should just get it fixed at the computer store?
Any sugestions would be more than welcome!
Easy Flasher will get you back to stock as long as you can access APX. You will lose all data however.
1st mistake read forum before you do something, coz you would have learnt abt CWM issues, anyway thatsvan old story
You got Two options, find an flash able twrp.zip and flash it using current recovery if its still working otherwise as the other guy says easyflasher
To use easy flash you need
Easy flash software from forum
Universal naked driver installed
Asus firmware and PATIENCE
Follow the steps given in the forum and you should get back a tablet running stock rom, then if you want then use easy flash to root your device again but this time use TWRP recovery.....
Sent from my Transformer TF101 using xda app-developers app
Right, so far I've done everything I could find. I have installed the naked ADB files and thus was able to make a connection through USB. However, I wasn't able to push any files onto the tablet through ADB commands.
I entered the (what I assumed to be) APX mode and tried to use EasyFlasher. It seemed to have worked, because a DOS screen asked me whether or not I wanted to overwrite several files. After ending the procedure I rebooted my tablet. And guesse what: CWM is still there and the tab is still stuck on the Splash screen. Also the internal SD still can't be mounted.
What am I doing wrong. I'm slowly but surely going mad here....
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Lethe6 said:
hmmm, easyflasher should not prompt you to overwrite anything, it should just wipe it clean. The only prompt is when you select SBK1 or SBK2.
Can you post screenshots? It'd help us understand what exactly is going on...
Click to expand...
Click to collapse
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
AlbertGJBos said:
Right. Apparently I didn't put it in APX mode correctly. Windows asked me to install APX drivers. Which I now did. I then (I assume) was able to install the new recovery. The screen says !!!!phone update succes!!!!!. As we speak I am trying to install the stock ROM. Fingers crossed.....
Click to expand...
Click to collapse
I'll just sum up what I've been doing so far, because it still ain't working for me....
1) Put the TF101 in APX mode using POWER + VOLUME UP
2) Started up EasyFlasher 0.8.3 and selected "Flash Asus stock zip / Unbrick"
3) When prompted "file ..\temp\META-INF\MANIFEST.MF" already exists I selected "A(u)to rename all"
4) And then starts doing it's thing
5) Stuck at creating and formatting 15 partitions with several three letter codes.
I've ran the program three times now, but without luck. Any sugestions?~
[EDIT]Alright, managed to get it to work! Ended the tasks in through task manager about 4 times, but the 5th time was a charm. Exactly work as said. All thanks to EasyFlasher![/EDIT]
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video
parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it
parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try