HP Slate 21 Autopoweron - Android Q&A, Help & Troubleshooting

I want to be able to have the Slate 21 tablet boot up automatically (if it's shut off) when power is plugged in.
i have tried to use the command that works on Nexus7, but no success:
reboot bootloader
fastboot oem-off-mode charge 0
Any idea what to do?
Thanks,

Related

Help, Tablet will not turn on AT ALL (NO APX or Anything!)

I am having problems , my tablet will not turn on AT ALL into APX, CWM, or Regular mode.... It simply does nothing.
I have searched and read people flash NVFLASH again to get it to boot up, however I cannot do this as my computer cannot read it (It is not turned on in APX mode) So is it totally bricked now?
I've held the button down for 15+ seconds both volume + and - with power , I've tried re-plugging in USB to see if maybe the computer can read it (while AC cord is plugged in) The tablet has juice, it just will not turn on.
(This is after having bootloop issues)
Do you have nvflash installed?
Have you read this thread?
http://forum.xda-developers.com/showthread.php?t=1038689
Yes I read that thread, it does not help... When I plug the tablet into the computer, my computer cannot read it as it as the tablet is not in APX mode. When I try to turn the tablet on in APX mode nothing happens.
I also did the recovery as listed by http://forum.xda-developers.com/showthread.php?t=861950 "[STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions)" when I was having bootloop issuses, It returned the tablet back to the original stock boot sequence however it was still boot looping. Now the issue is it wont boot at all, it wont turn on whatsoever.
I read that other people were having an issue similar to where they thought it wasn't on, and they managed to plug it into there compuer VIA usb and force NVFLASH there tablet to work again, however I cannot do this as my computer will not recognize the device is plugged in without the tablet being in APX mode
try on another pc
n21klin said:
try on another pc
Click to expand...
Click to collapse
+1 you should Try another PC answer if it is an error with your PC. Have you had it plugged into USB while trying to power cycle with power & volume - ?
Yes I have tried it plugged into USB while trying to turn it on
if you nvflashed it to stock then you may be experiencing the original bug. Unplug it from any power source and let it sit for 2 days then plug it back in and try and power it up. There is a bug in the original software that would lock the tab until the battery was completely drained. Or you can take it apart and hit the reset button or pull the battery
Is there any tips for removing the back cover?
Any other suggestions??
Let it sit for 2 days is a good test too. This did happen with stock a lot.
FIXED IT!!! Took apart the G-Tablet and unplugged the battery and pushed the reset button a few times,
Loaded into clockworkmod and repartitioned 2048 and 0, WORKED!!!!
THANK YOU BABY JESUS
that would be "thank you thebadfrog"

[Q] Gtab not booting :S SOLVED

I just got my gtablet, I had bought it used and it came with a ics rom, I had had it boot and reboot no problem, then I wanted to update the rom (as it had downloaded an update), so I had rebooted the tablet but I had accidentally booted into apx mode instead of the cwm mode and I haven't been able to find a way to exit. I have tried holding down the power button, but it doesn't seem to want to turn off. I tried hooking it to my computer where it asked for the apx driver so I thought I would just need to install that, I went home so I could try to run the procedure, and now it doesn't ask for a driver, pressing the power button does nothing, I have tried plugging it in to charge, and trying to go into apx mode or any mode for that matter and I got nothing, the screen remains black and I don't see a backlight... please don't tell me I bricked it....
I'm pretty sure it's turned on as if I plug in my thumbdrive the light blinks for a split second......
Update: Is definitely powered on, my light up game controller is lighting up if plugged in.
any ideas? Right now I'm trying the code triple red procedure.
... the battery in this thing is just freaking amazing.... I've charged my phone twice, had a light up controller plugged in for several hours and my ipod and it is still running....
thanks for any help you can give me
Yup the triple red plan worked the tablet is now working.... got stuck in the actual recovery (the one if you hold plus) while trying to power down so It's a portable charger again ... if anyone knows how to get it to power off properly in recovery let me know
Brainy142 said:
if anyone knows how to get it to power off properly in recovery let me know
Click to expand...
Click to collapse
Run these commands via ADB:
Code:
C:\SOME\PATH> [B]adb shell sync[/B] [I]Sync filesystems[/I]
[I]Then[/I]
C:\SOME\PATH> [B]adb shell reboot -p[/B] [I]Power off tablet[/I]
[I]Or[/I]
C:\SOME\PATH> [B]adb shell reboot[/B] [I]Reboot tablet[/I]
Thanks, I got stuck in recovery last time, so hopefully I'l be able to ADB the command to reboot next time .

[Q] HELP!! E: Can't read MISC: (No space left on device)

*Droid Htc Eris
HBOOT: 1. 49. 0000
RADIO: 2. 42. 01. 04. 27
-After doing a hard reset (volume down +send+End button)] i can NO LONGER boot into the hboot menu (shouldn't have done that) :-(
*Boot status after pressing the power button:
-phone comes to the white start screen with the 3 skateboard droids along the center of the screen, then goes straight into recovery:
----------------------------
ClockworkMod Recovery v 2.5.0.1
*reboot system now
*apply sdcard:update.zip
*wipe data/factort reset
*wipe cache partition
*install zip from sdcard
*nandroid
*partitions menu
*advanced
ClockworkMod Recovery v 2.5.0.1
E: Can't read MISC:
(No space left on device)
E: Can't read MISC:
(No space left on device)
E: Can't read MISC:
(No space left on device)
---------------------------
-Im able to put stuff on my sdcard via the -mount USB storage sub- menu under the *partitions menu. I did a status report using one of the zips i found on a thread (cant remember which one).
----------------------------------------------------------------------------
Eris MTD Partition Status Report Generated
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 5 5 30 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 20 20 0 0 0
system /dev/mtd/mtd3 178257920 1354 1360 0 0 0
cache /dev/mtd/mtd4 136314880 37 1040 74 0 0
userdata /dev/mtd/mtd5 167247872 745 1276 172 0 0
----------------------------------------------------------------------------
-Has anyone figured out how to fix this error?
ClockworkMod Recovery (as the default recovery image) and the Eris are a disaster waiting to happen. Almost every stuck Eris like this happens from Clockwork, while you never read it happening from Amon_RA recovery.
If you can flash something, I guess you may as well flash ErisMTDNuke_v0.9.zip and hope that clears the errors in the partitions.
See this post: http://forum.xda-developers.com/showpost.php?p=23034380&postcount=3
While this gives an overview of how to use the new unlockable 1.51.0000 bootloader to get the 1.49.2000 S-OFF bootloader on, it shows the steps as well to flash ErisMTDNuke. After you flash that, hopefully it will leave the phone in a state where you can get a working HBOOT and - more importantly - Amon_RA recovery.
I just walked somebody through the process in a bit more detailed steps a few days ago (including adding the flash of Flashback21_v2 in order to get the radio flashed back to the current version; flashing the old root PB00IMG.zip flashes an old radio). It starts with this post: http://androidforums.com/htc-droid-eris/556826-stuck-boot-up-screen.html#post4475687
But, in your case, since you cannot start in HBOOT, you'll have to try starting with ErisMTDNuke. Then flash ErisMiscReset_v0.9.zip (and hope that works) and then try flashing the root PB00IMG.zip file (renamed as PB00IMG.zip). From there you should be able to start HBOOT, put the phone in fastboot, flash Amon_RA recovery, and then you should be able to get the phone back in order.
(By the way, you start in HBOOT by holding only VolDn - you don't need to hold send as well.)
hi doogald, Thank you for replying. I will read and try this on the phone as soon as i get home from work.
Okay so i was able to flash both ErisMTDNuke and ErisMiscReset_v0.9.zip and both flashed without error, but for some reason when i went to flash the PB00IMG.zip, it was not showing up in my storage card even though i could see it every time i mounted back to my laptop. I'm not sure why it wouldn't come up in my sd card? Anyway i think i screwed up.... i was being distracted and pulled out the battery, so when i tried to turn the phone back on, it went straight to the 3 droid skateboarders. No more clockword mod recovery. I tried the vol down + Send + end and this brought up fastboot USB in the top left corner of the 3 droid scateborders screen. I figured i'd try to use an RUU to see if i could flash using that, but there was a bootloader driver problem. I searched around and found drivers for it. I then tried the RUU but it gave me the 170 error about the USB not being connected. So i did another battery pull cos i read its not good to leave the phone on in fastboot because it kills the battery. I put the battery back in and put the phone in the charger. I didnt get the orange charge light, so i tried turning it back on, no use... it wouldnt turn on Now im stuck.. have no idea what to do?
PB00IMG.zip does not get flashed from recovery - it is processed by HBOOT. As I said, you get into HBOOT by holding VolDn while starting the phone, not holding VolDn and Send.
Erisuser1 posted an illustrated guide to PB00IMG.zip updating here: http://androidforums.com/eris-all-things-root/75384-visual-example-pb00img-zip-update-method.html
You can try to leave the phone plugged in to a charger overnight (not to a PC but to a wall charger) and see if it will charge. Don't try to turn it on while charging - just let it sit for several hours. There is an external charger that Seidio Online makes and Amazon sells, so you can charge the battery outside the phone.
http://www.amazon.com/Seidio-Multi-Function-Battery-Charger-Incredible/dp/B003N1915S
Ressurection: Phone has come back to life, it has power again!!!
doogald said:
PB00IMG.zip does not get flashed from recovery - it is processed by HBOOT. As I said, you get into HBOOT by holding VolDn while starting the phone, not holding VolDn and Send.
Click to expand...
Click to collapse
I did a battery pull, and pressed the power button for about 5 sec to discharge the motherboard of the phone. I replaced the battery and pushed the power button again. The phone vibrated and went straight to the skateboard droids screen. I was semi relieved in a way
Doogald, i tried the volume down and End button to get into HBOOT, but it doesn't work. It just goes to the blank screen with the 3 droid skateboarders.
I can't really use the link you gave me because i'm not able to get into HBOOT. Is there another way to do this? BTW..Thank you for helping me!
I think that the only thing that you can try is to get the RUU for the new 1.51.0000 unlockable bootloader and try installing that.
You get it from here: http://www.htcdev.com/bootloader
Register for an address at the top, select "Droid Eris" from the dropdown, click "Begin unlock bootloader", answer the questions in the popup, and then you can download an RUU that will hopefully get you the 1.51.0000 unlockable bootloader.
I downloaded the RUU, i also downloaded HTC sync but my device is not being picked up. Is there any way to fix this, i think if i can just get my phone recognized by my computer, i should be able to run the RUU.
Try a different cable. However, it's quite possible that if the phone cannot get into HBOOT, it cannot be accessed by the PC. If that's the case, sorry to say that I think the phone is a brick.
Do you think this is a driver issue? is there some way i can connect to the phone using the fastboot command in sdk ? It does show the "fastboot USB" in the top left corner, though it shows that even when i disconnect the cable from the computer.
Is there anyone out there with this problem? Im not ready to give up.
If anyone is still stuck with an Eris that is bricked, i suggest you look into "JTAG" check out ebay for people that offer the service. They will do it for you for about $30 -$40. It fixes the fastboot and Hboot. You can load whatever firmware you want to after.
MY HTC ERIS LIVES ON !!! WOOOOHOOOOO

Went to change battery and now TF201 boots straight to TEAMWIN

So I have already unlocked and installed "[Guide/tutorial] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat" using the thread and have been very happy.
I ordered a new battery and after putting in I noticed the touch screen wasn't well...ok I didn't get the ribbon cable in correctly no biggy.
I opened back up and indeed the cable wasn't in properly. I reinserted and put back together. I pressed the power button and the transformer would power cycle. I pressed the power and + button and got to the TEAMWIN screen and that has where it has remained.
No matter what i do with the power and volume I can't get to any other screen.
I did do this:
4 - PREVENT BRICK : NVFlash
This step is optional but highly highly highly recommended, your tab will never be bricked after it !!!.
I have read other threads about the getting stuck on the splash screen but they all say to plug into computer, connect to tablet and power cycle and Start your device in APX mode [Power On + Volume Up]. But i can't get to the selection page at boot-up.
Any ideas? I thought maybe I disconnected a cable when I opened back up but i have since opened back up looking for any ribbon that came out.
I am going to try this.....https://forum.xda-developers.com/showthread.php?t=1927818
used this to get in APX mode:
https://forum.xda-developers.com/showthread.php?t=2034866
and after trying https://forum.xda-developers.com/showthread.php?t=1927818 multiple times I could get the "nvflash.exe -r --go" to work so I tried "If you device does not reboot after you see the text, force a reboot (long press the Power button)" also no go. I did learn that every time I ran a blob and the Tab rebooted I would have to rerun "wheelie --blob blob.bin" to get back into nvflash mode.
I tried a new tactic and used this thread, https://forum.xda-developers.com/showthread.php?t=2538028, and even though it was for a TF700 I used substituted my files from, 4 - PREVENT BRICK at this thread, https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237.
and happy days when I did this, At this point if it will not reboot or shut down do this
hold power button and volume down to boot into fastboot, it actually went into fastboot!! which was what I was not able to do before.
Hopefully some of my learning and searching is helping someone. oh another learned point, I don't do as well after having whiskey, beer, or wine!
Now I am back to, [Guide/tutorial] Asus Transformer Prime/TF201 stock to Android 7.1 Nougat, and Tab DID NOT reboot and launch the HairyBean TWRP recovery (androwook). It also does not want to recognize ADB it wants to be an MPX device. I tried this:
"2 - INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PRIME TF201
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type :
Code: shutdown -o -r -t 0
It opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart.
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
Once driver installation is completed, reboot PC as usual."
but it did not like both INF files. On Win 7 I did not have a problem but with WIN 10 it is being more difficult. So I have some more troubleshooting to do. Unless of course someone has found a way to get both android_winusb.inf AND android_apxusb.inf to work correctly.
I fully recovered to stock by back to backing the two threads, first this one..https://forum.xda-developers.com/showthread.php?t=1927818 then this one..https://forum.xda-developers.com/showthread.php?t=2538028
Whatever i did worked as I am back to unlocked stock.

[SOLVED] Fastboot : FAILED (low power, need battery charging)... (bootloop)

SOLVED : I managed to charge the battery enough in the stock recovery (several hours and using buttons so it doesnt turn off by itself), then proceeded to boot twrp to charge more and fix everything.
ORIGINAL POST :
Hi everyone, I have an issue preventing me from making a tablet work.
Let me guide you through what I have done and can do :
- Acer Iconia Tab 10 (A3-A40) runnig Android 6.0
Problem :
I cannot boot TWRL through fastboot (fastboot boot recovery.img) because it gives me an error (low power - need battery charging). But there is no other way to get the tablet back .
Plus, I cannot charge it while pwered off as I get the following message (along with a battery charging icon) :
Orange State - Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds .
This prevents off-mode-charging as it boots up the tablets after 5 seconds.
How did that happen :
Unlocked the bootloader, booted the tablet, had to use Magisk 13.0 modified by someone to work on the tablet (SU doesn't work.) and set the tablet up.
I then had a popup for Magisk having an update (to 16.0). Accepted it, which resulted in a bootloop.
Wanted to reflash the stock ROM and root it again, but it was 4am and people were sleeping, so I decided to do it the next day. Unfortunately, the battery died while I was asleep.
I can't run some commands in fastboot because it gives me an error : (not support on security).
What I have tried :
Charging the tablet in the (stock) recovery.
Charging the tavlet in Fastboot mode.
Charging the tablet while letting it bootloop.
fastboot getvar all doesnt give me any battery info.
I have all the files I need to make the tablet work (Stock ROM, root files, TWRP file...). I just can't get to flash anything, and the battery doesn't charge.
I just need either :
- A way to remove Magisk from stock recovery
- A way to bypass the fastboot (low power - need battery charging) error
- A way to charge the battery
- Or any suggestion you have
The fact that there is next to nothing about the tablet on the internet is very unfortunate and makes it harder to troubleshoot.
Thanks in advance for your help.
Did you try charging from a wall outlet, while the device is powered off?
HippoInWindow said:
Did you try charging from a wall outlet, while the device is powered off?
Click to expand...
Click to collapse
Yes. But everytime I do that, the device has a message stating "Orange State - Your device has been unlocked and cannot be trusted. Your device will boot up in 5 second".
I believe this prevents off-mode-charging by forcing booting up my tablet.
Strangly enough, fastboot tells me off-mode-charging is on, as of the following :
fastboot getvar all
(bootloader) off-mode-charging 1
FrWhyMe said:
Yes. But everytime I do that, the device has message stating "Orane State - Your device has been unlocked and cannot be trusted. Your device will boot up in 5 second".
I believe this prevenrts off-mode-charging by forcing booting up my tablet.
Strangly enough, fastboot tells me off-mode-charging is on, as when I do :
fastboot getvar all
(bootloader) off-mode-charging 1
Click to expand...
Click to collapse
Try charging if the phone automatically turns on, keep charging, then hold down the power button until it shuts down.
If it still reboots, try adb reboot bootloader, then choose power off. That should do the trick.
HippoInWindow said:
Try charging if the phone automatically turns on, keep charging, then hold down the power button until it shuts down.
If it still reboots, try adb reboot bootloader, then choose power off. That should do the trick.
Click to expand...
Click to collapse
It reboots before I can power it off manually with the power button.
And I cannot access adb as I only have access to the stock recovery and fastboot.
Plus, I can already choose "power off" in the stock recovery, and it stills boots up when plugged in.
SOLVED : I managed to charge the battery enough in the stock recovery (several hours and using buttons so it doesnt turn off by itself), then proceeded to boot twrp to charge more and fix everything.

Categories

Resources