unable to relock bootloader on op5? - OnePlus 5 Questions & Answers

I'm sending my op5 back and want to relock the bootloader. However fastboot oem lock doesn't work - it says its 'not allowed'.
Any advice?

You don't need to relock it, OnePlus warranty still covers unlocked bootloaders so it won't make a difference.

Thanks - would be useful to know how/why it isn't lockable though!

I just relocked bootloader on my Oneplus 5..
The normal way, fastboot oem lock.

gneville said:
I'm sending my op5 back and want to relock the bootloader. However fastboot oem lock doesn't work - it says its 'not allowed'.
Any advice?
Click to expand...
Click to collapse
Same here, I'm also sending back my OP5.
I have flashed the full zip stock from OnePlus.net, factory reset, reflash the rom... and still get the "not allowed" issue

Wahoux said:
Same here, I'm also sending back my OP5.
I have flashed the full zip stock from OnePlus.net, factory reset, reflash the rom... and still get the "not allowed" issue
Click to expand...
Click to collapse
Do you have wiped the dalvik cache, cache and data partition ? maybe then retry lock the bootloader en see of that works ?

Pieter20 said:
Do you have wiped the dalvik cache, cache and data partition ? maybe then retry lock the bootloader en see of that works ?
Click to expand...
Click to collapse
I have the same problem as OP. I wiped everything several times and is flashed a stock rom via adb sideload/ via twrp/ via stock recovery and is imposible to lock the bootloader. i tried W10, W7 and Ubuntu, no dice.
If i go to developer options the unlocking bootloader option is greyed out with this text:
The bootloader is already unlocked
I also tried with Hydrogen, the problem stays.
Can someone boot to fastboot and tell me what text appears to you in this colum?
PRODUCT_NAME -
After that mine says QC_Reference_Phone
I also interested in this fastboot command:
fastboot oem device-info
after that i get this
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.008s]
finished. total time: 0.008s
is the selinux_type the same as mine????

hardspartan360 said:
I have the same problem as OP. I wiped everything several times and is flashed a stock rom via adb sideload/ via twrp/ via stock recovery and is imposible to lock the bootloader. i tried W10, W7 and Ubuntu, no dice.
If i go to developer options the unlocking bootloader option is greyed out with this text:
The bootloader is already unlocked
I also tried with Hydrogen, the problem stays.
Can someone boot to fastboot and tell me what text appears to you in this colum?
PRODUCT_NAME -
After that mine says QC_Reference_Phone
I also interested in this fastboot command:
fastboot oem device-info
after that i get this
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.008s]
finished. total time: 0.008s
is the selinux_type the same as mine????
Click to expand...
Click to collapse
Reads the same for me, however I haven't tried relocking the bootloader.
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0

HueleSnaiL said:
Reads the same for me, however I haven't tried relocking the bootloader.
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
Click to expand...
Click to collapse
mmm... interesting.
Now we need someone that has relocked to compare. Your device product_name on fastboot is also the same?
i'm suspecting some people have a different bootloader than others and that's why some people can relock and others don't.
i erased almost everything (boot, system, recovery, data, cache) and the bootloader thing stays the same.
The other possibility is some file stored in "/" that prevents the relock but i'm afraid to brick, this files are accesible via twrp recovery file manager.

hardspartan360 said:
mmm... interesting.
Now we need someone that has relocked to compare. Your device product_name on fastboot is also the same?
i'm suspecting some people have a different bootloader than others and that's why some people can relock and others don't.
i erased almost everything (boot, system, recovery, data, cache) and the bootloader thing stays the same.
The other possibility is some file stored in "/" that prevents the relock but i'm afraid to brick, this files are accesible via twrp recovery file manager.
Click to expand...
Click to collapse
Mine says PRODUCT_NAME - QC_Reference_Phone. I think that's the same as everyone else.
I don't have any idea of what could be wrong, are you using the latest adb/fastboot version?

HueleSnaiL said:
Mine says PRODUCT_NAME - QC_Reference_Phone. I think that's the same as everyone else.
I don't have any idea of what could be wrong, are you using the latest adb/fastboot version?
Click to expand...
Click to collapse
Yeah, i'm using latest minimal adb fastboot.
I relocked a lot of phones in the past, including Op3 and Op3T but this one is a pain.
Enviado desde mi Nexus 5 mediante Tapatalk

gneville said:
I'm sending my op5 back and want to relock the bootloader. However fastboot oem lock doesn't work - it says its 'not allowed'.
Any advice?
Click to expand...
Click to collapse
Why do you want to do that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Verzonden vanaf mijn iPad met Tapatalk

