Database Info

Need help to install stock ROM on Moto G 2013 Falcon

Hi guys,
Im from the UK and I have a Moto G XT1032 device which was running Cyanogenmod 12 up until yesterday when I decided to re-install the stock rom. Unfortunately, I have well and truly botched it. The current situation is that I have TWRP set up as the recovery image, so I can get into 'AP Fastboot Flash Mode (S)' OR into TWRP.
I accidentally wiped the 'system' via TWRP which seems to have caused most of my problems. I have tried to install the stock rom using a flashable zip (which failed) and I have also tried around 10 times to install the stock rom using the fastboot commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
When I try to do a basic wipe using TWRP, this is what shows up: hxxps://s27.postimg.org/r1dax21mb/falcon.jpg (change xx for tt, I don't yet have 10 posts so I cannot post links)
I just cannot seem to get the stock rom installed and booting no matter what I try. Can someone please work with me to get this sorted?
I would very, very much appreciate the help.
Thank you

Ok so i've managed to fix the 'unable to mount storage' issue via TWRP. I changed 'data' to EXT4 and I don't get any errors now.
But the problem is, for whatever reason, I am just unable to install a stock rom. I've used tutorials and still cannot seem to get a stock rom to load/work.
I used fastboot to install the rom files is this zip: XT1032_FALCON_TESCOGBSL_5.1_LPBS23.13-56-2_cid7_CFC.xml.zip
When I do a normal boot it gets stuck on 'Warning bootloader unlocked'
When I go to 'recovery', it boots up to a dead android which says 'no command'
When I go to factory restore, it gets stuck on the 'Warning bootloader unlocked' screen
What am I doing wrong?
edit: I even tried sideloading cyanogenmod and it said it was successful, but then it boots up to TWRP. Totally confused! In desperate need of help.
EDIT: I have now made progress. Here are my basic instructions:
put all the files from the zip file in a folder
put mfastboot.exe files into the same folder
install TWRP, erase
run bat file (add/remove sparse depending on files)
reboot and wait. Should work
I have managed to install the OS but wifi isn't working. And i'm now learning about a file called persist that I need to look into regarding wifi.

Manually update Z3 Play to Pie

Story: I bought US version Z3 Play open market model from B&H. I could unlock the bootloader according to Motorola Developer site, but I encountered problem to root and I have struggled half day to make root done from booting TWRP to patching boot.img.
Eventually, I bit the bullet and make a step up to update to Pie bu downloading RETAIL ROM instead of RETUS. This time I patched the updated boot.img and I got success.
Prerequisite:
Full RETAIL Pie ROM
https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
Bootloader unlocked
It's recommended to flash in Linux (I used Ubuntu) as I didn't have luck with Windows
Main battery should be full and supplied battery module should be at least 50% (you can charge battery module with 9V PD charger)
Some typing (all fastboot commands typed as ./fastboot)
Be aware some components will be flashed in b partition. Failure to do it will cause bootloop
./fastboot erase userdata is optional, but it is recommended to avoid unexpected trouble
Steps:
1. Download the Pie ROM and extract to somewhere you know (you can drag and drop the file into terminal window).
2. Copy the boot.img to the phone and let Magisk Manager to patch it, and copy the patched_boot.img to where you can locate.
3. Backup your personal data just in case
4. Prepare USB C cable
5. Enter bootloader. Turn the phone off, press and hold both volume down and power button together, and connect you phone to host computer. (You phone should show USB conmected)
6. Enter the following commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
7. After the phone has booted up, wait until it completed the update process. Now you have to go back to bootloader for rooting.
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Booting process takes much longer, but it's one process until you update ROM and regain root again.
8. Run Magisk Manager to check root status
This is what I did to manually update to Pie and root it. Your milage may vary.
Good luck

Will this work on the amazon version?

CrimsonSaber5G said:
Will this work on the amazon version?
Click to expand...
Click to collapse
If the bootloader can be unlocked, it's likely

Will this still allow you to get OTAs or will it break it?

crazyjimbo said:
Will this still allow you to get OTAs or will it break it?
Click to expand...
Click to collapse
I used to flash stock on my rooted z3play, then take the OTA . For some reason that's not possible anymore. I really need the latest OTA to sideload it. I tried many different roms 8.1 and 9.0

How To Guide Restore OnePlus 9 to Stock via Fastboot Commands

