Database Users

Moto G4+ Bricked ---Help ASAP!!

My phone is Moto G4+ -
Indian Version
Android 7.0 (June Security Update installed)
32GB ROM / 3GB RAM
Black Variant
Bought online on amazon.in
My 1 year warranty expired on 18 July 2017.
I update to the June security update last week. Everything was going fine.
Today when my phone was charging (was around 50%), I opened WhatsApp to check my messages. As I reading my messages the whole screen got an "RED" overlay. And most of the things in the background became black but I was still able to see behind the overlay. Also there was a small "BLUE" circle in the middle above the overlay. I have taken a screenshot of it but can't post it (read further to know why). After taking the screenshot the phone was unresponsive to all inputs, nothing worked. Then it switched off. The following things I have tried till now to start it:-
1. Normal turn on (pressing the power button)
2. Forced turn on (pressing power button for more than 2 minutes while charging)
3. Boot in recovery (power button and volume down for approx 5 seconds)
I tried all the methods while charging and while not charging.
The phone is not giving any response. It dose not even turn the screen on (and I know the screen was off not just the backlight on and blank screen). The only respone is IT VIBRATES EVERY 2-3 minutes (do not know the exact interval) . It has been going on continuously. The LED (near the fingerprint scanner) is not turning on too.
I have never done or tried to root, unlock the bootloader, etc.
All my apps were installed from the Play Store except for "Terrarium Tv" (https://terrariumtv.com/).
I connected the phone to my laptop, it detected it as "Moto G4", I tried to open it but the laptop was not able to mount it. I tried after some time and now the laptop dosen't even detect it.

ADPL said:
My phone is Moto G4+ -
Indian Version
Android 7.0 (June Security Update installed)
32GB ROM / 3GB RAM
Black Variant
Bought online on amazon.in
My 1 year warranty expired on 18 July 2017.
I update to the June security update last week. Everything was going fine.
Today when my phone was charging (was around 50%), I opened WhatsApp to check my messages. As I reading my messages the whole screen got an "RED" overlay. And most of the things in the background became black but I was still able to see behind the overlay. Also there was a small "BLUE" circle in the middle above the overlay. I have taken a screenshot of it but can't post it (read further to know why). After taking the screenshot the phone was unresponsive to all inputs, nothing worked. Then it switched off. The following things I have tried till now to start it:-
1. Normal turn on (pressing the power button)
2. Forced turn on (pressing power button for more than 2 minutes while charging)
3. Boot in recovery (power button and volume down for approx 5 seconds)
I tried all the methods while charging and while not charging.
The phone is not giving any response. It dose not even turn the screen on (and I know the screen was off not just the backlight on and blank screen). The only respone is IT VIBRATES EVERY 2-3 minutes (do not know the exact interval) . It has been going on continuously. The LED (near the fingerprint scanner) is not turning on too.
I have never done or tried to root, unlock the bootloader, etc.
All my apps were installed from the Play Store except for "Terrarium Tv" (https://terrariumtv.com/).
I connected the phone to my laptop, it detected it as "Moto G4", I tried to open it but the laptop was not able to mount it. I tried after some time and now the laptop dosen't even detect it.
Click to expand...
Click to collapse
This maybe is the hardware issue bro .because it should get detected in PC eitherway

ADPL said:
My phone is Moto G4+ -
Indian Version
Android 7.0 (June Security Update installed)
32GB ROM / 3GB RAM
Black Variant
Bought online on amazon.in
My 1 year warranty expired on 18 July 2017.
I update to the June security update last week. Everything was going fine.
Today when my phone was charging (was around 50%), I opened WhatsApp to check my messages. As I reading my messages the whole screen got an "RED" overlay. And most of the things in the background became black but I was still able to see behind the overlay. Also there was a small "BLUE" circle in the middle above the overlay. I have taken a screenshot of it but can't post it (read further to know why). After taking the screenshot the phone was unresponsive to all inputs, nothing worked. Then it switched off. The following things I have tried till now to start it:-
1. Normal turn on (pressing the power button)
2. Forced turn on (pressing power button for more than 2 minutes while charging)
3. Boot in recovery (power button and volume down for approx 5 seconds)
I tried all the methods while charging and while not charging.
The phone is not giving any response. It dose not even turn the screen on (and I know the screen was off not just the backlight on and blank screen). The only respone is IT VIBRATES EVERY 2-3 minutes (do not know the exact interval) . It has been going on continuously. The LED (near the fingerprint scanner) is not turning on too.
I have never done or tried to root, unlock the bootloader, etc.
All my apps were installed from the Play Store except for "Terrarium Tv" (https://terrariumtv.com/).
I connected the phone to my laptop, it detected it as "Moto G4", I tried to open it but the laptop was not able to mount it. I tried after some time and now the laptop dosen't even detect it.
Click to expand...
Click to collapse
Hold down power and volume down for 2-5min if it booting into bootloader if it doesn't boot it may be a hardware issue
Sent from my Moto G4 Plus using Tapatalk

BlackBeats said:
Hold down power and volume down for 2-5min if it booting into bootloader if it doesn't boot it may be a hardware issue
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Gave no response, tried that.

ADPL said:
Gave no response, tried that.
Click to expand...
Click to collapse
Use the old twrp your new twrp might be corrupted
If nothing works then flash the stock rom
Using adb
Sent from my Moto G4 Plus using Tapatalk

BlackBeats said:
Use the old twrp your new twrp might be corrupted
If nothing works then flash the stock rom
Using adb
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Bootloader is not unlocked. Never rooted so TWRP dosent come in the picture.

ADPL said:
Bootloader is not unlocked. Never rooted so TWRP dosent come in the picture.
Click to expand...
Click to collapse
June update (14-8) has killed a lot of Athene. Sorry. A warning to others to stay away from this update. Stick with March Security Update ROM 14-4. If under warranty, send it in ASAP.

HueyT said:
June update (14-8) has killed a lot of Athene. Sorry. A warning to others to stay away from this update. Stick with March Security Update ROM 14-4. If under warranty, send it in ASAP.
Click to expand...
Click to collapse
Warranty ended on 18th July, bricked on 20 July

Does it vibrate? what about the LED @ the bottom?
ADPL said:
Warranty ended on 18th July, bricked on 20 July
Click to expand...
Click to collapse
sorry to hear about your phone! there is a high chance that its a hardware problem.
reason_
1. It should be able to get picked up with your Windows / Mac. as QHUSB_Bulk (if your bootloader was damaged)
2. If display was the problem. Connecting to PC should have detected anyway as adb sideloader or Moto Device / Android device.
PS_ try uninstalling moto drivers and reinstalling from **device manager.

jagpreetsinghmatharu said:
sorry to hear about your phone! there is a high chance that its a hardware problem.
reason_
1. It should be able to get picked up with your Windows / Mac. as QHUSB_Bulk (if your bootloader was damaged)
2. If display was the problem. Connecting to PC should have detected anyway as adb sideloader or Moto Device / Android device.
PS_ try uninstalling moto drivers and reinstalling from **device manager.
Click to expand...
Click to collapse
It was a hardware problem, display and motherboard had been shorted.

shubh01608 said:
This maybe is the hardware issue bro .because it should get detected in PC eitherway
Click to expand...
Click to collapse
But terrariumtv.com Not working now, may be https://terrariumtvz.co is working for me

Bricked Le Pro 3 727 (Blue Screen of Death)

Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.

Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium

My one did the same, the issue was motherboard. You should send it back to repair.

mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.

Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium

That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.

Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.

shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.

i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?

Is my Note 4 dead?

Hello dear community,
I'm posting there because I have some doubts about my phone and i'd like some answers from you.
1 month ago, I was charging my phone. When it reached 100% battery, It was fine but the problem is when I was trying to press "power" to turn it on but It didn't want to. So, I removed the battery because I couldn't even turn it off. When I tried to restart it again, it didn't want to. No reaction to the "power" button.
I followed EVERY tips on Google but none worked. I also tried to change my battery but nothing. I tried also to connect it to my computer, it was detected but my phone didn't turn on.
So, I guess my phone is dead unless if there is a solution to make it working? Also before that, my phone was becoming very laggy and when it had a small lag, it was turning off and was rebooting.
Thank you in advance for your answers.

CSM Fol said:
I have mustered some conclusions about your phone based on what you typed:
1st claim: The power button no longer works anymore
•Reason: "... when I was trying to press "power" to turn it on... it didn't want to... When I tried to restart it again, it didn't want to. No reaction to the "power" button."
—Seems like you're gonna have to find another Note 4 and replace its motherboard with the Note 4 whose power button doesn't work anymore after 5 years.
But before spending, I would like you to try this method from a Youtube comment:
"... you'll just have to keep the charger [cable connected] on [your phone] while you take off the battery, and put it back after; then, remove the charger quickly..."
—————
2nd claim: The screen no longer works
•Reason: "I tried also to connect it to my computer, it was detected but my phone didn't turn on."
—If the phone is charged, seeing nothing but blackness, but you still see an emitting LED light on the top-left corner, that's a sign that it still works, just not the screen. So I would suggest that you buy a new screen and replace it with your old one. If you think you can't, then go to a phone repair shop and let others do the repairing.
—————
3rd claim: The motherboard is dead
•Reason: "... before that, my phone was becoming very laggy and when it had a small lag, it was turning off and was rebooting."
—The motherboard might be dead if these are happening, but I don't think this is the right reason unless the first two conclusions are proven to be true. If the first two conclusions are proven to be false, then the motherboard is dead, and you may either buy another Note 4 motherboard or get a new phone.
Click to expand...
Click to collapse
Thank you for your answer.
To answer you clearly about all the points you clarified, there is no led light appearing when putting it on charge and I also tried the "Youtube comment" but nothing.
So I think, the motherboard is dead as you mentioned. I just don't understand how it died after a charge but as I saw on Google, it's a general problem on Galaxy Note 4, so I think i'm not surprised at all. It's been since 2015 I had it.
Thank you for your time and to have solved my doubts about the death about my phone.

xSLOom said:
Hello dear community,
I'm posting there because I have some doubts about my phone and i'd like some answers from you.
1 month ago, I was charging my phone. When it reached 100% battery, It was fine but the problem is when I was trying to press "power" to turn it on but It didn't want to. So, I removed the battery because I couldn't even turn it off. When I tried to restart it again, it didn't want to. No reaction to the "power" button.
I followed EVERY tips on Google but none worked. I also tried to change my battery but nothing. I tried also to connect it to my computer, it was detected but my phone didn't turn on.
So, I guess my phone is dead unless if there is a solution to make it working? Also before that, my phone was becoming very laggy and when it had a small lag, it was turning off and was rebooting.
Thank you in advance for your answers.
Click to expand...
Click to collapse
Put in cold fridge for 30 min without battery, then try to turn it on. If not, try the cardboard method under the emmc chip (search youtube)

Timpaa said:
Put in cold fridge for 30 min without battery, then try to turn it on. If not, try the cardboard method under the emmc chip (search youtube)
Click to expand...
Click to collapse
Is this a serious thing ? (fridge)

I did the oven trick on my n910t. I left my phone stuck in the grill of my truck when I changed the brakes. I took it for a test drive and ended up running over the phone. Me being a noob at the time didn't know the AT&T Note 4 would not unlock Bootloader for custom roms or custom recoveries. I purchased the AT&T Note and was sorely disappointed there after. Flash 2019 I still have the motherboard for my note that I ran over. I can only get in to go into download mode and only when it was plugged in. I flash custom ROM or custom recovery and it would say would pass but it would just boot loop and boot loop. So I read somewhere where you can put it in the oven for around 5 to 6 minutes at about 200° and that it would settle any of the cracked solder that be around the emmc or anywhere else on the board. So I tried it. I stuck it in two different times at five minutes a piece, pull the board out and let it set for a day. I installed the board just a little while ago and she fired right up. It's amazing

I've recently replaced the motherboard on my N910F with a used one bought from AliExpress. As it's used I've no idea how long it will last but for £30 was worth a try.
It was pretty straightforward replacing the motherboard using one of the tear down guides on YouTube.

Anyway to retrieve data from a *dead* LeEco Le Pro3 (x727)

I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?

easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
No fastboot or custom recovery ?
Then no theirs nothing really to do
Maybe a battery replacement would boot it up
Sent from my ONEPLUS A6010 using Tapatalk

No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?

easyxpress said:
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
Click to expand...
Click to collapse
Nope it's just a chip on a circuit board
Sent from my ONEPLUS A6010 using Tapatalk

easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.

twistyplain said:
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
Click to expand...
Click to collapse
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph

easyxpress said:
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
Click to expand...
Click to collapse
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.

twistyplain said:
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
Click to expand...
Click to collapse
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph

easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
what happened to TWRP ? thats stock recovery
will it enter fastboot mode ? if you can get into TWRP their is a chance of off loading your userdata to a PC

easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Sent from my LeMobile Le X526 using XDA Labs

twistyplain said:
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Click to expand...
Click to collapse
Sorry bad news.
As twistyplain said, your phone is absolutely fried, and there is no solution.
It's definitely no brick, that is a hardware issue... Most likely shorted solder connections. The same thing happened to two of our X727s, we have one left that still works.
I highly recommend buying a seemingly unbrickable Xiaomi phone. Their budget models are awesome and of course their flagships are awesome. Everyone in my family has Migrated to Xiaomi . I currently have Android 10 working flawlessly.

Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph

easyxpress said:
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
Click to expand...
Click to collapse
If you are in China and located in a large city or tech industrial area you should have plenty of shops that repair at the component level.
Your phone could very likely be repaired by a shop that has a hot air rework soldering station with an electron microscope.
We used to have these types of places in the US but they have all gone out business, replaced by board swappers, who charge a lot. I would suspect that you could get it repaired in China for 100 yuan or less.
I worked in Beijing for 3 months, about 18 years ago and these types of places were everywhere.

8227L HU: can it go to sleep mode after power off?

so i have a Chinese 8227L based touch only head unit, and as it is a chinese HU it comes with a custom rom.
i was wondering if the head unit can go to sleep mode instead of shutting down when shutting the car down.
just like our phones and tablets go into sleep mode.
i hate the wait for the unit to boot up, while it could be in sleep mode and just directly pop into live..
after asking the vendor for this option the simple answer was: no it is not possible since the HU does not have an internal battery.
but the HU is a part of my car, and my car has a big battery after all.. the HU has a constant 12V and a switched (acc) 12V..
so why can't it go to sleep (shut down screen, go into low power/hibernation and shut down power to usb) since it still has 12V power?
does anyone know of a rom/firmware that has this option for my 8772L unit?
specs:
model: 8227L
android version: 9 (haven't checked if that's actual android 9)
kernel version: 3.18.79 (gcc version6.3.1 20170404(linaro GCC 6.3-2017.05))
[email protected] #27
build number: full_8227L_demo-userdebug 9 011019 1550113051 userdebug

You have 3 power cable
Black is the ground
Red is the power
Yellow is the memory
I think that you have linked yellow and red
You need to find the same power cable on you car. If you link correctly the cable you will have the sleep of unit when you switch off your car
Inviato dal mio Mi 9T utilizzando Tapatalk

nokian95ita said:
You have 3 power cable
Black is the ground
Red is the power
Yellow is the memory
I think that you have linked yellow and red
You need to find the same power cable on you car. If you link correctly the cable you will have the sleep of unit when you switch off your car
Inviato dal mio Mi 9T utilizzando Tapatalk
Click to expand...
Click to collapse
thanks for your reply!
that's what i thought the first time it shut down..
so i swapped the wires..
it would shut down and loose all settings for the radio, the time and date, etc etc..
i think is a software setting that i can't set.

Accessibility > enable quickboot

shezi2243 said:
Accessibility > enable quickboot
Click to expand...
Click to collapse
thanks for your reply :good:
but i can;t find that setting..

dutchcommando said:
thanks for your reply :good:
but i can;t find that setting..
Click to expand...
Click to collapse
I went round and round with Pumpkin on their 8227 implementation. The only thing you can do is delay the shutoff from 0 to 120 minutes, with several different choices.
If you go past that clock time, it will reboot when you start up. Major design flaw.

bossman4 said:
I went round and round with Pumpkin on their 8227 implementation. The only thing you can do is delay the shutoff from 0 to 120 minutes, with several different choices.
If you go past that clock time, it will reboot when you start up. Major design flaw.
Click to expand...
Click to collapse
AH!
That is something i can work with! thanks..
or rather, not work with for longer than 120 minutes ..
but at least i can have stuff updated over wifi if the car parked near my house (wifi router) especially off line maps and such..
now i have to sit in the car with the keys in and wait for updates to finish..
btw: cpu-Z tells me it's a real android 9 pie, and not a spoofed 8 or 8.1 go android. :laugh: