Hello guys, this is my first post on this forum so i hope i don't post where i shouldnt.
So i was trying to integrate an android tablet onto my car so i can see everything that happens to my car real time with an OBD2 bluetooth diagnostic.The problem is im trying to integrate it so no buttons of the tablet are accesible. I got my hands on a cheap Vodafone Smart Tab 3G and i was searching ways to turn it on once it gets power. I managed (with the help of my dad, THANKS DAD !!!) to make a fake battery (a charger that connects back to the tablet and simulates a real battery). Now, all i have to do is make the tablet turn on once it gets power. On samsung devices if u hold down the power button it starts normally but on this device it just freezes at Powered by Android logo, so i dug up a little bit more and i managed to root it. I tryied then the ipod file modification. I tryied even to delete it and replace with the reboot file, still nothing. The charging animation dosnt show but it wont boot up either. Then i found out about bootloader oem on-charge 0 (or something like that, i cant remember, being searching for like 2 or 3 days) but the tablet dont support that either. Now im stuck with this. Tryied to find some custom roms to flash on my device but found nothing in particular.
So, any ideea how could i achieve this ?
Related
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
Hi folks,
first post but an important one. Important enough to join and hopefully get some answers.
My LTE Nexus 7 (running 5.0.2) bricked last night. It got stuck on the Google screen and I had no way to unlock the bootloader to flash a different version of the OS. SO this morning thinking I had nothing to lose I removed the back panel with the intention of tearing the thing down. Then it hit me. The common theory seems to be that it's the way the bootloader is not mounting the storage. So as the device never completely powers off what would happen if I cut the power manually. Hopefully a hard reset. So I detached the battery cable from the board and left it alone for a few moments. After popping the kettle on I returned, replaced the cable and tried turning on my Nexus. Lo and behold it works!
I have an unbricked device.
Which is great an all, but I have the proper tools and knowhow to delve into the hardware. More importantly though I'm trying to find out why that might have worked.
Any thoughts?
Has anyone else tried this as a solution to unbrick their device? Did it work?
There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button
Gorgtech said:
There is a way easier solution, in case you didn´t know before Push the power button for a few seconds ( >5 seconds ) and it will shut down the device, the same way you are used to shut down a PC by holding the power button
Click to expand...
Click to collapse
But surely that's not the same as disconnecting the battery?
Trev
It´s not the same but once you´re in a "boot loop", you have no chance of eg. entering the recovery. This is why you need a way to shut down the device first.
But in case even this "forced shut down" doesn´t help and you´re out of warranty, maybe it´s not the worst idea to open the device anyway since you´ve got nothing else to lose
Hi,
Ive googled about this matter and cant seem to find a solution for the galaxy tab s lte but for other samsung devices since s3 is possible.
Ive also tried the Auto Power On app (paid apps) both of them didnt work and requested a refund.
It seems that we have to modify the file /system/bin/playlpm or /system/bin/lpm or /system/bin/ipod for this to work.
Ive tried everything and still doesnt work on the galaxy tab s lte.
What i need is for the tablet to boot upon connected to charger when the state is off. Now all i can see is the battery icon stating its charging but never boot into android.
Anyone have any idea how to make this work for the galaxy tab s lte?
Cheers.
Well it begs the question as to why in the world would anyone want this?
I wouldn't want my tab on every time I charge it.
I think you would need a custom rom, don't the apps you can download/buy, need your device to be already running so they can shutdown or run an app or change a mode when they detect you plugging in or removing the charger.
John.
ashyx said:
Well it begs the question as to why in the world would anyone want this?
I wouldn't want my tab on every time I charge it.
Click to expand...
Click to collapse
ashyx said:
Well it begs the question as to why in the world would anyone want this?
I wouldn't want my tab on every time I charge it.
Click to expand...
Click to collapse
Why would anyone need this? Let me answer you.
Some of us use our android tablets in cars ... There's app to make the tablet shutdown when u turn off the engine and the power is disconnected (tons of them).
But when u start the engine back and the power is re-connected, the tablet wont turn on. Right now the only solution i can do is to use tasker to airplane mode on the device when the display is off, and airplane mode off when the display turns back on. This saves power so that the tablet doesnt run out of juice overnight in the car.
So most of this has to do with in-car tablet systems that you want it to boot up as you start your engine. I can custom rom my tablet to run CM12 however even CM12 doesnt boot up, some settings needs to be changed and im not sure which part so i need some help on this.
Cheers.
ashyx said:
Well it begs the question as to why in the world would anyone want this?
I wouldn't want my tab on every time I charge it.
Click to expand...
Click to collapse
And btw .... iPhone iOS Behavior is exactly like this ... So no body is begging the question of why anyone would want this ... Just you i guess
arsyan said:
And btw .... iPhone iOS Behavior is exactly like this ...
Click to expand...
Click to collapse
Another reason not to want it then
LOL thats a good one ....
Anyway back to serious matter ... Any one out here can help me with this problem? I think it would help a lot others too that are looking for a solution. a CM12 solution would be great also coz i can flash the tablet with CM12.
Thanks in advance.
arsyan said:
And btw .... iPhone iOS Behavior is exactly like this ... So no body is begging the question of why anyone would want this ... Just you i guess
Click to expand...
Click to collapse
C'mon. You and I both know that this is a niche scenario, and normally it's a bad idea. If your running low enough on battery to run you device dead, you want it to charge a while before turning on. We've all been waiting on a dead phone to get a few percentage points charged so that way it doesn't die immediately upon startup.
I've been leaving my Tab S on a constant power supply in the car. This means I have to turn it on and off manually. I have been toying with using Tasker to turn the screen on/off based on connection with a BT device that would be powered by an switched power source.
The problem I get is warning messages about trying to charge the battery while it is too hot or too cold.
stm8 said:
I've been leaving my Tab S on a constant power supply in the car. This means I have to turn it on and off manually. I have been toying with using Tasker to turn the screen on/off based on connection with a BT device that would be powered by an switched power source.
The problem I get is warning messages about trying to charge the battery while it is too hot or too cold.
Click to expand...
Click to collapse
Why dont u try this app https://play.google.com/store/apps/details?id=com.as.powerchecker it will close the android once ur power is disconnected from the car ...
As for turning it back on when u start. Still no solution ...
Any help guys? Last time asking ...
Using Tasker and Secure Settings, I can get the tablet to turn the screen on and off when the power is connected. If rooted, you could turn Airplane Mode on and off in Tasker also. But short of a change in the firmware, I have no idea how to power off and restart based on external power connection.
From what I remember, when CM12 was still buggy... when you connect a charger when it was powered off, it would show the battery icon and automatically reboot into recovery. Of course that was a bug, so I don't really know.
-DUHA
Same here, did you find an answer?
Same here but no solution found
Iam trying to set my tablet to auto start/boot when charger is connected in mini usb port. I didnot find lpm.sh in root\system\bin folder to modify. But i found ilm file with below script. Plz tell how to modify to make powered off tablet to boot when charger is connected.
Script to start "pm" on the device, which has a very rudimentary
# shell.
#
base=/system
export CLASSPATH=$base/framework/ime.jar
exec app_process $base/bin com.android.commands.ime.Ime "[email protected]"
You can instruct init to reboot the device whenever charger mode is detected. Create a new .rc file or edit any existing one:
# /system/etc/init/off_mode_charge.rc
on charger
setprop sys.powerctl reboot,leaving-off-mode-charging
Source: https://android.stackexchange.com/q...ower-on-android-when-the-charger-is-connected
So, unluckily today i find myself here lookin' for help with my phone. I had already took a look on other brick threads, but i can't find an appropriate answer to my problem.
I'm (i was) running lineage-14.1-20170602-nightly, i had ne0zone75's TWRP 3.1.0.0-0, and that's how the brick came in a strange way; i was simply on XDA Labs app browsing the forum, when i received a call. I've answered, and when i shut off the call the phone shut off immediately after. I thought it was a reboot, but keeping pressed the power button didn't switched on the phone anymore. So i've tried to remove the battery and re insert it after some minutes, but the only thing i can get is the screen with the samsung logo that goes all black after 5 seconds. I already had other bricks due some errors of mine in the past, but this time it's really difficult.
1: I can't access recovery mode. Ow, how i wish i could.
2: I can access download mode, but after that i reach the ODIN MODE screen with the details of product binary, KNOX, ecc. the phone shuts off again.
3: If i keep the power button pressed, the phone doesn't starts. It only starts if i replug the battery in, but after some seconds it shuts off again.
4: How could a call as another mess up the whole phone?
5: I didn't installed nothing new from at least a week... yesterday an automatic update of the Play Store took place, but except that nothing has been changed. Nothing of nothing! No settings, no apps...
What could i do? Installing Kies with Samsung drivers could help me flashing a stock rom for example? Because at the moment, there isn't too much that i can do with the phone in this state... I hope this little jewel won't have to become a stone to be thrown away. Any help would be great, and really appreciated. Thanks in advance...
Things has got worse. Now my device doesn't starts at all; no vibrations, no signs of life, nothing. I've tried even to put it for 6 hours in my refrigerator, because i've read that the cold temperature could be helpful to fix some broken contacts on some component, but i'm losing hope 'bout it. I supposed that at this point is something hardware-based and not software, because it's just impossible that a call like an other one could be the cause of this hard brick... The only thing is that if connected to my PC, it is being showed as QHSUSB_LOAD. I'll try some methods that i've seen in other forums, like softwares that tries to fix this, but i think that i'll be forced to buy a new device. Neither an usb-jig could help me to force the download mode if the phone is dead in every aspect... the only thing that i still didn't understood, is if a debrick.img on my SD card (sadly i've read that a microSD class 10 with at least 16 GB is required, and i don't have one) could help somehow on a situation like this one of not. Still no one could advice me with some tip, guys
Edit - feel free to close this thread, I have another phone now
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
no solution from me. But I have exact same problem and tried same things. Yesterday I did not used the phone. Day before shut down, today tunred it on and it starts with the issue. Strange it happens to both of us at the same time frame. removing sims did not help either.
By holding down "volume down+power" I was able to boot in safe mode but the same issue occur; no way to get into the phone.
Yeah that's weird. Draining the battery did nothing for us. There was not much data that we wanted to extract from the phone. Most of it was contacts and an emulated Pokémon game save file. So my wife eventually reflashed the OS with Xperia companion which did actually resolve the issue of not being able to use the phone.
I faced the same problem today ,i have xz2 , yesterday it was 24% and today i found it 0% so I put it in the charger ,but I faced this problem