Moto G6 Plus (XT1926-8) without wifi and mobile network - Moto G6 Plus Questions & Answers

Hello everyone,
my Moto G6 Plus does not detect wifi or mobile networks.
This happened when I rooted the smartphone and after testing what I wanted, I tried flashing the original Motorola rom and after that, blocked the bootloader again.
When the smartphone restarted, I noticed that it does not detect wifi or sim card and consequently does not detect mobile networks.
I tried flasing other roms to the smartphone, but the messages I get: permission denied
I tried more than 50 roms, it didn't work.
I installed Gnirehtet and can connect to the internet, but the OEM Unlock option remains grayed out.
Does anyone have any tips on how to revive my smartphone?
Current Android version: 8.0.0
Patch Level: november 1, 2018
Baseband version: Unknown
Kernel version: 4.4.78
Build number: OPWS27.113-92-5
Thanks in advance.

adaoduque said:
Hello everyone,
my Moto G6 Plus does not detect wifi or mobile networks.
This happened when I rooted the smartphone and after testing what I wanted, I tried flashing the original Motorola rom and after that, blocked the bootloader again.
When the smartphone restarted, I noticed that it does not detect wifi or sim card and consequently does not detect mobile networks.
I tried flasing other roms to the smartphone, but the messages I get: permission denied
I tried more than 50 roms, it didn't work.
I installed Gnirehtet and can connect to the internet, but the OEM Unlock option remains grayed out.
Does anyone have any tips on how to revive my smartphone?
Current Android version: 8.0.0
Patch Level: november 1, 2018
Baseband version: Unknown
Kernel version: 4.4.78
Build number: OPWS27.113-92-5
Thanks in advance.
Click to expand...
Click to collapse
Hello, try blankflashing or waiting 7 days with phone on and try to update it after.

mrsiri said:
Hello, try blankflashing or waiting 7 days with phone on and try to update it after.
Click to expand...
Click to collapse
Hello mrsiri, thanks for replying.
I waited more than 3 months, without restarting / turning off the smartphone and did not unlock the option to OEM Unlock.
Do you have a link that I can download a blankflash that works on this smartphone model?
Thanks in advance.

adaoduque said:
Hello mrsiri, thanks for replying.
I waited more than 3 months, without restarting / turning off the smartphone and did not unlock the option to OEM Unlock.
Do you have a link that I can download a blankflash that works on this smartphone model?
Thanks in advance.
Click to expand...
Click to collapse
That won't be toggleable for any time. Can you not update phone like regular OTA? or you're on latest version?
Blankflash link: https://mirrors.lolinet.com/firmware/moto/evert/

mrsiri said:
That won't be toggleable for any time. Can you not update phone like regular OTA? or you're on latest version?
Blankflash link: https://mirrors.lolinet.com/firmware/moto/evert/
Click to expand...
Click to collapse
Currently, Android 8.0 is installed.
When I check for updates, the system informs me that it has no updates.
I will test the blankflash and come back with the result

It says phone is updated or system is compromised? On my phone it used to show any new updates and let me install it too. There were no additional problems when updating. Same problems persisted during updates until the last pie update, which fixed my phone.

mrsiri said:
It says phone is updated or system is compromised? On my phone it used to show any new updates and let me install it too. There were no additional problems when updating. Same problems persisted during updates until the last pie update, which fixed my phone.
Click to expand...
Click to collapse
I installed the android 8.0 ROM on this phone.
My failure was after installing this ROM, executing the bootloader lock without first checking that everything was OK with the phone.
Blankflash say: < waiting for device >
... and nothing happens.
I tried EDL mode, but the smartphone restarts for the operating system.
Any ideas on how I could get this device into EDL mode so I can install the blankflash ?
Thanks in advance.

