Database Develop

tried to install JB, used Blackrose = can't get into recovery

Hello Folks,
I'm still stuck with my nexus one since I don't care that much about phones.
I've seen that jelly bean roms have made a significant progress. Thus I decided to give it a shot.
I started with installing adb and fastboot. :good: After that I rooted the nexus one :good: I've used this how to:
c2med blog, can't post links...
Next, I ran blackrose. :good: I saved the rom on the micro sd. Having done all the preperations I wanted to flash the JB rom.
I started the phone in bootloader mode but - unfortunately - couldn't access the recovery mode (ext4). I only get the Android figure and an exclamation mark.
In the how-to it sais i should use fastboot to flash the recovery made by ext 4.
Problem # 1: Ext4 generated a .zip, not a .img file
Problem # 2: I connect the device in fastboot mode, navigate to the adb/fastboot folder and use ./fastboot devices. The phone is recognized and I see the serial number. Next I try "flash recovery...." but I only get "command not found". Now, I basically have no idea what to do.
Which recovery should I flash? And how?
I'm so looking forward to your answers.

Androdicct said:
Hello Folks,
I only get the Android figure and an exclamation mark.
Which recovery should I flash? And how?
Click to expand...
Click to collapse
What you get is the stock recovery.
Flash 4Ext recovery or Amon RA recovery ( fastboot flash recovery recovery-RA-passion-v2.2.1.img)
Among the several guides to install JB, I suggest you to look at the following post:
http://forum.xda-developers.com/showthread.php?t=1804571
I just finished this morning the following process:
install RA recovery,
install Blackrose and resize partition,
install from SD card Evervolv-Perdo-3.2.0-Nightly-2013.01.13-passion.zip
install from SD card gapps-ev-jb-20120816.zip
I spent a lot of times reading and trying. I had an issue after installing Evervolv-perdo-3.1.0final-passion zip. That's why I switched to the Nightly (JB 4.2).
Once you are set install a2sd from within the terminal emulator on your N1.
In my opinion this is so far the best ROM I ever have had on my Nexus 1.:good:
I am impressed to the extend that I offer to my wife to do the same on her N1. She said no. No to unlock, no to root and of course no to custom ROM.
Good luck

Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...

Androdicct said:
Hi,
thanks for your reply. Thats basically what i did as well. But after using Blackrose i can't go into the recovery mode.
I used the same tutorial. The problem lies here:
"Note: some people have reported having problems getting into recovery at this point (if not move on to step 5). If that happens, luckily for you, 4ext put a recovery image in the downloads folder of your SD card and if you did what I said in step 2 you saved it. Try reflashing that recovery image using fastboot (remember the one that was in SD/Download/4EXT_Recovery_Touch/ and was named "recovery.img"). Put your phone into the bootloader by turning off your phone, turning it on again while holding the trackball down. To reflash the recovery open command prompt and cd to the location of the Android SDK tools. Then type in the following command (replacing "path" with the path to where the recovery image is located on your computer):
Code:
fastboot flash recovery /path/recovery.img
If that does not solve your problems (inability to get into recovery) then I would recommend going back to the cyanogenmod wiki and installing Amon_Ra's recovery. Then you can use it to flash your installation zip."
It seems like I am unable to understand what I am supposed to do. Could somebody give me a step by step advice? I would prefer using some other recovery.img than mine...
Click to expand...
Click to collapse
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?

gunner1937 said:
It happened to me. I just re-flashed Amon RA recovery from the fastboot mode. Maybe somewhere you missed a step?
Click to expand...
Click to collapse
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!

Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=611829 : read posts #15 and #16.
In other words open your folder android-sdk-windows installed on the root of your C: hd. Click on the folder platform-tools and download Amon RA recovery in this folder. Left click anywhere on a blank area of this folder then press the key Shift (keyboard) and right click your mouse. In the drop down menu select Open command window. In the CMD, to be sure that the N1 is recognized by the pc (meaning the right drivers are installed) type ADB devices and press enter. You should see a string of numbers like HT9C......
Type adb reboot bootloader and press enter. You are in the fastboot mode ( and mood if I may say so) and the phone shows that it is in the bootloader. You can check again that N1 is recognized by the pc by typing fastboot devices. Same string appears.
Type fastboot flash recovery recovery-RA-passion-v2.2.1.img.
After the installation is completed boot in recovery, select Flash zip from sdcard, select the ROM you have dropped on the card. When the installation is completed go back to Flash zip from sdcard ( you are still in recovery mode) and select the gapps you have dropped on the sdcard.
Go back to Reboot system now. You are then out of the recovery and it takes some times for the N1 to boot to this beautiful JB
Edit:
http://forum.xda-developers.com/showthread.php?t=1804571 this is for posts #15 & #16

