Database Users

Getting rid of the unlocked bootloader warning message

The way to get rid of the warning caused by unlocking the bootloader on other phones would be to flash the proper bootloader logo in fastboot using:
Code:
fastboot flash logo logo.bin
This is how I did it on my old LG Nexus 5X.
Does anyone have the correct logo for the V20? Has anyone tried this on the V20?

It's not a logo file. It's located in aboot and you can't change it.

androiddiego said:
It's not a logo file. It's located in aboot and you can't change it.
Click to expand...
Click to collapse
That wasn't true on the 5X: https://forum.xda-developers.com/ne...-change-bootlogo-images-imgdata-tool-t3240052
Are you positive that it's different now?

Sizzlechest said:
That wasn't true on the 5X: https://forum.xda-developers.com/ne...-change-bootlogo-images-imgdata-tool-t3240052
Are you positive that it's different now?
Click to expand...
Click to collapse
Here is the tool that might be useful to search for and dump the relevant partition, mount it and investigate the source of the picture and text warning:
Partitions Backup & Restore
https://play.google.com/store/apps/details?id=ma.wanam.partitions
In the best case scenario, even use reverse engineering to skip the warning and its delay altogether, anyone?
Or is aboot non-writable?

You modify aboot in any way / shape / or form, and you better open a ticket with LG. When you unlock your bootloader, that stops aboot from verifying the signature of boot, laf, and recovery. XBL still very much does verification of all the other pieces of firmware. One of the first things it checks is the signature of aboot. If aboot has been modified, or wasn't signed with the same RSA cert that matches the RSA key that is in your model's QFPROM, then the phone goes into 9008 mode. At this time, there is no fixing that -- except sending it back to LG (and there may never be now that LG uses UFS nand in their phones).
-- Brian

I've personally looked into this and looks like it can't be changed.

I'm pretty sure the images is in the *raw_resources* partition. Look here.
It must be very hard to modify though considering LG use it for (all?) many models, since I've only found a single development thread for it, and as you'll see that didn't go very far.

@askermk2000 You are correct. Every single boot, charging, download mode, etc image is on that partition, and it isn't signed / checked, so modify away with no risk of bricking your phone.
There is an index with offsets for each image, but the format of the images isn't immediately obvious.
-- Brian

runningnak3d said:
@askermk2000 You are correct. Every single boot, charging, download mode, etc image is on that partition, and it isn't signed / checked, so modify away with no risk of bricking your phone.
There is an index with offsets for each image, but the format of the images isn't immediately obvious.
-- Brian
Click to expand...
Click to collapse
so it is indeed possible to change the unlocked bootloader warning?

Security wise, there is no reason that you can't change them. It looks like LG is using RLE encoding, so finding the start and end of an image is going to be interesting. There are offsets in the index, but they don't seem to align.
Also, while I don't think having a corrupt raw_resources partition would give you a 9008 brick, you might want to have a backup ready to flash if you decide to modify it. But, (and there is always a but), since aboot loads this, if aboot pukes and doesn't load, that WILL give you a 9008 brick.
If I were you, I would buy a used V10 off of eBay, and test on that since you can recover from a 9008 with an SD card.
-- Brian

FYI: recovered G5 XT 1676 to stock and updated. :)

Just an FYI type thing that may save people a bit of digging around sometime.
I tried to get the update that just came out, but as i had TWRP as recovery, no good. Anyhow, in my trying i completely bollixed the phone. Would start, but always booted to TWRP and had various conniptions. Could not even get a TWRP backup to load. Strange not encountered before by me stuff............
Anyhow, recovered by the following method to stock and am back in business.
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Not my own work, adapted from this thread by t-bon3
https://forum.xda-developers.com/showthread.php?t=2542219
which I found thanks to eens post18 at this thread
https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084/page2
After this, Motorola system update installed. On Australian XT1676 is build number NPP25.137-15-7
Patch level 1-May-2017
Still get the I cant be trusted page on power up as have unlocked bootloader.
Many thanks to all at XDA, its a resource that can certainly get you into trouble, but then out of it again.

