Database Develop

[Q] Help? Softbrick, stuck in AP Fastboot: Security Version Downgraded / Boot Failure

Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:

You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..

DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?

audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight

Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?

I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.

Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/

Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.

DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.

TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"

Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.

Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.

have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems

Return to stock

Hey All,
I was looking for a "Return to stock" guide but couldnt find any. Does anyone here know where I can find stock images perhaps?
Need to sent it back to the retailer and gotta have it stock.
Hope someone can help me.
Thanks!

nerotix said:
Hey All,
I was looking for a "Return to stock" guide but couldnt find any. Does anyone here know where I can find stock images perhaps?
Need to sent it back to the retailer and gotta have it stock.
Hope someone can help me.
Thanks!
Click to expand...
Click to collapse
What did you do to it that you can't manually undo?

_MetalHead_ said:
What did you do to it that you can't manually undo?
Click to expand...
Click to collapse
Nothing it all, I just unlocked bootloader like everyone else and rooted it. But now when I try to do it manualy I get 2 errors, I do this:
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
On the boot.img and recovery.img flash I get this error for both:
D:\android-sdk\sdk\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10280 KB)...
OKAY [ 0.370s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.596s
I also tried it with mfastboot, both didnt work.. and when I do fastboot oem lock I get :
D:\android-sdk\sdk\platform-tools>mfastboot oem lock
...
sst lock failure!
OKAY [ 0.026s]
finished. total time: 0.026s

If you didn't flash a custom recovery and kernel, there is no reason to try and flash recovery or boot. Just hit the unroot option in SuperSU, and relock the bootloader and you should be good to go.

_MetalHead_ said:
If you didn't flash a custom recovery and kernel, there is no reason to try and flash recovery or boot. Just hit the unroot option in SuperSU, and relock the bootloader and you should be good to go.
Click to expand...
Click to collapse
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.

nerotix said:
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
Click to expand...
Click to collapse
That's weird, I've never heard of that before . It must be something unique to the X. Sounds like we need the stock boot and recovery images to relock the bootloader. Are the signed images even available to us yet? I have no clue...

nerotix said:
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
Click to expand...
Click to collapse
Sadly motorola hasn't put up any factory images on their website as far as i know. In their support forums they said they'll be coming up soon a month ago though. There's a tool posted on the Moto X dev forums which seemed to have a system.img and other images embedded, just read that up and see if it helps.
Alternatively, there's no real need for you to relock, most likely no one's gonna notice it. And if yours is not a pure edition they would know if they checked your imei if you have unlocked or not irrespective of you locking the bootloader or not. So the best and quick solution for you is to unroot, flash the logo.bin file posted on the Moto X dev forums so that you dont have any message showing up that you have unlocked the bootloader on starting up your device.

[GUIDE] How to ROOT HTC Desire 10 Lifestyle

Install TWRP recovery
First of all, the phone must be bootloader unlocked, if you didn't do that please unlock the bootloader first, you can find many guide for that.
https://www.htcdev.com/bootloader/
And one thing, there is a switch called "OEM Unlock" in developer options menu, make it turn on or you will fail to get unlock token.
Now you have a bootloader unlocked device right?
Please download this TWRP recovery
https://twrp.me/htc/htcdesire10lifestyle.html
Let phone reboot to bootloader and switch to fastboot mode then use the command to boot the recovery.
(Temporary)
Code:
fastboot boot twrp-3.2.1-0-a56dj.img
If you want install TWRP as main recovery please use the command
Code:
fastboot flash recovery twrp-3.2.1-0-a56dj.img
Okay, If everything are work in right way, your device should be in TWRP recovery, you can do everything you want.
I recommend to use Magisk to get root :good:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

can you help me. i cant unlock the bootloader cos the command is not working getting this message
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..

I am really tired, its been a month, tried every possible combination of unlock codes but this device bootloader is not going to be unlocked. Tried on 03 different PC's.
Any help will be appreciated.
Below is the log
PS D:\Cell Phones\HTC> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s

Haroon_ said:
I am really tired, its been a month, tried every possible combination of unlock codes but this device bootloader is not going to be unlocked. Tried on 03 different PC's.
Any help will be appreciated.
Below is the log
PS D:\Cell Phones\HTC> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
Click to expand...
Click to collapse
U didnt swiched on "OEM Unlock" in developer options menu, turn it on or it will fail to flash the unlock token.

after i unlocked bootoader.....
I cann't Enter to fastboot or bootloader by pressing on volume down + turn on or volume up + turn on while my device turned off
I have broken the bootloader lock but i couldn't root my htc lifestyle
please please developers.... i want to root my device to be able to setup new version of android after 6.0.1
If you know the couse help me plz
I am waiting ... bro

Hi OP,
The link given for TWRP recovery is not working ; "404 not found' is shown.
Plz help.

Eversmile23 said:
Hi OP,
The link given for TWRP recovery is not working ; "404 not found' is shown.
Plz help.
Click to expand...
Click to collapse
I've made desire 10 lifestyle officially supported on TWRP website, download TWRP recovery here.
https://twrp.me/htc/htcdesire10lifestyle.html

a56dj?
sabpprook said:
I've made desire 10 lifestyle officially supported on TWRP website, download TWRP recovery here.
https://twrp.me/htc/htcdesire10lifestyle.html
Click to expand...
Click to collapse
Thank you very much for letting me get the required link. I just wanted to know what is 'a56dj', is it the code for HTC Desire 10 Lifestyle? How can I get stock boot image for my device, which I think is required while using "magisk" to get root?
Prasanna

adb can help.
tyten said:
I cann't Enter to fastboot or bootloader by pressing on volume down + turn on or volume up + turn on while my device turned off
I have broken the bootloader lock but i couldn't root my htc lifestyle
please please developers.... i want to root my device to be able to setup new version of android after 6.0.1
If you know the couse help me plz
I am waiting ... bro
Click to expand...
Click to collapse
If you know adb, then you can connect your device to the PC/Laptop and use the command ' adb reboot-bootloader' to get into fastboot mode. I am also trying to root my device. I will flash 'twrp' and then see what I can do for rooting. But, I have to be careful. I must be able to flash stock recovery.

Getting error in flashing TWRP.
Hi Op,
The command 'fastboot flash twrp-3.2.1-0-a56dj.img' is not working on my device in fastboot mode. It says ' unknown partition twrp-3.2.1-0-a56dj.img' in the second line it says : can not determine image filename for 'twrp-3.2.1-0-a56dj.img'. But I tested the same '.img' file by booting into the TWRP recovery on my mobile through the 'fastboot boot ................... ' command. What is the cause of the error. Plz help.

Eversmile23 said:
Hi Op,
The command 'fastboot flash twrp-3.2.1-0-a56dj.img' is not working on my device in fastboot mode. It says ' unknown partition twrp-3.2.1-0-a56dj.img'......
Click to expand...
Click to collapse
oops, the command to flash recovery is missing partition name, try this please.
Code:
fastboot flash recovery <image>

sabpprook said:
I've made desire 10 lifestyle officially supported on TWRP website, download TWRP recovery here.
https://twrp.me/htc/htcdesire10lifestyle.html
Click to expand...
Click to collapse
Much appreciated, works perfect where the older test versions were having touch issues or at least for me a56dj-dugl

Hi OP,
I am really happy as I could gain root access on my HTC through your valuable guidance.

Help required for busybox.
Hi OP,
Can you guide me to any forum/tutorial for dealing with problems in installing busybox ? Busybox installation fails repeatedly on my device -- through 'busybox installer' & flashing zip file through recovery-- both not successful. Is it because SeLinux enforcing? Do I have to go for S-Off, then only I can install busybox? Plz help.

Sir I have HTC desire 10 compact
I have to flash custom recovery
Plzz help me

HTC Desire!0 LifeStyle Very Bad phone No more Update OS for Last TWO years

That TWRP (twrp-3.2.3-0-a56dj.img) file can't be mounted or is not valid.

Hi, does anybody know working custom rom for HTC Desire 10 Lifestyle? Thanks

Unbrick

Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks

frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry

danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>

frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/

danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:

not possible to flash firmware in downloade mode?

mrt box

elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..

Dude, I have the same problem with a P20 Pro since january!

Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.

deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?

Fashing Locked e Unlock OEM At Developer Option.. Moto G7 Plus

How to unlock the OEM when I could not activate the developer options, because the device does not turn on?
It is not possible to flash a ROM because it says: flashing_locked
In short, the device only goes to Fastboot.
------------------
I manage to do the following. I did a temporary boot via Fastboot.
fastboot boot "Original ROM file or Boot.img Patched with Root"

More information I have I will be putting it here.

An application to use adb and fastboot without a computer.
Bugjaeger or Bugjaeger Premium
ps: requires otg support on the device you are going to control.

I'm out of results at the moment, I couldn't recover my Moto G7 Plus.
I've already lost almost 100% of the hopes that I can manage.
I think I will have to send it to a Motorola Official Technician or buy another device, as it is not worth me to have it fixed. because the stores are far from my city.

I was able to start the device, but I still can't activate oem unlock.
it is already a progress.
I used a modified boot.img and started the device using:
fastboot boot boot.img
the problem I have to use this command to turn on the device without...

if i get more news i will talk here.

Anrito Kun said:
if i get more news i will talk here.
Click to expand...
Click to collapse
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?

wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
------------------
I don't know how to send files here.
I have no new results, but I will try to send the boot.img that could connect the device.

wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img

I haven't been able to do anything new yet.
I think that only specialist technicians will know how to fix the device.

Anrito Kun said:
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
Click to expand...
Click to collapse
------------------
After downloading use the command: fastboot boot file.img
This managed to start the device, but I couldn't get into Recovery ... At least I couldn't.

Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.

Anrito Kun said:
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Click to expand...
Click to collapse
------------------
I think it may be possible to join TWRP with the system's Boot.img. As if it were a magched patched, only instead of magisk it is TWRP.

delete

delete

poog said:
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....tried 2 things that fail
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.510s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
Click to expand...
Click to collapse
------------------
You're using the Moto G7 plus, right?
the command has to be this to use the file:
fastboot boot "file name".img

poog said:
I can boot to fastboot, but I cannot flash anything. I cannot get a proper return with "fastboot devices"
I cannot get RSD LITE to recognize my device. (win 10). I have read to try win7
Device Manager (windows 10) can only show the device as "Motorola ADB Device". I have not figured out how to force it to show as Qualcom ..............if that will make a difference or not. qualcom drivers are installed.
Before I messed it up I was able to load the device as a qualcom device on the right port and blankflashed after I hardbricked with nothing on screen.
Ability to boot to fastboot but not flash anything seems it is effectively dead for now.
Click to expand...
Click to collapse
------------------
There is no point in trying Flash on the device when the device is Flashing Locked.

My phone is in the same situation after I tried to re-lock the bootloader. Please do follow up on your progress.

hey I have the same problem have you found a solution?

Unfortunately, no.