[SOLVED] Stuck in APX mode, can't boot into CWM

[SOLVED] Stuck in APX mode, can't boot into CWM - Eee Pad Transformer General

Hi all, I've been having problems with my transformer... again. This time I have my transformer successfully rooted with an updated CWM, and flashed PRIME 1.6 and Netformer 1.5. The problem started when I held down power and selected the recovery option in the shutdown menu. the tablet went into a bootloop until I put it into APX mode to run the unbricking tool stickied in the dev section. For some reason, the tool didn't work and it did NOT say "phone update success on the tablet screen."
I then turned it off and my computer makes the USB disconnect sound, but then makes the connect sound right after, and Nvidia USB recovery shows up in device manager again, which means that it is stuck in APX mode. I cannot boot into CWM and I cannot boot up normally because it just dumps me back into APX.
I found a thread of someone who was also stuck in APX mode, but it doesn't help because he just returned the tablet whereas I cannot. http://forum.xda-developers.com/showthread.php?t=1169097
So to recap, I am stuck in APX mode, I can't boot normally or into CWM, and the unbricking tool does not work. Help please? I am starting to seriously regret flashing anything
EDIT: I did it! Thanks to all for the responses, I finally followed this guide to nv_flash prime 1.6r2 to my tablet and now it boots! The problem turned out to be that when I used the unbricking tool, it formatted all my data so the tablet was not able to boot into anything. By nv_flashing a rom onto it, it had something to boot into... again, thanks!

Anyone have any ideas? If I can't fix this then $400 went down the drain

Have you tried nvflash? I had that problem but nvflashing prime worked for me.
Sent from my PC36100 using Tapatalk

Vertiginouz said:
Hi all, I've been having problems with my transformer... again. This time I have my transformer successfully rooted with an updated CWM, and flashed PRIME 1.6 and Netformer 1.5. The problem started when I held down power and selected the recovery option in the shutdown menu. the tablet went into a bootloop until I put it into APX mode to run the unbricking tool stickied in the dev section. For some reason, the tool didn't work and it did NOT say "phone update success on the tablet screen."
I then turned it off and my computer makes the USB disconnect sound, but then makes the connect sound right after, and Nvidia USB recovery shows up in device manager again, which means that it is stuck in APX mode. I cannot boot into CWM and I cannot boot up normally because it just dumps me back into APX.
I found a thread of someone who was also stuck in APX mode, but it doesn't help because he just returned the tablet whereas I cannot. http://forum.xda-developers.com/showthread.php?t=1169097
So to recap, I am stuck in APX mode, I can't boot normally or into CWM, and the unbricking tool does not work. Help please? I am starting to seriously regret flashing anything
Click to expand...
Click to collapse
Did you actually flash a rom? That can happen when you dont have the appropriate files in the directory. Refer to the video that demonstrating an NVflash.
Sent from my Transformer TF101 using XDA Premium App

Yes, I flashed prime 1.6 and booted it successfully. I used the "recovery" option in the shutdown menu and that caused the bootloop, i never got into cwm

Did you compare md5's?
Sent from my Transformer TF101 using XDA Premium App

Backwardsblade said:
Did you compare md5's?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I didn't, but it did boot up fine, which means it was a legitimate download right?
I think I'll just try to send it to asus and see what they can do since NVflash doesn't work

I would probably download again, check the MD5 and reinstall.
Skickat från min ASUS Eee Pad TF101

I can't reinstall if I can't boot into cwm

Vertiginouz I can't reinstall if I can't boot into cwm
Click to expand...
Click to collapse
Are you sure you know what nv_flash is? This is only run in apx mode.

Did you try the one click batch method: http://forum.xda-developers.com/showthread.php?t=1185104
See whether that works for you...

keep this thread open, I would really like to know what the OP did to get out of this mess.
I would also like to know if other peeps running Prime 1.6 can press the recovery button instead of shutdown for some testing.

What kind of testing? I just did root a TF, backed it up, installed Prime, clicked the Recovery button and did a back up. Zero trouble.
I think this is my 7th or 8th root. People at work just keep bringing them to my office

