Database Develop

[Q] Unlocked But Not?

All,
I was trying to change my logo to not show the unlocked bootloader message and i keep getting the following messages:
Variable not Supported!
target max-download-size: 768MB
error: cannot load 'logo.bin': No error
Then looking at the all the variables using "fastboot getvar all" I see that my my unlocked and iswarrantyvoid variables are Yes, and my secure variable is Yes!?!?!
To me it seems that my bootloader is not fully unsecure. I do have TWRP so I am a bit confused, and well I dont do this stuff often enough to know what might be wrong.
Thanks Jeredish

Jeredish said:
All,
I was trying to change my logo to not show the unlocked bootloader message and i keep getting the following messages:
Variable not Supported!
target max-download-size: 768MB
error: cannot load 'logo.bin': No error
Then looking at the all the variables using "fastboot getvar all" I see that my my unlocked and iswarrantyvoid variables are Yes, and my secure variable is Yes!?!?!
To me it seems that my bootloader is not fully unsecure. I do have TWRP so I am a bit confused, and well I dont do this stuff often enough to know what might be wrong.
Thanks Jeredish
Click to expand...
Click to collapse
I'm not sure what the cause of the problem is, but I can confirm that the following is normal for an unlocked Moto X:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) secure: yes
Here is what happens when I flash a boot logo:
PC:
>fastboot flash logo Logo-darkclogo.bmp.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (524 KB)...
OKAY [ 0.299s]
writing 'logo'...
OKAY [ 0.839s]
finished. total time: 1.141s
Phone output:
Fastboot Reason: Reboot to bootloader
USB connected
getvar all
getvar partition-type: logo
getvar max-download-size
downloading 536871 bytes
done
flashing logo
done
Is your phone fully charged?

Jeredish said:
All,
I was trying to change my logo to not show the unlocked bootloader message and i keep getting the following messages:
Variable not Supported!
target max-download-size: 768MB
error: cannot load 'logo.bin': No error
Then looking at the all the variables using "fastboot getvar all" I see that my my unlocked and iswarrantyvoid variables are Yes, and my secure variable is Yes!?!?!
To me it seems that my bootloader is not fully unsecure. I do have TWRP so I am a bit confused, and well I dont do this stuff often enough to know what might be wrong.
Thanks Jeredish
Click to expand...
Click to collapse
The problem is that you don't have logo.bin in the same folder that you are RUNNING fastboot from. You may have it in the same folder as fastboot, but you must also run the command FROM that folder as well.
For instance:
If your command prompt shows: C:\Users\Yourname\
but logo.bin is in C:\MyDownloads\logo.bin
Then you need to RUN THE FASTBOOT COMMAND **from** C:\MyDownloads\
It is best to put the logo.bin in the same folder as fastboot, AND run the command FROM that folder.
That also explains why "fastboot getvar all" works. "error can not load....XXX" means that fastboot can not FIND the file trying to be flashed.
Good Luck.

k_t_b said:
I'm not sure what the cause of the problem is, but I can confirm that the following is normal for an unlocked Moto X:
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) secure: yes
Here is what happens when I flash a boot logo:
PC:
>fastboot flash logo Logo-darkclogo.bmp.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (524 KB)...
OKAY [ 0.299s]
writing 'logo'...
OKAY [ 0.839s]
finished. total time: 1.141s
Phone output:
Fastboot Reason: Reboot to bootloader
USB connected
getvar all
getvar partition-type: logo
getvar max-download-size
downloading 536871 bytes
done
flashing logo
done
Is your phone fully charged?
Click to expand...
Click to collapse
Oh gosh I am a complete idiot....
So I am working in the windows environment and I set the path variable with where my fastboot.exe is located to make the cmd line stuff more convenient, but when I referred to the logo file I thought it simply needed to be in the same location as the fastboot.exe and of course my cmd was not set to that path.
Thanks for the quick reply.
J

SOLVED: (bootloader) Preflash validation failed, even though I'm unlocked