Androdicct said:
Okay I see. Could you give me the exact steps for the fastbood method? :angel: And where did you get the recovery?
Cheers!
Click to expand...
Click to collapse
As c2med posted in his guide, sometimes, people lose their recovery when they repartition using Black Rose. Hence, its always best to have Amon-RA or 4EXT flashable .img file in your PC so that incase you lose recovery, you can always flash it back.
Once you are in bootloader ( also called FASTBOOT mode) you can flash your recovery.
Then reboot into recovery from FASTBOOT (Shutdown and then restart using the recovery combination)
Once you are in recovery, follow the steps in c2med's guide (wipe cache/dalvik/etc - except sd-card ofcourse) and flash your ROM from sd card.
Then reboot into JayBee

In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img

jolinnard said:
In the screenshot you type:
$ ./fastboot devices
then you type:
$ flash recovery ......../recovery.img
Command not found.... Sure, flash it's not a command...
You need to type fastboot command first!
$ ./fastboot flash recovery ......../recovery.img
Click to expand...
Click to collapse
Thank You! That's what I figuered out last night. Of course I also tried "fastboot flash" but forgot the "./". That was the key. Now the JB ROM works like a charm.
New Problem:
I can't install google apps. In fact I don't really need them. I only use a few apps and found the .apk files with google. Unfortunately the "official" Google apps like chrome don't work.
Plus, I wanted to install the camera (laggy in the evervolv - rom) and keyboard from here.
http://forum.xda-developers.com/showthread.php?t=1965290&page=38
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?

Androdicct said:
When I try to install the .zip files in recovery mode I always get an error because of the signing... any help?
Click to expand...
Click to collapse
When you're in recovery, select "Flash zip from SD card" and then select "Toggle signature verification" to disable signature verification, and then "Choose zip from SD card" and navigate to the zip file that you want to flash.

[Q] Bought phone with custom ROM, confused how to restore to stock