where do you get the stock firmware?

Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.

We're you able to revert to a locked bootloader after this, I am looking forward to do so

We're you able to revert to a locked bootloader after this, I am looking forward to do so
Click to expand...
Click to collapse
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.

astmacca said:
didnt try, didnt need to for taking take the update.
And, from my reading there is no way so far to relock the bootloader. I got it to stock, with stock recovery, and that was enough for me.
Click to expand...
Click to collapse
I can confirm what you said, but I am asking because I am sick of the warning before the device starts

ap4ss3rby said:
I can confirm what you said, but I am asking because I am sick of the warning before the device starts
Click to expand...
Click to collapse
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing

TheFixItMan said:
You can get rid of that easily
Put phone in fastboot mode
Download logo from link below
Enter the following in a windows command prompt where you have fastboot files & the logo file
Code:
fastboot.exe flash logo logo-g5-fix.bin
http://drive.google.com/file/d/0B-idWfPYugGvREJaR3B0UFIxUkU/view?usp=sharing
Click to expand...
Click to collapse
Thanks, but this is why I made a Google pixel themed logo.bin and used a matching boot animation to go with it some time earlier

downgrade
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance

distclean said:
thanks for the guide
- can i use this method to downgrade to this version?
- can i do this without unlocking the bootloader
- if it goes wrong can i unlock the bootloader later (i have an unlock code)
- is there a reason why we don't flash sparsechunk.0 ?
thanks in advance
Click to expand...
Click to collapse
No you cannot downgrade (same firmware version or newer required)
Yes - unlocked bootloader not required
As long as your phone still goes into the bootloader
You should flash all sparsechunks in number order

Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
You maybe able to - there are different variants of the same phone
As long as the firmware is the same or newer (as in the bootloader and API version) it may flash
It will either flash or error out
There's only one way to find out - if your phone is dead anyway it's not going to make alot of difference
No - generally you can never downgrade firmware - doing so would be dangerous and you may loose the bootloader for good

thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.

distclean said:
thanks again,
motoboot.img is the bootloader you talk about? is the partition layout described somewhere? would custom roms use a different one here?
do tell me by the way if i should get this information elsewhere/if i should read something to get started in the whole moto g world.
Click to expand...
Click to collapse
You can write in adb
Code:
adb shell
cat /proc
cat /proc/partitions

Hello,
Does anyone know where can I download the latest firmware for Moto G5 XT1676 baseband Version: m8937_ 8000.122.02.40 R
Thanks

astmacca said:
Boot into bootloader fastboot mode.
Extract .xml.zip format firmware file:
eg: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
to a folder on c drive of the PC that has the ADB and fastboot files in it.
In command prompt cd\ to that directory.
fastboot flash the following in sequence.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
boots to stock .
Click to expand...
Click to collapse
You're partially right. These commands won't work for our files. You have to flash the firmware according to the instructions contained within the "flashfile.xml" file within the archive. For example we have no "motoboot" partition

I've flashed every stock package available now (4 I think) and haven't been offered an update once. I've ran a couple of custom ROMs but they're just not right in one way or another. Might be time to move on.

distclean said:
Thanks a bunch,
So to be absolutely clear, my phone shipped with NPP25.137-15-7 i can't install the stock rom linked, and the same version isn't out yet,
if i unlock the bootloader, would i be able to downgrade ?
Is the software channel setting preserved across this method?
Click to expand...
Click to collapse
I upgraded to this and since then can't downgrade the phone to the stock roms available online. From memory trying to flash gpt.bin gave a "Security version downgrade" error. So I wouldn't assume you'll be able to downgrade and until there is a copy of this particular firmware, you won't be able to flash back or relock the bootloader

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Is this ROM is good to my XT1676 Baseband: M8937_11.16.02.51R ?