It sounds like you didn't have a Rom when you nvflashed. If you just downloaded nvflash file in the stickied unbricking post then you will format everything without putting anything back on. You need to Rom that was built nvflash and put it in the root directory of the nvflash folder. There are some stock Roms available somewhere & also a prime 1.4 nvflash. They will install a recovery and then you can flash whatever you want from there.
Sent from my Transformer TF101 using XDA Premium App

boglwe said:
keep this thread open, I would really like to know what the OP did to get out of this mess.
I would also like to know if other peeps running Prime 1.6 can press the recovery button instead of shutdown for some testing.
Click to expand...
Click to collapse
I am currently running Prime 1.6 and i did a recovery method the other day to update a rom and it worked just fine.
I did it since i updated from 1.5 to prime 1.6 and had to re install the Clemsyn-blades cause the overclocking rom got disabled after update...

Thanks for the suggestions guys, I'll try the link that Q.Entity posted first.
housry23 said:
It sounds like you didn't have a Rom when you nvflashed. If you just downloaded nvflash file in the stickied unbricking post then you will format everything without putting anything back on. You need to Rom that was built nvflash and put it in the root directory of the nvflash folder. There are some stock Roms available somewhere & also a prime 1.4 nvflash. They will install a recovery and then you can flash whatever you want from there.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Okay so the unbricking nvflash formats everything, meaning I can't boot normally because I have no ROM? Shouldn't I still be able to boot into CWM though?
Also, the prime 1.4 nvflash thread you're talking about is this right? If I follow that guide will it install prime 1.4 during the nvflash process? If so, that will probably solve my problem

should work, but why stop there, I went ahead and popped on Prime 1.6 and then flashed a different kernel as well. I mean, I nvflashed from temp brick, perhaps like yours, and instead of flashing 1.4 prime I went ahead and did 1.6 since I already had the zip. I also at some point did the unbricking nvflash to stock rom, then used the pure root for tranformer method that includes CWM and then flashed Prime. regardless, both ways I was temp bricked. The key for me was knowing that I was in APX mode even though Device Manager in wndows 7 64bit did not show I was. Hope I could help, I am only speaking from my OWN experience with this device and prior mistakes.
EDiT: I also noted as some point that I could not get into recovery becuase I was not paying attention to my recovery screen. If all is correct, then when you hold down Vol- and power button, you are only given 5 seconds to press vol+ button to enter CWM.
Sent from my Transformer TF101 using XDA Premium App

The batch pure root script didn't work for me, even though I tried nvflashing the stock boot.img and recovery. No matter what, I couldn't get out of APX mode. The transformer immediately turns back on and puts me back into APX mode after I turn it off. Device manager and the USB connect/disconnect sounds confirm this. I'm afraid there's no way to get out

Why are you doing a pure root, after nv_flash. Why not just nv_flash prime 1.6 and be done? That will have everything working.

Yep.. your doing things kinda backwords.
Sent from my PG86100 using XDA Premium App

Related

[Q] 3.2 wifi only root

hi all i cant seem to root my xoom.
to start i have a uk wifi only model and have flashed the 3.2 usa wifi.
works perfectly, i have unlocked the bootloader flashed root boot and then when i give the command fastboot reboot to then try and enter the recovery it just gets jammed on motorola logo does anyone know what im doing wrong i have followed several guides to the letter know and i cant seem to get root,

You didn't explain exactly what you are doing (have done) when you get stuck at the dual core screen.
One problem that can occur when rooting is overwriting your new Clockworkmod Recovery with stock recovery. In case this is the problem, here is
some important information to help get the new CWM recovery to stick.
From a thread called "an Idiot's Guide to flashing the Xoom" with info originally by public animal:
To install recovery image (CWM)
Download the recovery image file and save it to your computer
1 Boot into flash mode with 'adb reboot bootloader'
2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this process
4 Enter CWM with the following procedure: Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ... 5 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery.