I was following this guide in order to update my formerly rooted bootloader unlocked Nexus 6. I've been able to follow those instructions in the past to update my phone, but something went wrong this time. I'm on the MMB29Q version, so I downloaded the MMB29Q to MMB29V update, the link to which I found on this site. I also downloaded the MMB29Q factory image from Google's list of them and extracted the system.img file. My phone has the stock recovery, and my computer is on Arch Linux with adb version 1.0.36 and fastboot version 7.1.2_r6.
I was able to erase the system image easily enough:
Code:
$ ~ adb reboot bootloader
$ ~ fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.673s]
finished. total time: 0.673s
However, when I then tried to flash the system image,
Code:
$ ~ fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (518702 KB)...
OKAY [ 16.242s]
writing 'system' 1/4...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.250s
it failed on me. According to the bootloader splash screen, my "Device is UNLOCKED. Status Code: 3" (I read somewhere that the Preflash validation failed message corresponds with an unlocked bootloader).
One other thing to note is that I remember leaving the checkbox for allowing oem unlock in developer options unchecked, which I am now realizing was probably where I went wrong (I ran fastboot oem unlock as a test, and it told me to Check 'Allow OEM Unlock' in Developer Options). However, because I cleared the system image, I don't know how I can change that setting anymore. I also realize that I didn't need to do this step in the updating process because my phone was already unrooted and thus system.img should have been stock (I think, at least). I tried re-erasing the system image and reflashing it, but that unfortunately did not fix anything. Any advice would be much appreciated!

Progress! I was able to flash TWRP, back up all my data just in case, and then follow this guide, which toggles the "Allow OEM Unlock" developer settings without having a working operating system. Running fastboot oem unlock no longer gives the error about checking that box in Settings. However, I'm still getting that same error when I try to flash the system.img. After that failed, I am fresh out of ideas, given that the problem does not seem to be that option. Anyone have any ideas?
Edit: I now realize I am a moron. I found this thread on Android.SE and realized that I had in fact downloaded the Nexus 6P MMB29Q version and that is why it failed. After downloading the correct verion, rewiping the system partition, and reflashing it, my phone works again!

issue with flashing- Lineage 15.1

Hi Folks,
Need some help here. I'm new to flash and other stuff.
I tried to install Lineage 15.1. I did fastboot oem unlock which erased everything. I'm stuck in AP fastboot Flash Mode.
I tried below things.
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 18.385s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 18.400s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash recovery twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.422s]
booting...
OKAY [ 0.031s]
finished. total time: 0.469s
[PHONE GETS TWRP RECOVERY SCREENS]
I tried adb sideload as suggested in one of the pages and got this
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload lineage-15.1-20180402-nightly-shamu-signed.zip
Total xfer: 0.01x
In Phone :
Starting ADB sideload feature ..
Installing zip file '/sideload/package.zip'
Warning: No file_contexts
Target : google/shamu/shamu:7.1.1/N6F27m/4299435:user/release-keys
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid Argument
Failed to unmount /system : No such volume
script aborted (no error message)
Updater process ended with ERROR: 7
Finally, I tried with copying installer files in OTG Drive and tried to install from there. But couldn't mount it as I can't make OTG check in Mount in TWRP.
Please help .. How can I overcome this and install OS in my phone.

Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.

mal13 said:
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
Click to expand...
Click to collapse
Yes, I can boot into twrp using this command...
fastboot.exe boot twrp-3.2.1-0-shamu.img
This bringstwrp in my phone. But I can't move files to the phone. Even I tried adb push which pushes the files to the phone but while installing it got failed.. I'm not sure what I'm missing..

I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s

vigkumar said:
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
Click to expand...
Click to collapse
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.

vigkumar said:
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
Click to expand...
Click to collapse
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.

vigkumar said:
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
Click to expand...
Click to collapse
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

vigkumar said:
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
Click to expand...
Click to collapse
That was your first error! You can't flash a nightly via fastboot.
You need to boot into recovery and select it there to install.

ktmom said:
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Both method failed. :crying::crying:

vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, I'm trying stock and followed links that you provided. Both installation methods failed.
Fastboot devices returns,
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot devices
ZX1G525DZX fastboot

Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.