Sorry - trying to delete this, posted in wrong forum
Hello,
I've spent the afternoon reading and researching and I'm confused. I'm completely new to this and would love some advice. I have an HTC One, I BELIEVE it was a Rogers phone, canadian - not sure if this matters. The person told me it was Rogers and all I did after was pop in the imei number into one of the unlock sits to unlock it. I couldn't figure out why I wasn't getting any carrier updates when I finally figured out it had the Maximus 7 ROM installed.
So how can I tell if it definitely was a rogers phone? And does this matter if I want to restore it to factory?
It's currently not rooted, I checked with a root check app. The bootloader is unlocked. Can I follow mike1986's guide to restore it to stock?
These instructions specifically? He says only for users with .401 devices, how do I know if mine's a .401?
I've read and read and I haven't been able to find the answer. Any advice would be appreciated.
Thanks!
Method 1 - only for users with .401 devices (for more info click here - RUU variants)
Visit this thread - [ROM] HTC One *STOCK* ROM
Download stock odexed version of most recent firmware and recovery.img
Move recovery.img to c:\mini-sdk location
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of stock ROM (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device in bootloader mode.
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock

[Q] Bought phone with custom ROM, confused how to restore to stock

Hello,
I've spent the afternoon reading and researching and I'm confused. I'm completely new to this and would love some advice. I have an HTC One, I BELIEVE it was a Rogers phone. The person told me it was Rogers and all I did after was pop in the imei number into one of the unlock sits to unlock it. I couldn't figure out why I wasn't getting any carrier updates when I finally figured out it had the Maximus 7 ROM installed.
So how can I tell if it definitely was a rogers phone? And does this matter if I want to restore it to factory?
It's currently not rooted, I checked with a root check app. The bootloader is unlocked. Can I follow mike1986's guide to restore it to stock?
These instructions specifically? He says only for users with .401 devices, how do I know if mine's a .401?
I've read and read and I haven't been able to find the answer. Any advice would be appreciated.
Thanks!
Method 1 - only for users with .401 devices (for more info click here - RUU variants)
Visit this thread - [ROM] HTC One *STOCK* ROM
Download stock odexed version of most recent firmware and recovery.img
Move recovery.img to c:\mini-sdk location
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of stock ROM (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device in bootloader mode.
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock

Also, is this method that same as using a RUU if one was available? From what I understand the RUU restore is just a simpler method?

Check your CID in the bootloader power + volume down

I used CID Getter and it says CID is ROGER001

HM796 said:
Hello,
I've spent the afternoon reading and researching and I'm confused. I'm completely new to this and would love some advice. I have an HTC One, I BELIEVE it was a Rogers phone. The person told me it was Rogers and all I did after was pop in the imei number into one of the unlock sits to unlock it. I couldn't figure out why I wasn't getting any carrier updates when I finally figured out it had the Maximus 7 ROM installed.
So how can I tell if it definitely was a rogers phone? And does this matter if I want to restore it to factory?
It's currently not rooted, I checked with a root check app. The bootloader is unlocked. Can I follow mike1986's guide to restore it to stock?
These instructions specifically? He says only for users with .401 devices, how do I know if mine's a .401?
I've read and read and I haven't been able to find the answer. Any advice would be appreciated.
Thanks!
Method 1 - only for users with .401 devices (for more info click here - RUU variants)
Visit this thread - [ROM] HTC One *STOCK* ROM
Download stock odexed version of most recent firmware and recovery.img
Move recovery.img to c:\mini-sdk location
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of stock ROM (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device in bootloader mode.
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock
Click to expand...
Click to collapse
From what I understand, the Rogers One is not a .401 device, so i think this method you state is out for now. There is still methods 2 and 3, but I wasn't able to find a Rogers RUU or stock rom backup yet.

[Q] Remove Branding with a Mac

HI,
i own a HTC one with a T-mobile Austria branding which includes a million of apps i didn't need.
How can i change it to a Clean Stock HTC version on a MAC?
I really want to get the updates from HTC, not from T-mobile.
Thanks bye!

prognosticon said:
HI,
i own a HTC one with a T-mobile Austria branding which includes a million of apps i didn't need.
How can i change it to a Clean Stock HTC version on a MAC?
I really want to get the updates from HTC, not from T-mobile.
Thanks bye!
Click to expand...
Click to collapse
platform doesn't matter
gaining S-off is all you need
once you do that change the CID to match the unbranded HTC One device and install that RUU
You might have to change the Model ID (MID) as well but that's easy too.
Just pick an S-off method, you'll probably want revOne since it is just terminal commands.

Thanks but is there a way to get Soff without HTC-DEV on a mac also?
Edit:
Sorry just saw that it is no problem with revone!

gunnyman said:
platform doesn't matter
....... and install that RUU
Click to expand...
Click to collapse
I have no idea how to install a RUU via mac, google doesn't help.
My phone is now S-off and my CID is HTC__001.
What should i do next?

prognosticon said:
I have no idea how to install a RUU via mac, google doesn't help.
My phone is now S-off and my CID is HTC__001.
What should i do next?
Click to expand...
Click to collapse
oh you need windows to install an RUU I just did it with VM ware and an old windows disc I had laying around

As mentioned above, you'd need Windows in order to install an RUU. Follow this guide in order to install a RUU, and since you're on HTC__001, download and install this RUU:
http://bugsylawson.com/files/file/1...13323127-1031113105-release-310878-signedexe/
Here's the important part in the guide:
mike1986. said:
Going back to stock
What you need to know before going back to stock:
Your bootloader will never be "LOCKED" again. You can't restore it. You can only relock it.
"TAMPERED" text in bootloader will disappear only after proceeding method 2.
There are 3 main methods. All three will be described below.
Method 1 - only for users with .401 devices (for more info click here - RUU variants)
Visit this thread - [ROM] HTC One *STOCK* ROM
Download stock odexed version of most recent firmware and recovery.img
Move recovery.img to c:\mini-sdk location
Boot your device in recovery mode (power off the device and turn it on using power + vol down buttons and select "RECOVERY")
In main menu, select "install zip from sdcard" and "choose zip from sdcard".
Navigate to the location of stock ROM (zip) package and confirm flashing procedure.
After flashing process is complete, reboot the device in bootloader mode.
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock
Method 2 - flashing RUU (ROM Update Utility)
Visit this or this thread.
Find proper RUU for your device
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot oem lock
Flash RUU and follow on screen instructions.
You have now completely stock software on your device.
Method 3 - flashing nandroid backup
In custom recovery restore nandroid backup you did after flashing custom recovery for the first time.
If you performed nandroid backup before permanently flashing custom recovery, your stock recovery should be now flashed.
If you still have custom recovery, extract recovery.img from your nandroid backup.
Move recovery.img to c:\mini-sdk location
Connect your device to the PC
Boot your device in fastboot mode (like you did during unlocking bootloader - power off the device and turn it on using power + vol down buttons and select "FASTBOOT")
Open up command prompt ( Start > Run > type cmd and hit enter ). The window that appears is called Command Prompt. <click here to see the image>
Navigate to where you unzipped "mini-sdk" package (type in Command Prompt: cd c:\mini-sdk). Note: make sure the path is not c:\mini-sdk\mini-sdk
In the Command Prompt type following command: fastboot flash recovery recovery.img
You have now stock boot, system and recovery partitions. Time to relock your bootloader.
In the Command Prompt type following command: fastboot oem lock
Here are some videos you might find helpful:
1) by Flow-Wolf
How to Unlock the bootloader
How to Flash the recovery
How to root the HTC One
2) by udimars30
How to Unbrick/Unroot/Flash stock Rom Back on HTC ONE
[/FONT]
Click to expand...
Click to collapse
EDIT: You'll need to setup adb and fastboot on Mac in order to be able to use the terminal commands mentioned in the guide. This can help you do that: http://forum.xda-developers.com/showthread.php?t=1917237
DO NOT download the Android SDK as it is not necessary, however scroll down in the guide and you'll find a small zip file containing a folder called android which you should extract to your Desktop.

[Guide][TWRP 3.1] How to Flash TWRP 3.1 on Lenovo ZUK Z2 Pro

The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
Mega
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx

MariosFFX said:
The recoveries I post are and tested for Lenovo Z2 Zuk Z2 Pro ONLY!
Requirements:
Unlocked phone bootloader
and your phone booted in fastboot mode, otherwise it will not work.
Recovery.img is the same recovery found on Lenovo forums (link below)
Download from MEGA
https://mega.nz/#!zJhFCKRa!7FDyDKkqEL3bgz-lYBMf_Lj0RoMyzubg9tiZC3z9ttg
Images are in thumbnails, click on them to enlarge
Short guide:
1) Simply extract the zip
2) Open cmd.exe and cd to the directory you extracted
3) Put your phone in fastboot mode by shutting down your phone, if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
4) Paste the following commands:
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
You should get the same results I got:
Long guide for newbies with Windows 10 [the same might be for Windows 7/8]:
1) Download the zip I have uploaded and extract it to a folder with your favorite archive manager [I use WinRAR] and open it
2) Hold Shift and Right Click on empty space in the folder
3) Left click on Open command window here or open command prompt here
4) Put your phone in fastboot mode by shutting down your phone, power it on and if you have unlocked your phone, you will get the following boot message
"Your phone cannot be checked for file corruption...etc", press Volume Down, hightlight "Fastboot" option, press Power Button
5) Paste the following commands by copying one line each time
Code:
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c boot recovery.img
Contents of Uploaded RAR/Zip Archive:
adb.exe & fastboot.exe taken from adb-setup-1.4.3 zip/rar file, which was found on Google, don't have a source link
drivers where taken from ZUK_UsbDriver_1.0.6 zip/rar from a guide which was found on google, don't have a source link
recovery images where taken from the sources below
Sources & Thanks:
Recovery 3.0.8 was taken from:
https://forum.xda-developers.com/le...t/twrp-recovery-zuk-z2-standard-pro-t3415395/
credits go to @raimondomartire
Recovery 3.1 was found on official Lenovo Forums:
http://bbs.lenovomobile.cn/z2pro/t508552/
Google translated Lenovo Forum Page:
https://translate.google.com/transl...n&u=http://bbs.lenovomobile.cn/z2pro/t508552/
Q&A:
Q: I do the same steps you did, in command prompt after pasting your commands I get the following: "< waiting for device >
or I wait for long periods of time or I get a [ERROR] message
A: Chances are 100%, you have the wrong drivers or not drivers installed, most devices use their own drivers for fastboot mode or adb/fastboot commands
If you have a Lenovo Zuk Z2 Pro like me, your device needs to be identified as "ShenQi Composite ADB Interface" in device manager.
Not "Android" or "Android ADB Interface" and because of that fastboot does not identify your device at all
Q: Why do you use 2 commands (fastboot flash and fastboot flash) instead of one?
A: I am not 100% sure but I think fastboot flash recovery, flashes the recovery image you have selected [permanently, until you flash a different one] in your device and you can boot into it anytime you want without using a PC
and the second boots your phone with the recovery image but does not flash it, meaning you keep the stock or the one you have flashed in the past.
So I use the first commmand to permanently flash the recovery and the second to boot the phone in recovery mode without using any phone button combinations to boot into, saves me the time and hassle.
Q: Why use Chinese Custom Recovery instead of an English one?
A: This recovery has Chinese and English Language support. However, if you go to the translated google forum link which I have posted below, the thread's title is: Z2 pro Brush] [zuk z2Pro] Twrp Recovery 3.10 update, support Andrews 7.0 7.1 7.1.2ROM
So I think, Recoveries need to also support the custom ROMS you want to flash, also it is taken from official lenovo forums and chances are they have added more features and fixes.
For example using 3.0.8 recovery I couldn't install LineageOS 14.1 custom rom, I was getting Error 7 when I was trying to flash
Q: I get Error 7 when I try to Flash a Custom ROM:
A: Flash 3.1 TWRP Recovery, the custom recovery you have flashed, does not support the custom ROM you want to flash.
Q: I no longer have open command prompt here after intalling Windows 10 Creators update, I have Open Powershell instead, help?
A: Read the following webpage:
http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/
It provides a registry fix which adds/restores "open command window here" in Windows 10 Context Menu
Q: Custom Recovery 3.1 is in Chinese, how do I change it to English?
A: See the following images
Tested on Windows 10 x64 Pro with Creators Update, should work for Windows 7/8 as well.
If this guide helped you, please buy me a beer, thanks!
http://paypal.me/mariosffx
Click to expand...
Click to collapse
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.