When it gets jammed after the bootloader unlock process it stays on the Motorola dualcore logo' if I press power and up to restart it won't boot normally at all it just stays on moto logo and then I have to reflash for it to boot up normal' I don't understand where I'm going wrong' I have followed the threads to the letter a DB and fastboot fully working but something is stopping me from getting root.
Sent from my Xoom using XDA Premium App

bearusa said:
When it gets jammed after the bootloader unlock process it stays on the Motorola dualcore logo' if I press power and up to restart it won't boot normally at all it just stays on moto logo and then I have to reflash for it to boot up normal' I don't understand where I'm going wrong' I have followed the threads to the letter a DB and fastboot fully working but something is stopping me from getting root.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I would like to add I had no probs rooting my Sony experia play using adb and fastboot its weird I just can't put my finger on it'
Sent from my Xoom using XDA Premium App

bearusa said:
I would like to add I had no probs rooting my Sony experia play using adb and fastboot its weird I just can't put my finger on it'
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
It would help if we knew which guide you were using.

Guide for usa 3.2 wifi and 3g posted by jase33 in xoom android dev' than for your help guys
Sent from my Xoom using XDA Premium App

okantomi said:
It would help if we knew which guide you were using.
Click to expand...
Click to collapse
Than mate your guide sorted me out I'm now rooted and have recovery' I'm thinking I may have been entering a cmd incorectly'
or something or my recovery.img was corrupted I redownloaded files followed the guide you posted for me and it worked a treat.
Thanks for your help mate much gratitude and appreciation to you.
Sent from my Xoom using XDA Premium App

bearusa said:
Than mate your guide sorted me out I'm now rooted and have recovery' I'm thinking I may have been entering a cmd incorectly'
or something or my recovery.img was corrupted I redownloaded files followed the guide you posted for me and it worked a treat.
Thanks for your help mate much gratitude and appreciation to you.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I'm so glad it worked out. Now enjoy your rooted Xoom!

okantomi said:
I'm so glad it worked out. Now enjoy your rooted Xoom!
Click to expand...
Click to collapse
This thing is flying now' got rid of bloat once again thanks for your help
Sent from my Xoom using XDA Premium App

[Q] TF101 ASUS Transformer Bricked? What? Please...Help?

I think I am gonna speak out the honest truth and say I wasn't lying, and here goes...
I followed up on Brks Root Kit v7 and it worked beautifully, then I saw another thread about getting root with losing the bricking fault, so I tried the nvflash to remove bricking...but I think I rewrote it too fast before thinking I better check the APPs on my Transformer and see if I got a super user apk in there, but I didn't and forgot to hestitate but bricked my TF101 Transformer
Help, It only is showing power up when I press it and gets stuck at boot of ASUS Screen page.

It's not bricked yet. Read the forum carefully mate.
Sent from my TF running ARHD and Clemsyn kernel

run the nvflash again, make sure the recover and rom images are in the nvflash folder. it wil unbrick your TF, reroot and install the rom you put in the folder.

sonami said:
run the nvflash again, make sure the recover and rom images are in the nvflash folder. it wil unbrick your TF, reroot and install the rom you put in the folder.
Click to expand...
Click to collapse
I can put only a rom image file, correct?

You need to SLOW down and read carefully. Slow down a bit when you type too man.
Sent from my Transformer TF101 using Tapatalk

[ROOT] TF300TG WW_epad_9.4.4.40

Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris

blackynet said:
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
Click to expand...
Click to collapse
Unfortunately I don't know how to get back your recovery.
But I thank you for warning about "1-Click Transformer Root" in combination with the .40 firmware.
I can confirm, that rooting my TF300TG with .40 firmware using http://forum.xda-developers.com/showthread.php?t=1706588 works without problems.
Edit: I tried to get into the (stock) recovery and I can't get into it, too. Instead I get the lying robot with the warning sign. Seems that something during the rooting process kills the recovery.

I want to root mine, but do any of you know to get back the recovery or any recovery at all?
I also want to know if you do the root before the .40 update will you have recovery after?
Thank you big

