Database Info

Can't unlock bootloader

I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?

aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
There are How-to's on this site. It's probably unlocked now. Try flashing a custum recovery in fastboot.

aroshlakshan said:
I have a OPO Chinese 16GB version. When I bought it, it was running CM11S(Seller flashed it). Now I'm trying to wipe my phone and install cm-11.0-XNPH38R-bacon-signed-fastboot.zip on it. I have installed ADB Drivers on my Windows computer and when I type adb devices it shows me the serial number of the phone. And also when I type in fastboot devices, it shows me the serial number. But I can't get it to unlock the boot loader. When I type in the command, fastboot oem unlock, I can see the following message.
...
OKAY [ 0.002s]
finished. total time: 0.004s
But it does nothing after that. Even when I reboot, I can see all my previous apps, files etc. are there. It doesn't make any change. How can I get this phone to unlock the bootloader and allow me to install a custom recovery and let me flash the above file I have mentioned?
Click to expand...
Click to collapse
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.

ken_alpha24 said:
That means that the device was already unlocked. Where did you buy yours? Ali Express? Mine's from there and I have gone through what you're going through right now. No worries. Bootloader is already unlocked so you can root it already.
Click to expand...
Click to collapse
I bought that off of eBay. I have tried to flash a custom recovery but it doesn't seem to get installed as well. After I do it, I only see the stock recovery but when I run the command fastboot flash recovery recovery.img it gives me the following message.
target reported max download size of 536870912 bytes
sending 'recovery' (8134 KB)...
OKAY [ 0.264s]
writing 'recovery'...
OKAY [ 0.179s]
finished. total time: 0.445s
But when I go to recovery, I only see the stock recovery. It seems like even-though the command are executed successfully on the computer, they are not applied to the phone. Any ideas?

Any ideas guys?

aroshlakshan said:
Any ideas guys?
Click to expand...
Click to collapse
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.

zephiK said:
Settings > Developer Options > Update CM Recovery (untick)
Then flash your recovery via fastboot and it'll stick.
Click to expand...
Click to collapse
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?

aroshlakshan said:
I was able to flash a custom recovery. Thank you. I'm now about to CLEAN INSTALL XNPH38R on my phone. Any ideas on how to do that?
Click to expand...
Click to collapse
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk

zephiK said:
Download the factory stock images on cyngn. Find it online and fastboot flash it. There's a good guide online in the general forums that shows you how to go back to stock
Sent from my One A0001 using Tapatalk
Click to expand...
Click to collapse
I got it working. I flashed TWRP on my phone and wiped the phone. Downloaded http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip , extracted the contents and flashed it with fastboot using the following commands.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img
fastboot reboot
Hope this helps a newcomer like me. Thanks guys.

[Solution - NO SIM DETECTED] [CM13-based ROMs] - XT1562 Single SIM EU

Hi all.
If you are here, then you have likely experienced issues with custom ROMs not detecting SIM, or you are still experiencing this issue.
I have a XT1562 UK Single-SIM model and have had this problem with EVERY ROM I have tried and it was getting so frustrating.
Over the last few weeks, I have flashed custom ROMs based on CM13 and all have presented the SIM not detected issue. A simple fix was to pop-out the SIM module and reinsert - more often than never, the SIM was detected. Then I would restart (as is often the case with a custom setup) and alas, the SIM was not detectable.
After trying various suggestions from developers, nothing was working until I happened to flash a dualSIM firmware and I haven't looked back. I can now flash EVERY CM13-based ROM with successful SIM detection BUT it takes a few extra steps to get to that stage.
Here are the things you need:
This firmware
This fix
A custom ROM of your choice (Highly recommend crDroid or Temasek)
GAPPS of your choice - I would recommend this
TWRP
Okay - the solution (confirmed working and reliable):
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot​
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
Voila! You can now confidently flash ANY CM13-based custom ROM with the added assurance of SIM detection. IF, however, you flash a ROM and SIM is NOT detected, then simply reflash the DualSIMFix.
If this solution works for you, please give credit where it's due - thank me using the thumbs-up icon below AND vote in the poll at the head of this thread

So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?