adaoduque said:
I installed the android 8.0 ROM on this phone.
My failure was after installing this ROM, executing the bootloader lock without first checking that everything was OK with the phone.
Blankflash say: < waiting for device >
... and nothing happens.
I tried EDL mode, but the smartphone restarts for the operating system.
Any ideas on how I could get this device into EDL mode so I can install the blankflash ?
Thanks in advance.
Click to expand...
Click to collapse
You have to open back of the phone and short circuit the test points in the circuit board

Related

Installing new os in zuk z1

Hi... I have updated my phone to LineageOS successfully but I lost fingerprint option. I'm getting system update options in Settings but when I tried to update the stuck in bootloop and I was able to get it to work by entering some codes in this forum... First, I have unlocked the bootloader and rooted my phone and installed TWRP and flashed LineageOS. All went good but I lost the fingerprint option and auto rotate and some features are not working properly. If I want to update it again to the latest version, do I have to unlock bootloader, root again? Please help... My phone was good before I updated it
Kishorechittem said:
Hi... I have updated my phone os successfully but I lost fingerprint option. My concern is how to update os again as I have already unlocked bootloader and rooted my phone
Click to expand...
Click to collapse
Which os did you update and which rom was it before. Please tell exact versions and if you have the regarding links.
Normally that happens without the right firmware like marshmallow before installing a nougat rom. But let's see what's the problem of yours.

PH-1 not seeing OTA updates