How I relocked my One Plus 5
TL;DR to lock the phone:
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery (Maybe keeping TWRP works too, if you want to have the phone locked but keep TWRP?)
Run this command on your PC and select "Yes" on the phone. The phone will be wiped.
Code:
fastboot flashing lock
If you get "Your device is corrupt.", boot to recovery, find "Install from adb" and install full ZIP from your PC:
Code:
adb sideload OnePlus5Oxygen_23_OTA_013_all_1708032241_9a87b4.zip
More detailed story
I wanted to get rid of the scary boot warnings on my phone because I'm selling it. I flashed the stock recovery, wiped everything, booted to fastboot but the lock commands didn't work.
Code:
fastboot flashing lock &:: this didn't work
fastboot oem lock &:: also didn't work
I booted the phone and looked at the "OEM unlocking" slider, but this is greyed out.
After being annoyed at things not working, I reinstalled TWRP, booted into recovery, and I flashed the Magisk zip file to install Magisk. Booted the phone normally, now "OEM unlocking" can be enabled (I think Magisk tricks the system so this can be re-enabled).
I rebooted to fastboot mode, typed "fastboot flashing lock", and the phone prompted me if I wanted to lock it. Success! But before this, I realized I have to first flash the stock recovery. So I did that, booted to fastboot, and repeated "fastboot flashing lock" to lock the phone.
Rebooting the phone I get the warning that the phone is corrupt:
Your device is corrupt. It can’t be
trusted and may not work properly.
Visit this link on another device:
go.co/ABH
Click to expand...
Click to collapse
They probably see that the system's been modified. Maybe I should've uninstalled Magisk. I rebooted to recovery, selected "Install from adb" and on my PC
Code:
adb sideload OnePlus5Oxygen_23_OTA_013_all_1708032241_9a87b4.zip
After this, I rebooted the phone, and no more warnings! Yay!

you also need to flash stock recovery.

The way I did it:
- flash stock OOS with TWRP
- Fastboot flash stock recovery
- locked bootloader successfully