perfectsense72 said:
So, you want to say, that i need to flash stock DS ROM
and after that i'll can flash any custom CM13 based ROM and SIM will be detected?
Click to expand...
Click to collapse
It has worked for me and I have tried everything that has been recommended. Just by determined trial-and-error I have found my solution.

Just to reiterate
and my intention is to generate enough interest to further assist developers of the CM13 custom ROMs.
Click to expand...
Click to collapse

Can you write a sequence of actions? What nuances?

perfectsense72 said:
Can you write a sequence of actions? What nuances?
Click to expand...
Click to collapse
I fastboot flashed XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18.1 (here ); flashed ROM; flashed GAPPS and then flashed DualSIMFix (from here)
I've tested reboots and SIM is detected each time.
I am assuming you know how to flash a stock image - if not let me know.

I am assuming you know how to flash a stock image - if not let me know
Click to expand...
Click to collapse
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?

perfectsense72 said:
From PC by fastboot in stock recovery mode, right?
Did you perform any wipe between flashing stocj ROM and flashing CM13 based ROM?
Click to expand...
Click to collapse
Follow this:
1. Unpack the Firmware into it's own folder
2. Copy across the files to Fastboot folder
3. Restart phone into bootloader (power off first then hold power and volume down)
4. In the Fastboot folder hold shift and right click.
5. Select "open command window here"
6. Connect phone via USB to computer and in command window enter the following commands 1 by 1 making sure "[okay]" is displayed each time:
if nothing happens on screen, then simply use your volume keys on the phone to restart the bootloader
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
7. Once completed restart phone and setup as normal.
8. When setup is complete, restart phone into bootloader.
9. Flash TWRP
10. Restart phone into recovery
11. in TWRP, factory reset then flash ROM and GAPPS and DualSIMFix
12. Restart phone and setup. If SIM shows not detected, press "skip" and it should detect after WiFi setup.
13. Enjoy - but please let me know if not quite right.

@perfectsense72 - once you are able to confirm fully working, then I'll amend the OP to reflect necessary details for successful detection, etc. Thanks for trying this.

Thank you, i'll try tomorrow.

I can't confirm your problems with single sim modem.
I have german single sim and had problems after flashing french dual sim stock image and then flash cm13 roms.
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
After flashing back a single sim stock and completly boot the stock then flash again crdroid no problems appeared again. All fine with detected sim on every boot.

For now I'm using Pac-ROM (LP) and have no problem, I'll try CrDroid soon and I'll let you know.

Jeso said:
Sometimes the boot was fine with detected sim and sometimes without detected sim and with random reboots of the device.
Click to expand...
Click to collapse
This is what I'm aiming to avoid for those with issues such as this. Every firmware flash produced an error on flashing bootloader. The only one to not present me with the error is the 18.1 DS retasia.
This has, I believe, been the key to my issues as well as other users. I can flash any official firmware and use it perfectly well, it's just the custom MM ROMs that are problematic.

moozer said:
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Does it lock the bootloader?
(Sorry for noob question)

axxx007xxxz said:
Does it lock the bootloader?
(Sorry for noob question)
Click to expand...
Click to collapse
No - this just re-introduces the stock bootloader for the firmware

So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.

perfectsense72 said:
So, it's working. Flash Unoficial CM13 after stock DS asian and no problem, both simcards a detected.
Thanks, moozer.
Click to expand...
Click to collapse
You're welcome. Checked rebooting the phone? SIM remains?
You can now flash custom ROMs to your heart's content. No need to fart around with firmware flashes. All that you need to check is SIM detection on setup and if necessary flash the SIMfix.

^^

Yes, SIM remains after reboot, everything is OK

Thanks a lot! Worked perfectly for me aswell. Currently running ResurrectionRemix and I've had no problems with the sim card since.

Moto G4 play harpia stock firmware.

