Database Users

[Solved] Root with locked bootloader, flash failure XT907

Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.

cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641

aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
I did try that and that is how I obtained root. Didn't have a problem up until now.
Anyways, I managed to fix my issue on my own.
Long story short, RSD Lite was flashing the VZW_XT907_4.1.2-9.8.1Q-66_1FF I downloaded from droid-developers.
My phone kept rejecting the tz.mbn saying it was invalid.
Sooooo, I searched for a 98.18.78 OTA pull and I found one.
This is the one for reference.
I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it.
So, I won't delete this just as a reference for anyone who has the same problems as me.
Sorry for taking anyone's time.

cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse

aviwdoowks said:
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
Yes, I just went in my phone settings and did realize this is a previous OTA. I checked for updates and my phone wants me to update to 98.18.78.
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
Click to expand...
Click to collapse
Well, Pretty much, my phone had no rom at the time. I ruined it by trying to flash stuff.
So I downloaded the bottom rom from
sbf.droid-developers.org/scorpion_mini_xt907/list.php
and was trying to flash it onto my phone. My phone kept rejecting the tz.mbn file, it said it was invalid. So I found that old OTA and swapped the two files, and to my surprise, my phone accepted that file. I don't know why it wouldn't take the original one.
Anyways, I'm updating my phone to OTA 98.18.78 right now, so all is good.
Click to expand...
Click to collapse

Samuri HL Downgrade Tool
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
I lost root after the OTA update. Inused SamuriHL Downgrade tool to roll back to the stae my phone was in before update. then it gives instructions on how to retore and keep root. then yuo tkae the update again.

THANK YOU
I thought I was doomed to a bricked phone. This fix saved me.
Important to note for any other poor suckers who find themselves in the same spot - make sure you have an updated version of RSD Lite when you do this. My first (15) attempt(s) failed flashing system.img because I was running an old version of RSD Lite, but when I updated to 6.1.4 it worked fine.

cheno1115, THANK YOU!
I had the same issue with my xt907 after rooting with "DROID_RAZR_M_Utility_1.20" and after restoring my apps (including with framework mods.. stupid, I know) from xt890 via nandroid manager.
I thought oh my god, that is an expensive brick I have now.
I have just reflashed "VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip" via RSD (with "tz.mbn" file raplaced from "Blur_Version.98.16.1.XT907.Verizon.en.US.zip") and it did boot up, however it booted with all my "restored" apps. The problem is that I have tried to restore my home screen via nandroid backup manager and it failed, so I got only upper status bar, soft buttons and black screen... I'm lucky that Motorola placed a settings shortcut on upper drawer, so I was able to navigate to settings and do a factory reset. So this is how I got a fresh start again.
However if I launch "DROID_RAZR_M_Utility_1.20" with option 1 again, I get the same thing - many repeating "sending system.img", have to terminate it and then - a brick. So I had to repeat RSD reflash procedure once more. BTW flashing of "system.img" takes surprisingly long, like 5 minutes or so.
So that got me thinking... Isn't this repeating "sending system" and "writing system" just doing it in pieces and one should wait?
Anyway that has solved my problem. THANKS!

Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907

nifty101 said:
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
Click to expand...
Click to collapse
We have SafeRoot now. See the general section.
No custom roms though.
See my xt907 stuff

Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.

nifty101 said:
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
Click to expand...
Click to collapse
You are on tapatalk or xda app?
Go here & take your punishment. Lol.
http://forum.xda-developers.com/showthread.php?t=2610531
Links
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3

SamuriHL has fix for "cannot load system img"
http://www.droidrzr.com/index.php/topic/37658-green-robot-after-using-house-of-moto/#entry400767

No valid piv
Mr hello I have this problem with no valid PIV on my motorola RARZ M can you help me?

WARNING MOTO G 2nd GEN USERS PLEASE READ

