Database Info

Random Reboot \ Shutdown - Not another one, I know

Hear me out. I now this has been brought up in various forums, and trust me I have searched them all. I just have not seen anyone speak of the exact scenarios I have experienced. At least not together.
So I have 2 Nexus 5's, a 16GB and a 32GB. My 16GB has no issues at all with the random shutdown\reboot running L up to 5.1. My 32GB however exhibited issues immediately after upgrading to the 5.0.1. During the initial update it barfed and went in to a boot loop, even in Fastboot. I eventually got it back up and running and rolled all the way back to 4.4.4 and then stepped up to each new version up to 5.0.1 then 5.1 once it was official. Still experiencing the shutdowns and reboots under certain circumstances.
I have noticed 3 things that appear to cause the issue:
1st Wi-Fi - With Wi-Fi On it happens repeatedly when entering or leaving a new wireless network. With Wi-Fi Off I can go days without issue.
2nd 3.5mm Audio Cables - Jump in my car, fire it up, plug in to my stereo and poof, it reboots. Possible its just cheap audio cables??
3rd Car Chargers - I have only seen it with car chargers, but if I have it plugged in during a drive it will randomly reboot or power off. If I have it plugged in with the car off, as soon as I turn it (the car) on my phone reboots\shuts off.
Appears to be some impedance change on specific types of load or something. I am no electrical engineer so I could be way off. One thing I have noticed that I know others have as well, is that when a reboot\shutdown happens the battery drains like crazy. But I have also noticed that if it is plugged in to a power source between two back to back episodes that it charges super fast while it is down. I'm talking 25-30% increase in a matter or 2-3 mins.
So with Wi-Fi off, and good headphones plugged in I can go all day listening to music and it works like a charm. Bluetooth does not seem to be an issue, as I have my Moto 360 paired all day too. Running with Wi-Fi off, not plugging in to my car for audio or power I have not had a reboot\shutdown for 3 straight days.
I have seen some say its software, some hardware. Some say factory wipe, clear cache, etc. Send it in and get a new one (this one is out of warranty). Or download official and start from scratch. I've done these, and still it persists. Tried other ROMs as well. Have not gone down the route of different Kernels. Given that Wi-Fi is on one board, power on another I would assume its not hardware. Then again since I have flashed, and reflashed between official and custom ROM's I would say it is. At a loss. Willing to try anything, I really like this phone.

This might be a cracy solution.
As I experienced the same random reboots on 5.1, I worked myself through the usual process: hardreset, reflashing the rom and so on. Even called google for RMA, which got green light as they couldnt find the issue either.
Turned out my new case pressed too hard on the on/off-button, shame on me. Figured it out in time fortunatelly.
If theres no solution for you , send it in directly to LG. They repair it and hopefully the price wont be too high. Good luck!

W.O.P.R said:
Hear me out. I now this has been brought up in various forums, and trust me I have searched them all. I just have not seen anyone speak of the exact scenarios I have experienced. At least not together.
So I have 2 Nexus 5's, a 16GB and a 32GB. My 16GB has no issues at all with the random shutdown\reboot running L up to 5.1. My 32GB however exhibited issues immediately after upgrading to the 5.0.1. During the initial update it barfed and went in to a boot loop, even in Fastboot. I eventually got it back up and running and rolled all the way back to 4.4.4 and then stepped up to each new version up to 5.0.1 then 5.1 once it was official. Still experiencing the shutdowns and reboots under certain circumstances.
I have noticed 3 things that appear to cause the issue:
1st Wi-Fi - With Wi-Fi On it happens repeatedly when entering or leaving a new wireless network. With Wi-Fi Off I can go days without issue.
2nd 3.5mm Audio Cables - Jump in my car, fire it up, plug in to my stereo and poof, it reboots. Possible its just cheap audio cables??
3rd Car Chargers - I have only seen it with car chargers, but if I have it plugged in during a drive it will randomly reboot or power off. If I have it plugged in with the car off, as soon as I turn it (the car) on my phone reboots\shuts off.
Appears to be some impedance change on specific types of load or something. I am no electrical engineer so I could be way off. One thing I have noticed that I know others have as well, is that when a reboot\shutdown happens the battery drains like crazy. But I have also noticed that if it is plugged in to a power source between two back to back episodes that it charges super fast while it is down. I'm talking 25-30% increase in a matter or 2-3 mins.
So with Wi-Fi off, and good headphones plugged in I can go all day listening to music and it works like a charm. Bluetooth does not seem to be an issue, as I have my Moto 360 paired all day too. Running with Wi-Fi off, not plugging in to my car for audio or power I have not had a reboot\shutdown for 3 straight days.
I have seen some say its software, some hardware. Some say factory wipe, clear cache, etc. Send it in and get a new one (this one is out of warranty). Or download official and start from scratch. I've done these, and still it persists. Tried other ROMs as well. Have not gone down the route of different Kernels. Given that Wi-Fi is on one board, power on another I would assume its not hardware. Then again since I have flashed, and reflashed between official and custom ROM's I would say it is. At a loss. Willing to try anything, I really like this phone.
Click to expand...
Click to collapse
Tried http://forum.xda-developers.com/showthread.php?t=2821576 ?

