Related
Hi Folks,
Model number: Moto G (2nd Generation)
System Version: 22.46.12.titan_retuaws.retuaws.en.US retus
Build number: LXB22.99-24.12
Android version: 5.0.2
I've spent a couple hours so far trying to root this thing. Lots of guides that claim that they cover this device either don't really (the xt1064 isn't actually listed once you get into the guts of the how-to), or they just don't work.
The bootloader is unlocked, but I haven't found a working recovery. They're all too big, apparently. I've tried these, for instance:
openrecovery-twrp-2.8.5.0-titan.img
TWRP2.7.1.1-titan-motog-2014.img
twrp-2.8.3.0-titan.img
twrp-2.8.6.0-titan.img
twrp-2.8.4.0-titan.img
This is what happens:
Code:
[email protected] ~/Downloads $ sudo fastboot flash recovery twrp-2.8.3.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9674 KB)...
FAILED (data transfer failure (Value too large for defined data type))
finished. total time: 0.011s
Does anybody know of an actual working recovery for this thing?
Also, is there a special SuperSU, once I get it rooted?
Thanks,
Jamie
Actually, many of them work very well with the XT1064. Make sure everything (adb, fastboot, the TWRP image) are in the same directory on your computer. I've literally flashed my XT1064 dozens of times using the directions posted all over XDA.
You should be able to open up a cmd prompt in the directory with your files and type, fastboot flash recovery twrp.img, then fastboot reboot.
BTW, I believe TWRP is up to 2.8.7 now.
I'm on linux (Mint), and adb/fastboot are installed via package management, and they're on my path. I don't remember having to install a second set of tools and put the image in the same directory as the tools before (when flashing other devices). My output from above shows that the img file is found (it's just too big). Since I can't test it now (machine's at home), what's the rationale for having to put the image in the same directory as the fastboot executable?
FWIW, as of this writing, the downloads page only shows up to twrp-2.8.6.0-titan.img.
Jamie Jackson said:
I'm on linux (Mint), and adb/fastboot are installed via package management, and they're on my path. I don't remember having to install a second set of tools and put the image in the same directory as the tools before (when flashing other devices). My output from above shows that the img file is found (it's just too big). Since I can't test it now (machine's at home), what's the rationale for having to put the image in the same directory as the fastboot executable?
FWIW, as of this writing, the downloads page only shows up to twrp-2.8.6.0-titan.img.
Click to expand...
Click to collapse
https://twrp.me/
Hmmm, I see a newer version but I doubt that's your problem.
Sent from my SM-T530NU using Tapatalk
Try philiz recovery it will solve ur pblm i already tried it in 2 moto g phones
vaisakmct said:
Try philiz recovery it will solve ur pblm i already tried it in 2 moto g phones
Click to expand...
Click to collapse
Is this the one you're talking about, and have you rooted a titan, specifically?
Tel864 said:
https://twrp.me/
Hmmm, I see a newer version but I doubt that's your problem.
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
That's just the home page. When you drill into the titan download page, the versions aren't as new as the home page would suggest.
Jamie Jackson said:
Is this the one you're talking about, and have you rooted a titan, specifically?
Click to expand...
Click to collapse
sure many titan phones
{
"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"
}
Confirmed working with:Exodus for ZUK Z1 5.1.1.MOKEE CM Nightly 5.1.1.Cyanogen OS OTAs thanks to @EagleEyedTom
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards and so on. YOU are choosing to make these modifications.
* Bug reports or confirmation of working things are welcome.
*/
Click to expand...
Click to collapse
DO NOT USE ON AN ENCRYPTED FILE SYSTEM
For some reason I can't get my image to decrypt encrypted file systems. I lost all my data to this issue and at the moment I do not know of a fix. If you need to update or modify and encrypted partition you will have to back up EVERYTHING in your data partition and then do a complete wipe. Sorry.
This image has been recompiled with device checking disabled thank you to @TheCrazyLex for making the new .prop for the international variant.
Please note this image was compiled for the chinese variant of the ZUK Z1 it should work with the international version but zip flashing might not work properly due to device IDs. To flash zips with device specific build.props comment out all the device checks
There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.
Q: Does this work for ZUI devices? A: No, I don't think so. You're welcome to test it and report back but so far I have only tested it with Cyanogen OS
Q: What can I get with this I can't with Cyanogen OS Recovery? A: You can flash unsigned ZIPs such as SuperSU or Xposed (Although I don't recommend doing this as I put my phone into a bootloop installing Xposed)
First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.
Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.
If Windows is giving you an error claiming the best driver is already installed right click Z1 or whatever it is named in Device Manager and click Update Driver.
Then click "Browse my computer for driver software" then click "Have disk" once you have done this browse to the extracted USB driver and open the .inf file it will show you three options select ADB device (Top one). Click yes to any warning and it should be mounted!
Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type
Code:
adb devices
It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.
Code:
adb devices
You will also need to download the TWRP image from the spoiler below.
DON'T DOWNLOAD THESE IMAGES FROM ANYWHERE OTHER THAN ANDROID FILE HOST FROM ME WITH MATCHING MD5 SUMS. I AM AWARE SOMEONE HAS RE-UPLOADED MY IMAGES
Android File Host for Z1 TWRP V2.1 - DOWNLOAD LINK
Android File Host MD5 for Z1 TWRP V2.1 - d5fa8f50144316647b35af4a92a61ab9 - Has all currently reported bugs fixed!
Android File Host for Z1 TWRP V2.0 - DOWNLOAD LINK
Android File Host MD5 for V2.0 = 6226173f5cb17bc7b4ab67ac55efdbbb - Now uses Chroma Kernel to run, reduces heat output, fixes audio bug issues, fixes battery drain, and fixes brightness inside TWRP. Added new splash screen.
Android File Host for Z1 TWRP V1.3 - DOWNLOAD LINK
Android File Host MD5 for V1.3 = eaf29b2653a53d120146d1cedcb1e372p - Added support for both ZUK Z1 variants, international and Chinese.
Android File Host for Z1 TWRP V1.2 - DOWNLOAD LINK
Android File Host MD5 for V1.2 = 3b6fa140737b769f838169e997f58975 - Retired due to limited device compatability
Android File Host for Z1 TWRP V1.1 - DOWNLOAD LINK
Android File Host MD5 for V1.1 = 596816b87a45d78bed4063ac62fac137 - Compiling issue, uploaded without thorough test.
Android File Host for Z1 TWRP V1.0 - DOWNLOAD LINK
Android File Host MD5 for V1.0 = 62b72d5129591d6759bb1917868594f4 - Outdated, filled with bugs.
If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!
Type:
Code:
adb reboot bootloader
You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with
Code:
-i 0x2b4c
.
Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.
To check type:
Code:
fastboot -i 0x2b4c oem get-device-info
If it returns:
(bootloader) Device unlocked: true
Click to expand...
Click to collapse
Then you are ready to begin the flashing process.
Move the downloaded file to your platform tools folder and type:
Code:
fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE1.img
If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.
Special thanks to Anas Khan who made these awesome titles!
XDA:DevDB Information
Un-Official Breadcrust's TWRP 2.8.7.0 Recovery for ZUK Z1, ROM for the Lenovo Zuk Z1
Contributors
Breadcrust, TheCrazyLex
ROM OS Version: 5.1.x Lollipop
ROM Firmware Required: ZUK Z1
Based On: TWRP
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2015-11-09
Created 2015-11-11
Last Updated 2016-01-17
https://youtu.be/z5U5QIEbWtI
Version 2.0: TWRP image is now running with the Chroma Kernel as it's kernel. Reduces heat output and battery consumption of the device, added a new splashscreen too.
Version 1.3: Fixed zips not flashing on the international variant due to mismatched .prop files.
Version 1.2: Fixed version 1.1's compilation error causing it not to flash to recovery partition properly, could only be used tethered to PC.
Version 1.1: Fixed E: A render request has failed which was caused by a miss-written UI XML
Version 1.0: First working version of TWRP for Z1
Please be aware if you are running the official Cyanogen OS image OTAs will not apply automatically, you will need to install the incremental ZIPs posted by Titokhan in the "How to root ZUK Z1" thread in the Help and Troubleshooting forum. They will be on your device if you have downloaded the system update but I am yet to find this directory. If anyone finds the download location please post below and test if they will apply.
I am very aware you can't install OTA updates due to the device ID mismatching. I just posted a solution in the Android Development thread HERE credit to Radii for helping me out while working on this with him. Drop us a thanks for our hard work? Means a lot to use you know Each one counts!
Mad props for this!
Gesendet von meinem Redmi Note 2 mit Tapatalk
Hi Breadcrust, thanks for your wonderful work.
One doubt regarding Android 6.0 update, i saw a post on Internet about ZUK Z1 getting Marshmallow update and many users confirming it.
here is the link to this post explaining about updating procedure...http://apkmod4dl.com/howt-to/lenovo-zuk-z1.html
Can you confirm that it is working ? is Android 6.0 available for ZUK that soon ?
My ZUK is on my way, i am super excited to try new update with your recovery... Pls confirm it. Thanks in advance.
plikmuny said:
Hi Breadcrust, thanks for your wonderful work.
One doubt regarding Android 6.0 update, i saw a post on Internet about ZUK Z1 getting Marshmallow update and many users confirming it.
here is the link to this post explaining about updating procedure...http://apkmod4dl.com/howt-to/lenovo-zuk-z1.html
Can you confirm that it is working ? is Android 6.0 available for ZUK that soon ?
My ZUK is on my way, i am super excited to try new update with your recovery... Pls confirm it. Thanks in advance.
Click to expand...
Click to collapse
I'll be honest that post looks like a load of bollocks. The Android 6.0 source hasn't been released yet. Wait for Cyanogen 13 don't jump the gun and brick your phone.
Sent from my Z1 using Tapatalk
This recovery is useless
Cannot flash ZIP with CyanogenMod:
cm-12.1-YOG4PAS2WM-ham-signed.zip
Error appears.
LethalOne said:
This recovery is useless
Cannot flash ZIP with CyanogenMod:
cm-12.1-YOG4PAS2WM-ham-signed.zip
Error appears.
Click to expand...
Click to collapse
Worked for everyone else mate. You can't flash incremental OTAs over ZUI ROMs
It would also help if you told me the error instead of just saying it doesn't work. Especially considering other people have no issues.
Sent from my Z1 using Tapatalk
Ah. Thanks for info.
But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.
LethalOne said:
Ah. Thanks for info.
But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.
Click to expand...
Click to collapse
It will flash any ZIP just like any other TWRP it has not been modified in any way. If it will not flash I think there is an error with the ZIP or its user error
LethalOne said:
Ah. Thanks for info.
But me and many people need TWRP that will flash CyanogenMod ZIPs. Because it will make flashing ROMs faster. I have way to flash CM to chinsese ZUI Z1 but if you made TWRP that flashes the CM ZIPs it will all be faster.
Click to expand...
Click to collapse
Sent from my Z1 using Tapatalk
Android 6.0 source code is released 2 days back already. source: cnx/software.com
i think it takes more time for CM 13 Rom for ZUK Z1...
I found that out off my Dad when I got home, looks dodgy though.
It is dodgy and might be just a themed CM. We have to wait for the kernel source to come up first and then we can think about porting an AOSP. We must wait for an official CM though.
Thanks a lot for your work!!
.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c flash recovery temp\z1.twrp.2.8.7.0.By.Breadcrust-UPDATE2.img
target reported max download size of 1610612736 bytes
sending 'recovery' (8686 KB)...
OKAY [ 0.268s]
writing 'recovery'...
FAILED (remote: Invalid data)
finished. total time: 0.385s
Click to expand...
Click to collapse
.\Android\android-sdk\platform-tools>fastboot -i 0x2b4c boot temp\z1.twrp.2.8.7.0.By.Breadcrust-UPDATE2.img
downloading 'boot.img'...
OKAY [ 0.309s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.313s
Click to expand...
Click to collapse
Both failed... in bootloader mode (penguin logo). Any idea?
Maybe it's because I've updated to ZUI 1.0.062. with OTA...
mk1129 said:
Thanks a lot for your work!!
Both failed... in bootloader mode (penguin logo). Any idea?
Maybe it's because I've updated to ZUI 1.0.062. with OTA...
Click to expand...
Click to collapse
Most likely an issue to do with ZUI I was working through some installation issues with someone the other night and when we got it working it was through booting the image instead of flashing due to the broken boot loader switch in CM. So I'd bet its the OS stopping you.
Sent from my Z1 using Tapatalk
Breadcrust said:
There is a known issue with this where it will fill the log with "E: A render request has failed". I do not believe this stops the recovery from working and I will be looking into the issue. If you notice any bugs please report them below.
FAQ
Q: Does this work for ZUI devices? A: No, I don't think so. You're welcome to test it and report back but so far I have only tested it with Cyanogen OS
Q: What can I get with this I can't with Cyanogen OS Recovery? A: You can flash unsigned ZIPs such as SuperSU or Xposed (Although I don't recommend doing this as I put my phone into a bootloop installing Xposed)
What will I need?
First off you are going to need ADB and Fastboot, these can be aquired by downloading THIS for your OS, you do not need Android Studio you only need SDK tools. Once installed open Android SDK Manager and download platform-tools. You can untick everything else.
Now here is the tricky part, the part I had issues with. If you have a ZUI device you can install the ShenQi USB driver which is located on a partition of your phone which should mount as a CD when connected via USB, if you're running Cyanogen OS and your phone isn't mounted properly in Device Manager (Windows) then you can use the Google USB Driver ZIP, if it will not let you. Say for example if returns an error claiming the best driver is already installed. Then open the spoiler below if not continue on.
If Windows is giving you an error claiming the best driver is already installed right click Z1 or whatever it is named in Device Manager and click Update Driver.
Then click "Browse my computer for driver software" then click "Have disk" once you have done this browse to the extracted USB driver and open the .inf file it will show you three options select ADB device (Top one). Click yes to any warning and it should be mounted!
Next step is to check your device is mounted for ADB, open CMD and CD to the platform-tools folder in your Android SDK directory. Then type
Code:
adb devices
It will start the ADB Deamon and it should show your phone. If not, then it's probably because you haven't enabled ADB in Android, do this by going into Settings>About Phone and spam pressing build number until it says you are a developer. Then go back and in Developer Options enable ADB, you should get an RSA Authentication prompt on your phone. Click yes and type.
Code:
adb devices
You will also need to download the TWRP image from the spoiler below.
Download
Android File Host for Z1 TWRP V1.2 - DOWNLOAD LINK
Android File Host MD5 for V1.2 = 3b6fa140737b769f838169e997f58975
Android File Host for Z1 TWRP V1.1 - DOWNLOAD LINK
Android File Host MD5 for V1.1 = 596816b87a45d78bed4063ac62fac137 - Compiling issue, uploaded without thorough test.
Android File Host for Z1 TWRP V1.0 - DOWNLOAD LINK
Android File Host MD5 for V1.0 = 62b72d5129591d6759bb1917868594f4 - Outdated, filled with bugs.
If you have all the files downloaded and your phone has appeared in ADB then you are ready to flash!
Guide
Type:
Code:
adb reboot bootloader
You phone should reboot and boot into bootloader mode. Now because the ZUK Z1 isn't recognised as a fastboot device you will have to specify the OEM id. It is 0x2b4c meaning any fastboot command MUST be suffixed with
Code:
-i 0x2b4c
.
Next you need to check if the bootloader is unlocked, if you followed the "Convert Z1 from ZukUI to Cyanogen OS" guide HERE then it should already be unlocked.
To check type:
Code:
fastboot -i 0x2b4c oem get-device-info
If it returns:
Then you are ready to begin the flashing process.
Move the downloaded file to your platform tools folder and type:
Code:
fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE1.img
If fastboot returns "OKAY" then you can reboot your phone! To get into recovery and begin flashing ZIPs turn off your phone and then turn it back on. When it vibrates press and hold both Volume Up AND Volume Down until it boots into TWRP.
Click to expand...
Click to collapse
Not working for me. Mine struck at infinite when I type get bootlock info..... I have to reboot my phone.
Mine came with CM 12.1. When I skip this step and go straight away to flash custom recovery, it says flashing failed, device locked!!!
But I have already enabled OEM bootloader unlock option and I am sure that bootloader already unlocked and enabled for tweaking. What should I do now?
I have all the drivers installed and I reinstalled twice just incase... But no help.
Anyone guide me on how to successfully flash custom recovery and root my device?
Thanks in advance
plikmuny said:
Not working for me. Mine struck at infinite when I type get bootlock info..... I have to reboot my phone.
Mine came with CM 12.1. When I skip this step and go straight away to flash custom recovery, it says flashing failed, device locked!!!
But I have already enabled OEM bootloader unlock option and I am sure that bootloader already unlocked and enabled for tweaking. What should I do now?
I have all the drivers installed and I reinstalled twice just incase... But no help.
Anyone guide me on how to successfully flash custom recovery and root my device?
Thanks in advance
Click to expand...
Click to collapse
Any fastboot errors are caused by the device as fastboot will never stop you flashing an image even if it's not supposed to be flashed like flashing recovery to system. Open a thread and appeal there I unfortunately can't help on that front. People do seem to be having issues with the international device I am starting to think it's different in someway for the Chinese one. Maybe the USB id is different.
Sent from my Z1 using Tapatalk
Breadcrust said:
Any fastboot errors are caused by the device as fastboot will never stop you flashing an image even if it's not supposed to be flashed like flashing recovery to system. Open a thread and appeal there I unfortunately can't help on that front. People do seem to be having issues with the international device I am starting to think it's different in someway for the Chinese one. Maybe the USB id is different.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Thanks for your Kind reply. How do i find out what my Device ID is ? I mean, how did you come to know that the device ID of Chinese ZUK Z1 is 0x2b4c ?
Sorry for being noob.
plikmuny said:
Thanks for your Kind reply. How do i find out what my Device ID is ? I mean, how did you come to know that the device ID of Chinese ZUK Z1 is 0x2b4c ?
Sorry for being noob.
Click to expand...
Click to collapse
Paul O'Brien at MoDaCo found it
Sent from my Z1 using Tapatalk
Breadcrust said:
Paul O'Brien at MoDaCo found it
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Can you tell me what it shows when you type adb devices ?
i am curious... that might help me with my Problem.
Thanks in advance.
plikmuny said:
Can you tell me what it shows when you type adb devices ?
i am curious... that might help me with my Problem.
Thanks in advance.
Click to expand...
Click to collapse
D:\AndroidSDK\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
c783ecb7 device
Hello,
I have bricked X520. I read tutorials on xda but I have one big problem.
Phone is recognized as QLoader 9008 and this OK but when I trying flash it - it's fail
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
w QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
w QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
Please help me wit this problem
Download le x526 sparse images, use flashone tool to flash the sparse files
shivam321998 said:
Download le x526 sparse images, use flashone tool to flash the sparse files
Click to expand...
Click to collapse
I did it. I used Flashone. I used QFIL.
Still fail
Dzeezy said:
I did it. I used Flashone. I used QFIL.
Still fail
Click to expand...
Click to collapse
Download latest QPST, open the bin folder after installing, open download.exe, click on multi-image tab and select the sparse folder and try flashing with combinations which work
shivam321998 said:
Download latest QPST, open the bin folder after installing, open download.exe, click on multi-image tab and select the sparse folder and try flashing with combinations which work
Click to expand...
Click to collapse
not working etheir
@qfil
I recorded a video what I did
https://youtu.be/vOEGTNSBHg0
Dzeezy said:
not working etheir
@qfil
I recorded a video what I did
https://youtu.be/vOEGTNSBHg0
Click to expand...
Click to collapse
Use this version
https://androiddatahost.com/jj9ye
Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment blankflash.zip
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment FastBootAddOnFiles.zip
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Does it work for the power of Moto g7?
Anyway this works on unlocked g7? I need a blank flash or something to revive my hard bricked device
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
"Waiting for device"
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
mrufino said:
Hi WinnieH.
First off, i would like to thank you for explaining the necessity of the blankflash to recover the bootloader.
But when i try the steps you suggested, nothing happens. I get stuck in the message "Waiting for device..."
I noticed that the main command in the bat file is just: ".\qboot.exe blank-flash %*".
Wouldn't be necessary a reference to the singleimage.bin file in this command? Or maybe is a file missing in the zip.
I appreciate some suggestion.
Thanks,
Marcos
Click to expand...
Click to collapse
Sorry for late response.
if the message "Waiting for device ..." comes, then your phone is not recognized correctly. Your device when bricked should connect in Emergency Download (EDL) mode. You could see this when you go to the Windows Device Manager. Under the COM devices your phone should show up with the Qualcomm. If not, disconnect the phone for a minute and try it again.
If you have the driver not installed it, the installation video might help: https://www.youtube.com/watch?v=ezQJlBKN9hk
PS: The blank-flash.bat is fine. It will automatically use the singleimage.bin file
Hope you get your way
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
mrufino said:
Thank you WinnieH for the response. (that was not late at all!).
I will try to install the driver; I was unable to connect in Emergency Download Mode.
Click to expand...
Click to collapse
Well, first of all thanks to WinnieH for this useful thread. It worked fine for my phone.
@mrufino Maybe you have to install the moto drivers. Or try a different pc. The phone was not detected on my first pc, on my other pc it was detected immediately.
WinnieH said:
Recently by accident I downgraded the operating system on my Moto G7 Plus device (XT1965-3) and hard bricked my phone. :crying:
It took me some days on checking different threads to come to a solution. I managed to create a blankflash file that finally recovered my bootloader so that I could get into fastboot mode and flash the latest OS.
For those who are faced with the same problem, I'd like to share my solution and hope it works for you as well.
When the phone is hard bricked, it do not boot, it stays in black screen. The good thing though is that by default it goes into Qualcomms EDL (Emergency DownLoad) mode.
When connecting your phone to the PC (e.g. Windows 10) you should see in the device manager under COM the following device:
Qualcomm HS-USB QDLoader 9008 (COM..)
If this do not show up, unplug the phone, press Power + VolumeDown for about 30 seconds and connect the device again.
If it still not works, you might search for the correct drivers.
Assuming you see the device as mentioned above, then you can do the blankflash.
Open a cmd window (ideally with Administrator rights)
Unzip the blankflash.zip View attachment 4810965
Run blank-flash.bat
This should download the bootloader and your phone should get back to live (in fastboot mode)
After you have fixed the bootloader you can flash the latest OS with fastboot mode.
Download the latest version from: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Unzip the ROM and add the following files to the same directory View attachment 4810964
Connect the phone in fastboot mode
Run flashfile.bat from a cmd window
Now the ROM is flashed to the phone
Hope this helps recovering your phone!
Click to expand...
Click to collapse
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
diegovmsouza said:
Great post. Where did you find the singleimage for your phone? i've tryed to do with my G7 RIVER bricked, but unsuccessful need some help!
Click to expand...
Click to collapse
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
WinnieH said:
Hello,
I did the image by myself. I used a older image of a G6 device and replace a number of elements in the image from the stockrom. With "star" you can delete and add files to the "singleimage.bin" archive. It took me some trials. Check on the latest STOCK ROM "XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" from https://mirrors.lolinet.com/firmware/moto/lake/official/RETEU/ and you should find the most important files (such as partition table: gpt.bin).
Hope it works for you
Regards
Winnie
Click to expand...
Click to collapse
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
WinnieH said:
Just use "star list bootloader.img" and you get all the relevant file.
Code:
star list ..\..\XT1965-3_LAKE_RETEU_9.0_PPWS29.98-111-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\bootloader.img
1 339968 md5:e4c77bb1f8862444bedb908067d5063d abl.elf
2 519296 md5:4b8eaa75b77eae4981604f7893bf7279 cmnlib.mbn
3 519296 md5:ac35656340c5f87037a64ce4f937b16c cmnlib64.mbn
4 2722 md5:d3ee34bff4d352a045b7e42b447666a7 default.xml
5 126080 md5:4590a7b21b0d70d4403fa95ad23a6e9d devcfg.mbn
6 38400 md5:27ba16d71e0d16c86423192d5615a25c gpt.bin
7 519296 md5:0582b648798303e0441930fd84a39b9a hyp.mbn
8 519296 md5:2686fd49e16e78a0e9ef2335104e96bc keymaster.mbn
9 125 md5:c3a63b25166c5fcac0cc1426bf44a271 pkg.xml
10 519296 md5:1437d90bab43816d4a3541b18edac61c pmic.elf
11 257152 md5:5e3b6f2cf09747bd3bac33023c2014a7 prov64.mbn
12 519296 md5:31ab4015a996f2ad6dd61c94076fea98 rpm.mbn
13 126080 md5:5054d3c7863d09d6333c509003548e4d storsec.mbn
14 2092160 md5:44a6f561bab5d2822066574e3d0116eb tz.mbn
15 3665024 md5:a2a5945cf2ae44cd95da3ee180480662 xbl.elf
16 172 md5:1fd033214e7e36c4134a927f1ce944f0 index.xml
17 606400 md5:4b6e1345d3fb9b347ce7fc6357def85a programmer.elf
Extract the files from the bootloader and replace them on the singleimage.bin and thats it.
e.g.
Code:
star delete abl.elf
star add abl.elf
Pressing thumbs
Click to expand...
Click to collapse
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
diegovmsouza said:
thanks for listening. When I list the bootloader.iso file it returns me the following error: "Failed: simg_open () -> IO error". already extract the rom stock again, already downloaded it from scratch and the result is the same. When I extract the bootloader.iso file the same error occurs. what could it be? Can you help me extract these files? I am attaching the bootloader file of moto g7 river, if you can help me I will be immensely grateful.
Click to expand...
Click to collapse
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
WinnieH said:
Hello,
you are right. I should have written down how I created the singleimage.bin file. I replaced the following files in the singleimage.bin from the river stock rom version: XT1962-6_RIVER_RETEU_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (loaded from: https://mirrors.lolinet.com/firmware/moto/river/official/RETEU/)
gpt.bin
And changed the index.xml to the right CPU 632
You might to play around with the board id if it do not work (board id="204"). I hope the programmer file is the same for the G7 (processor type is slightly different: Snapdragon 632 instead of 636).
Give it a try with attached blankflashRiver.zip
Click to expand...
Click to collapse
Thanks for the help. the Programmer file isn't the same. After to work arround and beat my head over and over on the wall, I've took my phone to an authorized Motorola. For my surprise, as my phone shows oem_lock, they accepted on warranty. LOL. Now it's on repair and I'll catch tomorrow or another. Thanks for all. Thumbs up!
Rooting with patch security agost 2019
Hello
does this method work for the security patch of august 1, 2019?
does it works in moto g7 power? or others ways that qualcomm port not send error
I tryed in windows 7x64,10x64 without response, it shows me an error port just every time, qualcom usb drivers are shows correct ,
I cant continues with the fastboot part, people any advice?
diegovmsouza said:
Thanks for the answer. Trying to use "Star" I noticed that the files that are inside singleimage.bin are actually files that are inside bootloader.img right? How do I extract the bootloader.img file to use his files? I use linux but I have windows too.
Click to expand...
Click to collapse
Greetings Winnieh !, thanks for all the time and good information that you post,
I have doubts I would appreciate some advice, I have a motorola g7 power (ocean) tha's in hardbrick mode, I have already installed the correct qualcom drivers, the com port recognizes my device, but I cannot get the file blankflash.bat to load the phone to the moment executing it gives me an error:
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM3
[ 0.003] Detecting device
[ 2.218] ReadFile() failed, GetLastError()=0
[ 11.019] ERROR: sahara_greet_device()->device_open()->error opening device
[ 11.019] Check qboot_log.txt for more details
[ 11.019] Total time: 11.019s
FAILED: qb_flash_singleimage()->sahara_greet_device()->device_open()->error open
ing device
I realize that the blankflash.bat for the motog7 + version (river)
based on the blankflash file that you attached
I extracted the bootloader.img files from the stockrom of the motog7 power (ocean) XT1955-2 XT1955-2_OCEAN_AMX_9.0_PPO29.80-79_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml , so also delete and add all the files to the singleimpt.bin file - the gpt.bin file from stock rom copy and replace the one I saw in singleimage.bin
what you notice that index.xml refers to as "cpu.name: msm8953"
it also appears the same in the gpt.bin file, finally with the new singleimage.bin file compiled try to run the blankflash.bat again
unsuccessfully....
Could you tell me what are the mistakes that I can't solve?
i'm not a programmer just a bad lucky pal. if by chance have you a blankflash.bat for ocean version?, i'll really appreciate
Thank you! for your time
Hi WinnieH, I have a similar problem with a Moto G7 Power, can you tell me how I can create a blankflash for my specific model?
Lupask said:
is it possible to restore previously unlocked phone to out-of-the-box software and behaviour? specifically I would like to get rid of the bootloader warning and verity disabled message at boot. I wouldn't mind locking again
Click to expand...
Click to collapse
I have this exact same situation. did you find a solution to it?
Finally UNBRICK NUBIA Z20 in QDL MODE.
1. Extract Required Files from Original ROM:
abl.elf
xbl.elf xbl
config.elf
tz.mbn
2 Create a folder and paste the Rom files and the two downloaded files. (firehose)
DOWNLOAD:
https://drive.google.com/file/d/1zlwKSX_MKK1b2QtTTSrIgzmUCrt9LcYg/view
3 Download an active version of Qfil and follow the video.
Here is the video demonstration of the processes:
https://drive.google.com/folderview?id=1inlHKYyh4V3O23iRjG-yauLfCxplCjTJ
VIDEO:
<Mod edit: Link removed>
4 Upon completion press the Power, volume down and volume up buttons for 15 seconds.
Voalaaaa.
note when using what qfil turn off the computer wifi.
This apply only if he has flashed a rom via twrp or via fastboot... but with reformated phone , messed up partition table and maybe wrong LUNs .... will not do the trick.
credits to friend: @demonical
I'm do mad I send it for repair now, I still don't know how you guys found those firehose file
RomanLeFrais said:
I'm do mad I send it for repair now, I still don't know how you guys found those firehose file
Click to expand...
Click to collapse
i can see that the programmer for the sdm855 and sdm855+ are the same (the firehose)
justo download that file , and with QFIL from tools -> partition manager , restore the abl.elf xbl.elf xbl_config.elf and tz.mbn from orginal rom!
Broken links.
All the links are broken.
Cheako said:
All the links are broken.
Click to expand...
Click to collapse
OK NOW
This looks suspicious! Looks like it's a violation of the GPL, files the size of boot.img and rescue.img are encrypted. The included executable is also obfuscated.
Cheako said:
This looks suspicious! Looks like it's a violation of the GPL, files the size of boot.img and rescue.img are encrypted. The included executable is also obfuscated.
Click to expand...
Click to collapse
theese are the orignal issued by ZTE - NUBIA files.....
P.P. where did you saw a boot.img or rescue.img .? in the post or archive there is none of them?!
demonical said:
theese are the orignal issued by ZTE - NUBIA files.....
P.P. where did you saw a boot.img or rescue.img .? in the post or archive there is none of them?!
Click to expand...
Click to collapse
In order to get around being a violation things like this should contain a script that pulls the offending content from ZTE. Failing that links to where these "original" files come from would be an olive branch. As is, it's illegal to distribute these files.
They are published publicly by nubia.
demonical said:
P.P. where did you saw a boot.img or rescue.img .? in the post or archive there is none of them?!
Click to expand...
Click to collapse
Identified by size. Assuming some form of encryption... A violation of the GPL unless you share the private keys used to construct the image.
Can someone please walk me through this? i accidentally booted with no os.
Lusorocaba said:
Finally UNBRICK NUBIA Z20 in QDL MODE.
I just need a walkthrough please my phone is corrupted and wont boot for anything just only goes to edl mode and i need help installing things and getting the right files.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nubia-z20/how-to/tool-nubia-z20-unbirck-tool-t4009227
This works in "boot the edload" mode
Please i need firehose file for nubia z20. My phone is blank. Nothing shows on the screen, but my pc somehow detects it as "Qualcomm HSD QD Loader 9008". I want to try QFIL. Please any other suggestions on how to solve this would be appreciated.
how i Download an active version of Qfil
[email protected] said:
Please i need firehose file for nubia z20. My phone is blank. Nothing shows on the screen, but my pc somehow detects it as "Qualcomm HSD QD Loader 9008". I want to try QFIL. Please any other suggestions on how to solve this would be appreciated.
Click to expand...
Click to collapse
There's a tutorial on this forum.
Lusorocaba said:
Finally UNBRICK NUBIA Z20 in QDL MODE.
1. Extract Required Files from Original ROM:
abl.elf
xbl.elf xbl
config.elf
tz.mbn
2 Create a folder and paste the Rom files and the two downloaded files. (firehose)
DOWNLOAD:
https://drive.google.com/file/d/1zlwKSX_MKK1b2QtTTSrIgzmUCrt9LcYg/view
3 Download an active version of Qfil and follow the video.
Here is the video demonstration of the processes:
https://drive.google.com/folderview?id=1inlHKYyh4V3O23iRjG-yauLfCxplCjTJ
VIDEO:
<Mod edit: Link removed>
4 Upon completion press the Power, volume down and volume up buttons for 15 seconds.
Voalaaaa.
note when using what qfil turn off the computer wifi.
This apply only if he has flashed a rom via twrp or via fastboot... but with reformated phone , messed up partition table and maybe wrong LUNs .... will not do the trick.
credits to friend: @demonical
Click to expand...
Click to collapse
Unable to find anything in links. Please help