I can't seem to get the OTA. I've been on 7.1.1 this whole time (rooted with TWRP/Magisk) and have been waiting for the official 8.1 to be released.
I just flashed the full back-to-stock for 7.1.1 (using invisiblek's images), but after completing successfully, the OTA doesn't show up. I'm on T-Mobile, and I've confirmed that I no longer have root or TWRP recovery.
In fact, I noticed that there doesn't seem to be a recovery at all anymore (lying down droid). Is that normal? Is the stock recovery required for the OTA to be received? How do I get that back? TIA
Also, my bootloader is unlocked. Is that the issue? TIA.
bryanus said:
I can't seem to get the OTA. I've been on 7.1.1 this whole time (rooted with TWRP/Magisk) and have been waiting for the official 8.1 to be released.
I just flashed the full back-to-stock for 7.1.1 (using invisiblek's images), but after completing successfully, the OTA doesn't show up. I'm on T-Mobile, and I've confirmed that I no longer have root or TWRP recovery.
In fact, I noticed that there doesn't seem to be a recovery at all anymore (lying down droid). Is that normal? Is the stock recovery required for the OTA to be received? How do I get that back? TIA
Also, my bootloader is unlocked. Is that the issue? TIA.
Click to expand...
Click to collapse
Different carriers allow updates at different times.
Unlocked BL won't matter.
Try connecting to WiFi.
tech_head said:
Different carriers allow updates at different times.
Unlocked BL won't matter.
Try connecting to WiFi.
Click to expand...
Click to collapse
By different carriers, it means Sprint
Sent from my PH-1 using XDA Labs
avd said:
By different carriers, it means Sprint
Click to expand...
Click to collapse
Easily overcome...
I'm with Sprint and my phone updated OTA yesterday.
My phone is unlocked and unrooted.
Thanks guys. OK, I'll wait a bit longer. I've already removed/reinstalled my t-mobile sim and connected via Wifi, but still no updates showing. Not getting any Nougat security patches either (I'm still on the Dec patch).
Anyone still having these issues? I'm stuck on 7.1.1 still and OTA is not showing 8.1. Tried removing and reinserting the sim & a factory, reset, but still no dice.
When I try to download the latest build on essential's webpage, I get this error:
AccessDeniedAccess denied.Anonymous caller does not have storage.objects.get access to essential-static/PH1-OTA-OPM1.180104.092.zip "Android 8.1 Oreo (OPM1.180104.092).
Solved... Telus/Koodo in Canada is just terrible with software updates. For some reason, just removing the SIM didn't do it and I had to insert a SIM card from a different carrier entirely. Worked immediately without even clearing data or restarting the phone!
hi Guys,
I have different problem. my phone is 100% stock. i bought it in china where i live. phone sees the may update, but it never starts downloading. always tries tries and then automatically pauses. both on wifi and lte. i'm on oreo 8.1 with april updates. any ideas?
collller said:
hi Guys,
I have different problem. my phone is 100% stock. i bought it in china where i live. phone sees the may update, but it never starts downloading. always tries tries and then automatically pauses. both on wifi and lte. i'm on oreo 8.1 with april updates. any ideas?
Click to expand...
Click to collapse
Ad blocker on the phone like Blockada active?
collller said:
hi Guys,
I have different problem. my phone is 100% stock. i bought it in china where i live. phone sees the may update, but it never starts downloading. always tries tries and then automatically pauses. both on wifi and lte. i'm on oreo 8.1 with april updates. any ideas?
Click to expand...
Click to collapse
Download the current build fro Essential https://www.essential.com/developer/current-builds and reflash. Backup first of course

CRG1 OEM Unlock?

Hi all, I have a G955F and upgraded it to CRG1. The problem is that there is no OEM unlock toggle to be found in the Developer Options section. I've tried to bypass the 7 day wait by changing dates and that didn't work. Is there any other process I could try besides waiting 7 days? All help is appreciated, apologize if this has been posted before.
It should be there.... I say u should wait for 7 days.
khawarjaved said:
It should be there.... I say u should wait for 7 days.
Click to expand...
Click to collapse
I found a way to get it back. Thank you for replying, though.
Soapy! said:
I found a way to get it back. Thank you for replying, though.
Click to expand...
Click to collapse
how did you get it back? i have tried some methods and none work.. though i am s9.
Soapy! said:
I found a way to get it back. Thank you for replying, though.
Click to expand...
Click to collapse
So can you pls tell us what solution you found. I'm facing the same Problem
Soapy! said:
I found a way to get it back. Thank you for replying, though.
Click to expand...
Click to collapse
Mental fireballs in your direction.
Sorry guys, I didn't get a notification for your replies. All I did was reflash my phone's firmware and then performed the calendar date trick.
I didn't get the OEM unlock option even after the 7 days wait, I am on latest firmware CRGH, can anyone help me out here??
Hariiii said:
I didn't get the OEM unlock option even after the 7 days wait, I am on latest firmware CRGH, can anyone help me out here??
Click to expand...
Click to collapse
Reflash CRGH FW via Odin, keep Sim in, perform date trick. BTW skip all account setup prompts after reflashing FW
Soapy! said:
Reflash CRGH FW via Odin, keep Sim in, perform date trick. BTW skip all account setup prompts after reflashing FW
Click to expand...
Click to collapse
Should I flash HOME_CSC or CSC ??
Soapy! said:
Hi all, I have a G955F and upgraded it to CRG1. The problem is that there is no OEM unlock toggle to be found in the Developer Options section. I've tried to bypass the 7 day wait by changing dates and that didn't work. Is there any other process I could try besides waiting 7 days? All help is appreciated, apologize if this has been posted before.
Click to expand...
Click to collapse
Try
1.set day 10 ago (dis automatic)
2.dis download updates automatic
3.click download updates manually
4.reboot
5.set day 10 ago agin
6.check OEM
Soapy! said:
Reflash CRGH FW via Odin, keep Sim in, perform date trick. BTW skip all account setup prompts after reflashing FW
Click to expand...
Click to collapse
I tried flashing CRG1 and CRGB as well as CRGH, I am not able to get the oem unlock option after the date trick. Any help??
So I am thinking to stick to the old firmware with bootloader version 3, can you tell me which one is older CRG1 or CRGB??
New Update
I again refalshed CRG1 which is the older one with bootloader version 3, then I tried this date trick, first it actually did not work. So I tried and monitored my procedure every time. It worked finally. Here is the step by step guide,
1. Reflash the firmware and skip all account setups
2. Now change the date 20 days back
3. Now go and enable developer options
4. Check for OEM unlock(probably won't be there), now disable Auto update system
5. Software update option, disable automatic updates
6. Click on update manually(now you will see registering device toast message and a persistent device configuration notification), it will show you there is an update based on your region(I downloaded Poland region firmware). Most of the post about OEM unlock says you will get an error here due to date issue, but you won't get any errors.
7. Now do this step as fast as you can, again check for OEM option in developer settings((probably won't be there)), and reboot.
8. You should again see the persistent device configuration notification, Turn off wifi/data immediately. Now your date must have probably changed to current date even though you changed it earlier, change the date again, now when the notification goes off, go to software updates, turn the data/wifi on. check for software updates.
9. Now go to developer options you should see OEM unlock option.
If it doesn't work, shuffle up the step 8 instructions, like check for software updates first, then change the date and vice versa.
Samsung got a ****ty logic written under the code over there, but its messy. So I tried this multiple times just to make sure no one else end up with this issue. It worked for me probably it should work for others.
Better download the Poland firmware CRG1 and try it.
Thanks.
credits to @soapy
U dont need trial and error for this.
1. Enable developer options and check if OEM Unlock is already visible, if not proceed below.
2. Disable auto software update and mobile data to prevent auto date correction.(Leave wifi on)
3. Adjust your datetime to previous dates, let's say Month of May 15th, 2018.
4. Do Software Update manually, do multiple taps so that Software Update process will appear.
5. It should display an error in software update.(Let if fail)
6. Reboot
7. Once rebooted, change the datetime to older dates.(since date will revert back to present)
8. OEM Option should be in the developer options.
Im using the CRGH build, and it never fails me. never waited for 7+days idle phone,no trial and error, I just follow the simple steps above and OEM Unlock never disappears in my end , it was never "patched" as others have told.
Using XTC/SMA/GLB region firmware CRGH build, SM-G950FD..
Note:
I reverted back to stock due to NETFLIX and other related streaming premium apps not playing HD+ content. No workaround or permanent solution on this yet. I'm paying premium 4K hd content so it would be a waste of money playing netflix content on rooted device with just SD video.

Really Tricky Problem

Hello people!
I've been doing installation of custom ROM and any kind of configuration for a while now. But I have now in my hands a tough problem. My dad bought athene XT1640-DS (Moto G4 Plus), just like the one of mine own, but mine doesn't have the '-DS'.
But the device is stuck at Stock Android 6.0.1 and I can't update it.
The USB seems have some problem because any PC in my house recognize the 6.0.1 phone, but works fine with my up to date 8.1.0 athene, but it's charging only, and the turbo charging isn't working. the fingerprint isn't working neither.
It looks like the bootloader was unlooked, because everytime it's turned on shows the 'bootloarder unlock message'. But I was unable to root it, I tried all the one click root apps, but none of them worked.
It doesn't have any custom recovery, so I tried to update with the stock recovery but every OTA Blur Version rom that I found for athene shows a error telling that my ROM version isn't compatible with the updates (the ROM version code of this phone is MPJ24.139-23.1/ 1 user).
Anyone have any hints of what can I do to update this device?
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
From what I know one click methods doesn't work with this device. You need a proper kernel for android 6.0 like elementalx 1.0. And supersu or magisk zip flashed through a recovery like TWRP.
Is there a way to update de kernel, or do that other things without PC and root?
Or a way to use adb without USB connection?
Have you tried fastboot flash methods like in this thread?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
So.. the big issue is that this device isn't connecting to the PC, it's charges, but neither the PC not the Android show any signs that their are connected. I can't use adb from the PC because I couldn't make the computer recognize the phone.
can you at least transfer files in mtp mode with the usb cable? because looks like the micro usb port is messed up.
If you are on warranty period you should go for it
I can't use the mtp neither. The only thing I can do is charge. And I'm out of warranty :/

Device not starting/black screen after stock-ROM flash via Odin

Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want
Thanks a lot, this worked!
tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself

Categories

Resources