slide200sx said:
I want to root mine, but do any of you know to get back the recovery or any recovery at all?
I also want to know if you do the root before the .40 update will you have recovery after?
Thank you big
Click to expand...
Click to collapse
I root after the .40 update and no I have not found a way to fix my recovery for now.
I first use a tool that did root and flash a new recovery. But I did not get root and my recovery was broken.
The debugfs tool did only root your pad, so I think there will nothing happend with your recovery.
regards
Sent from my ASUS Transformer Pad TF300TG using XDA Premium HD app

Your recovery is fine. Nothing has changed unless you rooted successfully. Your recovery has not been touched yet to my knowledge. Does your tab boot to the operating system? If so you are fine.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
---------- Post added at 02:48 AM ---------- Previous post was at 02:47 AM ----------
I think you can only flash the new recovery AFTER you unlock the boot loader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

I don't know but can't you just flash a recovery.img or recovery.blob via fastboot? or is an unlocked bootloader needed for this?
(I did this and it worked, will also work for you if your PC still recognises the fastboot device...again, I'm unsure whether unlocked bootloader is needed)

I unlocked bootloader and then used adb to push the cwm recovery, then used the root zip
worked for me, i had just got mine and feeling bad that the update just downloaded and wanted to install .40 all it all time but after i did it was still good....plus i had to learn adb to do it as the commands given had been wrong and didnt work,,,lol

blackynet said:
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
Click to expand...
Click to collapse
For my case rooting worked with the one clock tool ???

blackynet said:
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
Click to expand...
Click to collapse
Hello ...
First, sorry for my bad english, I'm from Germany and use the google translator
Similar with me...
I rooted my TF300TG with the '1-Click Transformer root '.
It worked and I have root. However, I have now tried to boot into recovery I get after a while the lying Android.
My firmware version is ww_9.4.4.40
The tablet is working properly, I only have no recovery. Do I get now no more OTA updates? How can I fix the Recovery?
Who can help?
Regards, Wolf

Wolf Hamburg said:
Hello ...
First, sorry for my bad english, I'm from Germany and use the google translator
Similar with me...
I rooted my TF300TG with the '1-Click Transformer root '.
It worked and I have root. However, I have now tried to boot into recovery I get after a while the lying Android.
My firmware version is ww_9.4.4.40
The tablet is working properly, I only have no recovery. Do I get now no more OTA updates? How can I fix the Recovery?
Who can help?
Regards, Wolf
Click to expand...
Click to collapse
Are you saying you had recovery before? That version number is stock, so either you unlocked the bootloader previously and loaded recovery then lost it, or you never had it. In any case, to get it, you must unlock the bootloader to do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
Are you saying you had recovery before? That version number is stock, so either you unlocked the bootloader previously and loaded recovery then lost it, or you never had it. In any case, to get it, you must unlock the bootloader to do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
yes, i know... the 9.4.4.40 is stock ics.
i never tries before i have rooted to boot in recovery. i thought each version, if stock or custom, has a recovery?
my bootloader is locked end i never flashed e recovery.
so it is normal that the stock 9.4.4.40 ics has no recovery? but when i boot with power/volume down and then volume up, the tf300tg tries to boot in recovery and after a little while the android lay down... ist this normal behavior for the stock 9.4.4.40 ?

Wolf Hamburg said:
yes, i know... the 9.4.4.40 is stock ics.
i never tries before i have rooted to boot in recovery. i thought each version, if stock or custom, has a recovery?
my bootloader is locked end i never flashed e recovery.
so it is normal that the stock 9.4.4.40 ics has no recovery? but when i boot with power/volume down and then volume up, the tf300tg tries to boot in recovery and after a little while the android lay down... ist this normal behavior for the stock 9.4.4.40 ?
Click to expand...
Click to collapse
You do not have recovery by default, and you cannot have it without unlocking the bootloader.
Fortunately you can still root on ICS. Search the Dev section for the debugfs method for rooting on ICS.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

no, i have root. the one click tool has worked fine without errors... how it looks for ota updates? I read somewhere that i must have stock recovery for ota updates?! but with an open bootloader ota updates???

Wolf Hamburg said:
no, i have root. the one click tool has worked fine without errors... how it looks for ota updates? I read somewhere that i must have stock recovery for ota updates?! but with an open bootloader ota updates???
Click to expand...
Click to collapse
I'm told unlocked bootloader cancels ota but you can still manually update.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
You do not have recovery by default, and you cannot have it without unlocking the bootloader.
Fortunately you can still root on ICS. Search the Dev section for the debugfs method for rooting on ICS.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Wolf Hamburg said:
yes, i know... the 9.4.4.40 is stock ics.
i never tries before i have rooted to boot in recovery. i thought each version, if stock or custom, has a recovery?
my bootloader is locked end i never flashed e recovery.
so it is normal that the stock 9.4.4.40 ics has no recovery? but when i boot with power/volume down and then volume up, the tf300tg tries to boot in recovery and after a little while the android lay down... ist this normal behavior for the stock 9.4.4.40 ?
Click to expand...
Click to collapse
Well. I have a TF300TG with stock 9.4.4.40 firmware (never tried to root, mod or anithing else) and I would like to simply root it...
I've seen many comments saying that after rooting, the stock recovery is lost (lying Android robot after Power+VolDown key press), and other replies stating that this is normal and that there isn't any stock recovery on the pad.
My five cents to this thread are that on my fresh pad I've tried to start from poweroff with Power+VolDown and I get something like a raw menu, with two icons at the center of the screen, giving me the option to make a full wipe or a cold boot (and maybe something else but I hadn't have time to go deeper inside it due to the timeout).
In any case, I don't get any lying Android robot!
Now, I'm a little scared to go on rooting my pad until this matter becomes definely clear...
Cheers