astmacca said:
Think I worked out what I did wrong. Somehow, I changed the format of the data partition. Fat fingers at some point??
TWRP backups didn’t like that and would not mount or write to the data partition as it was not f2fs format that the backup had been made in??
Anyway, restored data from a TWRP backup after going to ....wipe…format data. All good.
That gave me the passcode lockout issue at next reboot which can deal with.
stock Firmware? http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
for me stock the phone came with is: CEDRIC_NPP25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Worked on my XT1676 dual sim, but CHECK if its appropriate for your model. There are files on that page that wont be and flashing some of their components (particularly bootloader), can i have read, be unrecoverable disastrous. Be warned.
Slow, but got it. At first i thought it was corrupt as TWRP wouldn't flash it. My gumby. The .xml.zips apparently need to be extracted and flashed file by file.
Click to expand...
Click to collapse
Hi, i own the same model of moto g5, i do this in fastboot window
fastboot erase userdata
now the phone only boot in twrp and show a message "failed to mount /data". i think that delete my userdata partition, how could i fix it?
once i can avoid this loop in twrp, i follow these steps to flash stock rom
thanks in advance
juan

LS 997 root or unlock bootloader?

I am new to LG devices... this is the first lg device for me.
I am on ZVA latest software version.
I want to have root in my phone or unlock the bootloader to install lineagos roms.
Could I do these two things without any risks to hard brick the phone?
I am familiar with adb and fastboot instructions.
Thank you.

If you can find out what ARB version you are on (I hear that Sprint pulled access to that hidden menu), and it is still 0, then maybe.
I am working to find a model that has a KDZ that is close enough to the LS997 that it will boot. If it will boot, then it can be rooted, and the proper firmware flashed back onto the phone.
-- Brian

The apk in first post of this thread may give you access to hidden menu. Let us know if it worked please
https://forum.xda-developers.com/v20/help/lg-v20-cdma-to-lte-gsm-switch-via-t3602409

loopytee said:
The apk in first post of this thread may give you access to hidden menu. Let us know if it worked please
https://forum.xda-developers.com/v20/help/lg-v20-cdma-to-lte-gsm-switch-via-t3602409
Click to expand...
Click to collapse
I think you are talking about unlock CDMA or GSM service.
But I am talking about unlocking bootloader and root.
I think this app doesn't work anymore since the production and lab menu couldn't be accessed.
But as I understand the main problem is how to return to the stock after root?

runningnak3d said:
If you can find out what ARB version you are on (I hear that Sprint pulled access to that hidden menu), and it is still 0, then maybe.
I am working to find a model that has a KDZ that is close enough to the LS997 that it will boot. If it will boot, then it can be rooted, and the proper firmware flashed back onto the phone.
-- Brian
Click to expand...
Click to collapse
What is ARB stands for?
Got it
Anti Rollback=1

anees02 said:
What is ARB stands for?
And how to obtain it?
I have came from Samsung world so don't know a lot about LG.
Click to expand...
Click to collapse
Anti roll back---Arb
In hidden menu. (if you can access it)
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.

loopytee said:
Anti roll back---Arb
In hidden menu. (if you can access it)
Choose SVC Menu then choose Version and scroll to the bottom. You will see Anti-Rollback Version.
Click to expand...
Click to collapse
Yes Got it
In my case ARB=1
What does that mean?
Couldn't flash old firmware?

anees02 said:
I think you are talking about unlock CDMA or GSM service.
But I am talking about unlocking bootloader and root.
I think this app doesn't work anymore since the production and lab menu couldn't be accessed.
But as I understand the main problem is how to return to the stock after root?
Click to expand...
Click to collapse
I am only referring to the apk linked in the first post. I realize that thread is not what you are looking for.
Did the apk work for you to access hidden menu? What zv# are you on?

loopytee said:
I am only referring to the apk linked in the first post. I realize that thread is not what you are looking for.
Did the apk work for you to access hidden menu? What zv# are you on?
Click to expand...
Click to collapse
Yes the app works and it said
ARB=1
And I am on ZVA software version.

Unfortunately there isn't any firmware out there that is ARB version 1 AND December 2016 security patch or older, so no, you can't root at this time.
I am guessing ZVA incremented ARB because ZV9 is still ARB 0.
-- Brian