I figured that since the Motorola web site doesn't have the firmware for this yet I would post a link to my Dropbox so others have access to the firmware. This is for us cellular Moto g4 play xt1607 not sure if it will work for devices on a different carrier. If someone could make a backup of their current rom and test it out to let us all know if it does that would be great. Please hit the thanks button if this helps anyone. https://www.dropbox.com/s/i6jsafelq...y-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?dl=0
This must be flashed with fastboot. If you do not know how to flash with fastboot there are tons of how to videos if you google it.
BACKUP YOUR DEVICE TO SD CARD OR PC BEFORE DOING ANYTHING!!!!!
DISCLAIMER: FLASHING ANYTHING TO YOUR PHONE HAS RISKS. IF YOU DO NOT KNOW WHAT YOU ARE DOING AND YOU HAVE JUST PURCHASED YOUR PHONE AND HAVE NOT UNLOCKED THE BOOTLOADER STOP!!!!! DO NOT CONTINUE. IM NOT SURE WHAT THE EFFECTS WILL BE IF YOU TRY FLASHING WITH A LOCKED BOOTLOADER, IT COULD BRICK YOUR DEVICE!!!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING THIS FIRMWARE. IF YOU DID SOMETHING WRONG AND DONT FOLLOW INSTRUCTIONS THAN THATS YOUR OWN T.S.

Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then download firmware, unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.

I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
DanHutchins said:
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
Click to expand...
Click to collapse

jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is the bootloader unlocked?

jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What command gives the error?

I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
DanHutchins said:
Is the bootloader unlocked?
Click to expand...
Click to collapse

jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Not sure. Did you make sure USB debugging is active for file transfer?

jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.

II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse

jestyr8 said:
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
Click to expand...
Click to collapse
That's because if you unplug the phone from the PC then plug it back in it defaults the USB debugging to charge only. If you get into twrp you can still put a custom ROM in root of phone to flash in twrp. I would try that then try to install the stock again. Be sure to have debugging set to file transfer.

I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse

jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Please do as of now that's the best I can do. Everything worked fine for me. I have flashed the same file many times on my g4 play

jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Were you able to get back to stock?

DanHutchins said:
Were you able to get back to stock?
Click to expand...
Click to collapse
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.

jestyr8 said:
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
Click to expand...
Click to collapse
I like cm13 there just aren't any real good themes for free. I don't mind donating to a dev. but if I can't test it out to see if I like it or not I don't want to pay.

I'm using the material glass theme along with stealth icons, i like it a lot

jestyr8 said:
I'm using the material glass theme along with stealth icons, i like it a lot
Click to expand...
Click to collapse
Looks cool.

DanHutchins said:
Looks cool.
Click to expand...
Click to collapse
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.

jestyr8 said:
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
Click to expand...
Click to collapse
No problem, ask around for anyone able to make it flash able with twrp I'm sure someone can or at least give you instructions on how to do it.

USB debugging to file transfer
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
Where/how to "change debugging to file transfer" on Win-7?
Thanks!
Until now, my only experience was flashing a recovery image to Moto E2 with command:
Code:
fastboot flash recovery twrp.img
Neither I have to change "USB debugging to file transfer", nor I needed to use command
Code:
fastboot oem fb_mode_set
Is that something new and specific to Moto G Play 4th Gen?
Edit:
I have just unlocked the bootloader of my new Moto G4 Play and flashed a new logo file with command:
Code:
fastboot flash logo logo.bin
Still puzzled by "change debugging to file transfer"

Can't install ROMs? Please check here.

Hi guys. If you can't install ROMs, this is your place to ask. Please be detailed, mention: ROM, build, your variant and firmware version. And tell us your specific issue.
Here's a guide on how to do it, and I'll link you to the files needed for the procedure:
1. If you're using a Google account, remove it in Settings > Accounts and factory reset. Else, skip this step.
2. Unlock your bootloader following Motorola's instructions. Google it, it'll be easy to find and follow.
3. Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And the next files:
TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
copypartitions.zip: https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
4. Hold power + volume down until you reach bootloader (fastboot mode).
In your extracted firmware folder open a terminal and flash your firmware files with these commands:
----------------------------------------------------------------------
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
--------------------------------------------------------------------
Don't worry if any error message appears.
5. Place TWRP .img file into your fastboot folder, and do "fastboot boot TWRP.img" - replace TWRP with file's real name, but it should be the IMG file's name, not the zip file's name. With TWRP booted, now check if the screen actually responds. If it doesn't, just turn your phone off, get into fastboot mode again, and boot TWRP until it works.
6. With that solved, now just copy copypartitions.zip to your sdcard (called external_sd in your phone) and install it. Also copy to your external_sd, just to save time, your ROM and TWRP's installer. And Magisk or GApps if you'll need them.
7. Reboot to bootloader, and do "fastboot -w".
8. "fastboot boot" TWRP again, flash ROM, and flash TWRP's installer (zip file). Boot system.
9. Reboot to bootloader, select recovery mode and flash Magisk/GApps if you need them.
10. Reboot to system, and enjoy
Any questions, feel free to ask 'em in the comments. Hope it works!
P.S.: OmniROM has its own recovery (TWRP is a recovery). So, keep that in mind and don't flash TWRP's zip in Omni if you want it to boot.
Also, if you want, you can try OrangeFOX. It's a cute TWRP replacement that has some interesting features. Worth checking out.

