• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Bootloader Unlock & Back to Stock for Motorola E4 Plus "owens"

Here's a log from magisk

01-01 07:38:51.210 444 444 I Magisk : Magisk v17.3(17302) daemon started
01-01 07:38:51.233 449 449 I Magisk : Magisk v17.3(17302) logger started
01-01 07:38:51.233 444 445 I Magisk : ** post-fs-data mode running
01-01 07:38:51.234 444 445 I Magisk : * Mounting /data/adb/magisk.img
01-01 07:38:51.267 444 445 E Magisk : mount /sbin/.core/block/loop08->/sbin/.core/img failed with 13: Permission denied
01-01 07:38:51.272 444 445 I Magisk : * Running post-fs-data.d scripts
01-01 07:38:51.279 444 457 I Magisk : * Starting MagiskHide
01-01 07:38:51.279 444 457 I Magisk : hide_utils: Hiding sensitive props
01-01 07:38:51.279 444 457 I Magisk : hide_list add: [com.google.android.gms.unstable]
12-05 15:33:41.891 444 766 I Magisk : ** late_start service mode running
12-05 15:33:41.891 444 766 I Magisk : * Running service.d scripts
12-05 15:34:28.441 444 457 I Magisk : proc_monitor: com.google.android.gms.unstable
12-05 15:34:55.636 444 457 I Magisk : proc_monitor: com.google.android.gms.unstable
12-05 15:39:57.113 444 8171 I Magisk : hide_list add: [com.nianticlabs.pokemongo]
12-05 15:40:03.935 444 457 I Magisk : proc_monitor: com.google.android.gms.unstable
 
insanetoker89 said:
Here's a log from magisk

01-01 07:38:51.210 444 444 I Magisk : Magisk v17.3(17302) daemon started
01-01 07:38:51.233 449 449 I Magisk : Magisk v17.3(17302) logger started
01-01 07:38:51.233 444 445 I Magisk : ** post-fs-data mode running
01-01 07:38:51.234 444 445 I Magisk : * Mounting /data/adb/magisk.img
01-01 07:38:51.267 444 445 E Magisk : mount /sbin/.core/block/loop08->/sbin/.core/img failed with 13: Permission denied
01-01 07:38:51.272 444 445 I Magisk : * Running post-fs-data.d scripts
01-01 07:38:51.279 444 457 I Magisk : * Starting MagiskHide
01-01 07:38:51.279 444 457 I Magisk : hide_utils: Hiding sensitive props
01-01 07:38:51.279 444 457 I Magisk : hide_list add: [com.google.android.gms.unstable]
12-05 15:33:41.891 444 766 I Magisk : ** late_start service mode running
12-05 15:33:41.891 444 766 I Magisk : * Running service.d scripts
12-05 15:34:28.441 444 457 I Magisk : proc_monitor: com.google.android.gms.unstable
12-05 15:34:55.636 444 457 I Magisk : proc_monitor: com.google.android.gms.unstable
12-05 15:39:57.113 444 8171 I Magisk : hide_list add: [com.nianticlabs.pokemongo]
12-05 15:40:03.935 444 457 I Magisk : proc_monitor: com.google.android.gms.unstable
Click to expand...

I'm still using magisk v17.1 with no problems..
 
kachman said:
hi, its on stock firmware
Click to expand...

Try reflashing official Stock FW, that should normally fix any modem issues.. Are you using another carrier than Sprint/Boost Mobile?

Edit: make sure ya use the same FW as is labeled in your device Settings-AboutPhone
 
bcrichster said:
Try reflashing official Stock FW, that should normally fix any modem issues.. Are you using another carrier than Sprint/Boost Mobile?

Edit: make sure ya use the same FW as is labeled in your device Settings-AboutPhone
Click to expand...

hi i just mentioned earlier that am using stock firmware ;-). I flashed the xml stuff and all. I even did some OTA updates after that and still didn't solve it. Or maybe do you have a way of sim-unlocking it that works with latest firmware?
 
