URGENT- Help!!! - Lenovo ZUK Z2 (Plus) Questions & Answers

Hello people of XDA!
I have a Lenovo Zuk Z2 Plus (4GB+64GB) and I was trying to unlock the bootloader, but I got the following error:
"
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.059s
"
Please help. I was running Nougat on it. I'd really appreciate it if someone could walk me through the process of installing RR on it!
(Yes I know, I'm a noob)
Thanks!

Well, how did you proceed to unlock your bootloader?
Here is a great guide, did you follow these steps?

archiesb6 said:
Hello people of XDA!
I have a Lenovo Zuk Z2 Plus (4GB+64GB) and I was trying to unlock the bootloader, but I got the following error:
"
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.059s
"
Please help. I was running Nougat on it. I'd really appreciate it if someone could walk me through the process of installing RR on it!
(Yes I know, I'm a noob)
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/quick-tip-bootloader-unlock-issue-t3742518/

Related

[ERROR] message when flash any help

When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Do what everyone should be doing... use Rezo's tool to root and install CWM. Then use CWM to flash your ROM. Simple.
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Is your bootloader unlocked? It must be to do that
UP_TO_KNOW_GOOD said:
When i try flashing the system rom or recovery.img or boot.img what ever i keep getting the same error message. FAILED (remote: not allowed) help is need bad thanks.
C:\Android>fastboot flash system system.img
sending 'system' (248075 KB)... OKAY [ 35.381s]
writing 'system'... FAILED (remote: not allowed)
finished. total time: 35.381s
Click to expand...
Click to collapse
Boot your device on HBOOT, and select FASTBOOT and then connect with PC. (USB Debugging must be enabled)
Follow the instructions here to Flash ROM :
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
It's done now.

Error Restorying Pixel to Stock

i am trying re-flash STOCK ROM to my Pixel XL and i get this error and i cant figure it out:
C:\Users\Helix\Desktop\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (32980 KB)...
OKAY [ 1.006s]
writing 'bootloader'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.742s]
finished. total time: 5.750s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (57192 KB)...
OKAY [ 1.708s]
writing 'radio'...
OKAY [ 0.563s]
finished. total time: 2.273s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
< waiting for device >
load_file: could not allocate 1850641679 bytes
error: failed to load 'image-marlin-nmf26u.zip': Not enough space
Press any key to exit...
now I'm scared that i have a brick . any help please.
Stop using minimal, it hasn't been updated for our partition size.
ok
ok ill install the Manager thanks
jjdw1970 said:
ok ill install the Manager thanks
Click to expand...
Click to collapse
Use this. Direct from Google and latest update always available. > https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv
thanks for the help. Pixel is back up and rocking again. This is a great site.
jjdw1970 said:
This is a great site.
Click to expand...
Click to collapse
Yes, it is.

(remote:unlock failed) Bootloader

Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
viknesh war said:
Hi, Yeah I tried to flash the unlock image,
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.031s]
writing 'unlock'...
FAILED (remote: unlock failed)
finished. total time: 0.053s
Now I am in latest version Nougat
Click to expand...
Click to collapse
Yup i was also facing the same problem a new bootloader image will fix it just request for a new bootloader image from zuk.
viknesh war said:
I fixed it ....
Solution ..just try one more time get new unlock_bootloader.IMG then flash it ...Enjoy
Click to expand...
Click to collapse
Thanks a lot bro.. I downloaded a new unlock_bootloader. Img file, and it worked just fine.
Actually I entered wrong serial number in zuk website while downloading the img file maybe because of that it didn't work at first

Need a Bootloader