optigiu said:
...My five cents to this thread are that on my fresh pad I've tried to start from poweroff with Power+VolDown and I get something like a raw menu, with two icons at the center of the screen, giving me the option to make a full wipe or a cold boot (and maybe something else but I hadn't have time to go deeper inside it due to the timeout).
In any case, I don't get any lying Android robot!
Click to expand...
Click to collapse
Yes, this menu also comes to me.
But if I by power / volume down when the top left of the logo appears, press volume up, the pad trying to boot into recovery.
in your virginal system as well?

optigiu said:
Well. I have a TF300TG with stock 9.4.4.40 firmware (never tried to root, mod or anithing else) and I would like to simply root it...
I've seen many comments saying that after rooting, the stock recovery is lost (lying Android robot after Power+VolDown key press), and other replies stating that this is normal and that there isn't any stock recovery on the pad.
My five cents to this thread are that on my fresh pad I've tried to start from poweroff with Power+VolDown and I get something like a raw menu, with two icons at the center of the screen, giving me the option to make a full wipe or a cold boot (and maybe something else but I hadn't have time to go deeper inside it due to the timeout).
In any case, I don't get any lying Android robot!
Click to expand...
Click to collapse
Wolf Hamburg said:
Yes, this menu also comes to me.
But if I by power / volume down when the top left of the logo appears, press volume up, the pad trying to boot into recovery.
in your virginal system as well?
Click to expand...
Click to collapse
Ok, I've tried to press Power/VolDown and then, soon after the ASUS logo appeared at the center of the screen and a couple of rows of (small fonts) text were displayed at the top left, I released the two buttons and pressed just the VolUP; the result was that the screen was cleared and a standing green android robot appeared at the center with (kinda of) a blue progress bar under it; then, after about 1 sec, the figure was substituted by a lying green android robot having an open door at his "stomach" and a yellow triangle with an exclamation mark inside.
Is there any other check we can make on my fresh and your rooted systems in order to verify that rooting a TF300TG with 'one click transformer root' is safe? (what version did you use, 1.0 or 1.1?)
Edit: only now I've read this ... so it should be safe :fingers-crossed:

optigiu said:
...Edit: only now I've read this ... so it should be safe :fingers-crossed:
Click to expand...
Click to collapse
yes, now we can relax and wait for Jelly Bean

If itt. Is just your recovery that is lost no worries use fast boot and flash twrp or cwm
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