anees02 said:
Yes the app works and it said
ARB=1
And I am on ZVA software version.
Click to expand...
Click to collapse
Ok thanks
Here is the current info about Arb and whats being worked on. As far as I know if your Arb is anything other then 0 then you can't root yet. I say yet because there is some great work being do with alot of hope for all.
Here are some links to whats going on currently
https://forum.xda-developers.com/v20/help/want-help-rooting-security-patches-t3680397
https://forum.xda-developers.com/v20/how-to/laf-download-mode-how-root-t3676011

runningnak3d said:
Unfortunately there isn't any firmware out there that is ARB version 1 AND December 2016 security patch or older, so no, you can't root at this time.
I am guessing ZVA incremented ARB because ZV9 is still ARB 0.
-- Brian
Click to expand...
Click to collapse
I think so. ARB
On ZV9 it was 0.
On ZVA it's 1.
So I have to wait until there's a method that doesn't matter about ARB value.

You could still do a really awesome thing for the people that are already rooted, or are about to be rooted -- dump your phone so that they can't have the latest firmware.
If you wouldn't mind, grab a copy of the patched LG UP, and use the dump function. This can not harm your phone in ANY way. What it does is reads the partitions on your phone, and saves them out to files.
We need:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
You can leave the rest unchecked. They are either not needed, or unique to your phone.
-- Brian

runningnak3d said:
You could still do a really awesome thing for the people that are already rooted, or are about to be rooted -- dump your phone so that they can't have the latest firmware.
If you wouldn't mind, grab a copy of the patched LG UP, and use the dump function. This can not harm your phone in ANY way. What it does is reads the partitions on your phone, and saves them out to files.
We need:
aboot
abootbak
apdp
boot
cmnlib
cmnlib64
cmnlib64bak
cmnlibbak
devcfg
devcfgbak
factory
hyp
hypbak
keymaster
keymasterbak
laf
lafbak
modem
msadp
persist
pmic
pmicbak
raw_resources
raw_resourcesbak
rct
recovery
recoverybak
rpm
rpmbak
sec
system
tz
tzbak
xbl
xbl2
xbl2bak
xblbak
You can leave the rest unchecked. They are either not needed, or unique to your phone.
-- Brian
Click to expand...
Click to collapse
Ok.
I will search for the patched version of LG UP.
And I hope that I find a time to charge my laptop and dump these partitions.

Some quick instructions for you:
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
Pick the one that says DUMP and click Start. You will be asked what partitions to dump, please check all the partitions listed above.

runningnak3d said:
Some quick instructions for you:
Download the patched LG UP from this thread: link.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Put your phone into download mode (power off / hold vol. up / plug in USB cable)
Use LG UP to dump your phone. When you run it, there will be additional radio buttons.
Pick the one that says DUMP and click Start. You will be asked what partitions to dump, please check all the partitions listed above.
Click to expand...
Click to collapse
I already dump the required partitions but LG UP recognized my software version ZV6 and it is really ZVA as shown on the attatched pic.
The size of the folder before compression is 5.88 GB. after compression 2.53 GB.
What about the difference in version between LG UP and the real version?

I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian

runningnak3d said:
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
Click to expand...
Click to collapse
Yes I am now uploading the zip file but the internet is very slow that before 4 hours I have started the uploading,until now it only upload 750 MB of 2.53 GB.
So if the uploading process finished successfully I will pm the link to your inbox.

This is from about phone>>software version

runningnak3d said:
I see ZV6 in the attached pic. That is weird. Obviously you aren't on ZV6 if you are ARB 1. If you don't mind, can you zip those up and post a link? The files I had you dump are the exact files that you get from a KDZ so there is no personal info.
-- Brian
Click to expand...
Click to collapse
PM sent to you.

[HELP] Return to stock before selling G5 Plus!

Hi! I could really need some help over here!
I have a G5 Plus that i bought in Sweden, Europe. I unlocked bootloader, and flashed a ROM.
But now i´m going to sell it, so i need to reflash the stock image (ROM). Also i need to relock bootloader.
Can someone help me find the latest, working firmware, and also with the right commands to use with fastboot to do this?
Modell is: X1685.