I Have noticed quite a few - as in 3+ Moto G 2nd gens's are having problems with corrupted partitions, i.e OTA fails to install half way through or cant install via Mfastboot and / or Custom recoveries.
Due to the corrupted partition (or rather partition table) IT wont allow flashing / erasing or clearing / factory resets
There's no proven cure but MAYBE locking and then unlocking boot loader again may fix this as it WIPES data.
AS a Precaution I suggest anybody that who is thinking of upgrading / downgrading or restoring does a FULL FACTORY reset AFTER they have backed up phone.
Yes its extra work but with memory cards being cheap and playstore / google accounts backing up your apps, contacts etc, it's simply lazy and Dangerous Not to backup....

so...
my moto gave up during OTA update to 5.0.2 -> flash and rebbot OK, but "optimizing applications", took an eternity, then (in the middle of the job) the screen went black.
after a cold reboot it finished and everythings allright now..

My Moto G has this problem too!
The userdata and cache partitions seem to be corrputed as they give the error: blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata ( /cache )failed
This happens in stock recovery.

Help
I have this Problem too.I was in lexodus Rom then my phone shutdown,then i Turned it on and all apps fc's .I tryed to flash it With twrp but it cames an error execute update binary .I cant restore or wipe anything .And when i try to restore it with you stock Rom installer in succes but it still the same rom with the same Problem .I need help Please PS sorry for my Bad english

When the partition table is completely hosed, you can't lock the bootloader, only unlock. And unlocking in this state does not wipe it.
There is no recovering from this state, and honestly you get what you pay for with these phones.
When the battery drops below 5%, there is a high probability of the eMMC being ****ed in this way (I have had it happen on 4 phones now!). Undoubtedly a major design flaw.

I messed up partitions on my oneplus one. Most specifically the data one trying out f2fs. I was able to recover the partition by formatting it with a combination of philz cwm, twrp, and parted. I don't remember what I did as I was desperate to fix my oneplus. You can look into learning how "parted" works and you may be able to reformart the partition through adb shell.
I know this is a bit of hogwash help, but I was able to recover my /data partition.
Edit: also if I understand correctly, just because your partition table gets effed up, doesn't mean your recovery doesn't contain the proper information to put it back properly. I was able to boot my phone into temporary philz and twrp by command line using fastboot. I'll see of I can find some info.
Sent from my Moto G 2014 using XDA Free mobile app

Here is the command to boot a recovery img from fastboot
fastboot boot customrecovery.img
from there, you can try to use philz to format your partitions, or TWRP. Which ever recovery works for you. Then, presumably if this works, you should be able to restore your device to factory or install a custom recovery or rom.

In twrp i can Format all expect infernal storage .when i Format data it says OK but the data is still there and When i try to boot philz cames a bootloop

rukusx7 said:
Here is the command to boot a recovery img from fastboot
fastboot boot customrecovery.img
from there, you can try to use philz to format your partitions, or TWRP. Which ever recovery works for you. Then, presumably if this works, you should be able to restore your device to factory or install a custom recovery or rom.
Click to expand...
Click to collapse
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.

Also no Chance to recover our moto g ?:crying:

Darkimmortal said:
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Click to expand...
Click to collapse
I'm on the same boat, but actually when I try to boot, it goes in an endless bootloop of a Motorola logo (not the animation particularly). I've tried only with TWRP. I'll try later with CWM.
Flashing goes well but.... crap, I hate this

Darkimmortal said:
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Click to expand...
Click to collapse
So if i unlock bootloader and root phone will i be at risk?? Or i am only at risk if i mess with partitions or try to lock bootloader again?

How come "qualcomm blank flash programmer" will affect on eMMC?
lol'd..
Nor the unlocking\locking will work in this state.

Darksl1der said:
How come "qualcomm blank flash programmer" will affect on eMMC?
lol'd..
Nor the unlocking\locking will work in this state.
Click to expand...
Click to collapse
Sorry to ask but, do you even know what a emmc flash programmer is?

