So as the title says, my Asus tf300t is stuck on the splash screen (I believe that is the right term, the screen where it says "devices is UnLocked). I have seen a lot of other posts that say this happens if you are in the bootloader and choose the wipe data option, however this is not what I did. I had my tablet flashed with a custom BAKED rom (though I dont remember exactly what it was called, I could probably find it again though) and I wanted to get to the recovery (I have CWM installed). I held down the power button and clicked reboot, and then chose the recovery option. That's all I did. When it rebooted, it stayed on the splash screen. I have tried to no avail to enter bootloader by holding down power and volume down, and that does not work. I have tried to let it die and then restart it, but that also seems to not work. The only thing that I can seem to do is get into APX mode. I know that if I had NvFlash I could "unbrick" my tablet, but I unfortunately didn't know about it until this happened. Is there any hope for my tablet? I have read that replacing the motherboard will solve this, but I'm hoping to avoid that if possible.
Also, I haven't been able to find this anywhere, but I'm curious as to what exactly APX mode is?
Many Thanks.
Flash twrp through fastboot
Sent from my SCH-I535 using Tapatalk 2
tylerlawhon said:
Flash twrp through fastboot
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
So, I'm confused at your short answer. See, I'm not sure how I can flash anything because I can't get it to connect either fastboot or adb. Should it be connect fastboot at the splash screen? or with apx? Is it possible to flash twrp through apx?
Also, why twrp? Is it just a preference, or is it more suited than cwm in this case?
Any more clarification would be very helpful.
Cmhulbert said:
So, I'm confused at your short answer. See, I'm not sure how I can flash anything because I can't get it to connect either fastboot or adb. Should it be connect fastboot at the splash screen? or with apx? Is it possible to flash twrp through apx?
Also, why twrp? Is it just a preference, or is it more suited than cwm in this case?
Any more clarification would be very helpful.
Click to expand...
Click to collapse
Well, I personally haven't had issues with twrp. Also, you have to reboot to bootloader and select fastboot if you're on the 4.1 firmware. Otherwise if you're on 4.2, it should start on its own.
Have you setup fastboot and adb on your computer correctly?
Sent from my SCH-I535 using Tapatalk 2
tylerlawhon said:
Well, I personally haven't had issues with twrp. Also, you have to reboot to bootloader and select fastboot if you're on the 4.1 firmware. Otherwise if you're on 4.2, it should start on its own.
Have you setup fastboot and adb on your computer correctly?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I think one of us is confused. I'm not sure that I understand you correctly. You see, I cant get into the bootloader. Whenever I try to restart my tablet into the bootloader it just stays on the screen that says "ASUS" and in the top left corner it says "This devices is unlocked". As far as I can tell, from this screen it is not possible to connect either adb or fastboot.
Cmhulbert said:
I think one of us is confused. I'm not sure that I understand you correctly. You see, I cant get into the bootloader. Whenever I try to restart my tablet into the bootloader it just stays on the screen that says "ASUS" and in the top left corner it says "This devices is unlocked". As far as I can tell, from this screen it is not possible to connect either adb or fastboot.
Click to expand...
Click to collapse
If you Power + Vol.Down for some seconds what can you read after "Device is unlocked"?
On which bootloader are you?
ale.spinelli said:
If you Power + Vol.Down for some seconds what can you read after "Device is unlocked"?
On which bootloader are you?
Click to expand...
Click to collapse
This is the problem, nothing shows up if I do that. I have done it before, many times, and I know what to look for as far as manually bootloading goes, and nothing shows up. It stays on the "device is unlocked" screen.
As for the bootloader, I'm not sure exactly how to tell which one it is, but it had four option I believe.
Related
As the title states I follow the directions to get into the stock recovery ans I dont have that option. Only have NVFlash, RSD and fastboot.
Any Ideas?
James
what are you trying to do in recovery?
There isn't any recovery for now I don't think.
To flash the overclock/root images you just use fastboot
I am very familiar with android. I am referring to the stock recovery. Since I have not gotten an update yet I am not sure how moto works but most updates run thru the stock android recovery however I don't even have the stock recovery and I sure as heck don't want to exchange it because of the large amount of customizations I have done. I know I can OEM unlock and drop the stock recovery on there but with no course of action to relock it makes no sense.
James
There is a recovery, but it doesn't show up in the boot menu for some reason.
With ADB, you can to an "adb reboot recovery" and it will boot into recovery, so it's definitely there.
-Jim
But in order to adb reboot recovery on needs su access unless the xoom is different than everything other device. And I am not interested in rooting until moto releases the stock images.
James
interesting.. one can adb reboot recovery non rooted. Granted it just gives you the stock flashing screen for android but atleast I know its there. Motorola must have made some changes
Thanks.
James
cj10488 said:
interesting.. one can adb reboot recovery non rooted. Granted it just gives you the stock flashing screen for android but atleast I know its there. Motorola must have made some changes
Thanks.
James
Click to expand...
Click to collapse
Did you find a way to standard recovery menu. I spend 1 hour speaking with Moto support. They told me that I need to send back my XOOM WiFi tablet, because something wrong. I'm sure I'm not wrong in pressing that bloody buttons, it's just wrong manual and support also don't know how to access to standard recovery on WiFi version.
When you adb into recovery hit Power and Volume up. Your menu is there.
stevenege said:
When you adb into recovery hit Power and Volume up. Your menu is there.
Click to expand...
Click to collapse
No, I'm trying to access to recovery menu without PC. My PC has problems with USB, so it didn't recognize XOOM (I checked it on the another pc, so I'm sure that only that bloody Dell D620 and corporate security programs doesn't regonize XOOM)
So I need to get access from tablet with locked bootloader and without root access. According to the troubleshooting manual I need to press volume down button, as soon as Motorola logo appears, but I made all that things several hundreds times and nothing. I could see only fastboot, RSD or NvFlash, bug no Recovery.
Also as I found owners of 3G version, doesn't have such problems, looks like only WiFi version had such problems.
If somebody who has WiFi version could make video how to get access to Recovery menu from device without PC, it could help really.
Kozdoba said:
If somebody who has WiFi version could make video how to get access to Recovery menu from device without PC, it could help really.
Click to expand...
Click to collapse
I don't think you can. I certainly couldn't find a way. The only way I could enter recovery was via adb. That said, adb doesn't require root. You just have to make sure "USB debugging" is turned on under settings->applications->development.
-Jim
Sent from my Xoom using Tapatalk
BeagleBoy said:
I don't think you can. I certainly couldn't find a way. The only way I could enter recovery was via adb. That said, adb doesn't require root. You just have to make sure "USB debugging" is turned on under settings->applications->development.
-Jim
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
The most strange that Motorola support sure that we could do it via buttons. I spend 2 hours with Level 2 specialist trying how to do it. After that they advice me to send it back, because something wrong with my XOOM.
if you push the vol down button when its in the moto logo and you get the "starting fastboot protocol support" message that means you pushed the vol down button too early
reboot then wait a little longer than before then push vol down(make sure your on the moto logo) you should get "android recovery text" when that comes up press and hold vol up
when recovery loads up press down the power key then let go of vol up and you should see the options
i dont remember what the options are since i dont have the stock recovery anymore but im sure its the same as any other stock android recovery
Use an app called Wireless ADB, it has helped me out in situations like this.
PaulG1488 said:
if you push the vol down button when its in the moto logo and you get the "starting fastboot protocol support" message that means you pushed the vol down button too early
reboot then wait a little longer than before then push vol down(make sure your on the moto logo) you should get "android recovery text" when that comes up press and hold vol up
when recovery loads up press down the power key then let go of vol up and you should see the options
i dont remember what the options are since i dont have the stock recovery anymore but im sure its the same as any other stock android recovery
Click to expand...
Click to collapse
I tried to do it several time, but always I see only "starting fastboot protocol support"
Do you have WiFi version of the tablet, because it looks like this problem only with it. 3G version doesn't have such problems(
Guys who has WiFi version of the tablet please make video how you did it. I already comes to Level 3 specialist at Motorola support, because the rest specialist couldn't find Recovery menu of WiFi version.))))
ateld said:
Use an app called Wireless ADB, it has helped me out in situations like this.
Click to expand...
Click to collapse
Yes I know, but I would like to know how to get access to that menu without PC at all. I bought XOOM tablet to leave my PC at home during my business trip, so I would like to be sure that everything ok with my XOOM tablet. Right now I don't see any proof that I could access to Recovery menu without ABD
PaulG1488 said:
reboot then wait a little longer than before then push vol down(make sure your on the moto logo) you should get "android recovery text" when that comes up press and hold vol up
Click to expand...
Click to collapse
This doesn't work for wifi. You get the choice of nvflash, rsd and fastboot, but not recovery.
Sent from my Xoom using Tapatalk
BeagleBoy said:
This doesn't work for wifi. You get the choice of nvflash, rsd and fastboot, but not recovery.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Welp, that sucks. I hope the UMTS Xoom is better.
i was trying to do a factory reset on my TF700, and it was rooted.. but it froze during the reset, now when i try to turn it on it says "device is unlocked" and shows the asus and tegra logos, but stays there, if i hold volume down when i hole the power button it says "booting recovery kernel image" and freezes... i have no selection that i can select between here.... and lastly if i hold volume up, im able to detect APX through my computer and have the proper driver installed, but i dont know where to go here
so is it bricked? what do i do now?
jason41987 said:
i was trying to do a factory reset on my TF700, and it was rooted.. but it froze during the reset, now when i try to turn it on it says "device is unlocked" and shows the asus and tegra logos, but stays there, if i hold volume down when i hole the power button it says "booting recovery kernel image" and freezes... i have no selection that i can select between here.... and lastly if i hold volume up, im able to detect APX through my computer and have the proper driver installed, but i dont know where to go here
so is it bricked? what do i do now?
Click to expand...
Click to collapse
Can your pc see it through fastboot mode? connect your pc to your device, then hold down volume down and power button, when see white text let go both buttons, hit volume down to switch to the USB icon, then hit volume up button twice. On your computer, open command prompt (cmd) go to the directory where fastboot.exe is installed and type :
fastboot -i 0x0B05 reboot
hit enter, is your computer reboot??
buhohitr said:
Can your pc see it through fastboot mode? connect your pc to your device, then hold down volume down and power button, when see white text let go both buttons, hit volume down to switch to the USB icon, then hit volume up button twice. On your computer, open command prompt (cmd) go to the directory where fastboot.exe is installed and type :
fastboot -i 0x0B05 reboot
hit enter, is your computer reboot??
Click to expand...
Click to collapse
as i said, when i hold volume and power i get no option to select anything, the white text just says "booting recovery kernal image".. no option to select USB or fastboot
jason41987 said:
as i said, when i hold volume and power i get no option to select anything, the white text just says "booting recovery kernal image".. no option to select USB or fastboot
Click to expand...
Click to collapse
Then not much you can do but to send out for repair, you could try to keep it off for awhile and try again, hopefully it can boot into recovery, but very slim at this point.
Just for the hell of it, hit the reset button too, maybe magic will come!
buhohitr said:
Then not much you can do but to send out for repair, you could try to keep it off for awhile and try again, hopefully it can boot into recovery, but very slim at this point.
Just for the hell of it, hit the reset button too, maybe magic will come!
Click to expand...
Click to collapse
ive tried the reset button too.... will asus repair it even though its been rooted?
jason41987 said:
ive tried the reset button too.... will asus repair it even though its been rooted?
Click to expand...
Click to collapse
Being rooted is not a problem. Being unlocked might be a problem.
jason41987 said:
ive tried the reset button too.... will asus repair it even though its been rooted?
Click to expand...
Click to collapse
MartyHulskemper is correct, you should be ok. You should exchange with the company you purchase it from if within 30 days.
buhohitr said:
MartyHulskemper is correct, you should be ok. You should exchange with the company you purchase it from if within 30 days.
Click to expand...
Click to collapse
aah, it was unlocked too
jason41987 said:
aah, it was unlocked too
Click to expand...
Click to collapse
Just return it and play dumb. Worst case you have to pay for your repair.
buhohitr said:
Just return it and play dumb. Worst case you have to pay for your repair.
Click to expand...
Click to collapse
what do you think such a repair would cost? not needing anything hardware fixed?
jason41987 said:
what do you think such a repair would cost? not needing anything hardware fixed?
Click to expand...
Click to collapse
I your case I think they just need to reflash the bootloader should cost around $100. If mainboard or screen range from 250-350 (shipping, parts and labor). Can you just exchange from where you purchased?
buhohitr said:
I your case I think they just need to reflash the bootloader should cost around $100. If mainboard or screen range from 250-350 (shipping, parts and labor). Can you just exchange from where you purchased?
Click to expand...
Click to collapse
i wouldnt want to exchange it.. wouldnt trust someone else with the data, and also, im partial to this one now.. kind of sentimental
according to other brick cases, bricked devices due to bootloaders need their motherboard replaced. after repairs you will not be able to unlock it again.
tweeklulz said:
according to other brick cases, bricked devices due to bootloaders need their motherboard replaced. after repairs you will not be able to unlock it again.
Click to expand...
Click to collapse
that sounds absolutely rediculous for a bootloader error, and unable to ever be unlocked again?.. thats insane that they would do that, but i heard about it before.. this all happened because of a faulty backup image to begin with, that froze my damn tablet while reverting to factory settings... makes me so angry that this is their policy....
so has anyone else had this issue before? and what did it cost?
jason41987 said:
that sounds absolutely rediculous for a bootloader error, and unable to ever be unlocked again?.. thats insane that they would do that, but i heard about it before.. this all happened because of a faulty backup image to begin with, that froze my damn tablet while reverting to factory settings... makes me so angry that this is their policy....
so has anyone else had this issue before? and what did it cost?
Click to expand...
Click to collapse
is it possible to fix this myself? i am able to get an apx connection with my computer... if o hold power and press volume down it attempts to load a backup image which im guessing was corrupted in the first place... not sure the bootloader is really the issue?
anyone?
If you don't have nvflash backup(for use with APX mode), and you can't get to recovery. You pretty much done.
Sent from my ASUS Transformer Pad TF700T using xda premium
nvflash backup had to have been installed on the tablet prior to this happening?.. or do i use nvflash to install a backup, and if so, couldnt i get a vanilla backup image somewhere?
jason41987 said:
nvflash backup had to have been installed on the tablet prior to this happening?.. or do i use nvflash to install a backup, and if so, couldnt i get a vanilla backup image somewhere?
Click to expand...
Click to collapse
Well obviousely you don't have nvflash backup. You only can make a backup of nvflash if you have build version .26, once you updated, there is NO WAY you can make nvflash backup. The problem is there is no way we can communicate with your device to dump any image since the recovery is gone (corrupted). You need this recovery so you can push or load file/image etc.. from your sdcard or from your PC. All you can do now is keep playing with it and hope for miracle for some how you can get back in recovery mode.
well this is exactly what comes up when i hold power and volume down... im not sure if this means much to anyone
also, it speaks of checking for an android ota recovery, however it cannot find one... where is an ota recovery image located? im assuming somewhere over the internet?... or is it on a removable SD card?
the device is unlocked.
Android cardhy-user bootloader <2.10 e> released by "US_epad-9.4.5.30-20120907" A03
checking for android ota recovery
Booting recovery kernel image
I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?
tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.
tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo
bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.
bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.
bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.
WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help
jerimynal wiley said:
WHats up guys? My tf300 is still bricked after like 6 months. It started with me flashing the wrong recovery image then a wipe data finished it off. I can get into apx mode and device manager sees it as an apx device with a yellow triangle, or as several different names according to which driver i use. I have tried all the asus ones, the adb, the composite adb, all the ones from the naked driver set. No matter which ones i use fastboot devices returns nothing and adb devices says "list of devices attatched but nothing. Is there something wrong with the way im using fastboot? I just go to the fastboot folder and open a cmd window and it starts like C:\user\fastboot or whatever and im stuck there please help
Click to expand...
Click to collapse
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.
graphdarnell said:
Questions: what rom did you have before? Did you wipe data from the Asus menu, and not from inside a custom recovery? When you now try to get into fastboot by holding volume down + power, what happens? No matter what, try Buster99's solution. If the only mode you can get into is APX, and you didn't generate NVflash files, then I'm afraid your motherboard is stuck, the only solution to which is replacing it.
Click to expand...
Click to collapse
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager
jerimynal wiley said:
i came from stock jb rom and i flashed an ics cwm recovery img i got into the bootloader screen but it wouldnt go into recovery so for some stupid reason i did a wipe from there, from the asus menu. volume down and power just shuts the screen off for a few seconds then straight back to the asus screen volume up and power will apx mode. the driver i had got from asus pulled up transformer prime apx interface in device manager
Click to expand...
Click to collapse
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.
graphdarnell said:
Must've been the wrong recovery that screwed up your tab. In my experience, wiping data from the Asus menu while you're on stock rom is not supposed to brick it as described by you. Try this method. It has saved quite a few semi-dead tabs. Good luck, and give thanks to the author if it helps.
Click to expand...
Click to collapse
im sure it was the wrong recovery i dont know why i did it. i had another ics tablet and for some reasone i put both recovery images in the same folder the link u provided is one that i had previously read. I cant even get fastboot to "see" the tablet.
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
netboy3 said:
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
Click to expand...
Click to collapse
That's exactly why we leave fastboot off in the settings
Maybe I don't understand the question. Could you not just use:
adb reboot bootloader
or
adb reboot recovery
cntryby429 said:
Maybe I don't understand the question. Could you not just use:
adb reboot bootloader
or
adb reboot recovery
Click to expand...
Click to collapse
You can only use those if adbd is running which means you either were successful in booting into recovery (and you can't do it as power+vol_down doesn't work), or you have a working ROM (see the OP).
xRogerxC said:
That's exactly why we leave fastboot off in the settings
Click to expand...
Click to collapse
I wish it was that simple. The ability to get to the menu seems to be related to the bootloader's ability to access /data. If the bootloader can't get to /data it looks to defaulting to NOT showing the hboot menu. I've noticed this on my phone. I have my phone encrypted which doesn't allow access to /data until you decrypt it. If you cancel out of the decrypt prompt then reboot the phone, you will not be able to power+vol_down (though I never changed the fastboot setting).
netboy3 said:
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
Click to expand...
Click to collapse
If you are rooted you can use the app quick boot to reboot to hboot without having to do the shutdown but.
Sent from my HTC6525LVW using Tapatalk
dottat said:
If you are rooted you can use the app quick boot to reboot to hboot without having to do the shutdown but.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
See the OP. Assuming your ROM is messed up and is not booting (happens a lot when your'e a flashoholic), you can't run any apps or even get to adb. I've never seen a phone that will not allow you to always be able to cold-boot into the bootloader. This is a serious problem for folks that plan to experiment with lots of ROM flashing.
netboy3 said:
See the OP. Assuming your ROM is messed up and is not booting (happens a lot when your'e a flashoholic), you can't run any apps or even get to adb. I've never seen a phone that will not allow you to always be able to cold-boot into the bootloader. This is a serious problem for folks that plan to experiment with lots of ROM flashing.
Click to expand...
Click to collapse
In that case you hold power and volume buttons until the phone tells you it's going to restart or vibrates or you see the screen flash. Depending on what mode you are in it will do different things. At this point you can release power and move to only volume down.
If timed correctly you will land in hboot. Practice makes perfect.
Sent from my HTC6525LVW using Tapatalk
dottat said:
In that case you hold power and volume buttons until the phone tells you it's going to restart or vibrates or you see the screen flash. Depending on what mode you are in it will do different things. At this point you can release power and move to only volume down.
If timed correctly you will land in hboot. Practice makes perfect.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
dottat, thank you for your post. You are correct. This requires quite a bit of proper timing to succeed. To recap: In case you are in fast-boot power mode and/or have your phone encrypted and power+vol_down doesn't get you into hboot:
1. Power down the phone.
2. Hold volume_up and power.
3. Keep holding the above, you should see the animated HTC splash show up.
4. Keep holding the above, the screen will go dark.
5. Once the screen goes dark, quickly release power and volume_up and press volume_down.
6. If timed perfectly, you should land in hboot menu.
Thanks again to dottat for pointing it out.