ktmom said:
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
Click to expand...
Click to collapse
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s

vigkumar said:
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Couple of questions.
You are working on a Nexus 6, right? Not a 6P or other device?
Did you reboot between each img flash? When you returned to the bootloader each time after rebooting, did you long press the power button because it still said "locked status 2"?
I have to say, this is the first I've ever heard of a reboot causing it to be locked then long pressing the power button to unlock. Either the bootloader is unlocked or it isn't.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
---------- Post added at 14:03 ---------- Previous post was at 14:00 ----------
Additional question, when you reboot using only the key combination, does it always show unlocked?
If yes to that, maybe it's back to my concern that the version of fastboot is not working well with the N6.
If you haven't, try with the minimal version you downloaded the other day.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I

vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
1] If u can get to twrp, use microUSB flash drive and move ROMs over to flash via TWRP. Must mount OTG drive in TWRP after plugin to recognize flash drive
2) if u can get to fastboot mode and your PC recognizes your device via "fastboot device" command, try using WUG NRT tool kit to restore back to stock, then root @ND put TWRP on there, then flash custom Roms via TWRP

novice here. screwed up my 6p and got in a similar place as you are. i started adb side load in my phone and linux pc terminal, adb start-server, then adb sideload [add a space] then i dragged and dropped the factory firmware to terminal then enter. i had to try a couple of googles angler firmware before it found the the right format. saved my bacon.

Good point. If fails on Windows, Linux PC may work

System integrity is compromised error after restoring using Moto smart assistant.

I've had my Moto G6 rooted for some time now. An ota update for PPS29.118-15-11-16 was continually nagging so I uninstalled Magisk and installed it.
Upon reboot when checking for updates I now get the following:
As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software.
I tried restoring to factory using Lenovo Moto smart assistant and that worked as it should. I still get the same "System integrity is compromised" error. I was under the impression that this would be reset upon doing this factory reset.
How would I get this message to be removed as I don't ever remember seeing it when this phone was rooted all this time.
Thanks

If I downgrade back to my last version PPSS29.118-15-11-9 the "System integrity is compromised" is NOT present.

Installing magisk seems to allow the ota updater to NOT report the "System integrity is compromised". As for stock, no dice.

minipretzel said:
Installing magisk seems to allow the ota updater to NOT report the "System integrity is compromised". As for stock, no dice.
Click to expand...
Click to collapse
without Magisk = system recognizes your unlocked bootloader
with Magisk = unlocked bootloader is hidden and OTAs and OEM-Unlock toggle are enabled, even SafetyNet check will pass.

I know this thread is old but I have the exact same problem.
I also restored stock roms from PPS29.118-15-11-16 using Smart assistant. I was already at this version, but I did the update anyway, as I have read that the smart assistant rescue would completely restore the phone to stock condition. But this didn't clear my "System Integrity..." message.
Just fyi, I actually ran the smart assistant commands manually... The SA failed to update my phone so I reconstructed the commands from the xml file and executed them one by one to find and fix this problem.
I re-ran the standard rescue after this and it was fine.
I noticed that my oem lock/unlock switch is enabled in my system->developer settings ( this was greyed out before).
Thing is, I do have magisk installed , as I wanted to root the phone. But this doesn't clear the message as it did for the OP.
I saw another article (thread) that recommended issuing "fastboot oem lock" twice, followed by some (re)flashing of the oem, system, and boot img files, and one final lock command. See "Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)" by alexmaisa.
But the article by alexmaisa is from 2019 and is for a G5S....
Any ideas would be greatly appreciated.

pdpantages said:
I noticed that my oem lock/unlock switch is enabled in my system->developer settings ( this was greyed out before).
Click to expand...
Click to collapse
With magisk installed it's quiet normal.
pdpantages said:
I saw another article (thread) that recommended issuing "fastboot oem lock" twice, followed by some (re)flashing of the oem, system, and boot img files, and one final lock command. See "Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)" by alexmaisa.
Click to expand...
Click to collapse
That's the correct way to relock your bootloader. Just follow the output lines in your cmd after executing fastboot oem lock.

