Related
ive used easyflash and the flash completes 100% but doesnot boot up just stays on the nv screen or it shows battery empty sign?
anyone? i have problems getting it into apx mode, been trying for half an hour and still cant get it in to apx. would the bootloaders be a reason why i cant restore via nvflash?
Could it have gone flat during a flash? and it wont go into apx mode after the failed flash? Someone can correct me if im wrong but im sure partitions doesn't effect nvflash. what screens are you stuck at currently?
Ausboy 2011 said:
anyone? i have problems getting it into apx mode, been trying for half an hour and still cant get it in to apx. would the bootloaders be a reason why i cant restore via nvflash?
Click to expand...
Click to collapse
When you press power+volume up buttons together it gets into APX mode... when you are in that mode "tablet screen will be blank" till you start working with it.... laptop will say APX device connected.... what kind of situation are you facing?
Sent from my ransformer TF101 using xda app-developers app
also stuck
i'm not sure if i'm jacking this thread, but i have the exact same issue- was stuck in cwm boot. could cold boot into the normal os, but who wants that. so i used easyflasher to flash the newest asus update and attempt to fix this situation. used sbk2. now stuck on the nvflash recovery screen. computer says i'm still in apx mode. can't get the sucker to reboot for the life of me. it will record on the tablet screen when i flash and reflash, but won't let me reboot. also tried to flash all three recoveries (cwm, twrp, and roachxm) to no avail. some help would be appreciated.
yup
i know somebody has an answer to this. i cannot be the only idiot to get stuck here.
jkieffer46 said:
i know somebody has an answer to this. i cannot be the only idiot to get stuck here.
Click to expand...
Click to collapse
Try flashing different kernel.... I'm on custom kernel with team EOS JB ROM...... currently I'm using the kernel from the link below..
http://forum.xda-developers.com/showthread.php?p=29675167
Sent from my Transformer TF101 using xda app-developers app
Dont i have to use cwm to flash a kernel? Right now its stuck in apx mode. I cant get it to do anything.
jkieffer46 said:
Dont i have to use cwm to flash a kernel? Right now its stuck in apx mode. I cant get it to do anything.
Click to expand...
Click to collapse
Doesn't nvflash (easy flash) flash rogue recovery by default... have you installed naked drivers ? You can get into APX mode and then u r stuck ?
Sent from my Transformer TF101 using xda app-developers app
I dont think it does. Theres an option to flash cwm, rogue, and one by roach (the name is slipping my mind), none of them seem to work. The computer is registering as apx but the tablet says im in nvflash recovery.
jkieffer46 said:
I dont think it does. Theres an option to flash cwm, rogue, and one by roach (the name is slipping my mind), none of them seem to work. The computer is registering as apx but the tablet says im in nvflash recovery.
Click to expand...
Click to collapse
There is option right... as far as i remember, when yo flash stock using nvflash it removes root access... so you need to root and flash cwm again using nvflash right... so best option is removing root n going back to stock using easy flash.... boot it normally... let it settle and then root it again and install rogue recovery
That what I did when I had issues with my tablet...
Sent from my Trasformer TF101 using xda app-developers app
fixed!!!
ok got it. easyflasher 0.8.3b fixed it. whitekidneys has it working great now. the problem was getting easyflasher to finish the recovery kernel. something stopped or failed to transfer to the tablet while flashing the recovery. that means no recovery. that means i get stuck in apx mode. he updated it to 0.8.3b and it worked right away.
jkieffer46 said:
ok got it. easyflasher 0.8.3b fixed it. whitekidneys has it working great now. the problem was getting easyflasher to finish the recovery kernel. something stopped or failed to transfer to the tablet while flashing the recovery. that means no recovery. that means i get stuck in apx mode. he updated it to 0.8.3b and it worked right away.
Click to expand...
Click to collapse
Hey there,
I had exactly the same problem , I had a boot loop tried easyflasher and after that only apx worked.
Now I have tried the new version and it boots again but the bootloop remains...
Any idea what else I could try?
MadMaddin05 said:
Hey there,
I had exactly the same problem , I had a boot loop tried easyflasher and after that only apx worked.
Now I have tried the new version and it boots again but the bootloop remains...
Any idea what else I could try?
Click to expand...
Click to collapse
You flashed a recovery and reflashed the os? When you say new version you mean 0.8.3b right? Cause 0.8.3 doesnt work. You have the newest system update zip from the asus site in the asusupdate folder? When you say bootloop do you mean you can only get to your recovery or do you mean a real bootloop- it just keeps rebooting on the eee pad or asus screen?
jkieffer46 said:
You flashed a recovery and reflashed the os? When you say new version you mean 0.8.3b right? Cause 0.8.3 doesnt work. You have the newest system update zip from the asus site in the asusupdate folder? When you say bootloop do you mean you can only get to your recovery or do you mean a real bootloop- it just keeps rebooting on the eee pad or asus screen?
Click to expand...
Click to collapse
I used the option Flash stock/unbrick at first but this didn't help so i tried flashing a recovery and then reflash the os from my external sd card but this result in an error code 7.
Yes I used 0.8.3b ( at least the zip I downloaded says so, program itself says 0.8.3)
With bootloop I mean that I can access recovery/apx but if the system trys to boot it gets stuck at the "Asus Inpiring inovation..." screen.
And yes I copied the latest zip from the asus site to the update folder.
I also tired putting the DE_epaduser9_2_1_21UpdateLauncher.zip from the asus site because I'm from germany and thought it may help...
But none of that worked for me
Thank you for your reply btw.
MadMaddin05 said:
I used the option Flash stock/unbrick at first but this didn't help so i tried flashing a recovery and then reflash the os from my external sd card but this result in an error code 7.
Yes I used 0.8.3b ( at least the zip I downloaded says so, program itself says 0.8.3)
With bootloop I mean that I can access recovery/apx but if the system trys to boot it gets stuck at the "Asus Inpiring inovation..." screen.
And yes I copied the latest zip from the asus site to the update folder.
I also tired putting the DE_epaduser9_2_1_21UpdateLauncher.zip from the asus site because I'm from germany and thought it may help...
Kidneys
But none of that worked for me
Thank you for your reply btw.
Click to expand...
Click to collapse
Crap. Try all of the updates. If you can get to your recovery its definitely a problem with the os. Try othe other updates or get ahold of whitekidneys. He helped me. Or maybe youre having another issue he needs to address.
Hi, I'm attempting the root my asus transformer tf101.
I used RootToolkit from here: http://forum.xda-developers.com/showthread.php?t=1688447
To do so, everything went well, I now have root, the trouble is that I cannot reboot into recovery.
I tried adb reboot recovery but all it does is reboot the system.
Volume Up + Power button access APX mode.
I tried flashing recovery using EasyFlasher tool http://forum.xda-developers.com/showthread.php?t=1688012
And Rogue MX Touch revcovery, it claimed to have flashed it succesfully, but still I can't boot into the recovery, it boots
into the system...
No idea what can be done :/ any help would be greatly appreciated.
Thanks!
Never mind, managed to do it using a tool from the market
GoatHunter said:
Hi, I'm attempting the root my asus transformer tf101.
I used RootToolkit from here: http://forum.xda-developers.com/showthread.php?t=1688447
To do so, everything went well, I now have root, the trouble is that I cannot reboot into recovery.
I tried adb reboot recovery but all it does is reboot the system.
Volume Up + Power button access APX mode.
I tried flashing recovery using EasyFlasher tool http://forum.xda-developers.com/showthread.php?t=1688012
And Rogue MX Touch revcovery, it claimed to have flashed it succesfully, but still I can't boot into the recovery, it boots
into the system...
No idea what can be done :/ any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Hey, never mind, I've succesfully managed to boot into recovery using
Transformer Recovery reboot tool
https://play.google.com/store/apps/...recovery&rdid=com.transformer.recovery&rdot=1
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Wiltuz said:
So i got a new T F 300T yesterday and wanted to root it today.
I unlocked it and rooted it successfully. But then I tried installing a recovery. Installed CWM using fastboot. tried booting into it using RCK. It says booting into recovery mode and just reboots to OS. Installed CMW touch, same problem. Installed TRWP since i read that cmw has some problems.Now i used the 1 click root 1.1 to boot into recovery mode. The device now keeps rebooting. IT starts on the asus screen, then reboots again. So im stuck in a boot loop. When I press vlm dwn +power, it doesnt give me a menu anymore , instead it says that its rebooting into recovery mode and reboots again. Im freaking out right now, anyway to recover my device? Or is it 400 bucks down the dran? I dunno why this happened , since i am not new to flashing ROMs and stuff, and ususally test out new ROMs using my GNex. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Hi there, sucks to hear what happened..
I believe you haven't put in enough research, ASUS has a publicly available unlocker for the 300T, why did you use a 3rd party root app?
Can you still boot Android? If you have root and your recovery partition is broken, there should still be a way to overwrite the recovery partition.
If not, this basically looks like a brick, unless you can hook up a debugger during the boot process somehow.
Someone with in-depth knowledge of this device might be able to help you out further, I'm just theorycrafting here.. Best of luck!
I would try using fastboot to reflash stock firmware, which you can download from the Asus website.
You could also try getting into APX mode and using nvflash to reflash it.
Sent from my Transformer Pad TF300T using xda app-developers app
I had unlocked my TF700T and installed CM10, but it has never had the capability to reboot into recovery when enabled in the developer options -- selecting that when rebooting simply makes the ASUS logo come up several times, then it boots normal without going into recovery.
A related issue is when I download a CM10.1 update and tell it to upgrade, it reboots but doesn't install the new version from recovery.
I'm assuming something isn't unlocked or enabled somehow... but on the ASUS boot screen it does say "device is unlocked".
Nerva said:
I had unlocked my TF700T and installed CM10, but it has never had the capability to reboot into recovery when enabled in the developer options -- selecting that when rebooting simply makes the ASUS logo come up several times, then it boots normal without going into recovery.
A related issue is when I download a CM10.1 update and tell it to upgrade, it reboots but doesn't install the new version from recovery.
I'm assuming something isn't unlocked or enabled somehow... but on the ASUS boot screen it does say "device is unlocked".
Click to expand...
Click to collapse
I assume you can still access the recovery per the button-press method?
Yes, that's the only way I can access it.
Nerva said:
Yes, that's the only way I can access it.
Click to expand...
Click to collapse
The button press method is the proper way to flash anything. If you unlock you BETTER know how to flash in recovery. Also, GooManager will not flash firmware on the TF700, you must do it manually from recovery, thus why the upgrade is failing.
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Yes I certainly can and do flash all sorts of stuff from recovery -- first CM, now TWRP. But on my Epic 4G I just use CM Updater to download the latest ROM, then it asks me if I want to install, I say yes, and it reboots and installs it for me. But on my TF700T it isn't happening -- when I answer "yes" it just reboots without installing the new ROM.
Is it NORMAL with the TF700T to be unable to boot into recovery by using the power menu??
Is there something I don't have configured properly or didn't install something properly?
Nerva said:
Is it NORMAL with the TF700T to be unable to boot into recovery by using the power menu??
Click to expand...
Click to collapse
Yes (with the stock ROM).
Sorry, I should have been clear: I meant "with any version of CM?"
I use goo manager just to reboot into recovery, than flash manually. If I had to do the button boot recovery I wouldn't flash anything anymore.
Always sweaty hands when I see those three icons.
Sent from my HTC One X using xda app-developers app
Interesting. Rebooting to recovery with Goo Manager doesn't work for me either -- it just flashes the ASUS logo several times and then boots normally.
Seems like my recovery isn't setup properly -- any suggestions on how I can fix it?
Nerva said:
Interesting. Rebooting to recovery with Goo Manager doesn't work for me either -- it just flashes the ASUS logo several times and then boots normally.
Seems like my recovery isn't setup properly -- any suggestions on how I can fix it?
Click to expand...
Click to collapse
Sorry I can't help you fix it. But getting into recovery is as simple as typing this at the terminal if you have busybox installed or use the rebooter widget from ROM Toolbox or the market app. They all do the same thing.
Code:
reboot recovery
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Stravor said:
Hi. I had endless issues last night trying to install a nightly build of Cyanogenmod 10.2 on my Asus tf300t. Long story short, after the CM update from within android, the recovery mod (CWM) had trouble mounting the sd card. I then flashed the latest version of TWRP and tried to update the bootloader by installing the latest firmware from asus, at this point everything went well. Back to the updated bootloader, I tried to install the nightly CM and still got mounting problems so again, I tried switching between TWRP and CWM. Now, I'm suck. I cannot get passed the asus boot logo: after a few seconds, it falls back to the recovery mod (I may have wiped the newly installed system). At any point, holding power+vol-down has no effect, I cannot get into the bootloader menu and enable fastboot. Only thing I have left is access to CWM and access the device via ADB. Can anyone recommend me a course of action?
Also, I'm trying to get one thing straight: what is actually needed to install a recent version CM? There seems to be some intricate dependencies between the bootloader version you're using along with the version of the recovery mod and the CM / android you're about to install. (If anyone can clarify this for me, it would be really appreciated).
Any suggestion regarding any ways on how I could recover my device will be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
noahvt said:
READ BEFORE YOU START!!!!!!
CM10.2 is for the 4.2 BOOTLOADER AND CWM IS NOT WORKING WITH IT! you now have a bricked tablet! sorry :'(
Click to expand...
Click to collapse
"Bricked" seems to be oftenly abused around here. Having ADB access and being able to boot into CWM, isn't there anything I can do to enable fastboot, force a bootloader downgrade or something?
Thanks!
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
noahvt said:
This is the only thing I can do for you
http://forum.xda-developers.com/showthread.php?p=45120193
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Stravor said:
Moral of this story: "bricked" really is an abused word around here. For anyone in my situation, namely: stuck in a boot loop where power+volume down has no effect and thus is preventing access to fastboot, if you still have adb access, you can issue: adb reboot bootloader, it should at least allow you to access the bootloader again and from there, fastboot. The above linked post really was helpful. Thanks!
Click to expand...
Click to collapse
"ricked" may be abused, but I don't understand your situation very well, much less how you extricated yourself from it. If you're in a boot loop, you cannot complete the booting process (much like a tab with bootloader, recovery, but no OS installed). Without it, you have no access to ADB. Which in turn doesn't allow you to issue ADB commands. If additionally, you have no access to fastboot because volume down+power, and/or reset+volume down, does nothing (bootloader with icons absent), you cannot issue fastboot commands. Without the two, and the uselessness of APX mode, I'm not sure why that's not characteristic of a soft brick.
I have a mainboard that shows nothing but the initial Asus logo (not the one with boot animation, i.e., spinning dots) and "the device is unlocked." If I use either fastboot or ADB from PC, it returns with "waiting for device..." You were in the same boat, were you not? Looks like part of the firmware is still there (I assume if you replace the nand with a brand new, blank one, nothing would show up on display) , but the bootloader is messed up. If you'd succeeded in resurrecting your tab, then how do I rectify it, if you care to enlighten? Thank you in advance.