Infinite104 said:
This might be a cracy solution.
As I experienced the same random reboots on 5.1, I worked myself through the usual process: hardreset, reflashing the rom and so on. Even called google for RMA, which got green light as they couldnt find the issue either.
Turned out my new case pressed too hard on the on/off-button, shame on me. Figured it out in time fortunatelly.
If theres no solution for you , send it in directly to LG. They repair it and hopefully the price wont be too high. Good luck!
Click to expand...
Click to collapse
I use a CruzerLite case, does not cover the power button, and I have had the case on my 16GB as well, so I "believe" this would not be the issue. Then again I might as well try to run it outside the case for a while just to see what happens.
I might have to go down the LG route, really hoping not to though as I have heard the cost is pretty high. Would rather then just save the money for a new device.

beekay201 said:
Tried http://forum.xda-developers.com/showthread.php?t=2821576 ?
Click to expand...
Click to collapse
I have not yet gone down this route. I did read this one, but didn't see it applying directly to my issue. Then again, what could it hurt.

W.O.P.R said:
I have not yet gone down this route. I did read this one, but didn't see it applying directly to my issue. Then again, what could it hurt.
Click to expand...
Click to collapse
My point exactly.

H96 Pro Plus

Hello world!
I just got this TV box and I think I broke it.
Looking for some advice please.
It comes with Android 7.1.2 and already rooted
I installed SuperSU and it asked if I wanted to update the binaries. So I did. Now the device won't boot at all.
I pressed the reset pin and wiped the system cache as well as done a factory reset. However it still won't boot.
I don't really know where to go from here as I don't know where to get the ROM from and reinstall it. Or even how for that matter.
The logo that comes up when it tries to boot is MBOX.
I would appreciate any suggestions and help.
Thank you for reading!

Any ideas anyone please?

Hi!
I did do the very same on mine MBOX H96 Pro+ 3g/32g/9377 , and
I've used the USB flash utility (you need a strange male-male usb cable) to flash this firmware:
https://androidtvbox.eu/new-firmware-h96-pro-tv-box-3gb-ram-amlogic-s912-20170602-release/
By using this utility:
https://mega.nz/#!k8hkBDxK!6RVuhh089bT_C_Bdn_LmbicenlIEFYj61OoDMsVqH8A
With these license files:
https://mega.nz/#!o8w0nKYR!J4_6kjS3j6TsgE1Ytl12OnnHnu8aCHb1AKppmh8xVD0
It is 7.1.1, I think, but it made the box boot again. For the moment I'm keeping SuperSU WITHOUT updating SU, and it works well in asking for Root rights when apps require them, but I'm searching for roms which can be rooted with Magisk, and I found this, which seems interesting BUT I haven't tested it:
http://freaktab.com/forum/tv-player...6-scv4a-7-1-2-ddr3-ddr4-and-9377-wifi-chipset
Hope this helps!

Where is the reset button or i have to use toothpick and press thru the av hole then sinultaneously power on the power plug to get into recovery mode ..please help...i am also stuck at boot when updating the binaries of the supersu

The same thing happened to me, I installed Supersu and did not start again.
I burned an image on an SD card and used a toothpick but had an added problem: If I removed the toothpick, the process stopped.
I stayed the whole process by pressing the toothpick.
If I stopped pressing with the toothpick the process stops .
When finished, remove the toothpick quickly or start again.