This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, then hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Final reboot:
Code:
fastboot reboot
7. If everything worked your phone should now boot into OxygenOS.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To check current slot:
Code:
fastboot getvar current-slot
To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.

If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. This will wipe your device! Reboot to the bootloader and run:
Code:
fastboot -w
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Edit: script attached. I've (unfortunately) had the opportunity to test it and fix all the bugs. So it works. You will need to have fastboot.exe accessible in your system PATH to run it.

Slikkster2k said:
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. Reboot to the bootloader and run:
Code:
fastboot -w
This will wipe your device!
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot bootloader
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Click to expand...
Click to collapse
That would be helpful indeed. Would this script run on mac as well?

Not unless there's a version of PowerShell for macs (there is for Linux, but I don't know if it's compatible).

@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?

AxelM said:
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
Click to expand...
Click to collapse
I used 11.2.2.2.LE25AA as I said in the original post (this is the global variant, which matches my device). I am not sure if this works for cross-flashing, or if it's possible to cross-flash an Indian phone to EU. Have you tried restoring the Indian ROM? Does that work?
You're getting an actual boot loop? The error I was getting (and the reason I had to restore) was the phone booting to the bootloader or fastbootd (depending on the slot I tried) instead of Oxygen, because it couldn't mount the user partition due to encryption. In fastbootd an error was reported (I forget the exact one) which made me suspect it was a partition mounting issue. At no point was my phone actually boot looping, even during partial/failed flashes.
I've never encountered the error with fastboot -w, but I only did that on my phone once. From some searching online, it can be caused by an old version of the platform tools, so did you download the latest version?

@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!

AxelM said:
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
Click to expand...
Click to collapse
Glad to hear you got it working!

PowerShell script added to second post. Totally untested, but I tried to make it as idiot proof as possible.

Slikkster2k said:
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Reboot back into the bootloader:
Code:
fastboot reboot bootloader
7. You should now be able to continue booting normally by pressing the power button.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
Click to expand...
Click to collapse
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button

toyanucci said:
That would be helpful indeed. Would this script run on mac as well?
Click to expand...
Click to collapse
Windows offered now to add to MAC - https://support.apple.com/en-us/HT201468

toyanucci said:
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
Click to expand...
Click to collapse
Thanks, updated OP.

ok i kind of bricked my phone using this and i need a little help PLEASE?
Ok i tried the fist 2 steps 1. fastboot -w than the first list of commands using cmd with admin rights it worked...i think but it did load everything without issues...now i go to do the "fastboot reboot fastboot"
and now my phone is stuck on a black screen with nothing and i just hear the chime windows makes when you disconnect and reconnect a device..... and in the Device manager this comes up for 10 seconds than goes away for 5 than comes back NON STOP
i cant adb i cant do anything please help !

I'm not sure if this will help you, but I had a lot of issues initially running this. First off you need to use the Oneplus drivers, I don't think the qualcom driver will work the same way. I could be wrong, but that's what I did. Secondly, you need to force install the driver because Windows doesn't like it.
Here are the steps I took.
1. Uninstall any old drivers.
2. Install the newest Oneplus Drivers from here https://oneplususbdrivers.com/
3. Extract the zip file and run the installer like normal
4. Once the installer finishes, you'll need to reboot your machine and bring up the Startup settings (hold down shift and reboot (keep holding down shift until you get a screen with options)) Then click advanced and startup settings and hit restart after that. Once the machines starts up, on the first boot you will have a bunch of options. Choose option 7 "disabling driver signature enforcement" mode.
5. Once Windows launches and you login, go back into the device manager and follow these steps:
right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.
----------------------------------------
The above should get your drivers working properly in all modes (adb, fastbootd, bootloader, normal)
One other issue that I ran into when I was using the powershell script was that I was seeing intermittent errors. After trial and error I realized that Windows was picking up a different version of fastboot. I was initially using the minimal adb/fastboot files, but if you compare those to the ones listed in the first post in the "SDK Platform Tools", they are very different from each other, so you need to make sure you use the SDK Platform Tools version. The minimal ADB/Fastboot version will NOT work.
After I got those 2 things ironed out, the powershell script ran without a hiccup and my phone is stock and booting without an issue.
I know I'm late to respond to this thread, but I hope someone finds this information helpful!

