Hi,
Earlier on today I was trying to root my phone (Well at least put TWRP on so I could mount a rom) and somehow the bootloader got locked during the process this has prevented me to install any roms....
I know it's locked because of -
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.079s]
finished. total time: 0.080s
I've tried to recover it back to normal during the "Fastboot Mode" state but not had any luck I believe the phones bricked? -
C:\Users\Liam\Desktop\One Plus Recovery\A2001_14_A.03_150805>fastboot flash user
data userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
I need this sorting as I don't have a phone to use, and would really apreiciate if someone could help me as i've spent like 8 hours today trying to sort it but not had any luck i've downloaded drivers (Qualcom), Android SDK, this Qualcom-download-tool for recovery and nothing seems to work
It will only boot into "Fastboot Mode"
i recommand you to ask this on OnePlus forums there is more people that answer
otherwize did you tried fastboot oem unlock and is your phone recognize by your computer ?
Use the Qualcomm recover method mentioned many times over in this forum.
try fastboot oem unlock.
did u enabled oem unlock option in dev settings while unlocking bl?
what exactly steps you followed?
Hello all,
I recently bought a OnePlus 2 and attempted to root it. I can only remember trying to root it with a locked bootloader (which caused the OnePlus startup to hang). Eventually, I put the OS back in. Now, in a second attempt to root my phone, the first step was to unlock the bootloader. Every time I type "fastboot oem unlock" it brings me back to TWRP. When boot back into fastboot and check device info, I get this:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.070s]
finished. total time: 0.070s
Also, attempting to flash any recovery (or any other command) returns this:
target reported max download size of 536870912 bytes
sending 'recovery' (22032 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.742s
Any suggestions? I've tried searching so many different threads all over Google.
Files that I have available to use: stock recovery, TWRP recovery, latest full ROM from OPT
Follow this guide:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
I already tried this guide. The phone is fully functional. I just cannot unlock the bootloader.
Every time I type "fastboot oem unlock" it brings me back to TWRP.
Click to expand...
Click to collapse
How did you install TWRP if the bootloader is locked? Did you install TWRP previously and re-lock the bootloader?
I have no idea. I think so. But it's fine I somehow managed to unlock the bootloader (finally). I just found out that OxygenOS 3.1.0 doesn't allow root.
My op2 is running Oxygen Os v.3.0 [A2003]. The problem i'm having is my device doesn't have recovery. I tried to flash recovery but couldn't unlock oem. fastboot oem unlock gives the below message:
E:\Android\OP2>fastboot oem unlock
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
But when I run fastboot device-info it gives the below message:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
And thus unable to flash recovery.
E:\Android\OP2>fastboot flash recovery stock.img
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.671s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.702s
Click to expand...
Click to collapse
I searched in internet and found few solutions but it was for A2001 OP2 device and there was no qualacomm drivers for A2003.
Whenever my OP2 shutdowns and i restart it is stuck on oneplus logo and i need to plug it into my pc and use fastboot continue command to run it smoothly.
The model number doesn't matter, it only shows where the phone was intended to sell. You can try any tutorial that is for Oneplus2.
Old thread: Unrooting gives me bootloop?
Hi there everyone,
After upgrading to Oreo, I unlocked my bootloader, flashed TWRP and Magisk. After that I did a backup of my System and Boot partitions on my currently active slot B. For some reason Slot A doesn't really boot up, so I don't really know what's up with that.
The problem is, before rooting everything was perfect and after the root I feel the instability. I've been using rooted devices for years now and I've never really had problems with the stock ROM being rooted.
So how do I unroot? Well, it's as simple as clicking Complete Unroot in Magisk. Yeah, that bootloops. Trying to flash MagiskUninstaller zip? That bootloops too. The only thing that saved me from those bootloops was that backup I did with TWRP. Yeah, that was after Magisk already had take a crap on my boot image.
Any suggestions that don't involve me losing my 30 Gigs of precious data? I would like to try with Mi Flash Tool but I'm scared from bootlooping for long periods of time (I don't have all day, after all).
New question: How to lock bootloader without wiping?
Hi there again!
I tried flashing the original system.img and boot.img from a fastboot Oreo ROM I found online. I just wanted to lock my bootloader, since currently I don't really need Root access anymore and I don't want this poor security a phone with an unlocked bootloader brings. The problem is, when I type fastboot oem lock it doesn't want to boot anymore, even without Magisk.
Does anybody know a fastboot ROM out there that can be locked? At the official MIUI.com website the fastboot ROM hasn't been updated for a very long time and I don't want to wipe my data. Does anybody have a perfectly working Oreo image that can be locked?
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Thank you very much for the help! I'm gonna try this now. I'm pretty new to this A/B partitioning scheme, I knew that there isn't a recovery partition but I didn't know that TWRP is stored in Boot.img
Thanks again! Have a wonderful day/night!
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
nicolasmart said:
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
Click to expand...
Click to collapse
Which stock boot.img exactly did you use?
_mysiak_ said:
Which stock boot.img exactly did you use?
Click to expand...
Click to collapse
The one from the Oreo fastboot ROM. Got it from here.
nicolasmart said:
The one from the Oreo fastboot ROM. Got it from here.
Click to expand...
Click to collapse
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
_mysiak_ said:
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
Click to expand...
Click to collapse
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
nicolasmart said:
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
Click to expand...
Click to collapse
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
_mysiak_ said:
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
Click to expand...
Click to collapse
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
nicolasmart said:
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
Click to expand...
Click to collapse
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
_mysiak_ said:
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
Click to expand...
Click to collapse
Well, I did all that and I now have a perfectly working system with stock recovery and I think it doesn't boot loop anymore with a stock boot image. Thank you!
However, I tried to lock my bootloader via fastboot oem lock, the first time I was using some shady boot image which should be "stock" but it really wasn't, and it said "The system has been destroyed." I really laughed at this label and went into fastboot to unlock my bootloader again. I switched the boot image to a legit one which has Magisk installed, tried to lock again but this time it flashed the Mi logo for a split second and then a dark screen appeared (can somebody please explain this weird behaviour?). I really scared because the PC wasn't detecting the phone but I held the Volume Down + Power buttons for 10 seconds hoping I will see the Mi Bunny on the Fastboot. Yeah, it worked. I unlocked the bootloader again (lol) and my phone was working again!
Don't worry! My phone's still OK and 100% functioning.
The only reason I tried to lock my bootloader with Magisk installed is because somebody said it worked for them. However, now I realize how risky would that be. Whenever an OTA appears you should hope you don't get locked out of your phone.
So, people with a rooted Mi A1 - don't lock your bootloader unless you fully unroot and revert to stock!!!
How can I lock my bootloader again without wiping? (See the updated first post for more information)
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
Just wait for an official Xiaomi fastboot Oreo ROM and either use MiFlash or included script "flash_all_except_storage.bat". It will lock bootloader at the end of flashing procedure. Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time (some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
For more detailed instructions have a look over here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
flash_all_except_storage = Keep your data, bootloader gets re-locked is the variant you are looking for.
Please keep in mind, that downgrading is not recommended. So this solution is absolutely fine when you are at 7.12.19 or below.
If you are not, you have to wait for the next fastboot update package to become available (like me)
It’s better to do a clean flash using the ROM and MiFlash provided on Xiaomi Website to ensure that the system is unmodified and you won’t get errors or bricks during a future OTA.
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
nicolasmart said:
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
Click to expand...
Click to collapse
Fastboot ROM should be out in a couple of days, usually it's released one week after first OTA update (the one from 19th December was online on 26th or 27th if I remember correctly).
Edit: Clean flash is not necessary, only full flash of all stock images, except user data.
_mysiak_ said:
Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time
Click to expand...
Click to collapse
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
_mysiak_ said:
(some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
Click to expand...
Click to collapse
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
_jis_ said:
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
Click to expand...
Click to collapse
Thanks for the confirmation. I consider it as a serious security flaw and was really surprised as well. I would like to know Xiaomi's reason to do it this way.. Users should be aware that they have to keep data encrypted with good PIN/pattern and request it on each boot to keep information secure.
So I have run CandyOS for a while, but since it got bricked for some reason (possibly something to do with magisk modules) I decided to run another ROM instead. This is what I've done, keep in mind my bootloader has been unlocked the whole time:
1. booted into TWRP
2. flashed LOS 17.1 (gave error 18)
3. booted into bootloader in order to boot into LOS native recovery which I here realized existed (although their installation page says to use TWRP)
4. phone reboots into a changed bootloader which now claims "oem_locked"
The bootloader:
Code:
(in the middle of screen) Power off
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-river_retail-0ff2095b20-200404
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
oem_locked
I've tried a couple of things, results below:
I tried to unlock the bootloader (I have the unlock code saved):
Code:
fastboot oem unlock XXXXXXXX (bootloader) feature disabled
OKAY [ 0.003s]
Finished. Total time: 0.008s
Tried to flash a recovery:
Code:
fastboot flash recovery lineage-17.1-20200719-recovery-river.img
target reported max download size of 536870912 bytes
sending 'recovery' (20318 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.701s
..boot into recovery:
Code:
fastboot boot lineage-17.1-20200719-recovery-river.img
downloading 'boot.img'...
OKAY [ 0.702s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.702s
The exact same things happens with TWRP
I have also tried the Lenovo recovery program with no success, it refuses to recognize my device.
So what would be my next steps? Any help would be appreciated as I've tried to ask in a couple of places with no success
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
No this actually didn't occur to me, I'll try it as soon as I get home and see what happens. Thank you!
Andvark said:
Did you try manually flashing to stock? If your bl somehow got updated to Android 10 along the way, it may explain some things. If stock 9 doesn't take, then perhaps try stock 10. :fingers-crossed:
Click to expand...
Click to collapse
It didn't work:
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.093s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.125s
Code:
fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.365s
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies
yarnbomb said:
It didn't work:
Did I do something wrong?
Edit: just realized I should've tried the same with 9 instead of instantly jumping to 10, I'll report back in a bit!
Edit 2: Nevermind, same result with 9 so the above still applies
Click to expand...
Click to collapse
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs
sd_shadow said:
Manual flashing rarely work with locked moto bootloaders anymore.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Oh, didn't know that. What would be my options with this?
yarnbomb said:
Oh, didn't know that. What would be my options with this?
Click to expand...
Click to collapse
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
LMSA's Flash Rescue or RSD Lite
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The former didn't recognize my device, the latter I didn't know about, I'll try it asap
yarnbomb said:
The former didn't recognize my device, the latter I didn't know about, I'll try it asap
Click to expand...
Click to collapse
RSD Lite doesn't work with most windows 10 machines, try windows 7 if you can.
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
timba123 said:
You need blankflash
Click to expand...
Click to collapse
Not if it's in fastboot mode.
Sent from my ali using XDA Labs
timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Fastboot OEM blankflash doesn't work if bootloader is locked.
timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
Timba, can you hook me up with the Telegram group for the G7?
Wondering if they have a blankflash for Android 10 or something.
timba123 said:
I had the same issues he described. Make sure Qualcomm QDLoader drivers are installed. While in that ap fastboot mode use fastboot oem blankflash command. The phone will reboot to blankflash mode. Then use the correct blankflash. All that oem locked, invalid partition, remote failure will be gone, fixed. I learned this in Telegram group Moto G7 Power Support
Click to expand...
Click to collapse
you are absolute about this because same issue happen to me and all has failed this definitely did the fix on my moto g7 power I just want to Thank You for this really appreciate it
timba123 said:
He stated he unlocked bootloader already. I did too and had same problem. Its saying oem locked due to a bad flash or didnt flash copypartitions zip in twrp. Can we contact him and try it? I bet it will work. I'm on XT1955-5 but it's the same issue I and many others have been in and fixed.
Click to expand...
Click to collapse
yes worked on mine xt1955-5 and yes was cause on flashing a custom rom thought was brick for good till had to came arcoss this fix and the only fix that got it out of that ap fastboot bullshits and yes had oem lock before it happen and when it bricked oem say's it's lock which got me thinking how in the hell going get out of this tryed all other method mention non work glad this did again thanks