WoKoschekk said:
That's the correct way to relock your bootloader. Just follow the output lines in your cmd after executing fastboot oem lock.
Click to expand...
Click to collapse
Thank you for the input. My bootloader was locked so the lock commands just reported this. When I ran the subsequent commands I got an error about unable to flash (bc the bootloader was locked)..... I thought maybe the original post had a typo so I switched to two "unlock" commands as the first commands. This unlocked me, and all the subsequent commands completed OK, including the final lock. But after setup I still have the System Integrity msg when I check for s/w updates under System menu.
The original post was from 2020 so possibly my version of Magisk (24.3) is the cause.?
I have most of what I want; latest stock ROMs and phone is rooted... just want to clear the problem with s/w updates.
I found another command set that that flashed the boot, system and oem twice.. I have cut these commands below. Unfortunately I don't recall where I got the bat file. It was called FLASH_OEM_LOCK.bat. Again these commands issue a lock command followed by some flash cmds which I thought would not work with the bootloader locked? Does a lock command not take effect until after reboot or something? Anyway, here they are:
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear

@pdpantages That's the way to relock the bootloader and get the status "oem_locked":
1. Flash the current complete firmware
2. !!! THIS STEP IS HIGHLY RECOMMENDED !!!
If your bootloader will be relocked successfully after these steps, you won't have any options to fix errors! So, this is your last chance...
Important functions to check: are you able to boot into system, mobile (data) connections, Wifi
boot into system and check everything's working fine.
3. Are you really sure everything`s fine?
4. *** The following shows fastboot commands + output for a better understanding of what we are doing here. I took them from the last relock of my Moto G6 ***
Reboot into bootloader and run these commands:
Code:
########################################################################
# new lines beginning with "#" are comments and should not be executed!!
########################################################################
$ fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.001s]
finished. total time: 0.001s
$ fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.002s]
finished. total time: 0.002s
# no need to flash the whole firmware (= valid Android images) again since we already did it in step 1.. Skip it and run lock command again.
$ fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.001s]
finished. total time: 0.001s
# ATTENTION: Cannot be skipped as we did before! Bootloader needs signed boot.img a second time!
$ fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.919s]
writing 'boot'...
OKAY [ 0.518s]
finished. total time: 1.438s
$ fastboot oem lock
...
(bootloader) Still require signed system.img and/or oem.img
OKAY [ 0.001s]
finished. total time: 0.001s
# ATTENTION: Cannot be skipped as we did before! Bootloader needs signed system/oem.img AND vendor.img (it's also signed since it contains sensitive firmware data, too) a second time!
$ fastboot flash system system.img_sparsechunk*
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 9.463s]
writing 'system'...
OKAY [ 5.836s]
finished. total time: 15.300s
(...flashing all other sparse images of system...)
$ fastboot flash vendor vendor.img_sparsechunk*
target reported max download size of 534773760 bytes
sending 'vendor' (254668 KB)...
OKAY [ 8.950s]
writing 'vendor'...
OKAY [ 5.484s]
finished. total time: 14.434s
( ...flashing all other sparse images of vendor...)
$ fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (153181 KB)...
OKAY [ 5.566s]
writing 'oem'...
OKAY [ 4.727s]
finished. total time: 10.294s
# now bootloader is satisfied and can be locked (yeah!!)
$ fastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.163s]
finished. total time: 0.163s

Thank you kindly for the into. The notes in particular clarified things for me quite a bit, and I understand that issuing the unlock commands as I did was incorrect. I will try it shortly and report the success or failure of my attempt.
My bl is currently locked- my intent is to unlock it (2 commands) , let the phone reset and boot, verify with "fastboot flashing get_unlock_ability" that it is in fact unlocked, and start your procedure from there...
Thank you again for the help. I expect your post will be helpful to others too.

pdpantages said:
I will try it shortly and report the success or failure of my attempt.
Click to expand...
Click to collapse
So I did as promised. The basic answer is that it worked as described. A few notes follow; things I wonder about and error msgs I saw.
Procedure: Not exactly as outlined above; my boot loader was locked so I issued some unlock commands:
rigel:/home/pdp/adb>fastboot oem unlock
(bootloader) invalid boot state
OKAY [ 0.006s]
Finished. Total time: 0.006s
rigel:/home/pdp/adb>fastboot oem unlock
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.001s
rigel:/home/pdp/adb>fastboot flashing unlock
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.001s]
Finished. Total time: 0.001s
So, I got errors trying oem unlock but "flashing unlock" worked and the phone booted when I entered the second one. Not sure if this is an issue or not.
Errors: I got a "not found" error with each img I flashed. I was a bit nervous about this as it looked like partition names were "not found". But despite this, the commands appeared to work so I carried on.
rigel:/home/pdp/adb> fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (22528 KB) OKAY [ 0.901s]
Writing 'boot' OKAY [ 0.381s]
Finished. Total time: 1.675s
In the end, everything worked as expected- the "System Integrity..." message was gone from the Software update setting, and the also the boot-time warming about unlocked bootloader was gone (I have seen many posts claiming it is not possible to clear this message).
Magisk: After all that, I still wanted to root my phone... I thought i would be able to install Magisk using twrp.
I tried booting into twrp recovery using adb (not flashing recovery.img ) but this didn't work. So in the end I unlocked my bootloader again. (required the unlock key) to install Magisk.
WoKoschekk said:
with Magisk = unlocked bootloader is hidden and OTAs and OEM-Unlock toggle are enabled, even SafetyNet check will pass.
Click to expand...
Click to collapse
I was hoping the above would apply to me but it didn't; I now see the "System Integrity message" again in my software update settings. It is manageable- if I really want a software update I now know how to revert the phone to stock. Now that I am rooted I can make backups with Titanium Backup which was my primary motive for rooting in the first place .
Thank you again for the help, WoKoschekk , it is much appreciated.

pdpantages said:
Not sure if this is an issue or not.
Click to expand...
Click to collapse
It seems to be an issue because oem unlock does work for me. But as long as your bootloader is unlocked it does not matter.
pdpantages said:
and the also the boot-time warming about unlocked bootloader was gone (I have seen many posts claiming it is not possible to clear this message)
Click to expand...
Click to collapse
It happens on Moto G6+ devices but not on our device.
pdpantages said:
Errors: I got a "not found" error with each img I flashed. I was a bit nervous about this as it looked like partition names were "not found".
Click to expand...
Click to collapse
This is related to the new fastboot versions that are used to flash devices with a partition /super. It contains /system, /vendor and some others and they are called "logical partitions". Moto G6 does not use a /super partition and you can ignore that check by fastboot.

WoKoschekk said:
This is related to the new fastboot versions that are used to flash devices with a partition /super. It contains /system, /vendor and some others and they are called "logical partitions". Moto G6 does not use a /super partition and you can ignore that check by fastboot.
Click to expand...
Click to collapse
OK thank you again. I see now that I get this error when I flash from Linux, but not Windows 10....
In case it might help someone here are my linux versions:
rigel:/home/pdp/adb>fastboot --version
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
rigel:/home/pdp/adb>adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-android-tools
Installed as /usr/bin/adb[/FONT]

pdpantages said:
OK thank you again. I see now that I get this error when I flash from Linux, but not Windows 10....
In case it might help someone here are my linux versions:
rigel:/home/pdp/adb>fastboot --version
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
rigel:/home/pdp/adb>adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-android-tools
Installed as /usr/bin/adb[/FONT]
Click to expand...
Click to collapse
What version is installed on your Windows system? If you don't get any "error" like that you are not using the latest version of fastboot. SDK Platform Tools

WoKoschekk said:
What version is installed on your Windows system? If you don't get any "error" like that you are not using the latest version of fastboot. SDK Platform Tools
Click to expand...
Click to collapse
Adb version 1.0.39
fastboot version 0.0.1-4500957
I don't like to use windows but I ran Motorola Rescue & Smart Assistant tool there... If I have to use windows again I will update it.

What to do with a fully cleansed phone?

My attempt to install a custom rom has failed horribly and I'm left with a wiped phone. Is there a way to reinstall EMUI? Or still somehow get a custom rom?
I flashed lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img on system, but although there was no error message it didn't seem to do anything.
It's a LLD-L31

hasl3r said:
Is there a way to reinstall EMUI?
Click to expand...
Click to collapse
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...

-Alf- said:
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.

hasl3r said:
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
hasl3r said:
The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
Do you have TWRP installed instead of Recovery or eRecovery?
hasl3r said:
It's a LLD-L31
Click to expand...
Click to collapse
What is your regional variant? (Cxxx)

-Alf- said:
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
Click to expand...
Click to collapse
That worked, I'm not around a PC at the moment, I'll run the commands as soon as possible
-Alf- said:
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
Do you have TWRP installed instead of Recovery or eRecovery?
Click to expand...
Click to collapse
That booted into TWRP as well, so I guess?
-Alf- said:
What is your regional variant? (Cxxx)
Click to expand...
Click to collapse
How to I find that out? I tried google but didn't find information.
All else I got are the IMEI and:
Serial number: FPM4C18622002338
Product ID: 71171281
Many thanks already for your help btw

hasl3r said:
How to I find that out?
Click to expand...
Click to collapse
through the mentioned fastboot commands.

-Alf- said:
through the mentioned fastboot commands.
Click to expand...
Click to collapse
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)

hasl3r said:
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
Click to expand...
Click to collapse
Okay, try the following:
1. Download Service ROM
Unpack it, there's a dload file in Software folder. Copy dload as it is to the SD Card (without unpacking it!)
2. Download TWRP 3.2.1 https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
and copy it to SD Card
3. also copy to SD stock Recovery_ramdisk-9.1.img , download here:
https://mega.nz/#!M0FHlYhb!4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
4. Boot into your TWRP, select storage - SD Card, select "Install image", find TWRP-9.1 file and mark eRecovery, swipe. Go back, find recovery_ramdisk-9.1 file , mark Recovery, swipe.
5.Turn off the phone, use option 'Power Off' in TWRP's menu.
6. Press and hold Power & both Volume buttons .

-Alf- said:
Okay, try the following:
Click to expand...
Click to collapse
Amazing, thank you so much!
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.

hasl3r said:
Amazing, thank you so much!
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
Click to expand...
Click to collapse
Glad to help

-Alf- said:
Glad to help
Click to expand...
Click to collapse
Sorry to bother you again, just wondering if you have any advice. I tried flashing LineageOS 17.1, but realised that the bootloader is locked again. My unlock code doesn't seem to work anymore (check password failed) and I figured it's because I have to downgrade EMUI 9.1 to 8.0. Took me a while, but turns out that was not the issue.
Do you happen to have any idea what to try? Do I have to buy another DC Unlocker license?
I don't know if it's related, but "adb reboot fastboot" just reboots the device and I have to use the volume down key to get there.

hasl3r said:
the bootloader is locked again.
Click to expand...
Click to collapse
it's normal after using dload method
hasl3r said:
My unlock code doesn't seem to work anymore
Click to expand...
Click to collapse
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)

-Alf- said:
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
Click to expand...
Click to collapse
Turns out the problem was copy/pasting the unlock code instead of hand typing it..
So I could flash it, but then the reset failed. Just realised that EMUI 9.1 is a requirement though, so I'll flash that first and try again.

Edit: Nvm fixed it. Sorry if you got a notification anyway.

-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s

hasl3r said:
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
Click to expand...
Click to collapse
1. be sure that your bootloader is unlocked, try to unlock it again
2. In fastboot mode run command
fastboot erase system
and try to flash GSI again
3. Install TWRP 3.2.1 gaguga edition, in TWRP select Mount - mark System, go back, select Wipe > Advanced > mark System > Repaire or etc. > Resize file system > confirm, reboot .
Then flash back stock recovery and try to install GSI.
4. Downgrade to the lower build number via dload method
5. idk...