netsharc said:
[*] Install TWRP and Magisk if you don't have them yet.
[*] Magisk should allow you to slide "OEM unlocking" to "enabled"
[*] Reboot to fastboot
[*] Flash stock recovery (Maybe keeping TWRP works too, if you want to have the phone locked but keep TWRP?)
[*] Run this command on your PC and select "Yes" on the phone. The phone will be wiped.
Code:
fastboot flashing lock
[*] If you get "Your device is corrupt.", boot to recovery, find "Install from adb" and install full ZIP from your PC:
Code:
adb sideload OnePlus5Oxygen_23_OTA_013_all_1708032241_9a87b4.zip
Click to expand...
Click to collapse
Thanks for sharing mate.
I`ve alredy rooted with SuperSu and TWRP installed. How do I flash Magisk over SuperSu ?
And I`ve tried to flash latest FW (OOS 4.5.10 Full Zip) with TWRP, but whenever I try to reboot it always says " No OS Installed .......".
I`ve tried several times, but every time it remains the same.
I totally new to OP devices. It would be very helpful, if you share how to revert back to stock OOS and lock the bootloader.

here in this video u can see in detail how to lock bootloader. hope this help
https://www.youtube.com/watch?v=CQYCSdDUdAU

Related

[Q] Nexus 7 Can't Unlock Bootloader, Bricked with No ADB Access

I've been searching for hours here but can't find a solution that works...
My wife's Wi-Fi Nexus 7 (running stock, unrooted) suddenly got stuck in a boot loop during the white Google logo (never gets to the Nexus "X" animation). I figured I'd simply restore to stock through fastboot/adb.
The problem is when I try to unlock the bootloader (which is needed to be able to flash the factory image) I get this error message:
Code:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
[COLOR="Red"][B]FAILED (remote: ()[/B][/COLOR]
finished. total time: 2.736s
Because of this, I can't go any further. I can't flash anything because it tells me I need to unlock the bootloader. I tried a couple of different toolkits with the same results.
I get fastboot access, and the device is listed when I type "fastboot devices" but I don't get adb access. When I type "adb devices" I simply see:
Code:
>adb devices
List of devices attached
...and nothing else. No devices listed. If I try other adb commands, I get "error: device not found".
I've tried installing the Google drivers as well as other USB drivers from toolkits. No change. But I can send it commands through fastboot fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can get into recovery, but can't flash anything. I am able to factory reset from recovery, but it doesn't help. The tablet just keeps boot-looping.
Am I screwed? Any ideas? Thanks in advance to anyone who responds
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
bigdaddy619 said:
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
Click to expand...
Click to collapse
What's PTP mode? Were you having the same issue I'm having?
The thing is my tablet is getting recognized, at least in fastboot. Just not in adb but I'm thinking that's because it never had debugging turned on.
Wrong input.
grisoxxl said:
If you can acces recovery make full wipe.
Click to expand...
Click to collapse
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
ecaggiani said:
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
Click to expand...
Click to collapse
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Sent from my Nexus 7 using xda premium
ganeshp said:
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Click to expand...
Click to collapse
That's what I'm trying to do! The guides I've seen have me unlock the bootloader to be able to flash stock firmware. Can you point me to a guide? Is there an RUU maybe?
ecaggiani said:
Am I screwed?
Click to expand...
Click to collapse
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
ecaggiani said:
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
Click to expand...
Click to collapse
Hi, im having the exact problem you're having, did you end up contacting ASUS? how was your experience like? Did you get it resolved? I think I voided my warranty by trying to pull the battery ):
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s
your help please?
regards
Ricey
Ricey_uk said:
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s.
your help please?
regards
Ricey
Click to expand...
Click to collapse
Hi, Ricey_uk...
Mmm... not sure, but I think you're trying to flash the wrong factory image for your device...
Reason being, is because (QUOTE: fastboot flash bootloader bootloader-tilapia-4.13.img) 'tilapia' refers to the 3G/GSM variant of the Nexus 7.
But you appear to have a (QUOTE: (bootloader) product: grouper) 'grouper' device. Which is WiFi only... this seems to be supported by the two lines in your output...
(bootloader) version-baseband: N/A
(bootloader) version-cdma: N/A
... which suggests your N7 has no 'radio' capability.
You need the factory stock image for "nakasi" for Nexus 7 Wi-Fi only (device board "grouper").... NOT "nakasig" for Wi-Fi & Mobile (device board "tilapia").
(See my sig for download links).
-----------
In short, there is an incongruity/contradiction in your reported outputs.... the device is either 'grouper' or it's 'tilapia'
It can't be both.
If it has a SIM card (like a mobile phone), or a space for a SIM card, then it's 'tilapia'... if it doesn't, then it's 'grouper'.
Ensure you are flashing the correct factory stock for your device.
-----------
But having said all of that... (and if there is confusion, it needs to be cleared up)... it doesn't explain why something as straightforward and innocuous as...
Code:
fastboot oem unlock
...isn't working.
Two possibilities occur to me...
1) A bad USB connection. Try a different USB port on your PC... Or, maybe, a different USB cable.
Once the fastboot oem unlock command is issued at the PC end, it will need to be confirmed at the Nexus 7 end (see attached thumbnail). Use either of the two VOL buttons to choose YES and confirm by pressing the POWER button.
2) It's possible there could be a hardware failure... some problem with the EMMC flash memory chip. As alluded to by a previous poster...
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Whilst I don't discount the possibility that it COULD be EMMC chip failure, I'm not inclined to think that this is a likely possbility. More prosaic explanations need to be explored first.
First... check the integrity of of your USB connections - at both ends; change to different USB ports on your PC; if you can, try a different PC; try a different USB cable. And confirm at the Nexus 7 end, once the unlock command has been issued. (again, see attached thumbnail).
Second... if you are going to try to fastboot flash back to Android factory stock... make sure you do so with correct version for your device. If you're device is Wi-Fi only, you need the 'grouper' version... if not, the 'tilapia' version.
Hope this helps.... and good luck.
Rgrds,
Ged.
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Ricey_uk said:
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Click to expand...
Click to collapse
Hi, Ricey_uk...
Yeah... that, unfortunately, does not sound good at all. Unlocking the bootloader just sets some 'flag state' on the internal EMMC flash chip. Specifically, somewhere in the mmcblk0boot0 partition, where the bootloader lives.
There's some technical info here... http://forum.xda-developers.com/showthread.php?t=2068207
If fastboot oem unlock is performing as you describe, then it strongly suggests some sort of hardware failure. It just shouldn't behave that way... once you have confirmed the oem unlock request on the Nexus 7, the PC should display (if I remember correctly), the following...
Unlocking....
The device is unlocked now...
The whole procedure should take no more than a few seconds. Blank screens and forced reboots have happened many times on my Nexus 7... but never whilst unlocking the bootloader (and yes, I have locked and relocked several times, when I was experimenting with the 'motochopper' root exploit).
----------------------------------
Incidentally, you won't find 4.13 on the factory downloads page, as that number refers to the bootloader version for JellyBean 4.2 and 4.2.1. (It's not always the case that with each new version of JellyBean the bootloader is updated).
Anyway... looking through my collection of system images on my laptop, I find the following...
JellyBean 4.1.2 -> bootloader-grouper-3.41.img
JellyBean 4.2.0 -> bootloader-grouper-4.13.img
JellyBean 4.2.1 -> bootloader-grouper-4.13.img
JellyBean 4.2.2 -> bootloader-grouper-4.18.img
JellyBean 4.3.0 -> bootloader-grouper-4.23.img
With JellyBean 4.3 being the latest, and it updating the bootloader to 4.23.
If you're still stuck on bootloader version 4.13, then that means it was last updated with the rollout of JellyBean 4.2, sometime around November 2012.
----------------------------------
All of which is technically interesting... but probably doesn't help you.
I think there is a hardware problem on your Nexus 7, that is preventing the bootloader-lock-state flag from being correctly set.
Wish I could be of more assistance.
Rgrds,
Ged.
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Ricey_uk said:
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Click to expand...
Click to collapse
Give me half an hour or so, and I'll upload it to my dropbox and I'll post a link. Gotta get it of my laptop first.
Although I'm not convinced it will solve your problem... but I suppose you have nothing to loose by trying.
Rgrds,
Ged.
---------- Post added at 12:53 PM ---------- Previous post was at 12:21 PM ----------
OK... here is the bootloader .img file - v4.13... extracted from nakasi-jp40d-factory-6ac58a1a.tar... or in English, Jellybean 4.2.1.
https://dl.dropboxusercontent.com/u/37483979/bootloader-grouper-4.13.img
Code:
File size: 2.05 MiB (2,146,892 bytes)
MD5: a119629c89ad06c7e49bebd260df9cf3
SHA-1: fd60a0d9da5c814e2c1ee049f537700cbbe2c3cc
Flash as follows....
Code:
fastboot flash bootloader bootloader-grouper-4.13.img
---------------
Be careful with this.
Flashing a bootloader is the riskiest single operation you can undertake on the Nexus 7.
All it takes is one false step, and you have a hardbrick.
The device will never boot again.
Make sure you have good USB connections at both ends... and before flashing... type...
Code:
fastboot devices
If you don't see a serial number, you have either a driver problem OR a possible dodgy USB connection.
Do not proceed with this flash until you see a serial number.
Normally, I would suggest test flashing something innocuous first, like a recovery, for example.... but since your bootloader is locked, that's not possible.
I'm not even sure flashing a bootloader is possible with a locked bootloader... but then, I've never directly flashed a bootloader before.
Very best of luck - really hope this fixes your problem.
Rgrds,
Ged.
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Ricey_uk said:
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Click to expand...
Click to collapse
Damn... thought that might happen... but wasn't 100% sure.
You can't use fastboot with a locked bootloader, even to flash a bootloader... and you can't unlock it because - well, who the hell knows why (but I suspect a problem with the internal EMMC).
What is the precise current status of your Nexus 7?
Android version?
Rooted?
Stock or Custom ROM/kernel?
Custom recovery (CWM/TWRP) installed?
Did you receive any OTA notifications regarding the recent release of Android 4.3? and if so did you allow the OTA update to proceed? What happened?
Rgrds,
Ged.
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Ricey_uk said:
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Click to expand...
Click to collapse
You can get the Android version info by going to SETTINGS>>ABOUT TABLET.
Without further details, what is odd about your predicament is this...
If your bootloader is v4.13, then that means the device hasn't been updated since November of last year. Since then, there have been, I think, 3 official updates from Google... the most recent being JellyBean 4.3 about a couple of weeks ago
Normally, when an OTA update is pending, you get pestered endlessly with an endless stream of notifications.
Upon the user accepting the lastest update (whatever that might be - but is currently JellyBean 4.3)... the device downloads the OTA, runs a checksum test on the current files in /system... and then'patches' them, meaning it brings them up to date.
The very last thing the OTA does is update the bootloader, by dropping BOOTLOADER.RAW into the USP(staging) partition. Upon automatic reboot, the new bootloader is then copied (from the USP/staging partition) into the bootloader partition proper... thus obviating the risks associated with flashing the bootloader partition directly.
Since November, the bootloader has been updated by this means twice... 4.13->4.18 (in, I think February, when JellyBean 4.22 was rolled out) and just recently 4.18->4.23 when JellyBean 4.3 was rolled out.
It's odd you haven't received any notifications of any OTA updates.
----------------------------------
Anyway.... A possible workaround...
A slightly rhetorical question... why do you want to unlock the bootloader anyway?
I assume it's because you want to root... or maybe flash a custom ROM...
That 'might' still be possible...if you're running a version of Android THAT ISN'T JellyBean 4.3, you can root via 'exploit'.
Details here - http://forum.xda-developers.com/showthread.php?t=2233852
This requires no fastboot commands and thus, no need for an unlocked bootloader.
It's really simple to implement. Indeed, I ran my Nexus 7 for several month BOOTLOADER locked, but rooted.
(But with the advent of JellyBean 4.3, root exploits no longer work.... so I've had to root the old fashioned way).
But it might be useful to you...
Anyway... once you are rooted, you can then flash a Custom Recovery... like CWM or TWRP.
Normally this would be done via fastboot. But there are two great apps available that will 'write' a recovery partition... directly from the Nexus 7.
These are Flash Image GUI and Flashify.
Both will request root access.
It doesn't matter which one you use, as they essentially do the same job... but IMHO, Flashify is the better of the two.
Once you have a Custom Recovery installed, the metaphorical gateway is open to whatever Custom ROMs or Custom Kernels you like.
----------------------------------
It's possible none of the above will work... maybe for the same reason why you can't unlock the bootloader. A suspected fault with the internal EMMC chip.
But it just might... and it's gotta be worth a shot.
To summarize
Root via 'exploit'
Use Flashify or Flash Image GUI to install a Custom Recovery
Good luck.
Rgrds,
Ged.

[GUIDE] Unlock the bootloader of Zuk Z1 without using fastboot & wiping userdata

Introduction
As we know, the official way to unlock the bootloader of Zuk Z1 is through fastboot.
For a untouched device, the status of the bootloader should be:
Code:
fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]false[/COLOR]
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first, then via bootloader/fastboot interface:
Code:
fastboot -i 0x2b4c oem unlock-go
It'll eventually erase the userdata.
Then the status of the bootloader should be:
Code:
fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: [COLOR="Red"]false[/COLOR]
(bootloader) Device unlocked: [COLOR="Red"]true[/COLOR]
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
Inspired by the findings on similar devices, we can actually unlock the bootloader of Zuk Z1 without using fastboot, while keeping the userdata intact.
How-to
Warning!
It is dangerous! This whole thing is basically one giant hack - which is not intended to be done by normal users. It is messing with the bootloader partition, so it is possible that something goes wrong and you will have a nice & costly brick in your pocket. Be prepared to revive the device from a hard-brick.
1.
Enable 'OEM unlocking' under Developer options. You may need to tap the Build number 7 times under About phone to get the Developer options under Settings.
2.
We need root access (kinda expected!). To root the device without unlocking bootloader, use KingRoot. Use the Android version.
Now there is a catch! KingRoot can root the device, cause the latest build of Cyanogen OS (cm-12.1-YOG4PAS3OH-ham ATM) contains such vulnerabilities which can be exploited by the root exploits used by KingRoot. But we can't ensure about future.
3.
After being rooted, use adb shell or any terminal emulator to dump the 'aboot' i.e bootloader partition in internal sdcard:
Code:
su
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.img
4.
Now we need to modify the dumped image using hex-editor. For Zuk Z1:
Code:
Unlock Bit Position - 0x001FFE10 Hex
Tamper Bit Position - 0x001FFE14 Hex
'00' means false, '01' means true. So to set the bootloader as unlocked, we just need to change the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Save the modified image as 'abootmod.img' inside your sdcard.
5.
Now its time to flash back the modded bootloader. Execute the following from adb shell or any terminal emulator:
Code:
su
dd if=/sdcard/abootmod.img of=/dev/block/bootdevice/by-name/aboot
Do a reboot & voila! You have unlocked the bootloader! Don't just believe me - check the status of the bootloader to ensure.
Note
1. We can also reset the tamper bit using this procedure.
2. If you prefer GUI, then you can use this fantastic app by @wanam.
3. This is tested on an international Zuk Z1 running cm-12.1-YOG4PAS3OH-ham. Please test & post feedback to ensure compatibility.
4. I'm not providing pre-modified images as it increases the risk of bricking the devices having older/newer bootloaders - please do it yourself. The offsets should be unchanged in future, though.
Credits
1. @osm0sis
2. @segv11
3. @Mnt-XDA
4. @Tengo10 - for risking his device for this experiment.
5. Users of XDA.
Happy tinkering! :highfive: :good:
Reserved for future.
I tested now and working okay. Thaaaaaaaaaaaaaaaaanks
after using dd for writing the modified image it worked. seems to be a problem using the app Partitions Backup & Restore
old post
Doesn't worked for me.
fastboot -i 0x2b4c oem device-info still shows
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.009s]
finished. total time: 0.010s
when I read the aboot-partition after writing the modified image my modification is gone, i used Partitions Backup & Restore App for reading and writing
Click to expand...
Click to collapse
Hi everybody
I am trying to unlock the bootloader with fastboot but I am stucked (I have the drivers installed properly, adb recognize my device):
C:\adb>fastboot -i 0x2b4c oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
I am trying for hours to unlock the device, can you tell me what is wrong?
Thank you
Lems84 said:
Hi everybody
I am trying to unlock the bootloader with fastboot but I am stucked (I have the drivers installed properly, adb recognize my device):
C:\adb>fastboot -i 0x2b4c oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.003s
I am trying for hours to unlock the device, can you tell me what is wrong?
Thank you
Click to expand...
Click to collapse
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
yes I did it, USB debogging and OEM unlocking on the ZUI interface.
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
I also have the same problem.I enabled OEM.solutions please?kindly?
Thanks!
Hello Titokhan,
can you please upload the modified abootmod.img for the international version. Then it will be very easy for me and the only thing i must do is to install the file... many thx
carstenheuer said:
Hello Titokhan,
can you please upload the modified abootmod.img for the international version. Then it will be very easy for me and the only thing i must do is to install the file... many thx
Click to expand...
Click to collapse
The Problem is that he don't own that phone.
Tengo10 said:
The Problem is that he don't own that phone.
Click to expand...
Click to collapse
what happen when i flash TWRP with flashify app when the bootloader is still locked?
carstenheuer said:
what happen when i flash TWRP with flashify app when the bootloader is still locked?
Click to expand...
Click to collapse
Nothing special, you only can't flash unsignt zips and IMG.
Hello, I'm having this problem. I do not see the "OEM Unlocking". I have enabled USB Debugging already. Please help.
Planet X said:
Did you do this?
To unlock the bootloader, you need to enable 'OEM unlocking' under Developer options first
Click to expand...
Click to collapse
Problems with fastboot
I was going to follow this guide but fastboot doesn't recognize my zuk. I tried to install all the drivers from sdk, and then i tried also to manually select them in the devices settings of windows but my pc says that there aren't any drivers in the folders. Ho can I solve it? I looked over and over the internet but this phone is apparently really rare so there are no working solutions for this. Can someone help me? :crying:
It works!
Zuk Z1 international, it worked perfectly! Just, I had to change the name of abootmod in about to substitute the original file, so " dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot "
You should have written a bigger warning that it ERASES USERDATA!
Tuberomix said:
You should have written a bigger warning that it ERASES USERDATA!
Click to expand...
Click to collapse
Well, this method doesn't touch the userdata partition.
Titokhan said:
Well, this method doesn't touch the userdata partition.
Click to expand...
Click to collapse
Whatever it wipes, I do ask that you put a warning in big, bold, red letters!
@Tuberomix
Looks like there is some misunderstanding; this method doesn't wipe anything. Can you please elaborate about your experience?

No solution for bootloop in Android 7.0

Hi guys, first time posting.
I have now a moto g4 plus that was OTA updated from Android 6.x to Android 7.0 and that caused it to bootloop and die later. Before that I had no knowledge of ROMs, bootloaders, fastboot, flashing, sideloads, ADB, RSD or anything like that. But this last week I acquired a superficial knowledge thanks to google, foruns of all kinds and you guys from XDA.
My phone started doing nothing at all and I progressed, solving the not charging battery problem (disconnecting and reconnecting it), the not lighting up led (with the original turbo charger and a three minute hold of the vol - and power up buttons) and finally accessing the fastboot mode and later the recovery mode which allowed me to dive into all kinds of tutorials about the reasons that I could not use ADB (usb debugging disabled) or flash custom ROMs (unlocked bootloader and unchecked "allow oem unlock"). All the research ended up to the conclusion that the only thing I could do was to flash the stock rom of Android 7.0 through RSD or fastboot/mfastboot. Did that, wiped cache and users data/factory reset and... nothing. The phone installed the stock ROM but it still doesn't pass the Motorola logo screen.
After that I came to three possible solutions:
1) Try to install the brasilian ROM version I have in my sister's Moto G4 plus (NPJS 25.93-14.4), but I can't find it anywhere (thought about backing it up from her phone, but root would be needed and her phone is still in warranty).
2) To wait till Android 7.1.1 or 7.1.2 stock ROM be released for Moto g4 plus flash it and hope it do the trick.
3) Send to Motorola assistance so they change it's motherboard (last resource considering the phone is not in warranty anymore).
Well, as I said my knowledge is new and superficial so I need your help and opinion about my conclusions and other possible solutions.
I thank you all for all I've learned so far and for any tips you can spare on me. Thanks again and keep doing what you do here.
Kyrohn said:
Hi guys, first time posting.
I have now a moto g4 plus that was OTA updated from Android 6.x to Android 7.0 and that caused it to bootloop and die later. Before that I had no knowledge of ROMs, bootloaders, fastboot, flashing, sideloads, ADB, RSD or anything like that. But this last week I acquired a superficial knowledge thanks to google, foruns of all kinds and you guys from XDA.
My phone started doing nothing at all and I progressed, solving the not charging battery problem (disconnecting and reconnecting it), the not lighting up led (with the original turbo charger and a three minute hold of the vol - and power up buttons) and finally accessing the fastboot mode and later the recovery mode which allowed me to dive into all kinds of tutorials about the reasons that I could not use ADB (usb debugging disabled) or flash custom ROMs (unlocked bootloader and unchecked "allow oem unlock"). All the research ended up to the conclusion that the only thing I could do was to flash the stock rom of Android 7.0 through RSD or fastboot/mfastboot. Did that, wiped cache and users data/factory reset and... nothing. The phone installed the stock ROM but it still doesn't pass the Motorola logo screen.
After that I came to three possible solutions:
1) Try to install the brasilian ROM version I have in my sister's Moto G4 plus (NPJS 25.93-14.4), but I can't find it anywhere (thought about backing it up from her phone, but root would be needed and her phone is still in warranty).
2) To wait till Android 7.1.1 or 7.1.2 stock ROM be released for Moto g4 plus flash it and hope it do the trick.
3) Send to Motorola assistance so they change it's motherboard (last resource considering the phone is not in warranty anymore).
Well, as I said my knowledge is new and superficial so I need your help and opinion about my conclusions and other possible solutions.
I thank you all for all I've learned so far and for any tips you can spare on me. Thanks again and keep doing what you do here.
Click to expand...
Click to collapse
Hello Kyrohn, before I go into any specific idea on what you should do have you ever tried considering flashing Lineage OS onto your device?
if your phone has charge i would suggest you to do the following
1. make sure it's switched off, drain the charge and then recharge if you can't be sure if it's switched off or not.
2. install your drivers properly.
3. then connect your device(in switched off condition) via usb cable while simultaneously holding power button and volume down button only.
4. the phone should enter into a black area and from there reboot to bootloader.
5. follow this link properly
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
this should do it. cuz it should always boot to recovery/bootloader from moto screen
HIT LIKE IF IT HELPED
justinwgeiger said:
Hello Kyrohn, before I go into any specific idea on what you should do have you ever tried considering flashing Lineage OS onto your device?
Click to expand...
Click to collapse
Hi Justin, thanks for reply. Lineage OS is a custom ROM, right? So the stock bootloader won't allow me to flash this ROM considering my bootloader is locked and the OEM unlock option is unchecked (and inaccessible).
Have you tried flashing stock marshmallow?
Kyrohn said:
Hi Justin, thanks for reply. Lineage OS is a custom ROM, right? So the stock bootloader won't allow me to flash this ROM considering my bootloader is locked and the OEM unlock option is unchecked (and inaccessible).
Click to expand...
Click to collapse
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
MisterSteve said:
Have you tried flashing stock marshmallow?
Click to expand...
Click to collapse
Hi Steve, yes I tried, but I can't downgrade the system, the stock bootloader doesn't allow me
justinwgeiger said:
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
Click to expand...
Click to collapse
Thanks for the reply and patience again Justin. But as I said before the option "Allow OEM Unlock" in Android Settings > Developer Options is unchecked. So when I try unlock the bootloader with the commands you passed I get the following error: Check 'Allow OEM Unlock' in Android Settings > Developer Options. But I can't do that considering the phone doens't boot Android.
Ayan Uchiha Choudhury said:
if your phone has charge i would suggest you to do the following
1. make sure it's switched off, drain the charge and then recharge if you can't be sure if it's switched off or not.
2. install your drivers properly.
3. then connect your device(in switched off condition) via usb cable while simultaneously holding power button and volume down button only.
4. the phone should enter into a black area and from there reboot to bootloader.
5. follow this link properly
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
this should do it. cuz it should always boot to recovery/bootloader from moto screen
HIT LIKE IF IT HELPED
Click to expand...
Click to collapse
Hi Ayan, thanks for reply. Tried all of that before, but tried again now just in case I had made something wrong the first time. It does everything as it's supposed to do, but after reboot it still doesn't pass the logo screen
Kyrohn said:
Hi Steve, yes I tried, but I can't downgrade the system, the stock bootloader doesn't allow me
Click to expand...
Click to collapse
You should no use the bootloader and gpt commands as the bootloader is not downgraded once it has been updated.leave those two and try to fastboot stock marshmallow.
[email protected] said:
You should no use the bootloader and gpt commands as the bootloader is not downgraded once it has been updated.leave those two and try to fastboot stock marshmallow.
Click to expand...
Click to collapse
Hi Chaitu. I tried that now but I'm getting an "invalid PIV signed" error. Could you check the commands I'm using?
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Maybe I'm using one I shouldn't. The first error appears on this command line "mfastboot flash oem oem.img" and the error is "Invalid PIV signed oem image". I also tried the next line "mfastboot flash system system.img_sparsechunk.0" and the error is "Invalid PIV signed system image". Isn't that an error when we use an incorrect ROM for a region? I'm trying the asian ROM cause I couldn't found a brasilian one.
Just tried to flash a supposed brasilian retailed marshmallow ROM, but got the same PIV error. Any ideas about the reason why?
Kyrohn said:
Just tried to flash a supposed brasilian retailed marshmallow ROM, but got the same PIV error. Any ideas about the reason why?
Click to expand...
Click to collapse
Could redownload your ROM to double-check it's not corrupted. Also, is your device carrier unlocked or provided by a carrier? I've had a quick look on that error and in a few cases may be due to a carrier restriction.
However, in order to downgrade, you need an unlocked bootloader which isn't achievable as you've mentioned. And the fast boot won't work either...
When did you buy your device? I recall reading on the Motorola website the warranty is 12 months in Brasil, unless you've been told different? (Edit:https://help.motorola.com/hc/apps/settings/legal/global/pt-br/index.html?t=T1700272834 unless this is out of date)
echo92 said:
Could redownload your ROM to double-check it's not corrupted. Also, is your device carrier unlocked or provided by a carrier? I've had a quick look on that error and in a few cases may be due to a carrier restriction.
However, in order to downgrade, you need an unlocked bootloader which isn't achievable as you've mentioned. And the fast boot won't work either...
When did you buy your device? I recall reading on the Motorola website the warranty is 12 months in Brasil, unless you've been told different? (Edit:https://help.motorola.com/hc/apps/settings/legal/global/pt-br/index.html?t=T1700272834 unless this is out of date)
Click to expand...
Click to collapse
Hi Echo, thanks for reply. I'm almost sure the phone isn't locked by carrier, but can't assure that. Your're right about the warranty but I didn't buy the phone new, it's a used phone and due to Motorola legal contract the warranty is intransferable. And even if wasn't I asked for the bootloader unlock code in one of the tutorials, so I lost the warranty cause of that too.
About this "PIV", what does it mean? How can I find out the required PIV for my phone, do you have any ideia about that?
Thanks again.
Kyrohn said:
Hi Echo, thanks for reply. I'm almost sure the phone isn't locked by carrier, but can't assure that. Your're right about the warranty but I didn't buy the phone new, it's a used phone and due to Motorola legal contract the warranty is intransferable. And even if wasn't I asked for the bootloader unlock code in one of the tutorials, so I lost the warranty cause of that too.
About this "PIV", what does it mean? How can I find out the required PIV for my phone, do you have any ideia about that?
Thanks again.
Click to expand...
Click to collapse
Ah okay, so we've got no warranty/Motorola will charge for repairs, gotcha (and is probably looking like a motherboard repair )
As for PIV - I've read that is read by the bootloader to verify if your image is signed properly (i.e. by Motorola) and thus if it's not the right signature will fail to flash. Short of obtaining the correct, signed, image for your device (what is your device btw?), I'm not sure if you'll be able to bypass that. You may wish to have a look here, see if there are any images for your device (though I cannot say if they'll flash properly). https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
The strange thing is that flashing the stock Nougat ROM as you mentioned (and Ayan suggested) should have worked (since the NPJ25.93-14 build seems to be a global, universal build), the only thing I can think of was that something happened with the Marshmallow build on there (either a bad flash or an incorrect ROM, for example), but without asking the former owner, we just don't know.
For information, are you able to reboot into the bootloader, attach your device to your computer and in minimal ADB, execute 'fastboot getvar all' and post the info here, please? You may wish to remove your IMEI and serial number from the output.
echo92 said:
Ah okay, so we've got no warranty/Motorola will charge for repairs, gotcha (and is probably looking like a motherboard repair )
As for PIV - I've read that is read by the bootloader to verify if your image is signed properly (i.e. by Motorola) and thus if it's not the right signature will fail to flash. Short of obtaining the correct, signed, image for your device (what is your device btw?), I'm not sure if you'll be able to bypass that. You may wish to have a look here, see if there are any images for your device (though I cannot say if they'll flash properly). https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
The strange thing is that flashing the stock Nougat ROM as you mentioned (and Ayan suggested) should have worked (since the NPJ25.93-14 build seems to be a global, universal build), the only thing I can think of was that something happened with the Marshmallow build on there (either a bad flash or an incorrect ROM, for example), but without asking the former owner, we just don't know.
For information, are you able to reboot into the bootloader, attach your device to your computer and in minimal ADB, execute 'fastboot getvar all' and post the info here, please? You may wish to remove your IMEI and serial number from the output.
Click to expand...
Click to collapse
I didn't know this firmware center, surely will be usefull in the future. Got the latest version updated there for my XT 1640 (answering your question). Flashed it and still the same, flashs ok but don't leave bootloop (I was afraid to find out it's a motherboard problem )
Here is the result of that command line:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: EC9AEB0100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-22-2016
(bootloader) sku: XT1640
(bootloader) battid: SNN5966B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 23:34:21 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_BRAZIL_DS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retbr
Thanks for the patience
justinwgeiger said:
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
Click to expand...
Click to collapse
I already had unlocked my bootloader and then installed twrp later, without resatring the device. Now I re locked the bootloader and I am stuck with the MOTO "M" logo, please help

How to unlock a Moto G7 xt1962-6

I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
rsshilli said:
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rsshilli said:
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
Click to expand...
Click to collapse
It seems that your USB debugging or OEM unlock toggle was un-ticked.
Do you have recovery available to format/reset device?
RSDLite doesn't work with your model?
Negative
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
rsshilli said:
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
Click to expand...
Click to collapse
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Well, that's weird
Huh. I tried LMSA tonight again just for fun and it worked fine this time. It found the image, downloaded it, and reflashed the phone to factory settings. Yay! I'm back in. I tried it many times before. I know my firmware updated on the phone a few days before this happened. I guess I just needed to wait for a bit. Thank you everybody.
Ryan
WoKoschekk said:
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Click to expand...
Click to collapse
For next time, how does one find the exact firmware needed? I could never figure that out.
rsshilli said:
For next time, how does one find the exact firmware needed? I could never figure that out.
Click to expand...
Click to collapse
Code:
fastboot getvar all

Struggling to flash the x720 , Help !

Hi
Long story short
i got my leeco le pro 3 x720
i got it from aliexpress and this is how it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So When i received the phone i went and installed the usb drivers and the adb tool ofc after i did my research
so in the adb and after checking for the devices there , i reboot into fastboot mode and checked for the device and it was recognized , i sent "fastboot oem unlock-go" to unlock the boot loader , i received this :
...
OKAY [ 0.008s]
finished. total time: 0.009s
then i checked with "fastboot oem device-info"
and i got :
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
now into the problem
when i reboot and check again with "fastboot oem device-info" :
i receive :
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.084s
So i went and did everything again but instead of reboot i flashed the latest twrp from the official stie
then i did "fastboot boot [recoveryname]" to boot to the recovery , that did work and i got into the twrp
but when i shut my device and enter to the recovery via "power button and volume up"
i get the leeco logo + recovery underneath it , then everything turns black
when i connect to the adb and check for adb devices it says recovery
but the screen stays black until I reboot to to the system again
so heres what i tried ( another twrp version "old ones" and didnt work i tried the stock recovery again and it did not work)
i get the same black screen when I get to the recovey i can access the recovery only via "fastboot boot recovery.img"
even if i did "adb reboot recovery" i get black screen
i tried All in one tool to check with the bootloader again when i check the statue of the boot loader nothing happens
when i try to unlock it it says failed , i didnt wont to press lock bootloader cause i dont know how to use the tool yet.
and one more thing : when i got to twrp on the first time via "fastboot boot...." when i try to flash i get vendor errors and stuff.
so please help me , i spent two days or more searching for any clue :'(
its my first time into custom roms and i really want to flash the leeco le pro 3 into a better rom
i even tried to flash my Lg stylo 2 plus to 8.1 oreo and that was a piece of cake i got it running in less than an hour
as a test subject.
HELP ! ​
Yep, EUI will restore the stock recovery. You have to do the TWRP installation this way, especially step 5:
Installation:
1. Make sure your bootloader is unlocked
2. Download the recovery image from above
3. Reboot into fastboot
4. Run this command (Change the .img to whatever the name of file is you downloaded): fastboot flash recovery twrp-3.5.0_9-1-zl1.img
5. Once it is flashed, please force a reboot to recovery by holding down the Power and Volume Up buttons at the same time until the phone reboots and you see the LeEco logo and the word "recovery" underneath it. (This is because if you allow normal boot after flashing TWRP while you are using EUI and your phone reboots to EUI it will overwrite the recovery with the stock EUI recovery. Forcing a reboot from the bootloader to recovery prevents this issue)
is it okay if the bootloader unlock temporarily ? i did try unlocking the bootloader then flashing the twrp then rebooting to recovery with the power key and volume but same issue the screen turns black after the leeco logo with the recovery word , the only way i can access twrp by fastboot boot "name".img , but i dont know if its the correct way
Ehm, sorry, right now I see that you didi not flash the bootloader. You have to do this with:
fastboot flash recovery.img
did everything you suggested , still when i go to recovery i get a black screen cant install my roms like this , im sad now
No, I think we missed something. Check this step by step guide completly:
https://www.getdroidtips.com/unlock-bootloader-leeco-le-pro-3/
Did you OEM unlock before you unlock the boitloader?
i did every single thing oem unlock usb debugin my pc is recognizing the phone in adb and fastboot
i unlocked the bootloader with the command fastboot oem unlock-go
then checked with fastboot oem device-info
then i flashed latest twrp recovery with "fastboot boot recovery [name].img
then i pressed and hold power and volume up untill i got leeco logo + recovery word then the screen goes black thats it
So first part should be OK. But you did not flash the recovery. fastboot boot recovery.img is just to started the recovery from memory and not to install it. The correct command to flash is: fastboot flash recovery.img
After this you have to do the force reboot.
i typed the wrong command xD i really flash it with fastboot flash you can check the whole steps i did in the main thread above , anyways i found the problem and got everything working all i need to do was to flash a new firmware to unlock the bootloader and thats it , thank you for helping :3
Well done. Wih the the new firmware you removed EUI. So the bootloader isn't reset anymore. Have fun with the device.
THANK YOU SO MUCH !!

Categories

Resources