Stuck in APX mode - Eee Pad Transformer Q&A, Help & Troubleshooting

First time rooting the tablet. Thoroughly read and understood all instructions and have had multiple android phone devices that I have rooted/soft bricked/unbricked/restored to original so ive been through the process.
adb working and got tablet into apx. performed every step in the pure root for tablets thread and everything went well.
ran root.bat, tablet says it updated successfully
ran cwm.bat for clockwork and it shows to update successfully
instructions say to restart tablet, done. Now it stays in apx mode and will not go into booting screen.
tried to use nvflash to restore since i have apx access. run it and it appears to complete on the computer but on the tablet it only shows that i got into nvflash recovery and the chip uid. It never shows if it is successful.
Is there anything else I can do from while in APX? restarting the tab immediately dumps me back into apx even if i dont hold the up button.
Thanks for the help
puma

Did you try holding the power button down for 10-20 seconds?
If you are using the pure root method, you can use nvflash --resume --go to kick start the bootloader. You might have to add ./ or \ and .exe.

I managed to fix it after looking over everything.
the recovery nvflash would exit faster than i could read if there were any errors so i changed the batch file to incorporate /k
(edit your batch file and before the 'nvflash.exe' command put in 'cmd /k' include the space and add a space after the /k. Save it and let it run and it wont close after it does whatever its doing so you can now see what the prompt is doing)
after that I saw that nvflash failed bc it didnt have the boot/system/recovery images in the folder.
i cant post external links and cant link to the img's i got but just do a quick search for nvflash and prime you'll find em.
I knew it was prime and wanted to keep stock but with root but whatever, I'll look to get back into stock later.
just posting this up so if someone has the same problem they can fix it.

You MUST use apx to restore your device it seems the boot partition is wrong you should restore that with nvflash.

Related

[Q] 3.2 Update Problems, trying to understand APX

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.

HELP! I Brick the Tab.

Hi, im from Argentina.
My problem is the next.
I was trying to flash the new Flashback Rom 10.3.
Mi Clockworkmod was old, (cause i didnt have many options like the advance features). So i tried to update the recovery using ROM MANAGER from the market.
I use the first option (install clockworkmod) and then the fist item (dont remember wich, the name was like Elysium or so).
Then the tab restar and didn power up again.
My pc cant recognise the device by any form. Its not in APX mod cause of it
C:\Users\PC\Desktop\Gadgets\Gtablet\Nvflash>"nvflash.exe" --bct gtablet.bct --se
tbct --bl bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
USB device not foundPress enter to continue:
Please any help of the advanced users. Thanks so much.
Problem solved. Had to Open te Gtab and use the Hard Reset button on the back.
My problem now is the CWM. I try to re install it. Put the update.zip and the recovery folder (copy and paste above the cracked recovery from Rom Manager).
When i try to Boot into recovery it freezes on Loading kernel Image.
What can i do now?
hawksneo said:
Problem solved. Had to Open te Gtab and use the Hard Reset button on the back.
My problem now is the CWM. I try to re install it. Put the update.zip and the recovery folder (copy and paste above the cracked recovery from Rom Manager).
When i try to Boot into recovery it freezes on Loading kernel Image.
What can i do now?
Click to expand...
Click to collapse
If you can get your tablet into APX mode for NVflashing you need to get the latest pack to update your CWM and stock rom to a 1.2 bootloader in order to update to Flashback.
http://forum.xda-developers.com/showthread.php?t=1118898
This will help guide you into switching from 1.1 to 1.2 bootloaders.
.....and for God's sake, whatEVER you do with any other Android device, DON'T use Rom Manager on the GTab. You'll soft brick it 9 out of 10 times you use it. It's a fairly well documented issue with this device. just my 2 cents....
I would have to agree that if you are now able to get into APX mode, the best thing you can do is to NVFlash back to a stock 1.1 or 1.2 bootloader (see the previously mentioned thread) and start over from the beginning. Know which ROM you intend to use before you choose an NVFlash path, so that you flash to the proper bootloader version for the ROM you want to use.
Help, Gtab won't boot
My G-tab will not boot. It will only go to the APX mode. I have been reading this site for the past three days and have tried everything that I can find but nothing works. I can load CW and complete all of the steps, I can even get the gtab to boot up when I nvflash it but as soon as I reboot the gtab it goes into the APX mode. I would appreciate any help with this.
dakota_ev said:
My G-tab will not boot. It will only go to the APX mode. I have been reading this site for the past three days and have tried everything that I can find but nothing works. I can load CW and complete all of the steps, I can even get the gtab to boot up when I nvflash it but as soon as I reboot the gtab it goes into the APX mode. I would appreciate any help with this.
Click to expand...
Click to collapse
Take a look at gtabletfordummies website. Start with code RED if you haven't already done exactly those steps. Use the NvFlash file from their site for your bootloader version with CWM already installed. If you have to use code DETOX and have problems after, you may need to search XDA again for "magic value mismatch error". (Sorry I can't post links so you will have to search!) Make sure you read everything and don't skip any steps.
Thanks for the reply but I have already went through all of the different sections of Gtablet for Dummies and my gtablet will still not boot past the APX mode.
Only other thing I can think of to try would be to remove the back cover of your tablet and hold (10 - 15 seconds) the internal reset button on the back of the board. That should factory reset it. Search this site (xda) for "gtablet hardware breakdown" for pictures and some info about taking it apart.

B70 bricked - is there no way out?

Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?
Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev
After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.
Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?
df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?
My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.
Not getting anywhere with ADB, device is offline
hmm.. can you cold boot? just hold vol-down and wait?
df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.
Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.
I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.
Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.
Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.
Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day
Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.

[Q] [How-To Root] video removed-- help!

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

cant enter apk after uninstalling

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

Categories

Resources