Same to me, today installed super su and now won't boot. Thanks, tomorrow I will try this solution. I have another box, the same. It's possible to clone the box upon the broked one?

Glad I skipped installing SuperSU on my device

7.1.2 firmware
https://drive.google.com/file/d/1x0rkkYRrmtKke1QiN21-0KqLsXc30v16/view?usp=drives there is no su but is rooted, do not update su

Help. I think my 4 mths old H96+ is dead. I tried updating the firmware using SD card burn method. I pressed the reset button and inserted power. The green Android robot appeared showing it was flashing and immediately I stopped pressing the button. The screen went blank and the blue light went off. Thereafter the H96 won't turn on. No blue light but there is light at the optical out connector. Is the H96 fit for the bin.

Mine is MBox too BTW Have you tried booting to recovery I managed to by pressing reset 3x then held for 10 secs around ten secs no sure which side of 10 tho soz cus one way will go update one to fastboot and one to recovery
---------- Post added at 01:10 PM ---------- Previous post was at 01:08 PM ----------
Here is the firmware I've been using...
Stock: https://drive.google.com/file/d/1x0rkkYRrmtKke1QiN21-0KqLsXc30v16/view?usp=drivesdk
Supercelerons ATV http://freaktab.com/forum/tv-player...b-scv7a-7-1-2-ddr3-ddr4-and-9377-wifi-chipset

curiou5 said:
Help. I think my 4 mths old H96+ is dead. I tried updating the firmware using SD card burn method. I pressed the reset button and inserted power. The green Android robot appeared showing it was flashing and immediately I stopped pressing the button. The screen went blank and the blue light went off. Thereafter the H96 won't turn on. No blue light but there is light at the optical out connector. Is the H96 fit for the bin.
Click to expand...
Click to collapse
What a shame. It is good box but didn't last. It was having some issues before I decided to give it an upgrade.

curiou5 said:
What a shame. It is good box but didn't last. It was having some issues before I decided to give it an upgrade.
Click to expand...
Click to collapse
Sorry i only seen your post today you need to get the right image for your box and then flash it it appears that you are flashing a different software and its conflicting your ram thas way it turns off aftwr flashing the boot, get the right firmware and you iwll be fine, same happend to me but know all is well sd card flashing is the safest one good luck
Enviado do meu GT-N8000 através do Tapatalk

PTHugo said:
Sorry i only seen your post today you need to get the right image for your box and then flash it it appears that you are flashing a different software and its conflicting your ram thas way it turns off aftwr flashing the boot, get the right firmware and you iwll be fine, same happend to me but know all is well sd card flashing is the safest one good luck
Enviado do meu GT-N8000 através do Tapatalk
Click to expand...
Click to collapse
Thanks.
I have open up the box and printed on the circuit board is 2017-02-10 which I am assumed is the date. The other info is H96-S912-TVBOX(DDR4)-VO.2. Does it mean that the RAM is DDR4 RAM and not DDR3 RAM as stated in the market place.
Update : Found firmware for DDR4 RAM and managed to flash the original H96 Pro+ firmware.
I followed the steps found here http://freaktab.com/forum/tv-player...k-gt1-ultimate-scv2-atv-android-tv-ddr4/page3 post #37.
Edit :
First I tried the Super Celerons Standard Android firmware from http://freaktab.com/forum/tv-player-...l-android-ddr4 but my wifi could not connect. Then I download and flashed the firmware from https://mega.nz/#!74hSDb5A!nkqPR4tnp...bvCDquoJ5BJok0 and the box is back to how it was when I first bought it.

Man I wish I saw this thread before installing supersu... totally bricked my box. Tried a bunch of firmwares & sd cards, it's not going so well

pete.xda said:
Man I wish I saw this thread before installing supersu... totally bricked my box. Tried a bunch of firmwares & sd cards, it's not going so well
Click to expand...
Click to collapse
You must first find out whether your RAM is DDR3 or DDR4. As I have learned there are a few versions of this H96 Pro+. Flashing DDR4 firmware on DDR3 version and vice versa will not work.