TL;DR:
1. Remove your Google account
2. Flash firmware with the set of commands attached.
3. "Fastboot boot" TWRP and flash copypartitions.zip.
4. Go to bootloader mode and do "fastboot -w".
5. Boot TWRP, flash ROM and TWRP's installer
5.1. Boot system
(optional) 6. Open recovery mode and flash Magisk/GApps.
-----------------------------------------------------------------------------------
Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/app...mless-t3473445
. TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
. copypartitions.zip: https://drive.google.com/file/d/1oir...t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.

All ROMs posted in XDA are actually working in this device.

Thank you for creating this thread. People need to get used to this A/B partition format. This is the proper forum to discuss these issues, not in the development section.

Using these instructions:
crDroid -> bootloop
bootleggers rom -> bootloop
lineageos -> bootloop
ressurection remix -> bootloop
Twrp is screaming at me "Failed to mount /data partition "invalid argument"
I noticed your instructions fail to mention you need to run through the setup process of android, then run fastboot -w, then run twrp format data as fastboot -w will (using retus and amz stock rom) create a "raw" partition table and so on. None of the current roms can handle this and will bootloop.
These incomplete instructions will waste people's time and cause problems.
Please reconsider the purpose of this thread. It is the developers responsibility to add a filesystem check during rom flash and write working instructions. Currently only bootleggers instructions will work to any capacity due to their inbuilt sanity checks.

derek12213 said:
Using these instructions:
crDroid -> bootloop
bootleggers rom -> bootloop
lineageos -> bootloop
ressurection remix -> bootloop
[...]
Click to expand...
Click to collapse
Hey. like I said at the beggining of the thread, it's not possible to help you without giving specifics. Give that info and I'll help you.
I made this thread because this steps worked to dozens of users, and I'm not joking. Literally. They are not incomplete since they worked for everyone. Search for our group in Telegram if you think it's not true. We might be able to help you there too.
TWRP screams "Failed to mount /data partition", that's why internal storage won't work temporarily until you flash a ROM. Could that be better? Of course. But still the procedure works.
"I noticed your instructions fail to mention you need to run through the setup process of..." Nope. There's no need for that. That's why I didn't mentioned it, because I've tried lots of ROMs and never needed to do that.
Also, do you have latest fastboot? Some users had issues because of using older versions of that program.
But yeah, I'm not some friend who can go to your house and see what you've got. So, we need information. I won't be able to help you further if you don't do your part. Tell me what you've got please.

