XT1955-5 bootloader unlock install TWRP & Root with Magisk

[zapjb]

I'll take a look at this after I get mine in hand & check the IMEI. Thanks OP.

 

[Maveric1313]

Sim not found issue resolution

I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM

So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone

I had this issue as well. copy the stock rom files into the same folder as the adb and fastboot tools then use the powershell terminal with the following commands to re-flash the modem firmware:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

Cleared my issued right up. Also worth noting that I reflashed my phone with the stock retail rom before doing it.

 

[Hyoretsu]

I had this issue as well. copy the stock rom files into the same folder as the adb and fastboot tools then use the powershell terminal with the following commands to re-flash the modem firmware:

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

Cleared my issued right up. Also worth noting that I reflashed my phone with the stock retail rom before doing it.

That's the default solution, one of the first I found/tried. I only solved it after 3 months when an update showed up and I had to manually flash it to update. (after going to stock, trying those commands, trying to lock bootloader and a lot of other things)

 

[Economic_Hitman]

Hi, I am going to flash LineageOS to my ocean. It's the first time doing this and the first nightly build for 17.1 on ocean was just released today.

I'm curious about Magisk. It seems like a very powerful tool but I don't know if I need it at all, or will need it down the road.

I bought my Moto G7 Power last week, it has been updated to Android 10. I have not flashed Lineage 17.1 yet but I intend to. I have a few questions:

1. Is it best to install Magisk at the same time?
2. Can I install Magisk at a later date after I flash LineageOS?
3. I have read several posts saying you need to flash back to stock ROM before flashing Magisk, so if I'm coming from stock ROM on a brand new device, is that necessary?

 

[roadkill42]

Hi, I am going to flash LineageOS to my ocean. It's the first time doing this and the first nightly build for 17.1 on ocean was just released today.

I'm curious about Magisk. It seems like a very powerful tool but I don't know if I need it at all, or will need it down the road.

I bought my Moto G7 Power last week, it has been updated to Android 10. I have not flashed Lineage 17.1 yet but I intend to. I have a few questions:



Is it best to install Magisk at the same time?
Can I install Magisk at a later date after I flash LineageOS?
I have read several posts saying you need to flash back to stock ROM before flashing Magisk, so if I'm coming from stock ROM on a brand new device, is that necessary?

Have u ever flash a b device before

 

[roadkill42]

Have u ever flash a b device before

Here is a file to help out

 

[Economic_Hitman]

Have u ever flash a b device before

I have never flashed any devices before, so no. This is the first time I have installed a custom ROM or any cousin software.

I have read a little bit about A B devices, I know that those are the two slots that some phones have and that usually the manufacturer leaves one slot empty.

 

[roadkill42]

I have never flashed any devices before, so no. This is the first time I have installed a custom ROM or any cousin software.

I have read a little bit about A B devices, I know that those are the two slots that some phones have and that usually the manufacturer leaves one slot empty.

Yes u format one slot data and cache and thingshttps://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw go here and I and some others there can help u get started with out getting bricked or soft bricked have the files there and get the links to the roms it late now here going to bed I checked that group in about 8 hours when I get up

 

[wbill2k]

...

So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://xdaforums.com/showthread.php?t=2317790 or https://xdaforums.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE

Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.

TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.

Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.

Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear

I tried this and the first time it let me select wipe, but when i did it got stuck, so i attempted again and now it wont let me select anything, any ideas how to get this to work?

 

[WoKoschekk]

I tried this and the first time it let me select wipe, but when i did it got stuck, so i attempted again and now it wont let me select anything, any ideas how to get this to work?

You got an unresponsive TWRP screen?

 

[roadkill42]

Ugh

 

[roadkill42]

Try this one by syber hexon

 

[WoKoschekk]

Try this one by syber hexon

@wbill2k I think that's for you.

 

[wbill2k]

@wbill2k I think that's for you.

ok, thanks...

---------- Post added at 03:36 PM ---------- Previous post was at 03:30 PM ----------

You got an unresponsive TWRP screen?

Thats EXACTLY what i got!

 

[WoKoschekk]

Thats EXACTLY what i got!

Try the other version, that should fix your problem.

 

[wbill2k]

Try the other version, that should fix your problem.

what other version?

 

[roadkill42]

what other version?

What rom and kernal u using certion roms and kernal don't like twrp I stalled but will fastboot boot twrp and touch works now there is another recovery out cauld pbrp based off the official latest twrp and don't have any touch issues we use it in tellagram group g7 power discussion group

 

[WoKoschekk]

what other version?

Post #32 by @roadkill42

 

[zapjb]

What rom and kernal u using certion roms and kernal don't like twrp I stalled but will fastboot boot twrp and touch works now there is another recovery out called pbrp based off the official latest twrp and don't have any touch issues we use it in tellagram group g7 power discussion group

PBRP & rk42 sorted me on Telegram group g7 power discussion group.

 

[Deleted member 5437200]

was this device released with Android 10 and does it use dynamic partitions(super.img)?