How I unbricked mine after an age!!
What worked for my Banggood H96 Pro plus box to unbrick it. First - it says on the back of the green board in the box CZ-S32-V2.2/ 3+32/9377 DDR3. I was trying to update the firmware with the burncard method connected to the TV with HDMI and reset button and power connect like I'd done many times before with one of the Tanix 8 Max roms (well it had worked before), only not this time and it bricked hard. Nothing was working to put life back into the box with either different roms with burncard method or that USB burning tool method (what disastrous software that is). My box did have the front blue light and back red one on when I plugged the power in and something I had read said that if that was the case I should be able to get the box resurrected. Then I saw this segment on Youtube - https://www.youtube.com/watch?v=CUfKNNgxb9E
So, I moved back to my TV with my sdcard done by burn card maker with this rom - aml_7.1_s912_q9377-H96PROPLUS_KDMC_mac-20171129_Shonk.img. I don't remember which pin combo tripped the wonderful pic of the android robot on screen (first time in over 2 months that I saw anything visual from my H96) with the UPGRADING below it (I had the power in, the reset button activated, and of course the HDMI plugged in when I was routing around for the the correct pin combo)(I was not looking at the screen because those tiny pins required my attention but the sound caused me to look up at the screen). As soon as I saw the little robot I pulled the paper clip from the box and let it run on it's own to completion. A check mark came on the little robot and I pulled the power and put it back in and it took off with that H96 Pro + splash screen and finished the set up. To finish - it's seems like a wonderful rom so far. Wifi works great and I have not run into any problems so far after 2 days - it is faster than my Nexbox A1 2gb/16gb s912. Did I miss anything? Just ask.

McGiles said:
What worked for my Banggood H96 Pro plus box to unbrick it. First - it says on the back of the green board in the box CZ-S32-V2.2/ 3+32/9377 DDR3. I was trying to update the firmware with the burncard method connected to the TV with HDMI and reset button and power connect like I'd done many times before with one of the Tanix 8 Max roms (well it had worked before), only not this time and it bricked hard. Nothing was working to put life back into the box with either different roms with burncard method or that USB burning tool method (what disastrous software that is). My box did have the front blue light and back red one on when I plugged the power in and something I had read said that if that was the case I should be able to get the box resurrected. Then I saw this segment on Youtube - https://ru-clip.com/video/CUfKNNgxb9...in-method.html
So, I moved back to my TV with my sdcard done by burn card maker with this rom - aml_7.1_s912_q9377-H96PROPLUS_KDMC_mac-20171129_Shonk.img. I don't remember which pin combo tripped the wonderful pic of the android robot on screen (first time in over 2 months that I saw anything visual from my H96) with the UPGRADING below it (I had the power in, the reset button activated, and of course the HDMI plugged in when I was routing around for the the correct pin combo)(I was not looking at the screen because those tiny pins required my attention but the sound caused me to look up at the screen). As soon as I saw the little robot I pulled the paper clip from the box and let it run on it's own to completion. A check mark came on the little robot and I pulled the power and put it back in and it took off with that H96 Pro + splash screen and finished the set up. To finish - it's seems like a wonderful rom so far. Wifi works great and I have not run into any problems so far after 2 days - it is faster than my Nexbox A1 2gb/16gb s912. Did I miss anything? Just ask.
Click to expand...
Click to collapse
the video is not there anymor can you post a picture please
Sent from my ATVXperience using Tapatalk

Hey Shores,
please, provide another download link. The source from the link you provided is infected heavily.
Zoli

Hi,
For the second time no more signal from the h96 pro plus hdmi output the front blue led don't light on. I have returned the box to the Chinese supplier and after 2month the box come back with no defects found....
This time after 6 month same problem.
But I have connected the USB output from the box to the PC. (Idea was reload firmware). But suddenly the blue LED light on. Now the box is working properly by using one TV USB port without the external power supply.
Is there any other way for solve the problem?
If not I hope this message will help others h96 user's ..[emoji6]
Envoyé de mon MI 4S en utilisant Tapatalk

New Link to try
PTHugo said:
the video is not there anymor can you post a picture please
Sent from my ATVXperience using Tapatalk
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=CUfKNNgxb9E

Unit not shutting down correctly