Flash to stock -> fine
follow your instructions for any rom -> bootloop
from stock flashed metropcs rom per crDroid developers recomendation (I am amz fw)
flash all that commands using metropcs firmware (crDroid said to use this one, I am AMZ fw, tried AMZ fw and RETUS fw and it doesnt matter, same result)
fastboot boot twrp
twrp flash copy partitions
reboot bootloader
fastboot -w
boot twrp
flash rom flash twrp
reboot system
bootloop
output of twrp and fastboot during the process :
Erasing 'userdata' OKAY [ 0.117s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
install rom zip and twrp zip (downloaded your versions)
could not mount /data and unnable to find crypto footer
failed to mount /data invalid argument
unable to recreate /data/media folder
updating partition details...
failed to mount /data invalid argument
...done
unable to mount storage
failed to mount /data invalid arugment
Full selinux support is present
unable to mount /data/media/TWRP/.twrp
after flashing twrp says
Failed to mount /data invalid argument
...done
Your guide says " Boot system."
I am interpreting this as reboot system
Bootloop
All roms.
I dont install gapps because I dont need spyware. I would use stock if I wanted to be spyed on 24/7.365
I dont install magisk outside of booting a magisk patched boot img to modify hosts for less CONSTANT TRACKING

Hey, did you read my last reply, as well as the first line of this thread? Where I require specifically to give me some info first to be able to help you. I'm like trying to help a question mark... try to follow a simple rule.
In step 9, you're doing "fastboot boot" to TWRP, or you're actually going to recovery mode? We need to know if TWRP install actually works. Even if you won't use any Magisk or GApps, check if it is actually installed AND working.
I've also heard of users that had issues booting of the first time a ROM with TWRP installed. Maybe just do the procedure until you have to flash a ROM, and boot the system instead of installing TWRP. And flash TWRP after the ROM already booted and it's running.
Also, how much time should pass for you to consider for a ROM to be bootlooping?
Well, both fastboot -w and TWRP mount /data errors are the same thing. Fastboot isn't able to format it properly, so data is not mounted by TWRP. Like I said before, it's a temporal thing that's fixed when flashing the ROM. Don't worry about that.
But please, I don't know if you do this on purpose, you're not following even a simple request stated at the beggining of the thread. Please answer that to keep the conversation going, I won't reply you any further if you don't do your part.

derek12213 said:
Flash to stock -> fine
follow your instructions for any rom -> bootloop
from stock flashed metropcs rom per crDroid developers recomendation (I am amz fw)
flash all that commands using metropcs firmware (crDroid said to use this one, I am AMZ fw, tried AMZ fw and RETUS fw and it doesnt matter, same result)
fastboot boot twrp
twrp flash copy partitions
reboot bootloader
fastboot -w
boot twrp
flash rom flash twrp
reboot system
bootloop
output of twrp and fastboot during the process :
Erasing 'userdata' OKAY [ 0.117s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
install rom zip and twrp zip (downloaded your versions)
could not mount /data and unnable to find crypto footer
failed to mount /data invalid argument
unable to recreate /data/media folder
updating partition details...
failed to mount /data invalid argument
...done
unable to mount storage
failed to mount /data invalid arugment
Full selinux support is present
unable to mount /data/media/TWRP/.twrp
after flashing twrp says
Failed to mount /data invalid argument
...done
Your guide says " Boot system."
I am interpreting this as reboot system
Bootloop
All roms.
I dont install gapps because I dont need spyware. I would use stock if I wanted to be spyed on 24/7.365
I dont install magisk outside of booting a magisk patched boot img to modify hosts for less CONSTANT TRACKING
Click to expand...
Click to collapse
Dude, I had the same issue as you, couldn't load any roms, no matter what guide I followed, it always bootlooped. Turned out to be my microSD was causing it. I followed Life_goes_on's solution on this thread (post #74):
https://forum.xda-developers.com/g7-power/development/rom-resurrection-remix-t3994687/page8
Substituted 'fastboot erase userdata' for 'fastboot -w' and took out my microSD before booting it up and it worked.
I'm using the MetroPCS version on RETUS firmware.

BETA215 said:
Hey, did you read my last reply, as well as the first line of this thread? Where I require specifically to give me some info first to be able to help you. I'm like trying to help a question mark... try to follow a simple rule.
In step 9, you're doing "fastboot boot" to TWRP, or you're actually going to recovery mode? We need to know if TWRP install actually works. Even if you won't use any Magisk or GApps, check if it is actually installed AND working.
I've also heard of users that had issues booting of the first time a ROM with TWRP installed. Maybe just do the procedure until you have to flash a ROM, and boot the system instead of installing TWRP. And flash TWRP after the ROM already booted and it's running.
Also, how much time should pass for you to consider for a ROM to be bootlooping?
Well, both fastboot -w and TWRP mount /data errors are the same thing. Fastboot isn't able to format it properly, so data is not mounted by TWRP. Like I said before, it's a temporal thing that's fixed when flashing the ROM. Don't worry about that.
But please, I don't know if you do this on purpose, you're not following even a simple request stated at the beggining of the thread. Please answer that to keep the conversation going, I won't reply you any further if you don't do your part.
Click to expand...
Click to collapse
After i flash rom and twrp I can go to twrp by holding volume down and pwr then selecting recovery at that point or can boot it via fastboot. I think that it changes parition (from a to b) during this process so I always use twrp to reboot to recovery even if I am not flashing gapps or magisk to rule out problems.
---------- Post added at 12:38 AM ---------- Previous post was at 12:11 AM ----------
framila said:
Dude, I had the same issue as you, couldn't load any roms, no matter what guide I followed, it always bootlooped. Turned out to be my microSD was causing it. I followed Life_goes_on's solution on this thread (post #74):
https://forum.xda-developers.com/g7-power/development/rom-resurrection-remix-t3994687/page8
Substituted 'fastboot erase userdata' for 'fastboot -w' and took out my microSD before booting it up and it worked.
I'm using the MetroPCS version on RETUS firmware.
Click to expand...
Click to collapse
bootloop

Alright I figured it out. It was my sdcard. I did everything using the Dave Chappelle method and it fixed it.
Dave Chappelle method:
1- remove sd card. In fact just remove the whole tray.
2- go back to stock, boot it, do whatever you gotta do. There is a thread on how to go back to stock, follow those instructions, its beyond the scope of the Dave Chappelle method.
3- go to bootloader with vol+pwr held
get your copypartitions.zip, your rom.zip, and twrp.img and twrp.zip in a folder. I like sybers twrp mod but whatever use official doesnt matter.
fastboot boot twrp
wait 3 seconds
adb push copypartitions.zip /tmp/
go to twrp install and go up a level, click copypartitions.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm copypartitions.zip
# you dont have to do above, but we dont want too much stuff in memory, rebooting SHOULD clear memory, but I havent used android extensively they may have windows hibernate thing or whatever.
exit
adb reboot bootloader
fastboot boot twrp.img
adb push rom.zip /tmp/
go to twrp install and go up a level, click rom.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm rom.zip
exit
adb push twrp.zip /tmp/
go to twrp install and go up a level, click twrp.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm twrp.zip
exit
twrp select reboot bootloader
wait a tic
fastboot erase userdata
select recovery and boot
alright so at this point I am good because I dont want gapps or magisk I am done. I would boot a modified boot partition once a month and install adaware hosts modifications, then reboot. I dont want to be walking around with root or google proprietary code. I would then select reboot, make sure slotb is selected, and reboot system.
If you want gapps, then you flash your gapps at this point. I discourage you from doing so and encourage microg for google maps or whatever google service you actually need. I also discourage the idea of walking around with "hot" root. Where you can grant an application root at any time. It is trivial to write an application that modifies what the screen is displaying to trick you into accidentally granting root permissions.

Great guide! We really needed one. Btw you don't necessarily need a SD card to install zips, you can install them directly from your computer by sideloading them with adb on twrp. You can do that by going into twrp, then to Advanced and press on ADB Sideload, now on adb type in: "adb sideload thezipyouwanttoinstall.zip" and twrp will start installing that zip.

BETA215 said:
Hi guys. If you can't install ROMs, this is your place to ask. Please be detailed, mention: ROM, build, your variant and firmware version. And tell us your specific issue.
Here's a guide on how to do it, and I'll link you to the files needed for the procedure:
1. If you're using a Google account, remove it in Settings > Accounts and factory reset. Else, skip this step.
2. Unlock your bootloader following Motorola's instructions. Google it, it'll be easy to find and follow.
3. Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And the next files:
TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
copypartitions.zip: https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
4. Hold power + volume down until you reach bootloader (fastboot mode).
In your extracted firmware folder open a terminal and flash your firmware files with these commands:
----------------------------------------------------------------------
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
--------------------------------------------------------------------
Don't worry if any error message appears.
5. Place TWRP .img file into your fastboot folder, and do "fastboot boot TWRP.img" - replace TWRP with file's real name, but it should be the IMG file's name, not the zip file's name. With TWRP booted, now check if the screen actually responds. If it doesn't, just turn your phone off, get into fastboot mode again, and boot TWRP until it works.
6. With that solved, now just copy copypartitions.zip to your sdcard (called external_sd in your phone) and install it. Also copy to your external_sd, just to save time, your ROM and TWRP's installer. And Magisk or GApps if you'll need them.
7. Reboot to bootloader, and do "fastboot -w".
8. "fastboot boot" TWRP again, flash ROM, and flash TWRP's installer (zip file). Boot system.
9. Reboot to bootloader, select recovery mode and flash Magisk/GApps if you need them.
10. Reboot to system, and enjoy
Any questions, feel free to ask 'em in the comments. Hope it works!
P.S.: OmniROM has its own recovery (TWRP is a recovery). So, keep that in mind and don't flash TWRP's zip in Omni if you want it to boot.
Also, if you want, you can try OrangeFOX. It's a cute TWRP replacement that has some interesting features. Worth checking out.
Click to expand...
Click to collapse
Is there an orange Fox recovery for Moto G7 power?

Ljw4884 said:
Is there an orange Fox recovery for Moto G7 power?
Click to expand...
Click to collapse
Yes and it's absolutely amazing!
You can find it here

@BETA215, I see some folks mentioning bootloops. I personally had many many bootloops before I found out that TWRP/ ROM flashing on this device does not play nice with exFAT filesystem. maybe a note about that in the OP? formatting my SDcard to VFAT resolved all my issues, when it was ExFAT I couldn't get anything past the boot logo

I've just spent the past 10 days trying to root my phone and use a custom ROM working (and detecting SIM card and most important functions). But it's always problem after problem after problem and at this point, I'm ready to give up. I feel broken. I'm at the point where I'd literally pay someone to take control and do it for me. I just can't do it no matter how much I learn, always a new problem and now I'm stuck at this one and I just can't take it anymore. Swear to god, I will pay .

Deleted

SIM Card issue and no gapps?
Hi,
I installed Havoc OS on my moto g7 power XT1955-5, using these steps:
1) Switched off device
2) Volume down+Power to go in bootloader
3) CMD: fastboot erase userdata (maybe useless)
4) CMD: fastboot boot "C:\...\twrp.img" (or orangefox.img)
5) On Slot B mount "system" then wipe and format (maybe useless)
6) On Slot A mount "system" then wipe and format
7) Flash copy-partition-AB.zip
8) Flash Havoc ROM
9) Reboot -> Recovery
10) Flash GApps
11) Reboot -> Bootloader
13) CMD: fastboot erase userdata
14) CMD: fastboot reboot
(from time to time the message: failed to mount /data (invalid argument) popped up, and I don't know why)
However, havoc installed. I don't think Gapps installed though, because all I see in the os that is google related is a searchbar for apps only, gallery go, and the file manager. I used the "arm, 9.0, nano" options from the Gapps website, but when I flashed it, it said no changes were made. Did Gapps flash properly? If it didn't, how do you flash it properly? (I would expect the google play store to be in there somewhere, perhaps I need to get a heavier Gapps than nano?)
More importantly though, the OS says there is no sim card. I am on T-mobile, and calling and texting worked when I used lineage OS.
Does anyone have any advice of how to fix any of these issues? Again, my end goal is to have havoc os with the play store, and have the sim card working to make calls and texts.
Thank you one million to who ever can answer this.

Octodad said:
I've just spent the past 10 days trying to root my phone and use a custom ROM working (and detecting SIM card and most important functions). But it's always problem after problem after problem and at this point, I'm ready to give up. I feel broken. I'm at the point where I'd literally pay someone to take control and do it for me. I just can't do it no matter how much I learn, always a new problem and now I'm stuck at this one and I just can't take it anymore. Swear to god, I will pay .
Click to expand...
Click to collapse
Hey I literally am feeling the same way!! I know it's been a few months, but if you are still working on it, would you like to share knowledge and see if we can help each other?

timba123 said:
MetroPCS Moto G Power .I can't flash anything. And it oem locked. Is there any way to flash a stock partition ? Like Samsung's pit file
Click to expand...
Click to collapse
Try rsd light check into it might b what u looking for

Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.

Hello, friends. So I am here following this exact tutorial :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards

krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.

Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.

krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.

Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards

SOLVED

krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8

Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?

mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.

Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)

I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.

If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.