kachman said:
hi i just mentioned earlier that am using stock firmware ;-). I flashed the xml stuff and all. I even did some OTA updates after that and still didn't solve it. Or maybe do you have a way of sim-unlocking it that works with latest firmware?
Click to expand...
and yes am using a gsm simcard, no sprint
 
kachman said:
and yes am using a gsm simcard, no sprint
Click to expand...

Hrmm..
- Which Carrier?

Did you do the correct Carrier bypass with custom ROM method? If you had done any data connection and device updates before using the bypass method, your device is Locked and needs approved Sim-Unlocking for your device...
 
bcrichster said:
Hrmm..
- Which Carrier?

Did you do the correct Carrier bypass with custom ROM method? If you had done any data connection and device updates before using the bypass method, your device is Locked and needs approved Sim-Unlocking for your device...
Click to expand...

I have the same problem as kachman. My XT1776 phone had lineage and was working fine on at&t. It went haywire and I went back to sprint stock using this thread (thanks for the instructions!), reflashed lineage, inserted my at&t sim card, and got the no service message.

You mentioned that the device might be locked and needs approved unlocking. What do you mean by that? Is that the method of flashing back to stock, inserting a sprint SIM card to have it provision data, and then flashing a custom rom? Thanks
 
ocnbrze said:
can you be more specific? like a bad link? or it did not unbrick your phone? can you go into detail on whats wrong so that we can help you better?
Click to expand...
It didn't unbrick my phone. I put the SD card into my phone and nothing happened. I followed all the instruction except the part where you have to right click and "open as root" because I didn't have that option in the context menu. I drag and dropped the file into the terminal to get the path of the file instead. I don't think this would have prevented it from working though.
 
Last edited:
doodalydoo said:
It didn't unbrick my phone. I put the SD card into my phone and nothing happened. I followed all the instruction except the part where you have to right click and "run as root" because I didn't have that option in the context menu. I drag and dropped the file into the terminal to get the path of the file instead. I don't think this would have prevented it from working though.
Click to expand...
where are you seeing this unbrick file? is it not part of the op? i do not see this file. or its instructions.
 
ok well first off.....i want to apologize. i should have scrolled down further ( i blame this on my glass of bourbon i'm drinking

second it does say untested.......i have not read this thread so i'm not sure if it actually has been tested and works.

third......you mentioned sd card. according to the second post you need to have the file on your computer and you need to use adb commands to have twrp flash the file.
 
Last edited:
ocnbrze said:
ok scratch that entire post.......i should not drink and post.......my apologies.

this is the acxtual guide that is mentioned in the second post:
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012/amp/

it does mention you need to have linux running on your pc to make this work.
Click to expand...
I did prepare the SD card using Linux. The only deviation from the guide was when it came to "open as root", but the guide also says you can get around using it by altering the terminal command.
 
ok thanx for the clearing that up.

i would not have dragged and dropped the file to get the correct file path. i would type it in as the guide suggests. there is 2 versions of the code depending on how the file is seen.

which version did you use?
 
ocnbrze said:
ok thanx for the clearing that up.

i would not have dragged and dropped the file to get the correct file path. i would type it in as the guide suggests. there is 2 versions of the code depending on how the file is seen.

which version did you use?
Click to expand...
I used the first one because that was what my SD card matched. The code as written didn't work. It gave me an error saying no file existed, which is why I had to drag and drop to get the path to the file and replace the bold part of the code with it
(sudo dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync)
 
doodalydoo said:
I used the first one because that was what my SD card matched. The code as written didn't work. It gave me an error saying no file existed, which is why I had to drag and drop to get the path to the file and replace the bold part of the code with it
(sudo dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync)
Click to expand...
and what happened after you entered the command correctly? nothing?
 
You must log in or register to reply here.
Back
Top Bottom