Why would you need to relock the bootloader? I guess you will sell the device warning the person that it doesn't have warranty, right?

I was going to type this but then found this post....
lvvine said:
NPN25.137-35
https://drive.google.com/file/d/0B3G...ew?usp=sharing
Watch the Video which will help you to flash the firmware.
https://www.youtube.com/watch?v=blYQ28DZJQk
Use FastBoot Command to flash the firmware (Backup you data as it would erase the internal Memory)
Fastboot command:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse

eemgee said:
I was going to type this but then found this post....
Click to expand...
Click to collapse
Be careful, it will flash the bootloader. If you have a newer version of the bootloader than th one you sumbitted, you will harfbrick your device.

M1810 said:
Be careful, it will flash the bootloader. If you have a newer version of the bootloader than th one you sumbitted, you will harfbrick your device.
Click to expand...
Click to collapse
If the stock ROM is older than what you have on your device, then the bootloaders usually prevent you from downgrading.
Hard bricks usually do not happen when you downgrade, they happen if you've downgraded and then take OTA updates (mismatches between the bootloader patch level and system patch level are a culprit). Best way to avoid this is to not downgrade.
At any rate, you cannot lock a bootloader with a build older than your existing stock firmware, regardless of custom ROMs flashed. You need a firmware of the same or newer build than your device stock firmware to relock. To the best of my knowledge, NPNS25.137-33-11 appears to be the newest or nearly newest firmware for EU devices. You can download from here https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ please confirm that this firmware is suitable before flashing.
You could try re-locking with other firmware, however NPN25.137-35 is for US devices, so would not likely receive OTA updates if flashed onto EU devices. As for warranty, the warranty isn't transferable as far as I know and as Motorola's got a record of the device being unlocked, the warranty is void. However, under EU consumer laws, you or the buyer could still get repairs if you're both resident in the territory. Would be wise to check this and let the buyer know.

Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.

syl0n said:
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
Click to expand...
Click to collapse
Original current gb version is as screenshot, anything else may screw up you phone.

syl0n said:
Do not do this! I lost my IMEI flashing that ROM on my XT1685, UK model.
Click to expand...
Click to collapse
hi, i have similar issue. can you tell me how you fixed it?

Smeagal192 said:
Original current gb version is as screenshot, anything else may screw up you phone.
Click to expand...
Click to collapse
There appears to be no fastboot flashable file for this version available anywhere on the internet. I've searched for days and had absolutely no luck!
Looks like both the OP and I are stuck on custom ROMs. Why Lenovo don't make these available I don't know...
If anyone knows of anywhere to get this please help us.
EDIT: Oh, also mine is XT1684 which I've seen virtually nothing about on XDA.

darkglobe87 said:
There appears to be no fastboot flashable file for this version available anywhere on the internet. I've searched for days and had absolutely no luck!
Looks like both the OP and I are stuck on custom ROMs. Why Lenovo don't make these available I don't know...
If anyone knows of anywhere to get this please help us.
EDIT: Oh, also mine is XT1684 which I've seen virtually nothing about on XDA.
Click to expand...
Click to collapse
Mines a 1684, seems moto made 2 models for UK with same specs.
Regarding fastboot did you extract download zipped archive into fastboots folder.
When I say download follow the link above to firmware centre, if using phone to browse you need phone in landscape otherwise you cannot get name.

Smeagal192 said:
Mines a 1684, seems moto made 2 models for UK with same specs.
Regarding fastboot did you extract download zipped archive into fastboots folder.
When I say download follow the link above to firmware centre, if using phone to browse you need phone in landscape otherwise you cannot get name.
Click to expand...
Click to collapse
Thing is, there's no xt1684 version or retgb version. I fear it could be the wrong one, can't afford to replace phone so can't risk hard bricking it. Thanks though.

8T on OOS A12 - C.16 Recovery with ADB Enabled

Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.

LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?

Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment

Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.

houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.

But for flashing do I need to unlock bootloader or it can be done without unlocking?

houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.

Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.

houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).

LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom

houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img

LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11

1

LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.

lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery