Related
Hi everyone! i search everywhere in the forum but I can't find any solution for my htc one m7 bricked...
I can go in the bootloader that is unlocked i can locked too,,,i can flash a custom recovery and use it but i can't see my usb otg cable with usb stick (i try other usb stick and all work fine in galaxy s2 not in my htc one m7 so i think the cable and the usb stick are not the problem,,,) i can't use adb (i use pc with win8.1 win7 win xp and mac osx and all can't find the devices connected in adb sideload from the custom recovery...i use twrp and i try clockworkmod but both don'twork...)i can flash boot or zip from fastboot but when i flash zip always appeare remote 12 signature failed...because i can't find a ruu for my cid: tim__401....
i have no other ideas for resuscitate my htc one m7_ul...can anyone help me???
Sorry for my bad english greatings from italy Luke
luca89s said:
Hi everyone! i search everywhere in the forum but I can't find any solution for my htc one m7 bricked...
I can go in the bootloader that is unlocked i can locked too,,,i can flash a custom recovery and use it but i can't see my usb otg cable with usb stick (i try other usb stick and all work fine in galaxy s2 not in my htc one m7 so i think the cable and the usb stick are not the problem,,,) i can't use adb (i use pc with win8.1 win7 win xp and mac osx and all can't find the devices connected in adb sideload from the custom recovery...i use twrp and i try clockworkmod but both don'twork...)i can flash boot or zip from fastboot but when i flash zip always appeare remote 12 signature failed...because i can't find a ruu for my cid: tim__401....
i have no other ideas for resuscitate my htc one m7_ul...can anyone help me???
Sorry for my bad english greatings from italy Luke
Click to expand...
Click to collapse
use this guide to install a rom to your phone. I suggest you to use arhd 81.0
alray said:
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-20130219\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
You need TWRP recovery 2.6.3.3 on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone after the installation is completed
Click to expand...
Click to collapse
Click to expand...
Click to collapse
alray said:
use this guide to install a rom to your phone. I suggest you to use arhd 81.0
Click to expand...
Click to collapse
i can't use adb pc don't "see" my htc...i have alredy tried this guide....
luca89s said:
i can't use adb pc don't "see" my htc...i have alredy tried this guide....
Click to expand...
Click to collapse
Can your PC Detect your phones storage space? I know it's a bit late now as you've bricked it? but it sounds like to me that your PC isn't detecting your phone so install the phone drivers?
badd1e said:
Can your PC Detect your phones storage space? I know it's a bit late now as you've bricked it? but it sounds like to me that your PC isn't detecting your phone so install the phone drivers?
Click to expand...
Click to collapse
my pc detect htc only in fastboot usb mode...when i connect in custom recovery mode the phone connect and disconnect immediatly...i can't see the internal storage....and when i try to use usb otg via twrp i can't select usb otg mode from the menu...
I CAN ONLY USE FASTBOOT command at the moment..but i can't find a ruu for my cid: tim__401....
luca89s said:
my pc detect htc only in fastboot usb mode...when i connect in custom recovery mode the phone connect and disconnect immediatly...i can't see the internal storage....and when i try to use usb otg via twrp i can't select usb otg mode from the menu...
I CAN ONLY USE FASTBOOT command at the moment..but i can't find a ruu for my cid: tim__401....
Click to expand...
Click to collapse
so what is the error in CWM when you choose install from externel_sd or USB OTG ?
luca89s said:
I CAN ONLY USE FASTBOOT command at the moment
Click to expand...
Click to collapse
so your drivers are probably not installed correctly. Re-install your drivers following the guide and you should also reflash twrp 2.6.3.3, fastboot erase cache and reboot bootloader
clsA said:
so what is the error in CWM when you choose install from externel_sd or USB OTG ?
Click to expand...
Click to collapse
any erroe only when i select usb otg mode i return in the menu...
alray said:
so your drivers are probably not installed correctly. Re-install your drivers following the guide and you should also reflash twrp 2.6.3.3, fastboot erase cache and reboot bootloader
Click to expand...
Click to collapse
now i can use adb on my old pc with win xp...i see the devices but when i try to push a zip in sdcard come out this error..: protocol failure (when i try in the menu of twrp) error: closed (when i try in adb sideload)... any suggestion? thanks
luca89s said:
now i can use adb on my old pc with win xp...i see the devices but when i try to push a zip in sdcard come out this error..: protocol failure (when i try in the menu of twrp) error: closed (when i try in adb sideload)... any suggestion? thanks
Click to expand...
Click to collapse
It sounds like you do not have the right drivers installed, try installing them from here http://forum.xda-developers.com/showthread.php?t=2588979 and see if that works. There is an update there for Windows 8.1 as well.
chuckwago88 said:
It sounds like you do not have the right drivers installed, try installing them from here http://forum.xda-developers.com/showthread.php?t=2588979 and see if that works. There is an update there for Windows 8.1 as well.
Click to expand...
Click to collapse
RESOLVED!!
i flashed a stock recovery....do a factry reset then installed a twrp 2.6.3.3 and following the guide linked by @alray and installed inestrcoin custom rom...
Thank at all of you!
You sir. You deserve a medal... Thanks for sharing. I was able to get my phone out of brick after following your instructions. THANK YOU SOO MUCH :victory::victory::victory:
alray said:
use this guide to install a rom to your phone. I suggest you to use arhd 81.0
Click to expand...
Click to collapse
hello xda people,i thought i might share this with you since i've tested and done it myself about rooting kitkat eu update.My bootloader was factory locked and proceeded unlocking it and i barely managed to install Hazou's unoficial twrp recovery(see this thread:http://forum.xda-developers.com/showthread.php?t=2278483) wich was done via fastboot,but mostly even after the custom recovery install i didn't managed to get root on kitkat,so i've tried ChainsDD superSU update pack witch seems to resolve the problem because the update package installs the propper package according to system specs,so if anyone there wishing to root or doesn't quite figure out,here's an simple how to:
1Make sure you have all the drivers installed.
2install or download android sdk
3 from the sdk,copy on your desktop platform-tools (for easier job)
4 download recovery image from Hazou thread,see: http://forum.xda-developers.com/showthread.php?t=2278483 extract and place it on platform-tools folder you copied on your desktop
5in platform-tools folder open cmd line and enter your phone in fastboot
6type "fastboot devices" without quotes
7 if your device is listed,type: fastboot flash recovery recovery.img
8now after cmd confirms if the flash was succesfull, either head to recovery from fastboot mode and see if twrp is installed,if it does keep your phone connected to pc
9 download chainsDD superSU update to external sd,link to download https://drive.google.com/file/d/0B8m4rdNFVU4_YjV4X2gtUjNhZVE/view?usp=sharing
10 install via twrp,wipe davik+cache, reboot and enjoy
You can get the latest CWM / TWRP / MobileODIN installable ZIP from here. It has x86 support and works on the Razr i.
drunk_ryder24 said:
hello xda people,i thought i might share this with you since i've tested and done it myself about rooting kitkat eu update.My bootloader was factory locked and proceeded unlocking it and i barely managed to install Hazou's unoficial twrp recovery(see this thread:http://forum.xda-developers.com/showthread.php?t=2278483) wich was done via fastboot,but mostly even after the custom recovery install i didn't managed to get root on kitkat,so i've tried ChainsDD superSU update pack witch seems to resolve the problem because the update package installs the propper package according to system specs,so if anyone there wishing to root or doesn't quite figure out,here's an simple how to:
1Make sure you have all the drivers installed.
2install or download android sdk
3 from the sdk,copy on your desktop platform-tools (for easier job)
4 download recovery image from Hazou thread,see: http://forum.xda-developers.com/showthread.php?t=2278483 extract and place it on platform-tools folder you copied on your desktop
5in platform-tools folder open cmd line and enter your phone in fastboot
6type "fastboot devices" without quotes
7 if your device is listed,type: fastboot flash recovery recovery.img
8now after cmd confirms if the flash was succesfull, either head to recovery from fastboot mode and see if twrp is installed,if it does keep your phone connected to pc
9 download chainsDD superSU update to external sd,link to download https://drive.google.com/file/d/0B8m4rdNFVU4_YjV4X2gtUjNhZVE/view?usp=sharing
10 install via twrp,wipe davik+cache, reboot and enjoy
Click to expand...
Click to collapse
I like this method, you're always left with a fallback or the option to the Rom flash again or use an alternate when using recovery, I've started to prefer TWRP over clockwork recently
Can not go to Recovery mode or Fast boot Mode or Boot up "Black Screen"
but still detect USB mode at PC (device manager)
Must conect to PC:
1.Download and install adb driver
2.Download and install Miphone Module (MiFlash Module)
3.Download Stock miui rom (Fastboot Rom not flashzip rom)
4.extract your fastboot miui download rom (extract file should be one image folder and some flash file.bat)
5.Copy MiFlash.exe from your instalation from step 2 to fastboot rom extract directory
6.Conect your phone to pc
7.Start MiFlash exe from extract directory
8.Browse Fastboot rom when you already extract before from MiFlash.exe Taskbar
9.Choose one method flash from bottom taskbar
10.And Click Flash...wait until 100% succesfull
11.Your Done
Note:Mode Flash All (All Data will erase)
Test under Xiaomi Mi4W
OS:Win.8.1 x64
Hope this is can help
My Regard
Dona55 said:
Can not go to Recovery mode or Fast boot Mode or Boot up "Black Screen"
but still detect USB mode at PC (device manager)
Must conect to PC:
1.Download and install adb driver
2.Download and install Miphone Module (MiFlash Module)
3.Download Stock miui rom (Fastboot Rom not flashzip rom)
4.extract your fastboot miui download rom (extract file should be one image folder and some flash file.bat)
5.Copy MiFlash.exe from your instalation from step 2 to fastboot rom extract directory
6.Conect your phone to pc
7.Start MiFlash exe from extract directory
8.Browse Fastboot rom when you already extract before from MiFlash.exe Taskbar
9.Choose one method flash from bottom taskbar
10.And Click Flash...wait until 100% succesfull
11.Your Done
Note:Mode Flash All (All Data will erase)
Test under Xiaomi Mi4W
OS:Win.8.1 x64
Hope this is can help
My Regard
Click to expand...
Click to collapse
i have tried this method but somehow my phone is still in bootloops. i cant access recovery but fastboot is still possible on the MI 3
bnambiar1997 said:
i have tried this method but somehow my phone is still in bootloops. i cant access recovery but fastboot is still possible on the MI 3
Click to expand...
Click to collapse
bootloops it is ROM Problem maybe You have FLASH with the wrong ROM...
If Success with the right ROM, it is should be Done/Fine, and can not access Recovery Mode Perhaps your Volume Up Button has Broken....
My Regard
bnambiar1997 said:
i have tried this method but somehow my phone is still in bootloops. i cant access recovery but fastboot is still possible on the MI 3
Click to expand...
Click to collapse
Your issue resolved? If not and you don't have recovery then get the latest TWRP recovery and rename it to recovery so the file would be "recovery.img" and put it inside the folder where you have fastboot.exe file.
Now connect your phone to Windows PC and in the same fastboot folder open command prompt (Shift + Right click > then you will see "open command window here" - click on it).
Now type : fastboot devices + enter. If you can see an entry then enter the next command as below
fastboot boot recover.img - This will format the recovery partition with the TWRP and also boot into recovery.
Now you can flash ROM as you want.
Please hit the Thanks button below, if I have helped.
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.
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?