Database Develop

Q: Howto get my X4 to a working LOS setup after having bricked it and used blankflash

Hello,
I few weeks ago I got myself a Moto X4 XT1900-7 after my old mobile suffered a broken display.
I unloaded the boot loader and proceeded to install LOS right after getting the phone and getting it unwrapped from its shipping box.
This is now my 4th mobile were I installed LOS or Cyanogenmod and out of hubris I did not create a backup before the install.
I followed the instructions on the LOS website for installing and ended up with a bricked X4 (https://wiki.lineageos.org/devices/payton/install).
Now after xmas I investigated further and was able to use the blank flash as provided here (https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529/page6) to get to the state were the mobile is at a fastboot screen after the blank flash.
https://imagebin.ca/v/4RUBbOmjIGs9
At this point I can fastboot boot twrp (https://dl.twrp.me/payton/)
fastboot boot twrp-3.2.3-1-payton.img
to get into a twrp recovery.
But installing a LOS install package (https://download.lineageos.org/payton) and rebooting only gets me back to the state of the bricked phone, so I must be missing something.
So my question is how do I proceed to get the phone back to a working state ? The LOS install instructions to not work at this point - I tried and after installing LOS I just get back to the state were the mobile is bricked and I have to use blank flash again.
My end goal would be a working LOS installation.
Thanks
BR

Hey let's compare build numbers and kernel info, Android version etc. Maybe ours differ from others on here. Since I had a similar experience as you in that flashing a ROM bricked my phone, maybe we'll find a commonality that others here don't have...
I could not get blankflash to work for me. The phone showed in device manager the way the instructions said it should with the port number. I downloaded stock rom unzipped it to my address folder and unzipped the blankflash package to the same folder. I would run the .bat file but it errored out everytime. Luckily I was able to bring the phone back and Fry's just accepted it and gave me another one .
I don't want to end up with another bricked phone. Out of curiousity was yours freezing up after rooting, but before the rom installation.?
---------- Post added at 02:52 AM ---------- Previous post was at 02:36 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you try following the guide in the ROM thread (https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265)?
I bricked my device on the first attempt while following the LOS site install instructions, but after getting it back to stock I followed the ROM thread instructions instead (with a minor adjustment).
First things first, if you haven't gotten back to working bootable image on your device, boot to the bootloader and follow this thread's instructions. I am not 100% sure this is necessary, but I don't have another device to test with atm. One thing to note, make sure to get your variant's stock 8/8.1 Firmware. I have an XT1900-1 variant while that thread features links for the XT1900-6 variant.
Next follow these instructions:
erfanoabdi said:
How to install:
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Click to expand...
Click to collapse
Following those instructions should get you a working LOS install. Make sure to get the correct Copy Partitions Zip for your variant.
All that said, I diverged a bit at the start and end:
Before starting TWRP, I ran the Copy Partitions Zip flash_all.bat/sh at the bootloader.
Before letting the system start, I ran the flash_all.bat/sh at the bootloader again.
For the first change, I couldn't get TWRP to run the ZIP, so I extracted it and realized the bat/sh scripts were fastboot flashing the contents of the ZIP. The second deviation is because my system wouldn't make it past the boot logo screen and when I loaded TWRP, it was giving errors about firmware issues in the terminal.
After performing all that, your LOS should boot and be configurable. Your experience may be different to the difference in variant.

Ty for the pointer to the ROM thread, I am reading through that.
How do the different variants of the X4, i.e. XT1900-1 through XT1900-7 (that is the one I do own), differ ? And connected to that question - can I flash a stock image from a different variant (maybe a XT1900-1) than my XT1900-7 to my XT1900-7 without causing further problems ?
Also what is the purpose of Copy Partitions Zip ? What does it do ? I downloaded the zip file and I understand that I shall install it via adb sideload or from the sd card when I have booted the twrp recovery from fastboot. Do I need to modify anything in copy partitions zip specifically to match my XT1900-7 ? Or does Copy Partitions Zip work the same on all variants of the moto X4 ?
Ty
BR

I'll be honest, a more experienced member would have to answer that because I don't really know how they differ. You can try to push a XT1900-1 to -7, but I wouldn't recommend that. I have two versions of this device, an A1 and Retail. The A1 version is generally Fi related and I accidentally loaded the firmware for the Fi version on my Retail and now it is giving me issues with my carrier (I think this is the cause, but am not 100% sure).
From what is said by TadMSTR in the thread, the Copy Partitions Zip is for duplicating partitions between the two OS slots:
TadMSTR said:
The Moto X4 uses the A/B slot setup that Google introduced with the Pixel. However, Motorola decided to only setup the partitions in slot A. The copy partition zip copies the partitions from slot A into slot B. This allows you to now flash/install a ROM into slot B. Without flashing copy partitions zip I'm not sure you would even be able to change to slot B. You definitely would not be able to flash anything to it.
ROMs should include everything needed to boot into the OS. Lineage includes boot, system, and recovery. If you don't want to use Lineage recovery then you need to flash the TWRP zip after flashing Lineage, even after just flashing an update. So technically all you need is the Lineage zip to have a fully functioning Android OS. However, you will most likely also want gapps. You should be good following the tutorial in the beginning of this thread. For applying updates see my post above.
Click to expand...
Click to collapse
You won't be sideloading that zip. As I stated before, it's a bunch of fastboot commands in the a bat/sh file with support files included. You will be running while at the bootloader according to Skeeterdrums in the thread:
Skeeterdrums said:
See the previous post, you need to unzip and run the flash_all bat/sh file while connected to your phone in the bootloader. Those scripts run a series of fastboot commands to get everything copied over and installed.
Click to expand...
Click to collapse
You don't need to modify the zip, it should work on your variant according to posts in the thread.

erukami said:
I'll be honest, a more experienced member would have to answer that because I don't really know how they differ. You can try to push a XT1900-1 to -7, but I wouldn't recommend that. I have two versions of this device, an A1 and Retail. The A1 version is generally Fi related and I accidentally loaded the firmware for the Fi version on my Retail and now it is giving me issues with my carrier (I think this is the cause, but am not 100% sure).
From what is said by TadMSTR in the thread, the Copy Partitions Zip is for duplicating partitions between the two OS slots:
You won't be sideloading that zip. As I stated before, it's a bunch of fastboot commands in the a bat/sh file with support files included. You will be running while at the bootloader according to Skeeterdrums in the thread:
You don't need to modify the zip, it should work on your variant according to posts in the thread.
Click to expand...
Click to collapse
@erukami I have the Android One variant with the Fi firmware. Only had data when using my Verizon work sim. Flashing the US Retail firmware loaded the correct radios and I was able to get full service on Verizon. Custom roms typically do not include the radio files. Restore the US Retail firmware and you should be fine. Can flash any custom rom after that.
I may have misspoke a bit about the copy partitions firmware. It doesn't setup the partitions as they are already there. It merely copies what is on A to B and vice versa, depending on which slot you are currently on. Though I think when coming completely from stock the B slot is "empty" as Moto didn't bother with it. Not sure if you need to bother flashing the zip when restoring to stock but I did anyway. Fastboot was only flashing to slot A. Maybe that can be tweaked with the flash-all.bat file.
@Afongo You should restore the stock firmware for your variant and start over. Making sure to flash copy partitions zip in TWRP before flashing LOS. When I restored stock firmware I made sure slot A was the active slot. After the restore let the phone boot up into stock. Reboot to the bootloader then boot TWRP. Flash copy partitions zip. Flash Lineage and then flash TWRP zip. Reboot to recovery. Flash gapps and Magisk (if you want root). Factory reset or wipe data/cache as needed before booting into Lineage the first time.
You need to reboot back into recovery after flashing a ROM due to the A/B slot logic. Flashing a ROM automatically changes the active slot so in order to flash anything after the ROM, with the exception of TWRP, you need to reboot to recovery to continue. Due note that LOS overwrites TWRP recovery on a fresh install and any updates. You'll need to boot TWRP from the bootloader if you need to get back in TWRP or you can just use LOS recovery.

Ty all for the provided info. I understand more now than before.
I am still looking for a firmware for a XT1900-7, does anybody know the filename so that I can google for it ?
For example I downloaded a PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, but how do I know for which variant of the Moto X4 that file is ? What is the naming scheme ?
Ty
BR

Afongo said:
Ty all for the provided info. I understand more now than before.
I am still looking for a firmware for a XT1900-7, does anybody know the filename so that I can google for it ?
For example I downloaded a PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, but how do I know for which variant of the Moto X4 that file is ? What is the naming scheme ?
Ty
BR
Click to expand...
Click to collapse
You have the correct and most recent Android 8.1 firmware for you device (PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip). This works for all regions. The firmware does not determine the region. The xt1900-7 is 'reteu'.

Look here for Pie ROM.

[RESOLVED] Bricked after flashing firmware for Pie, stuck in md5 checksum bootloop

Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.

bump pls
even bad news is appreciated

Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?

Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.

Hmm.. does phone in TWRP works like USB storage?

Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok

swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?

vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.

swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.

swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.

redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?

swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).

swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.

redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.

I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?

swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.

Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?

Can i Root Galaxy Note 8 with latest security Updates

Samsung releases security updates every month, and i think they are the culprit, since i just cant flash TWRP with Odin on My Galaxy Note 8. It says failed. Ive tried 3.3.1and even latest 3.5.0 and both fail.
Its the Exynos CPU which can be rooted. At least i know this for sure
Do you know of any solutions to this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

therock003 said:
Samsung releases security updates every month, and i think they are the culprit, since i just cant flash TWRP with Odin on My Galaxy Note 8. It says failed. Ive tried 3.3.1and even latest 3.5.0 and both fail.
Its the Exynos CPU which can be rooted. At least i know this for sure
Do you know of any solutions to this
Click to expand...
Click to collapse
I recently flashed the latest filmware and managed to flash TWRP 3.5 after so it's not Samsung blocking it. What Odin version are you using? I'm using 3.13.3. I had to install 15 second Adb for it to work though which can be found in the link below. You enabled the OEM toggle?
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com

Whats the OEM toggle.
Are you sure that adb install is legit cause it looks like a 2013 post. Anyway i even tried the latest 3.14.1 odin and also that adb package you posted. It still fails

therock003 said:
Whats the OEM toggle.
Are you sure that adb install is legit cause it looks like a 2013 post. Anyway i even tried the latest 3.14.1 odin and also that adb package you posted. It still fails
Click to expand...
Click to collapse
You have to enable the OEM toggle in the development settings (settings/about phone/software information/the click on the build number 7 times will enable dev setting) for TWRP to be able to flash. This is probably why it's not flashing for you. If you don't know about the OEM toggle, do you know that as soon as you flash TWRP that it trips Knox and Samsung Pay will never work again unless you get a motherboard replacement?
Yes the 15 second adb is legit. Used it for a long time.

If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening

therock003 said:
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
Click to expand...
Click to collapse
I did not mention auto update...
therock003 said:
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
Click to expand...
Click to collapse
I have not said anything about auto update. In the dev setting you should see "OEM unlocking" toggle, like in the screenshot I added. If you don't see this option let me know and I will see if I can find the thread that might help you get the toggle.
FRP lock is Factory Reset Protection. So if your phone is lost or stolen that person can't just flash stock firmware to use your phone it makes it so they have to login to your account to be able to use the phone, although this only works on the stock rom without root as it needs encryption.

No you were right. didnt notice the oem unlocking toggle. Read another page that told me to turn off auto updates and this was misleading
Does Odin Unlock Bootloader? - codekomusic.com
What happens if I unlock bootloader? A device with a locked bootloader will only boot the operating system currently on it. You can’t install a custom operating system – the bootloader will refuse to load it. If your device’s bootloader is unlocked, you will see an unlocked padlock icon on the...
codekomusic.com
How do I turn off OEM lock?
Open developer options (in the Settings app itself), and find the option called ‘Auto update system’. Use the toggle button to disable it.
Click to expand...
Click to collapse
Anyway i got TWRP running now, and im off to install magisk and the rest of the steps. Thanx man for helping me

therock003 said:
No you were right. didnt notice the oem unlocking toggle. Read another page that told me to turn off auto updates and this was misleading
Does Odin Unlock Bootloader? - codekomusic.com
What happens if I unlock bootloader? A device with a locked bootloader will only boot the operating system currently on it. You can’t install a custom operating system – the bootloader will refuse to load it. If your device’s bootloader is unlocked, you will see an unlocked padlock icon on the...
codekomusic.com
Anyway i got TWRP running now, and im off to install magisk and the rest of the steps. Thanx man for helping me
Click to expand...
Click to collapse
Glad to hear! Happy flashing.

Oh man now I get a verirication failed. Followed this guide and flashed magisk , no verity opt and rmm state. After that it says reboot your mobile
Root Samsung Galaxy Note 8 SM-N950F Pie 9.0 using TWRP and Install Magisk
After Samsung released One UI Pie 9.0 version, most of the users who blame Samsung's Custom skin OS, Praising Samsung. It may not be best like OnePlus
www.androidinfotech.com
And it has a footnote. "Oh we didnt actually mean that. We meant reboot into recovery otherwise youll have to reflash your firmware."
I mean cmon how stupid csn these guides get. So what now hoe do i reflash the stock firmware

Seriously i need some help cause thst guide inposted previously is the worst. I refladhed stock firmware and redid the procedure. Based on thst guide you must first flash twrp. After you boot into TWRP you install magisc no verity and smm and reboot. I do all that and end up eith no firmware. Whats going wrong here

therock003 said:
Seriously i need some help cause thst guide inposted previously is the worst. I refladhed stock firmware and redid the procedure. Based on thst guide you must first flash twrp. After you boot into TWRP you install magisc no verity and smm and reboot. I do all that and end up eith no firmware. Whats going wrong here
Click to expand...
Click to collapse
You must have wiped "system" in TWRP for that to happen. You only need to format data where you have to type "yes" to confirm, then you can flash Magisk.
Make sure to backup your EFS folder with TWRP too! So important to do this

Wait doni need to format or something, cause i was under the impression that i get to keep.my files. I havent wiped anyrhing besides cache. I only do advanced wipe and select cache each time i installed anyrging. I never did a full wipe. Do i need to?
So here is what i do in detail step by step.
I flash TWRP on AP on odin and then boot in TWRP. I select full permission and not read only and go to instal.
I install magisc 20.3.zip then go advances wipe and wipe cache.
Then repeat with the rest. Install thst opt verity then clear chache. Instal smm state then clear cach and finally i reboot.
What did i not do here

therock003 said:
Wait doni need to format or something, cause i was under the impression that i get to keep.my files. I havent wiped anyrhing besides cache. I only do advanced wipe and select cache each time i installed anyrging. I never did a full wipe. Do i need to?
So here is what i do in detail step by step.
I flash TWRP on AP on odin and then boot in TWRP. I select full permission and not read only and go to instal.
I install magisc 20.3.zip then go advances wipe and wipe cache.
Then repeat with the rest. Install thst opt verity then clear chache. Instal smm state then clear cach and finally i reboot.
What did i not do here
Click to expand...
Click to collapse
I'm not sure as I have never flashed the RMM and Verity, I just flash a custom Rom which has all that patched already.
I thought we had to format data to be able to flash anything in TWRP, I didn't think keeping all data was possible.

Then i guess ill have to spend all day to backup all apps and files and try to fully erase memory

[ROM][SOFIAR][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679

Agh, plain AOSP. I miss Havoc already.

Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.

Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?

jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)

Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here

This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.

Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.

RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d

Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.

RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?

Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.

Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.

Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?

jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.

ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?

Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.

jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.

actually it is rescuing me to android 11 no matter what i do

Root any BL UNLOCKED T-Mobile/Metro OnePlus Nord with Magisk and temp root

Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES
YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK
My first tutorial, gonna keep this short and sweet
1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices

I'm going to try this now. Thank you for the idea!

I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.

bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
Unfortunately, I can't even get into EDL mode. So this brick might be permanent. I'm asking for help from the community here: https://forum.xda-developers.com/t/nord-n100-edl-mode-dead-gone.4341305/

bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it

luridphantom said:
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
Click to expand...
Click to collapse
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB

bouyakasha said:
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
Click to expand...
Click to collapse
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine

I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.

bouyakasha said:
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
Click to expand...
Click to collapse
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it

luridphantom said:
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
Click to expand...
Click to collapse
Oh, thank you! That makes sense. I will try to UN-Tar it

I used Zarchiver to unarchive the TAR into boot.img for both, and this all worked! Thanks so much. Awesome guide.

@onlycash You should try this!

luridphantom said:
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
Click to expand...
Click to collapse
I tried several times and it's not working for me.
Everything appears to be fine till I try to "fastboot boot patched.img".
I'm trying to do this on an Metro N100 which is on 11.0.1BE82CF
I downloaded the global: 11.0.1: OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056 MD5: a895312987628f21d0232d44575d0742
I extracted the payload and dumped the boot.img
I patched it in Magisk
I successfully "fastboot boot" that patched file but then it just hangs at the at the Metro boot screen.
I waited a minute or two but it didn't move past that screen, should I have waited longer?
In any event, I could hold down the power key and reboot into the unrooted stock 11.01 without issue.
Does anyone have an idea what I'm doing wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.

onlycash said:
I tried several times and it's not working for me.
Click to expand...
Click to collapse
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.

thomaskmaagaard said:
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
Click to expand...
Click to collapse
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.

onlycash said:
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
Click to expand...
Click to collapse
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it

My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.

luridphantom said:
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
Click to expand...
Click to collapse
I posted a good deal on the TWRP thread. I can fastboot the TWRP on my phone but I can't see any files only folder tree, even with my SD card I don't see any files either with TWRP.
I should add I'm running TWRP on a Metro N100 which is both SIM and bootloader unlocked. Also I didn't flash the TWRP I only fastbooted it, could that be the problem?
I really would rather flash the zip and root that way if I could get the TWRP to work.
I'm unsure what "disable dm-verity by flashing an empty vbmeta image" means in my case. What does this do?
Again I'm truly grateful for any help, thank you.

bouyakasha said:
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
Click to expand...
Click to collapse
Just to be clear I have a Metro N100 BE2015 running 11.0.1BE82CF.
With that being said, did you only get root when you went back to 10.5.8?
Are you rooted now on 11 and if so how did you get there?
Did you brick and go back to 10 then root 10 and update to 11 and keep root? How did you patch the img file after going to 11?
Any help and info would be much appreciated.
.

@onlycash I have constructed a small/random theory with no real basis. Could your problems be related to OOS 11? It sounds as dumb to me as it probably does to you, but I'm getting a nagging sensation that folks with success on your model aren't running the new update.
Just a weird hunch with no proper research, but I find it weird that you have these "unique" problems so I'm just spitting random junk at this point.