Well I was screwing around with my gtab, trying to put honeycomb on it, (I was on cyanogenmod) and I knew that I needed to put build 4349 on it. Unfortunately, I put that build on it, and installed my rom, but it didn't work. I decided to do the exact same thing over again, to see if it worked the second time. Halfway through the process, while restarting my gtablet, I had a serious problem. My gtablet will turn on after holding down the power button for about 30 seconds, but the screen is completely black and blank. Also, if I hit the (+) button, it says it will boot a recovery image, but it never does. If I hit the (-) to put it in APX mode for a NVflash, it simply turns off.
PLEASE, I have no idea what to do, because I really don't know what is going on with my tablet. I am just trying to put a honeycomb rom on it, but it seems I have completely screwed it up.
To put it straight: It won't go into APX mode
The screen is supposed to go black and blank when you start up in APX mode. Plug it into your computer and check to see if it is or not.
yea but supposedly it shows the viewsonic logo for a second. Mine when I hit the power button and hold the minus and just hit the power button are both the same. Also, I plug it in and nothing happens.
I tried holding the power for 15 seconds, nothing, if I hit the power for about 5 seconds it turns on that blank screen, if I hit + it says recovery key detected and booting recovery, but nothing happens after that
the black screen is the APX screen, it is blank and black.
You don't see an android symbol first.
my computer never says anything about a tablet without drivers or anything as stated in all guides
It's not unusual for the VS Birds splash screen to get lost during flashing operations that go bad. You also might not get a missing driver message for a number of reasons (especially if the driver isn't missing). So...
If the splash screen is missing, when you turn the tablet on while holding the volume down key the backlight should come on momentarily then the screen will go black. If that happens then you are in APX mode. If you have a linux box handy you can plug it into that and issue an "lsusb" command in a terminal window to verify that. There might be an equivalent for windows but I don't use it so I can't tell you what it would be.
If you are really having that much trouble with it I'd be happy to look at it for you if you cover shipping.
Related
Hello All!
My brother gave me his Asus Transformer TF101 to sell but it was heavily modified so I set about putting it back into factory state.
He had TWRP installed so I booted into that (recovery mode, volume down + power, etc.) and proceeded to do a restore. I selected the restore point and clicked "go." Everything seemed to work but now my TF never gets beyond the boot screen (the screen that says "ASUS, Inspiring Innovation..." and has the spinning circle). Obviously something went wrong with the restore and I can deal with that, however, I have a BIGGER PROBLEM now.
I cannot power down my TF. When I press and hold the power button it shuts down (the screen goes black) but then it starts right back up again. I have tried to hold the power button down for 3 seconds, 5 seconds, 10 seconds, 30 seconds, etc. but it always reboots.
Can someone please let me know how I can stop my TF from rebooting over and over again?
Thank you,
Jan
P.S. The main reason why I am needing to power down is I am trying to boot into APX mode so that I can use Easy Flasher.
try vol - and power more than 15secondes. Until you get 2 icons (1 for reset 1 for boot android)
tackyjan said:
P.S. The main reason why I am needing to power down is I am trying to boot into APX mode so that I can use Easy Flasher.
Click to expand...
Click to collapse
When the tf turns itself off just start holding volume-up, eventually the screen will stay blank and you are in APX mode, I've had this issue a few times, just hold volume up and it will eventually boot into apx.
Also try volup and power to hard reset then it will turn on again automatically, be sure to keep holding volume up, apx will eventually come on.
I got an HTC One S from a friend who got it from another friend. I don't have any history on the device. He gave it to me to fix because I'm the only Android user he knows and his phone won't start.
If I keep the power button pressed, the capacitive buttons flash exactly 15 times and occasionally the phone vibrates. I don't have a One S so not sure if that indicates that phone was started or shutdown.
Neither fastboot devices not adb devices shows the device. But every once in a while when it vibrates, if the phone is connected to the PC with a USB cable, it beeps - like it's connected. I don't see Android Phone in Device Manager. But I see a MTP USB Device with a yellow exclamation mark. Uninstalling and reinstalling HTC Drivers didn't fix the problem.
I have tried Power+Volume Down key. Shining a torch on it (seemed to work for a few people), keeping it plugged into the mains for 3 days, kept it in the freezer for 2-3 minutes (also seemed to work for one person).
I think when I first got the phone and plugged it into the mains, I saw a red charging light. But I may be mistaken. In any case, there is no light anymore indicating charging. But I don't think that's the problem.
I have no idea whether the device is bricked or not. And if there is any way to fix it. Samsung has Odin which makes any Samsung phone practically unbrickable. I haven't used any HTCs since the G1 so have not been in touch too much with the HTC development. But from reading, it seems that messing around with Romming with S-ON can cause the phone to be bricked. And perhaps that's what my friend or his friend did. Does this sound like that's what could have happened?
Thanks for any pointers.
I dont think the device is bricked. its just a little harder to press the power and volume down when you see the buttons flashing.
just check and do these steps.
connect the mobile to charger and see if the orange light comes and stays on
if the orange light is there, press the power button and keep your finger ready near the volume down button
you should keep the power button pressed and as soon as the orange light disappears you should press the volume down button until you end up in boot loader screen
give this a few tries and see if the device boots up in bootloader
ayyu3m said:
I dont think the device is bricked. its just a little harder to press the power and volume down when you see the buttons flashing.
just check and do these steps.
connect the mobile to charger and see if the orange light comes and stays on
if the orange light is there, press the power button and keep your finger ready near the volume down button
you should keep the power button pressed and as soon as the orange light disappears you should press the volume down button until you end up in boot loader screen
give this a few tries and see if the device boots up in bootloader
Click to expand...
Click to collapse
The problem is that I no longer see any light at all when I connect the phone to a charger. It's probably fully charged. Would that show a green light? If so, that's not visible either. I have a feeling that the bootloader has got wiped out or something.
I read in one post that the phone may be stuck in the QHUSB-DLOAD mode.
So I followed the steps in http://unlimited.io/qhsusbdload.htm. But that didn't help. I don't remember the exact statement since I was running an Ubuntu Live CD. But the gist was that it couldn't connect to the phone so presumably it's not stuck in QHUSB-DLOAD mode. Although the site states that it will NOT fix QHSUSB_DLOAD issues encountered by flashing ROMs - which may well be what may have happened.
I understand that running an RUU for the HTC One S may set it back to factory state. But for that I need fastboot to work.
So my sister-in-law has an Acer Iconia A1-810 tablet, somehow it crashed and she used "Power+volume up" to enter the bootloader and start a recovery, or maybe erase, I really don't know what she selected, but now all the tablet will do is turn on and go strait to a screen with the android with the spinning stomach and says "Erasing..." but it stays on this screen for hours and hours and does nothing.
I have a bit of experience with androids and lots of experience in software/hardware development but I can not get this thing to do anything. I have used the little paperclip shutdown hole to turn it off and then tried to get back in to the bootloader with "power + volume up" (tried volume down too, along with both volume buttons) and that wont work, still goes strait in to the "Erasing..." screen. I have tried with adb and fastboot to interupt the boot process and get it to do anything, it won't. When you do something with fastboot, it will say "waiting for device" so I restart the tablet, and when the tablet first starts to boot, during the Acer logo screen, fastboots cursur stops blinking but won't go any further.
As far as I can tell, nothing I do will get me to the bootloader again, now it just goes to the "Erasing..." screen everytime and ignores everything else you try to do. Is there anything that can be done? Or is this thing just a paperweight now? I'm about ready to start pulling this thing apart and seeing if I can do anything at the hardware level....
So my sister-in-law has an Acer Iconia A1-810 tablet, somehow it crashed and she used "Power+volume up" to enter the bootloader and start a recovery, or maybe erase, I really don't know what she selected, but now all the tablet will do is turn on and go strait to a screen with the android with the spinning stomach and says "Erasing..." but it stays on this screen for hours and hours and does nothing.
I have a bit of experience with androids and lots of experience in software/hardware development but I can not get this thing to do anything. I have used the little paperclip shutdown hole to turn it off and then tried to get back in to the bootloader with "power + volume up" (tried volume down too, along with both volume buttons) and that wont work, still goes strait in to the "Erasing..." screen. I have tried with adb and fastboot to interupt the boot process and get it to do anything, it won't. When you do something with fastboot, it will say "waiting for device" so I restart the tablet, and when the tablet first starts to boot, during the Acer logo screen, fastboots cursur stops blinking but won't go any further.
As far as I can tell, nothing I do will get me to the bootloader again, now it just goes to the "Erasing..." screen everytime and ignores everything else you try to do. Is there anything that can be done? Or is this thing just a paperweight now? I'm about ready to start pulling this thing apart and seeing if I can do anything at the hardware level....
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
yellownese said:
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
Click to expand...
Click to collapse
Which OOS build are you on? And your device is unlocked or not?
Getting into EDL mode is tricky. Power off device completely. With the device powered off, hold down volume up and volume up at the same time, keep them pressed all the time, and during that time plug into PC (phone all the time powered off). Still hold both of the buttons. By the time you plug into PC, you should be in EDL mode, BUT it only lasts about 10 seconds. I mean you have to click start in this 10 seconds time bracket, other way phone exits EDL itself. After you click start, you can release button, obviously