I have a moto g4 plus on nougat 7.0 september update and suddenly it gave me the system UI stopped working and the screen went black (The ambient display is working and when I use the gesture of the flashlight it works) despite the nothing works and the screen remains black. I tried to reset the phone from the bootloader but every time the phone starts normally to this problem.
Thank you in advance.
omar_yasser said:
I have a moto g4 plus on nougat 7.0 september update and suddenly it gave me the system UI stopped working and the screen went black (The ambient display is working and when I use the gesture of the flashlight it works) despite the nothing works and the screen remains black. I tried to reset the phone from the bootloader but every time the phone starts normally to this problem.
Thank you in advance.
Click to expand...
Click to collapse
Flash the following rom(it is stock of September security) via bootloader.
Read the disclaimer properly and all the steps too, flash lock bootloader only(if you haven't yet unlocked it).
Link : goo.gl/3BQwd4
DgnrtnX said:
Flash the following rom(it is stock of September security) via bootloader.
Read the disclaimer properly and all the steps too, flash lock bootloader only(if you haven't yet unlocked it).
Link : goo.gl/3BQwd4
Click to expand...
Click to collapse
Thank you and sorry because I didn't thank yoi sooner.
Related
[HELP THREAD] Stuck in a "Your device has been unlocked and can't be trusted" loop
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
lologke said:
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
Click to expand...
Click to collapse
Ask and answered yesterday in help thread for example. Please have a look at here and the posts before and after https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post72528225 for the message at boot.
Because of your bootloop after displaying of the message your device can't be trusted": why you install the abandoned cm14.0? Use newer LineageOS or other supported roms instead of that discontinued one.
I think it's because of the newer twrp maybe. Did you tried an older version like twrp 3.0.2? Did you tried installing the rom without gapps? Maybe the gapps doesn't play well with the old rom?
I got same problem but i solved it.. if u need to solved this problem Flash your device. It works 100%.^_^
Mariashaik said:
I got same problem but i solved it.. if u need to solved this problem Flash your device. It works 100%.^_^???
Click to expand...
Click to collapse
If you have nothing useful to say, say nothing. It can irritate new users.
I guess you should try some other ROM as suggested! You can go to Recovery by using Power+vol down Button for 5 sec... that should take u to bootloader and then recovery and other options!
Let me know if that works!
Ummm.. just read the post again... moto g4 plus (12 GB)... I hope that's a typo!
lologke said:
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
Click to expand...
Click to collapse
umm. why do you flash unofficial cyanogenmod instead of lineageos?
Try flashing the latest roms, with latest twrp and see if it works or not. If it still doesn't, flash stock ROM and start again. I hope you have a backup made.
My Moto G4 plus has peculiar problem
1.) when i switch on Hello moto boot animation with sound and after few seconds i cant hear any audio from my phone speaker.
2.) Later when i reboot my device in safe mode, my adudio is working fine and i could able to hear music.
If it is a hardware issue , speaker will not work in safe mode right. except speaker everyting is fine in normal mode. it is happing all of the sudden. my warrenty is over can anybody help me
san.a703 said:
My Moto G4 plus has peculiar problem
1.) when i switch on Hello moto boot animation with sound and after few seconds i cant hear any audio from my phone speaker.
2.) Later when i reboot my device in safe mode, my adudio is working fine and i could able to hear music.
If it is a hardware issue , speaker will not work in safe mode right. except speaker everyting is fine in normal mode. it is happing all of the sudden. my warrenty is over can anybody help me
Click to expand...
Click to collapse
I think its caused due to some installed apps in your phone, because in safe mode 3 rd party apps (i.e other than system apps) is disabled. If you factory reset everything will be fine , I think (THINK AND DO) IS your device rooted, or running any custom ROM . Please give more information.
san.a703 said:
My Moto G4 plus has peculiar problem
1.) when i switch on Hello moto boot animation with sound and after few seconds i cant hear any audio from my phone speaker.
2.) Later when i reboot my device in safe mode, my adudio is working fine and i could able to hear music.
If it is a hardware issue , speaker will not work in safe mode right. except speaker everyting is fine in normal mode. it is happing all of the sudden. my warrenty is over can anybody help me
Click to expand...
Click to collapse
try to hard reset your phone, it may-be resolve your problem.
or just flash stock ROM using fastboot, but it needs unlocked boot-loader.
siddhesh9146 said:
just flash stock ROM using fastboot, but it needs unlocked boot-loader.
Click to expand...
Click to collapse
Please do not spread false information. Flashing a stock ROM does NOT require an unlocked bootloader, because, if I'm not wrong, those files are signed by Motorola.
zeomal said:
Please do not spread false information. Flashing a stock ROM does NOT require an unlocked bootloader, because, if I'm not wrong, those files are signed by Motorola.
Click to expand...
Click to collapse
Flashing anything from Fastboot requires unlocked bootloader. It's not false. Now you are the one who is spreading false info
siddhesh9146 said:
Flashing anything from Fastboot requires unlocked bootloader. It's not false. Now you are the one who is spreading false info
Click to expand...
Click to collapse
Flashing a stock ROM or any image signed by Motorola DOES NOT require an unlocked bootloader. Try it on your own before you accuse another of spreading false information. I've flashed stock ROMs on locked Motorola devices, so I told you that the information you supplied was false. I was merely unsure of the reason (the signed images).
How do you think most customer care servicing takes place? First thing they do is flash a stock ROM. On a locked bootloader. They have no special facility to unlock and lock as per the need without voiding warranty.
Why are stock images so important? Because they act as a basic fail-safe. Your phone gets messed up, easiest way to get it fixed (assuming it isn't hard-bricked) is to flash the stock ROM.
Hi guys, i will try a solution for this bug, but i need of the folder proc/asound, can anyone disponibilize for me?
Sorry my bad english, i'm brazilian.
Just flashed my XT1622 (UK Moto G4, NOT the plus version) using Nougat stock rom with September security patch(https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138). Thanks @tywinlannister7 who made the guide. It worked smoothly although it's in Moto G4 Plus forum.
Now, I got some questions regarding root. I did a forum search to find the post (https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918), which is quite good actually. However, I flashed my xt1622 for two reasons. The first is to upgrade to the latest system - Nougat (well, it not 'the latest' at the moment). The second is because I flashed TWRP on Marshmallow immediately after buying my Moto G4 to get root access, which stopped me to update the phone via OTA for a long time. I can still get the OTA notification, but it just won't let me update - failed after ~20 minutes. So what I did is just manually delay the update notification for 24 hours every day at 12.00pm. It bothered me a lot so I decided to go for a clean flash.
By flashing the new system, I lost some features I used quite a lot.
1. The root access for sure. I am not going to flash TWRP this time in case new patches would come over OTA again. If I flashed TWRP, I will face the same issue as I was on Marshmallow before this flashing. Is it possible to root without flashing TWRP that stops me to update over OTA?
2. I used to flash a specially made logo.bin to prevent the unlocked bootloader screen to appear. Now on Nougat, is there any similar logo.bin to do the same? A download link would be appreciated.
3. I used Llama with different profiles for some automated work such as change alarm volume at home or at workplace, make the phone ring loudly everywhere else, switch to flight mode at 12.00am at midnight and go back at 6.00am in the morning, automatically restart my phone at 1.00am while I am sleeping, and so on. This app won't work properly without root access. - well, looks like we go back to the first question of gaining root access.
Thanks for reading anyway.
Okay guys firstly i have a hope that some one would definitely help to come out of this ....
lets directly jump into the matter
i unlocked boot loader started using Custom ROM everything was fine until i got this into my mind
planned to re flash the stock rom and to be honest i had a november patch before flashing Lineage 15.1 custom ROM or unlocking boot loader and i totally forgot to Take a back up of my Nougat 7.1.2.
Today morning when i Flashed stock Rom for my device it booted up properly, but there was no service when i checked my IMEI they were 0 and asked for an update due to wifi connectivity .. Okay this is where the problem started i used
i downloaded the update and i just gave install then it restarted and went to the boot loader saying installing updates then my phone is switched off in half way ... now when i connect it to my PC it just makes noise like it is connected but when i try to switch on it is no switching on ..... when i put for charge notification light next to the speaker keeps blinking .....
is it hard bricked ?? or is it my phone dead or literally i cannot do anything at all ?
Please........
Any help would be appreciated
not able to switch on my phone
please delete this thread ... i fixed my issue
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Visseroth said:
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Click to expand...
Click to collapse
If you took the time to the dirty santa thread then you'd know that your phone's security patch date is date where ds has been patched, you need to be on a security patch date prior to Dec 2016
Sent from my LG-H910 using XDA Labs
Now I remember why I didn't post on these threads much. People just assUme that the posting person is a COMPLETE idiot.
This is a HELP forum where people come to get HELP and information, there's no reason to point fingers. A simple, "BTW that version you're running is a patched version, you'll need to roll it back to a prior, follow these links..." version would have done just fine.
With that I'd reply........
I realized I needed a older firmware last night when I was fighting with it for hours. I rolled it back to a firmware, dated 12-24-2016 and managed to get BadSanta to work but it caused my phone to go into a non-stop vibrate, it wouldn't complete boot and was basically bricked. I then found from another site that explained EXACTLY how to put the phone in download mode and then re-flashed the ROM (BTW, for those that don't know, you power off, hold the volume up and then plug in your data cable) but then put Android 7.0 Build number NRD90M.
The problem I am running into is everyone's information isn't is sync.
Some say how to proceed but don't say on what build number to proceed.
Some say to roll back to Android 7 Naugut but don't say which version because there are many versions of that version.
Personally I don't understand why a ROM can't be flashed via the download mode but then again I'm not a programmer.
So with that, after many hours I've made some progress but I am disappointed in how complicated and time consuming it is. I'm seriously considering a Pinephone for me and this phone (once completed) for my wife.
Right now I'm in the process of following this thread....
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Later, after I get some work done.
Thanks for the reply though.
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Visseroth said:
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
The vibration is normal if it's the VS995, which I'm sure you are using, right?
And the phone is not bricked, it's normal to see that warning at the start-up screen (about the device being corrupt....). Just be patient and give it time to boot.
The scrambled screen (static on boot) is also normal, just flash lineage 17.1, afaik it doesn't have static on the vs995
On a side note: double check the dirtysanta thread, you'll find most of these there
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Visseroth said:
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Click to expand...
Click to collapse
On stock, after it is done booting, press the power button once to turn off the main screen, then cover the upper left corner with your hand till the second screen turns off (abt 5 - 7 sec). Turn the screen back on and use your phone.
About lineage,