So my android head unit randomly stopped working. Basically it boots normally but then it says Optimizing apps 1 of 1 for like 5 minutes, then it turns off, boots again, optimizing apps 1 of 1. It just cycles indefinitely. I cannot seem to get it into recovery mode. I've tried holding reset, holding power, holding reset plus power.
My unit is a 7 inch Bondroad Android 5.1.1 2G. I didnt mess with it or anything.
If you need more info please inform me.
Thanks
Related
Gents,
I have just got a Xoom 2 16GB Wi-Fi only model and seem to be having a problem.
I have read the original Xoom tips & tricks thread and searched but want to clarify a few things...
On the Xoom2
1. The charging LED does not light. Apparently it only lights when the unit is powered off. Ok, I can accept that.
2. When plugged in, if I try to power my unit off it powers up again on its own.
I spoke to Motorola tech-support about this and they said that was "designed" behaviour. The unit will automatically power on when the charge level is above a certain threshold.
Is the above true? Does the unit have to be VERY low on battery before the LED will indicate that charging is taking place?
I'm rather confused as all of the above seems totally counter intuitive to me.
Any advice appreciated.
Yes you cannot charge the tablet while it is powered off, it will automatically turn on and charge.
Apparently they changed this in the latest software update but I have yet to test this out.
Sent from my Motorola Droid Xyboard 10.1 with Verizon 4G LTE
The behavior will change when you get the 3.2.2 update. There's a powered off charging mode for quick charging now.
Xoom 2 charging
Yes, my xoom 2 also turns on to charge! found this weird but it must be the case.
Hrm.
Ok so I've done more digging and it does say on the Moto website that the "on to charge" behaviour is normal.
I am keep to get mine updated to 3.2.2 however my "System Updates" option just tells me that my system is up to date despite being only 3.2
Furthermore, I had trouble powering my device up again. I had what seemed like problems straight out of the box but after speaking to tech support they told me to charge the unit for a while (like a few hours) and then give it a go.
I did this and still no joy. I called again and they asked me to try pushing and holding all three buttons (i.e. vol up, vol down and power) together for 15s.
After I did this the unit powered up, I managed to get through the setup procedures and have a little play.
Then I put the unit in my bag and left for home. I got home and the unit wouldn't power up. So I tried the reset and got presented with a funny menu (looked like a bootloader to me).
Not sure what I selected here but it booted albeit with some weird apps showing.
I rebooted again and now it seems fine but not sure it's actually charging!!!
I might have to send this unit back for a fresh one.
Ok,
I've narrowed down my problem. If the unit is plugged into the wall adapter it will charge and work as normal. If it enters standby mode the unit will power on when the power button is pressed
Great.
However, if the unit IS NOT plugged in and it enters standby the power button WILL NOT turn the screen back on. It will just sit there lifeless.
The only way to recover from this state is to "reboot" it by pressing and holding the 3b buttons (vol up, vol down and power) for something like 10-15 seconds until the bootloader menu is shown.
Here's the real kicker though, if the unit is on but SHUTDOWN using the power button pressing the power button subsequently WILL turn the unit back on (i.e. it will go through the boot process showing the Moto logo/circles animation).
But again, once powered on, if the unit enters standby the power button will not turn the screen back on.
What is going on here? Does it just sound like my unit is faulty and needs to be replaced?
Any help appreciated...
SF
Bump.
Anyone got ideas/suggestions regarding the power button/standby issue I am describing above???
have you fully charged it yet?
Yup.
I charged it for a good 8 hours + (overnight) and it still exhibited the same behaviour.
I think the power button is dodgy/intermittent and that is what is causing the issue.
Either way, I've RMAed the unit back to Expansys and am awaiting a replacement.
Hello,
I have been having a few odd issues with my Nexus 4, random reboots, no sound from speakers unless a reboot. Anyway Last night I had it on charge and it started rebooting itself in a loop so I managed to break the cycle and I ended up on a screen with a android on its side with a big arrow pointing at the power button, so I pressed the power button and it rebooted and was sat on the Nexus 4 logo.
I left the phone doing that and when I came back a while later the phone was still on the Nexus logo (which was still animating) but the phone was roasting hot, I turned the phone off by holding the power button.
Anyway, now the Nexus will not turn on, when it is plugged into a power source I get a red LED for a couple of seconds and then it goes out. In device manager I have qhsusb_dload in device manager.
I have done many hours of searching, I tried a few things suggested on other posts using Ubuntu but nothing.
This was a stock device that had only ever been updated with official updates. I can send it back no problem but I thought I would try save everyone's time and effort and see if there was anything I could try.
Thanks
qhsusb_dload stands for Qualcomm high speed download mode. Theres nothing you can do, other than a jtag. Sorry
I have a galaxy s4 (i9500) and got it in used condition, a year ago. Never suspected a single problem in it.
Today I powered off my mobile for charging then after 25 minutes I took it off. I held the power button then I saw my boot logo(Where there is written Samsung Galaxy S4 GT-i9500). That logo kept showing as usual for 2 seconds and screen went black and again that logo appeared for 2 seconds and screen gone black and again it appeared, so, I'm stuck in kinda loop not a bootlooop exactly(maybe because bootloop refers to being stuck on boot screen while in my case its boot logo). I then removed the battery and inserted it back after an hour and as soon as I inserted it back the mobile itself turned on as if I held power button but this time again I was stuck in that loop. Moreover when I tried going into download mode, I didn't even need to hold the power button along with the volume down and home, it itself proceeded to confirmation screen of odin mode. And after that confirmation screen appeared saying that whether I really want to boot into download mode, disappeared itself after like 3 or 4 seconds even though I didn't press any key. And in case I press vol up key confirming to boot to download mode, then it again takes me to that loop. I'm too much confused . I can't even flash the firmware as it won;t boot to download mode neither am I able to boot into recovery.
Now do u really think the problem might be the power button(Which is maybe stuck in the state of pressed).
Or else it can be the battery coz my battery is also just average not too good?
I also inserted the command( in build.prop file) for enabling nav. bar and the code was correct but I never rebooted after inserting that. this was the first time I rebooted after that.
SOrry for some bad English.
Do you have something like this? I'm now having problem with getting my phone back to work...
https://youtu.be/HxnV-tn2vpA
From what you say it seams like power button problem, try to start the phone and connect it to the charger. When it start take out the battery, it will be powered by charger and you will eliminate battery problem.
Hi guys
I wanted to upgrade the user interface on my Android head unit. ( Carsara, Android 8,1,)
Started upgrading via USB, the update went thru and i thought it was finish. So I turned off the car to restart it. I started the car, but the screen was completely black. Nothing is working
Later I find out that i should have waited 15-20 minutes for the update to reboot, something i didn’t do. In other words, I turned off the power before it was finished with the reboot. And now it’s dead
Any suggestions so I can get it back to life? Or is it a lost case?
Hi all,
i bought a new head unit abd have installed it last weekend on my car. First hours the new HU runned well, so i updated to HAL9k Rom 4.0.0. Approx 1h later the HU went down to a black screen. I checked power and fuse, everything seems to be allrigt, my old radio run without any issue when put it back into the car. The day after i have tested the new Pumpkin, again black screen - but after 10min the HU get booted and everything worked as there have never been something.
When i went to my car today after some minutes the HU shutdown again (has been signaled on the screen), since this there is again a black screen
details HU
PX6
MTCE_HT_V3.30_1
Kernel 4.4.167
rk399-userdebug 9 PQ2A.190305.002 20191104.1620055 test-keys
what i've done so far:
- pressed reset to reoot - no success
- pressed reset longer then 1min - no success
- pressed power button longer then 1min - no success
- put SD card with imcu.img ans hal9k update.zip in the HU, pressed/hold power button then presse reset and release both - button lights blink on time
no recovery mode, no reboot, only if i press reset one time blink on button lights
any ideas?
best regards
also tested: press/hold Power and reset, release reset after 5sec while keep power pressed: no success
got an update from my dealer: connect batterie pülus with acc direct an radio plug, HU start after this. It seems to be an issue with the external canbus box with to less power on ACC cable