Hello,
I'm not new to flashing / rooting / modding or Nexus / Pixel scene.. But that is a first for me.
I've updated my Pixel 2 XL to the latest version and I wanted to try out the P preview.. The problem is that apparently I have an newer version of the bootloader.
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
So if anyone could upload the TMZ20f I would really appreciate it.
That error is usually because you didn't unlock critical.
TonikJDK said:
That error is usually because you didn't unlock critical.
Click to expand...
Click to collapse
Hmm.. So I need to relock the bootloader and unlock it again?
Welp! I've unlocked critical.. But now I get "check console" error. Great.
Bucika said:
Welp! I've unlocked critical.. But now I get "check console" error. Great.
Click to expand...
Click to collapse
Are you using the latest version of fastboot?
RMarkwald said:
Are you using the latest version of fastboot?
Click to expand...
Click to collapse
I tought I do. I mean I could unlock the phone before.. now it says it's unlocked, and If I try to lock it it says it's locked. Device status is locked tho, at least thats what the bootloader says.
Btw when i've relocked the bootloader the phone finally booted up, so the phone is indeed working, but I can't unlock nor lock it, apperently it's both.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (36344 KB)...
OKAY [ 0.901s]
writing 'bootloader_a'...
FAILED (remote: Flashing is not allowed in Lock State)
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
but when I do unlock comad (dose not matter if oem unlock, or unlock_critical it says failed cuz is unlocked.
It was all working fine (with unlocked bootloader via oem unlock command) until I've tried to flash the P. .then there was at first the wrong bootloader thing, and then I've just unlocked the unlocked bootloader again this time via the critical unlock, and the phone did not load the P it said the console thing.. and the phone didn't want to boot up, until I've flashed oem lock.. it boots up fine, but it's apperently locked and unlocked at the same time, lol. So I cant flash anything..But the phone does work, tho.
So I am basicially back to start, just can't do anything lol!
Bucika said:
I tought I do. I mean I could unlock the phone before.. now it says it's unlocked, and If I try to lock it it says it's locked. Device status is locked tho, at least thats what the bootloader says.
Btw when i've relocked the bootloader the phone finally booted up, so the phone is indeed working, but I can't unlock nor lock it, apperently it's both.
Click to expand...
Click to collapse
You should verify you have the latest version of the Android SDK Platform Tools from here.
Are you running via fastboot the following two commands (back to back)?:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
From there, proceeding with the instructions on flashing the Android P Dev Preview images (link)?
RMarkwald said:
You should verify you have the latest version of the Android SDK Platform Tools from here.
Are you running via fastboot the following two commands?:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
From there, proceeding with the instructions on flashing the Android P Dev Preview images (link)?
Click to expand...
Click to collapse
target reported max download size of 536870912 bytes
sending 'bootloader' (36344 KB)...
OKAY [ 0.815s]
writing 'bootloader'...
OKAY [ 0.371s]
finished. total time: 1.194s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.342s]
writing 'radio'...
OKAY [ 0.579s]
finished. total time: 1.930s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ20f
Baseband Version.....: g8998-00202-1801251558
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (40960 KB)...
OKAY [ 0.923s]
writing 'boot'...
OKAY [ 0.377s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.593s]
writing 'system'...
OKAY [ 2.431s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.585s]
writing 'system'...
OKAY [ 2.445s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.252s]
writing 'system'...
OKAY [ 2.438s]
sending sparse 'system' (521136 KB)...
OKAY [ 12.083s]
writing 'system'...
OKAY [ 2.412s]
sending sparse 'system' (109860 KB)...
OKAY [ 2.632s]
writing 'system'...
OKAY [ 0.512s]
sending 'vendor' (374836 KB)...
OKAY [ 8.308s]
writing 'vendor'...
OKAY [ 1.734s]
erasing 'userdata'...
OKAY [ 0.289s]
sending 'userdata' (140898 KB)...
OKAY [ 3.125s]
writing 'userdata'...
OKAY [ 1.517s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 78.718s
Press any key to exit...
I did downloaded the latest one.. where do I need to put it? Even tho I'm pretty sure I do have the latest one, as I use Android Studio daily.. Btw now It did unlocked again with oem unlock..
Bucika said:
I did downloaded the latest one.. where do I need to put it? Even tho I'm pretty sure I do have the latest one, as I use Android Studio daily.. Btw now It did unlocked again with oem unlock..
Click to expand...
Click to collapse
Once you have extracted the factory image, place all of the extracted contents in the platform-tools folder. Like in the pic, then open up the command prompt on the platform-tools folder :good:
Badger50 said:
Once you have extracted the factory image, place all of the extracted contents in the platform-tools folder. Like in the pic, then open up the command prompt on the platform-tools folder :good:
Click to expand...
Click to collapse
You sir, are a Legend! :good::highfive:
Saved me!! This is absolutely the first time something like that happened to me in years of owning and tinkering with phones.
Thank you once again.
Bucika said:
You sir, are a Legend! :good::highfive:
Saved me!! This is absolutely the first time something like that happened to me in years of owning and tinkering with phones.
Thank you once again.
Click to expand...
Click to collapse
Oh please bruh!...legend? No..just old. Just helping out my fellow tech brothers/sisters to keep more hair on their heads, and not turn phones into desktop paperweights! ???

Unlock Bootloader For Bricked Mate SE

Hello, i've got a Mate SE and it is bricked, I have access to the bootloader but the phone is bricked, and has no os.
I tried to flash twrp so I can restore a backup
and I got
target reported max download size of 471859200 bytes
sending 'recovery' (25158 KB)...
OKAY [ 0.905s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.914s
and
target reported max download size of 471859200 bytes
sending 'recovery2' (25158 KB)...
OKAY [ 0.900s]
writing 'recovery2'...
FAILED (remote: Command not allowed)
finished. total time: 0.909s
I found out boot loader was re-locked and I need to unlock it again.
I have my IMEI and Serial, but I need my Product ID to get the code.
How can I get my Product ID?
If someone can get the Product ID it would be appreciated.

Categories

Resources