Mine keeps trying this and it isn't running and or rebooting into Fastbootd when the script is ran. Should I just try and invoke this manually? I've tried that as well an I'm seeming to get errors left and right with no resolve.

I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?

Good work

toyanucci said:
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Click to expand...
Click to collapse
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.

ilikepie___ said:
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
Click to expand...
Click to collapse
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.

toyanucci said:
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
Click to expand...
Click to collapse
I’ll give it a shot, yeah it doesn’t do anything. Can’t see a display or anything on the screen.

Motorola g7 Play touch screen not working after root attempt

Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!

nimbussecond said:
Hey everyone. So recently I tried rooting my motorola g7 play. I followed this guide on youtube
and everything was going fine until one point I received something like "bad error" (or something like that) when I tried installing magisk patched boot.img file on my phone. It then asked if I would try installing again or do a factory reset. I tried again and it didn't work so thought I had no choice besides to do a factory reset. When I booted it back up, it put this code on the top left of the screen: 80012A99-86FDA48-4E357816-0E549F1B-B067FD5 and then everything was working fine until it asked to do the language selection. The problem was that the touch screen wouldn't work anymore, but the side buttons still work. So I tried restarting my phone, safe mode and using things in bootload mode (factory mode, recovery mode, etc.) and the screen still didn't work. I think the problem may be where I got the boot.img from, which is here: https://forum.xda-developers.com/t/magisk-on-g7-play-xt1952-4-installed-succesfully.3975477/ and I feel like this problem is still able to be fixed. I was considering buying an otg adapter to try connecting my mouse to the phone, but I'm not sure since it might be considered a waste of money. any help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...

Dauksza72 said:
Accident... Don't know how to delete it now...
Click to expand...
Click to collapse

Dauksza72 said:
I started flashing TWRP a month or so ago on my g9 Power with the wrong version and the touchscreen did the same thing, I attached an OTG and hooked the mouse and it worked great... As for your failed flash, is your firmware xt1952-4? I suspect that boot.img is from a phone with a different touchscreen. I would find the correct firmware from lollinet and reflash a stock boot.img and you should be fine. Install Magisk as an app then modify your own boot.img and install root that way. ALSO if you can still use side buttons you should still be able to flash a new stock boot.img from inside fastboot without digitizer support...
Click to expand...
Click to collapse
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.

nimbussecond said:
OK, thank you so much. In fastboot mode it says Product/Variant: channel XT1952-4 32GB PVT, so I assume that the firmware is indeed xt1952-4. Also could you clarify how to flash a new stock boot.img from inside fastboot because I'm not sure how to modify anything on my phone without allowing usb debugging (which I can't do since the phone factory resetted). If there are no other options I plan on trying the OTG adapter then.
Click to expand...
Click to collapse
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.

Dauksza72 said:
I've not had issues with using fastboot after a stock flash even without going in and enabling adb thru developer mode. When you hold volume - while powering up and plug in the usb cord from the PC you should go into the bootloader and can flash the new boot image from there with fastboot commands. You may already know but open cmd prompt on pc, type cd then drag your fastboot directory folder over to cmd prompt and drop it, click anywhere in cmd prompt and hit enter. Put your system boot image inside the folder with you fastboot files and type "./fastboot flash boot boot.img" and hit enter and you should be flashing.
Click to expand...
Click to collapse
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?

nimbussecond said:
Thanks so much, my phone seems to work fine now. I ended up finding the right boot.img file and wanted to try following the video again, but at the last step where I have to flash the magisk patched img file, command prompt gives me the error (bootloader) is-logical:boot_b: not found. Do you know what I can do to so that it can flash properly?
Click to expand...
Click to collapse
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.

Realized I typed flash product_a/b instead of boot_a and boot_b... SORRY. Total oversize. Delete product , flash boot

Dauksza72 said:
In fastbootD, (go to bootloader and type
./fastboot reboot fastboot)
./fastboot erase-logical-partition product_a
./fastboot erase-logical-partition product_b
then flash the Magisk_modified.img to boot_a and boot_b from fastboot.
./fastboot flash boot_a Magisk(whatever Magisk named it)
./fastboot flash boot_b Magisk(whatever Magisk named it)
./fastboot -w
./fastboot reboot
Now that you know how to recover from a soft brick don't be afraid to play around with it. Eventually you'll make a text document and have all your commands on it so all you have to do is copy the whole page and paste it in fastboot and pretty much automate the whole process... Let me know if that helps.
Click to expand...
Click to collapse
For some reason I can't get into FastbootD, it gives the error FAILED (remote: 'Unknown command') fastboot: error: Command failed. I tried searching up stuff, removing the passcode, switching USB ports and more but I couldn't get the screen to pop up. What can I do about this?

Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.

