my device moto g4 plus xt1643 7.0 unrooted after a bootloader unlocked turn off automatically without caution then turn on manually when I use it sometimes opening a app sometimes incoming calls I tired restore,changed different roms and full reset but I have the same problem why is this coming...?
You security patch seems to be too old and try to elemental x kernel that might sort the problem
My G4 just started with this problem too. When I get a text on using random app. Stock rom, lock bootloader
Related
1st off I've been on XDA for many years and this Sub-forum confuses the hell out of me. Threads are cluttered with talk over all the variants of the G4 which confused me on what I could do with my device. That being said here is my issue...
I just got a XT1625 G4 and proceeded to try to get the adds removed. Reading this thread. It failed so it said to unlock the bootloader via getting a key from Moto which they let me do and I am unlocked according to the boot screen warning and fastboot info reporting "flashing_unlocked".
I then ran the script again but the device was unable to boot and went straight into recovery with it reporting at the bottom "WE HAVE DETECTED AN ATTEMPT TO FLASH UNAUTHORIZED SW ON YOUR DEVICE. CONTACT CUSTOMER SERVICE FOR ASSISTANCE." which I fixed by following this thread
Now reading more users say that this device can not have the bootloader unlocked (um mine is) and that amazon/moto have patched removing adds. Not sure what is true so I need some clarification.
Ideally I want to just flash a stock rom with no adds if possible and receive ota updates...can i?
OR remove the adds on the amz rom and get ots updates.
This phone is not for me so i dont want to have to fix it all the time. If this is not possible im going to send this amazon virus infected phone back....
I would honestly spring for the normal xt1625, you can even flash the nougat update on it since it's the xt1643 with a lower camera, no laser focus, and no fingerprint reader.
I got mine at best buy and did unlocks with no issues. It's definitely an Amazon thing. Like my old Moto g on Verizon I couldn't unlock.
Hi,
I just installed Resurrection Remix on my X Style and realiced that there were no text coming in (for the double step auth) so I decided to reboot my phone. When I did I saw that the network icon was empty like in no connection. Trying to call or text will display "Mobile network not available". I also tried with Ground Zero and same thing. It connects for 2 minutes on the very first boot but then it begins to fail.
This is the first time I'm flashing my Moto X with a custom ROM. I opened the bootloader and rooted the device previously to get Xposed (a couple of weeks ago) so I don't know what might be failing. When trying to flash the only error that TWRP shows is that he couldn't write to a log file but that's all. What can I do to solve this? Are there different Moto X style models and should I flash something on top of it? (I had a Z2, that's why I am asking that). Previously flashed my One Plus X and my Xperia Z2 without any issues.
Any help will be highly appreciated. In the mean time I'll try to go back to stock MM
Edit: I went back to stock. Nothing happened. I tried LineageOS and still nope. It only catches like a minute or two of signal and then goes down. Can't make or receive calls or texts. Can't do 2step auth... Can't do anything. Should I call for guarantee after I relock the bootloader? I've only seen three people with this issue. One of them solved it by flashing stock and the other one idk. This shouldn't be happening, right?
and_buitrago said:
Hi,
I just installed Resurrection Remix on my X Style and realiced that there were no text coming in (for the double step auth) so I decided to reboot my phone. When I did I saw that the network icon was empty like in no connection. Trying to call or text will display "Mobile network not available". I also tried with Ground Zero and same thing. It connects for 2 minutes on the very first boot but then it begins to fail.
This is the first time I'm flashing my Moto X with a custom ROM. I opened the bootloader and rooted the device previously to get Xposed (a couple of weeks ago) so I don't know what might be failing. When trying to flash the only error that TWRP shows is that he couldn't write to a log file but that's all. What can I do to solve this? Are there different Moto X style models and should I flash something on top of it? (I had a Z2, that's why I am asking that). Previously flashed my One Plus X and my Xperia Z2 without any issues.
Any help will be highly appreciated. In the mean time I'll try to go back to stock MM
Edit: I went back to stock. Nothing happened. I tried LineageOS and still nope. It only catches like a minute or two of signal and then goes down. Can't make or receive calls or texts. Can't do 2step auth... Can't do anything. Should I call for guarantee after I relock the bootloader? I've only seen three people with this issue. One of them solved it by flashing stock and the other one idk. This shouldn't be happening, right?
Click to expand...
Click to collapse
*BEST* Answer is to restore your TWRP backup and get out of that rom! If you do not have a TWRP backup (Shame on you!) your only other choice is to flash stock firmware and then go from there. This time, ALWAYS make a TWRP backup before you to, *anything*!
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.
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.
this message started to appear after I tried to install an updated rom on my g6 plus, my smartphone has the bootloader unlocked so I had to try to install the updated rom
If you are forcing the update installing from an local .zip file like anyone in mirrors.lollinet always appears because that SO isn't signed by Motorola. So you can't do anything. It never will disappear, but it not mean you have a big problem, it just say you are out of warranty