slide200sx said:
I unlocked bootloader and then used adb to push the cwm recovery, then used the root zip
worked for me, i had just got mine and feeling bad that the update just downloaded and wanted to install .40 all it all time but after i did it was still good....plus i had to learn adb to do it as the commands given had been wrong and didnt work,,,lol
Click to expand...
Click to collapse
Could you write a step by step guide about how to unlock bootloader and push the cwm recovery? Thanks.

[Q] bricked after ics update

yes i have search all over the internet, not just xda. may problem is very simaler to others but no quite the same.
here's what happened
ok. so i have a gen2 A500
it was running on stock 3.2 unrooted
i updated the acer update tool from the play store and then searched for the ICS updatit downloaded the update and asked me if i wanted to contine ue with the update.
i clicked yes and it started to do it's thing.
it completed as far as i could tell and rebooted
it got stuck at the acer log for 30 min until i decided something was wrong
i turnned it off but when i turn it on it still wouldn't boot past the acer logo.
i downloaded the stock ics update froma link here on xda and copied it to my sd card.
booted into recovery on the a500 whih automatically started the flashing process again.
still stuck at acer logo
i flashed it again and then this time did the power, vol+, switch hard reset combo. it booted into ICS
after logging in as a new user, i put the tablet down for maybe 5 minutes. it shut itself off and it's back to being stuck at the acer logo.
doe anyone know wth is going on?
i can get into download mode but i'm not sure what good that is doing me. it does say it has ics bootloaders.
Is there a program simaler to ODIN for samsung that i can boot into download mode and try to reflash that way?
thanks for any and all help.

Used this to get all the required info like cpuid and so on
http://forum.xda-developers.com/showthread.php?t=1675939
Sent from my GT-N7000 using xda app-developers app

Then used this to flash back to stock rooted honey comb.
http://forum.xda-developers.com/showthread.php?t=1516012
Anyone who's a500 locked up from doing a factory OS upgrade can use this to solve their issue
Sent from my GT-N7000 using xda app-developers app

CMW recovery.

i've installed rom manager on my TF101 and flash the recovery. i've tried to format/wipe data, it froze and i left it sit there for about 20 mins still nothing. so i decided to reboot my device and now its stuck on the Asus screen with the circle kept spinning. what could i do to save my TF? thanks for the help!!!

t061509j said:
i've installed rom manager on my TF101 and flash the recovery. i've tried to format/wipe data, it froze and i left it sit there for about 20 mins still nothing. so i decided to reboot my device and now its stuck on the Asus screen with the circle kept spinning. what could i do to save my TF? thanks for the help!!!
Click to expand...
Click to collapse
There's another recovery out called Team Win Recovery Project.. It seems to work better for a lot of folks..
http://forum.xda-developers.com/showthread.php?t=1818452

i can't even boot up the device right now.

No need to post multiple times.
I answered in the other thread:
Use EasyFlasher. Boot to APX and install a working recovery. I highly recommend TWRP over CWM.
http://forum.xda-developers.com/showthread.php?t=1688012

i've tried it but it keep saying done but dont work.
http://imageshack.us/photo/my-images/812/85472138.png/
this is what it said when i used the naked APX driver you recommend.

Did any text appear on the TF screen during the process? If not, it didn't work.
Are you sure you are using the correct SBK version?

no text appears on the TF screen. i've tried both of them.. nothing seem to work...

Are you sure it's detected in APX when you try it? It can be tricky sometimes...
Sent from my Transformer TF101 using xda app-developers app

ok thank god i've figure out a way how to install the APX drivers and now on the TF screen it said Entering NV Flash Recovery mode/Nv3P

Lethe6 said:
Are you sure it's detected in APX when you try it? It can be tricky sometimes...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
i've rooted the device and it happens and now im trying to bring it back to stock.

http://img716.imageshack.us/img716/7320/59799318.png
does this look right now?

t061509j said:
http://img716.imageshack.us/img716/7320/59799318.png
does this look right now?
Click to expand...
Click to collapse
Looks right. Did any text appear on the tablet screen?

Database Users

welcome