bluegrass55 said:
Thanks for this.
I'm waiting for delivery of a Z2 Pro and getting necessary stuff ready.
The Mega link wants a Decrypt key.
Click to expand...
Click to collapse
check again, the link is with decryption key.
I have double checked and made sure it was with the key.

I've tried again on Chrome,IE and Firefox but still get Decrypt message.

Do you copy and paste the link or you click on it?
Seems to me you copy and paste it.
Because the link is way too big, xda forums shorten it (notice the dots).
Click the link don't copy and paste iit

Finally managed to download it.
I clicked on the link in Chrome & it worked. Firefox didn't like it.
Thanks for the help.

fastboot claims to work, but doesn't
Code:
[email protected] ~/Downloads> fastboot -i 0x2b4c flash recovery twrp.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18372 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.145s]
finished. total time: 0.670s
[email protected] ~/Downloads> fastboot -i 0x2b4c reboot
rebooting...
finished. total time: 0.071s
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.

Philo.Phineas said:
Yet it goes back stock recovery. I've tried many variations of these commands, and always get the same results.
Click to expand...
Click to collapse
I am having problems with this Chinese twrp why not get fixed in the bootloader nor accept after even running without installing the program supersu via twrp

Hello All,
So originally I had TWRP 3.0 on my Z2 pro, and i attempted to just install the 3.1 img file from it(per another instructional video from the 7.1 mokee thread), and after installing the recovery file, my phone restarted, however now when I attempt to go into Recovery mode from the boot menu, my phone just goes to a blank screen.
I've tried to flash the image from CMD to see if i could essentially "re flash" 3.1 TWRP, but I always get this message(see attached image). What am i typing in wrong in CMD? As you can see, the directory name is right, as well as the fastboot code. I'm also IN fastboot mode on my phone already. I changed the file name of the folder containing the recovery from it's orginal name to make it shorter, but that should not matter at all. It seems as if CMD can't find the folder though?
Well XDA won't let me post a damn picture(how am i supposed to ask for help if i can't show people what im doing), so I guess if someone would PM me i can post the image.

People do you try to flash the recoveries right after unlocking your bootloader?
Because if you can't flash the recovery and it goes back to stock, it means you haven't fully unloxked your bootloader.
Make sure you run the last following command when you unlock your bootloader
Code:
fastboot -i 0x2b4c oem unlock-go
Then follow my guide here.
Also bootloader unlock tutorial here:
https://zukfans.eu/community/threads/zuk-z2--unlock.62/
Its for Zuk Z2, but the instructions are also for Z2 Pro.

MariosFFX said:
rl].
Click to expand...
Click to collapse
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.

which files about phone mobile data at a TWRP BACKUP ? i see a lot of files inside of a twrp backup . i need to learn that . thanks.

jsto69 said:
Any idea about what's happening with the situation in my post by chance? When I try to flash from CMD i get this text. "Z2 is not recognized as an internal or external command, operable program or batch file"
"Z2" is the name of the folder that contains the recovery image, so it seems like it's not finding it.
Click to expand...
Click to collapse
Use directory names without spaces. Like c:\zuk and perform all operations from there.

Hello, this works fine very thx, but you have recent/new mix version?