So, yesterday I got in my car and it wouldn't start, the battery was flat.
I fitted a new battery as the other one was the original and I figured it was due a change anyway.
When I got in and started the car this morning, my MTCE unit immediately came on as though from sleep and not shut down. It didn't need to boot like it normally does. So, I checked in settings and it is still set to shut down after 30 seconds of ignition off. So I powered it off, waited two minutes and put it back on, it came on immediately. So it looks like it isn't shutting down as it's supposed to although when I pull the ignition key out the unit waits a few seconds and then says shutting down before the screen goes off.
Is it worth me trying a full factory reset and see if it solves it? I'd rather not but don't want this to continue in case that is what was draining the battery yesterday. It has always shut down and booted normally until then.

What version of Android is it running and is it wired up correctly. A few of them had the red and yellow wires revered on the unit.
Sent from my ONEPLUS A5010 using Tapatalk

It's on Malaysk ROM and is definitely wired correctly as it was working for two years until yesterday. I see there is a later MCU for me so may try that later

I updated the MCU and it shuts down correctly now. Only annoying thing was the device did a factory reset at the same time, never had that happen with an MCU update before. Doesn't matter, will spend some time end of this week reinstalling my apps and stuff.

Trying to understand the "standby" or sleep mode for fast boot

I have a PX6 mtce 4/64 unit and am confused as the when the unit reboots on start up vs when it just resumes. This thing seems to have a mind of its own and can't seem to find a rhyme nor reason as to what happens when it restarts. Sometimes it quick starts. Sometimes it reboots. Even after setting overnight. It is not having any problems, just trying to figure out how it works.
Sent from my SM-T387V using Tapatalk

Usually such units perform a cold boot, if the unit was in suspend-to-ram mode ("fast boot") for several days.
Over night the unit should always do a fast boot in the morning.

i.t.works TM1008 tablet Bricked: How can I solve this?

Hello everybody,
I hope I don't post this question where I should not post it, if so, I do apologies.
Some times ago, my father-in-law gave me one tablet he didn't use anymore, an i.t.works TM1008 as said on the box and on the back of the tablet.
It was sold by the French shop Darty, youcan have a preview of the specs over here. It's nothing fancy, a chinese tablet with a rebranding from what I could understand. After some search on the net, I found out it also exist with the Kesa name - Kesa TM1008.
After getting the tablet, I've erase everything on it as you normaly do when you want to have a fresh tablet from factory, using the android tools already onbard: long story short, I use the settings of the device as far as I remember, I did not flash it or anything crazy. It didn't worked, I had the setup menu, but I couldn't do much. The only thing I have is the quad core boot image, then the android logo, then nothing at all.
Lately I tried to go a bit further with firmware update, etc. and it worked so well I've bricked the device *facepalm*. I was a bit stupid to say the least, because I tried to put the TM1007 firmware on it. And from what I can see herew, the processor is not the same. It's a MT8127 Quad Cortex A7 but the TM1008 has a MTK MT8163 Quad Core.
So from my understanding of the situation, that what messed everything up. And after browsing for a long long time, I did not find any firmware for the i.t.works or the kesa TM1008. And with the "I.T.Works" name, it makes my researches much harder.
Anyway, still from my understanding, if I find a ROM for the MTK MT8163 Quad Core, I would believe it would work. So first question: Am I right to think such insanity? Or is the tablet fully bricked and dead?
The state actual of the tablet is:
I have no indication if it's charging or not when I put it on charge.
When I plug it to my laptop, it is not recognise. I have a Windows 10 installation, and when I plug it, there is nothing: no sound notification that something has been plugged, nothing in the device manager tool. Nevertheless, if I plug it and keep the power and return buttons, I can sometimes hear a notification that something has been plugged, but that's it.
I can't see it with SP Flash Tools
I can switch the tablet at all: no recovery menu, no android logo, nothing.
I've find the scatter of the MTK MT8163 processor, I wanted to try if it would do something, but there is no way for me to see if it could work. So for my second question: Would a scatter file of something like 10ko would restore a firmware, or substitue a ROM? (I would assume no, but I don't know much about tablets)
How can I restore it when there is nothing on internet regarding that firmware, or brand? I could go to a Darty shop, but I'm living in UK, and the warranty of the tablet is way overdue, so...
Thank you for your help!
EDIT: I tried to follow that guide, but as I don't have the ROM, I don't really think I can go that far.