jhonnyx said:
Sorry to ask but, do you even know what a emmc flash programmer is?
Click to expand...
Click to collapse
Am enthusiast of device-modding, IT-engineer and a big fan of Motorola phones since 2005.
Of course I understand.
I mean this tool could help somehow by taking part of restoring, but supposed to fix issues over WRITABLE memory.
In case of RAW partitions - should delete partition table and recreate then, since plain format refused.
Anyway, my point was about this tool - it's not classic HardBrick state, Bootloader is working thou. We will use flasher if we'll replace eMMC-chip, for example

OPT bootloop, no recovery, cant boot into twrp.

So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!

Are the drivers accurate? Does your PC recognize your device as it should in Device Manager? That's usually what I check first when I have fastboot errors. I think the only way to fix this is through fastboot... so I would focus on trying to get that to work first.

SynderBlack said:
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Click to expand...
Click to collapse
**** man. I'm in the same boat as of a few hours ago. I was having a ProxyController wakelock and the few Google results I saw told me I should reflash the modem. I accidentally flashed the old modem (OOS2, I believe). I can't boot into my rom OR TWRP. BUT fastboot does work. I also get the "remote: dtb not found" error when trying to boot from the recovery image.
As long as we have fastboot, we can always go back to OOS 3 using the various unbrick methods. I'm trying to avoid having to go through that whole mess of re-rooting/unlock the bootloader etc etc. I'll post on here if I'm successful.
Update: I NEED a functional phone so I just went and erased everything. Sorry I couldn't be of much help to you man. What I did:
I went here and downloaded the fastboot version of OOS3 and converted the bat scripts into bash scripts (I only have Linux computers near me right now...; the commands in that bat script are exactly the same as they would be in bash, I just had to rename the ".bat" to ".sh" and make it executable). I'm back in OOS 3 now, unfortunately. There IS a way mentioned on the page below that talks about how you can prevent userdata from being formatted, but I didn't really care too much. Hope that helps.
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?

First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.

Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

messed up unlock.

Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks

thugscorpion said:
Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks
Click to expand...
Click to collapse
First, this thread is for g5 plus not for g5, so post in that thread.
Solution:- which firmware you are trying is it for g5 or g5+, if you flash wrong firmware then this happen, try downloading your firmware and then flash it.now you are on stock. If you don't know how to Flash, you can prefer XDA threads or use Lenovo Moto smart assistant app (pc) that will flash the firmware for you.
If you want to go on custom ROM then, first go to stock rom as it will restore your boot.img and custom ROM can work. If you directly want to go to custom rom (skiping above procedure) then flash boot.img from ADB or twrp and install custom ROM.
Here is the thread to Flash stock ROM:-
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Link for Lenovo Moto smart assistant app:-
https://support.lenovo.com/in/en/downloads/ds101291
And if you are using XDA threads it has old firmware which can brick you Device you can get your firmware from here and chose which firmware channel you belong:-
https://mirrors.lolinet.com/firmware/moto/potter/official/
At last to not take risk remove bootloader and gpt commands from ADB.

It is a G5 Plus and I get permission denied with adb or fastboot.
In android I van go go developers option and OEM unlock is ON, if I go fastboot, flashing is locked.

thugscorpion said:
It is a G5 Plus
Click to expand...
Click to collapse
Well LOS14....-cedric is the G5 variant. You didn't flash the wrong firmware did you?

Apperently I did...
Is there a way to fix it?
the Lenovo recovery tool mentioned above doesn't do anything with the "flash" option.
Put the phone in fastboot mode and it is not recognized by the Lenovo application.
Can still manual send fastboot and adb via the Windows command line but still "locked" and "pemrission denied".

the command fastboot flashing unlock did the trick for now.
But, I want to revert to stock, what is the correct way?
Can someone point me to a good how to or tutorial with recent files?
EDIT: I see LineageOS officially is not supporting the G5 plus, but there is a unofficial version in the G5 plus forums.
I'm still thinking of customizing because of all the bloatware and sluggish performance.

reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.

thugscorpion said:
reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.
Click to expand...
Click to collapse
Yeah security does show as Moto X4. That's normal.

One final question: On reboot I always end up in the fastboot menu without holding power and volume down, I also always get the unlock warning.
Is this a sign the bootloader is still not okay?
And is there an easy way to fix it?