Dauksza72 said:
Have you tried reflashing stock recovery? You also may be able to delete partition and flash through regular fastboot. If you still haven't got it by this evening then I'll brick my wife's g7 and figure out a work around for you.
Click to expand...
Click to collapse
So I tried flashing stock recovery and I seem to get a similar error to when I flash the magisk patched file and I've tried deleting partition and flash through regular fastboot, but it didn't work either (error in the image). I might be doing something wrong since I'm still very new to this, but I also tried downloading TWRP since I know that's another way to root and it lead to the same problems as well (bootloader) is-logical whatever I'm trying to do not found. I also tried LMSA (Lenovo Rescue and Smart Assistant) to see if there was something wrong with my phone, but it made no difference. I might consider an alternative rooting method, let me know what's the best option. You don't have to brick your wife's g7, but either way I appreciate it.
{
"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"
}

Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info

Are you sure the g7 Play has a separate recovery partition? It may be part of the boot partition... Instead of flashing the modified image to a/b just try
./fastboot flash boot "modimg".img

Dauksza72 said:
Ok, do this and post a screenshot again and we'll get it pinpointed. I think your tools are out of date but it could still be a firmware issue.
Make sure you're using latest platform tools, https://developer.android.com/studio/releases/platform-tools.
./fastboot --version
./fastboot -w
./fastboot getvar current-slot
./fastboot oem device-info
Click to expand...
Click to collapse
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run.

Are these the files you have?
Post a screenshot of the flashfile.xml or servicefile.xml

nimbussecond said:
Ok I updated it to the most recent version and also fastboot flash boot "modimg".img says boot_a not found as well. Here are the results of the commands you told me to run. View attachment 5295077
Click to expand...
Click to collapse
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin

Spaceminer said:
The G7 Play doesn't have fastbootd and recovery/boot are merged. You can't have twrp and magisk at the same time. Magisk must patch the boot.img as recovery. (Check all 3 boxes) When you boot up, you must hold Vol↓+power, and select recovery from the fastboot menu to have root.
Inside your firmware zip, there's a flashfile.xml, open it and flash everything as directed, and in order. It'll start with gpt.bin. That's the only tricky one, it repartitions the phone so it flashes to "partition" like so...
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Thanks, that's where I was headed with this.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR

Dauksza72 said:
Thanks, that's where I was headed with this.
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase DDR
Click to expand...
Click to collapse
I did a lot of dev work for this phone. I had to help.

Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).

nimbussecond said:
Alright so I did what you guys told me to with the flashfile.xml, the zip I used is XT1952-4_CHANNEL_RETCA_10_QPYS30.52-22-11-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. I tried doing recovery mode after this and after flashing the magisk boot.img, but it had the same result. I'm not sure what to do after this step. (These are the screenshots after I did the commands).View attachment 5295529View attachment 5295531View attachment 5295533
Click to expand...
Click to collapse
Install magisk manager, patch your boot.img as "recovery". Flash the patched boot.img. Use the volume buttons while in the bootloader menu to select recovery, and hit the power button. Open magisk and it should be rooted. If it needs additional setup allow it.

Question Help! ADB sideload LOS rom doesn't work with TWRP

I got Motorola Edge S from China, and plan to:
1. Unlock (Succeeded !)
2a. fastboot flash boot twrp-3.5.2_11.0-2-nio.img
fastboot flash boot_b twrp-3.5.2_11.0-2-nio.img
SD card cannot work properly, as well as Adb sideload, so Official LOS.zip cannot be flashed,
OR
2b. fastboot flash boot lineage-19.1-20220604-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220604-recovery-nio.img
Stucked on the Boot-up screen with Logo before Recovery mode.
3. flash Stock EU rom
(to achieve more international firmware, since I don't find independent firmware.zip)
4. flash LOS rom
N.B. [data] partition had been cleared, and I should haven't cleared [system] partition, but I cannot boot back to stock rom after Step 2, and I believe the stock rom has been removed for any accident.
Please help

Might be a long shot here, but I bricked G100 when trying to flash to both slots. Use the Motorola device recovery tool to bring it back to stock and flash only ONE slot (the active one) with your rom. There's installation scripts on this forum that do exactly this for you.

twelfth said:
Might be a long shot here, but I bricked G100 when trying to flash to both slots. Use the Motorola device recovery tool to bring it back to stock and flash only ONE slot (the active one) with your rom. There's installation scripts on this forum that do exactly this for you.
Click to expand...
Click to collapse
Initially I just flash one slot. Then I read that inconsistency between 2 slots can cause problem, so I have flash 2nd slot also, by copy-partitions-20210323_1922.zip or by "fastboot flash boot_b ...".
Now, I can also recovery and boot back to stock rom, by flash boot.img extracted from stock rom.zip with the same version as mine.
So the KEY problem is:
Under TWRP recovery loader, with ADB sideload turned on, the PC seems cannot connect & send below crucial command to Android:
$ fastboot flash boot lineage-19.1-20220604-recovery-nio.img
N.B. I have already used USB driver from Motorola, so ADB commands can run without problem, except ADB Sideload mode. Also, I have tried using USB 2.0 hub port with 2.0 cable (4-pins) as well.

TWRP for nio is not stable (yet). Use the instructions for lineageos official.

patwwh said:
I got Motorola Edge S from China, and plan to:
1. Unlock (Succeeded !)
2a. fastboot flash boot twrp-3.5.2_11.0-2-nio.img
fastboot flash boot_b twrp-3.5.2_11.0-2-nio.img
SD card cannot work properly, as well as Adb sideload, so Official LOS.zip cannot be flashed,
OR
2b. fastboot flash boot lineage-19.1-20220604-recovery-nio.img
fastboot flash boot_b lineage-19.1-20220604-recovery-nio.img
Stucked on the Boot-up screen with Logo before Recovery mode.
3. flash Stock EU rom
(to achieve more international firmware, since I don't find independent firmware.zip)
4. flash LOS rom
N.B. [data] partition had been cleared, and I should haven't cleared [system] partition, but I cannot boot back to stock rom after Step 2, and I believe the stock rom has been removed for any accident.
Please help
Click to expand...
Click to collapse
Late here but on 2a step, you can actually copy the ROM zip to internal storage since windows can detect your phone as storage device when it is in TWRP recovery.

https://wiki.lineageos.org/devices/nio/install is telling everything you need to know.
Though:
NEW:
Code:
fastboot devices
fastboot --set-active=a
// Update firmware
// Files taken from https://mirrors.lolinet.com/firmware/motorola/nio/official/RETEU/
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot erase mdmddr
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase mdm1m9kefs1
fastboot erase mdm1m9kefs2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot erase carrier
fastboot erase ddr
fastboot reboot bootloader
fastboot devices
fastboot --set-active=a
// First setup
// Files taken from https://mirror.math.princeton.edu/pub/lineageos/full/nio/
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
fastboot reboot bootloader
fastboot devices
fastboot --set-active=a
// Install recovery
// Files taken from https://download.lineageos.org/nio
fastboot flash boot <recovery_filename>.img
for example:
fastboot flash boot_a <recovery.img>
fastboot flash boot_b <recovery.img>
fastboot reboot recovery
// Be sure all firmware is consistant
// Files taken from https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
adb sideload copy-partitions-20220613-signed.zip
fastboot reboot recovery
FRESH INSTALL OF LINEAGE
Code:
Reboot into recovery
CHECK WHICH IS THE ACTIVE PARTITION, FIRST TIME A
Goto “Factory reset”
Goto “Format data/factory reset”
Goto “Format data”
Goto “Apply Update”
Goto “Apply from adb”
adb sideload <lineageos.zip>
Goto “Advanced”
Goto “Reboot to recovery” (now active partition is changed to the updated one)
CHECK WHICH IS THE ACTIVE PARTITION, FIRST TIME SHOULD BE B!!
Reboot to system and setup...
(This is how I do it...)
(On updates, active partition is switching on reboot after you have done a flash of lineageos.zip file)
(Forget TWRP for this device as it is not finished and several bugs are there. Just use Lineage OS)

TWRP only works on Android 11, above that nothing will work and it will be very buggy