No OS Installed! Message After LineageOS 15.1 Flash - Moto X4 Questions & Answers

Hi All,
I've run into an issue whilst trying to flash LOS 15.1 on a Moto x4 (XT1900-01). After flashing LOS 15.01, I get the message "No OS Installed! Are you sure you wish to reboot?" for every Reboot menu option available in TWRP (3.2.3-1) (reboot options from Reboot menu: System, Recovery, Bootloader, Slot A, Slot B). I'm not sure what happened. Here are the steps I took prior to hitting this:
1. Unlocked the bootloader
2. Flashed TWRP per the instruction on TWRP for Payton on TWRP site
2-1. fastboot boot twrp-3.2.1-1.img
2-2. adb push twrp-3.2.1.zip /sdcard
2-3. Installed the twrp-3.2.1.zip from TWRP (apparently to install to boot partition on both slots)
3. Installed LOS 15.01:
3-1. Formatted via TWRP by doing Wipe -> Format Data
3-2. Advanced Wipe via TWRP by doing Advanced Wipe -> Select System
3-3. copied LOS to sdcard: adb push Lineage15.zip /sdcard
3-4. TWRP Install by Install -> select the Lineage15.zip
4. Once complete, select reboot and this is where the message "No OS Installed! Are you sure you wish to reboot?" comes up.
I haven't opted to reboot for fear of not being able to get back to recovery. I'm not sure what to do at this point. I'd like to understand what happened, but I would also like to find a way to recover from this and either get back to square 1 with stock ROM or even better complete the LOS install. Thanks in advance!

Just reboot recovery

St.Noigel said:
Just reboot recovery
Click to expand...
Click to collapse
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?

mikeybravo said:
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
Click to expand...
Click to collapse
Did you try to connect phone to the PC? Is phone charged?

St.Noigel said:
Did you try to connect phone to the PC? Is phone charged?
Click to expand...
Click to collapse
Yes, phone was at about 98 percent when doing reboot. Plugged into computer (Mac), adb devices returns nothing. Not sure how this could've gone as bad as it seems it did? Not sure of anything else I can try here...

have you access to Windows or Linux PC? I know nothing about Mac... (

St.Noigel said:
have you access to Windows or Linux PC? I know nothing about Mac... (
Click to expand...
Click to collapse
Yes, I plugged into both Mac and PC. MDM installed on PC as well adb tooling. Plugging into either computer does nothing, doesn't show up in device list. Tried the key combos while connected to each (vol up + power, vol down + power, power, power + vol up + vol down all for a couple/few minutes each). What I don't understand is what the heck happened. TWRP should've been flashed to boot on both slots based on TWRP docs for Payton. I read something about some issues with A/B slot switching (or not switching), but if TWRP was flashed to boot on both slots, I would've expected to at least be able to get back to recovery? I'm not really sure what to do from here since I can't even get the phone to turn on.

I have had seen that message on my phone too. I just reboot and it works just fine.

I ran into the same problem. I managed to fix my phone. From what I understand this happens if no OTA update was flashed before to initialize the partition structure in slot B. Check out [1] which suggests to install copy-partitions-payton.zip via sideloading it into TWRP before installing Linageos.
Concerning your brick: Your phone should still be recognized by your computer. Check the device manager or lsusb on Linux. For me I got something like "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". Reading through the threads [2,3,4] it became clear to me that I needed a "blankflash" or the qboot utility to recover the phone. The utility talks to the phone via a serial interface over USB. Look through the threads to find the qboot utility. I needed many tries to find the correct qboot utility and to get it to successfully blankflash my phone. The --debug=2 command-line switch of qboot helped me to get confidence that something is happening at all. I needed to press vol+ and power before starting the qboot utility with "./qboot blank-flash --debug=2" on Linux. I think it was also necessary to then _not_ hold these buttons for too long. As I said the debug outputs help to figure this out. Good Luck!
[1] https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
[2] https://www.reddit.com/r/LineageOS/comments/9yahhc/i_hardbricked_my_new_phone_looking_for_advice/
[3] https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
[4] https://forum.xda-developers.com/moto-x4/help/q-howto-x4-to-los-setup-bricked-t3883645

@macin42, thanks for the info on this. It makes sense, and I will give it a go. I'll follow up with the outcome as soon as I do; planning by the end of the weekend to give it a go.

@macin42, your instructions worked perfectly! Thanks so much for the help on this. As a recap on the issue: the problem for me was that I skipped the "Copy Partitions" step as it was a new phone and the phone hadn't received any "first" OTA updates. This step was necessary and wasn't mentioned in the official LineageOS install instructions on the LineageOS site. This step was mentioned however on the XDA LineageOS install instructions.
To recover from this, I followed the instructions that were given as help above by doing the following:
1. Downloaded the blankflash.zip from link provided above
2. Installed the Motorola Device Manager drivers (already had)
3. Installed adb and fastboot (already had)
4. Plugged in phone to PC via USB
5. Ran the following command while holding down the power up + volume buttons: qboot blank-flash --debug=2
NOTE: The qboot command didn't work for me the first time, but I re-tried a couple of times and it ended up working after the second or third try.
6. Once this completed the phone turned on and made it to the bootloader.
7. Once I made it here I was able to redo the steps that were given on the XDA thread to install LineageOS (post above), which were:
- Download the Copy Partitions zip from link above then:
- fastboot boot twrp.img
- adb sideload copy-partitions-payton.zip
- In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
- adb sideload lineageos-nightly.zip
- Navigate back to the Reboot menu in TWRP, select reboot, then select recovery, swipe to reboot. I did get the same "No OS installed" warning here but it wasn't an issue.
- This brought me to the LineageOS recovery.
- I chose to install Mind the GApps, so from the LineageOS recovery I selected Apply Update, Apply from ADB, then on computer adb sideload mind-gapps.zip
- Reboot
From here it was business as usual with the typical phone setup. Thanks again to those that helped on this!

Glad it worked out. In case your microphone and or sound does not work (silence in calls, recorder app does not work) please let me know - that's where i am currently stuck with my xt1900-7.

Related

[Q] Can I ADB pull media files from device? Help please!

Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didnt get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Solution
Attention: If you want your media files, backup your current state first. Go to backup and restore -> backup. Then do steps written below. Backup will be in CWM folder on your sdcard.
This is called a soft-brick. It's good that you can access download and recovery mode using 3 button combinations. First, download a stock Gingerbread ROM for your device model and put it on your sdcard. Boot into CWM and select Wipe user data -> Yes. Wipe Cache Partition -> Yes. Go to Advanced menu and select Wipe Dalvik cache -> Yes. Now return to previous menu and select install zip from sdcard -> choose zip from sdcard -> select name.of.downloaded.rom.zip -> Yes -> Wait 1-2 minutes to flash -> Wipe user data -> Wipe Cache Partition -> Wipe Dalvik Cache. Then select Reboot system now from main menu, and wait 4-5 minutes for it to boot first time.
DaniTheMan said:
Hey guys!
I've been having a lot of problems with a Samsung Galaxy S Plus recently. After my girlfriend entered the wrong picture password a number of times in a row, the phone locked down. I tried to activate data connection using the power menu (hold power button), which I had deactivated before it locked down. My attempts to log in failed when the device returned either 'invalid username' or 'invalid password' (they are - of course - neither). This is apparently a known problem. I then followed the following instructions to trick the device into thinking the google account had been verified: droidwiki .de/Muster_vergessen#Muster_l.C3.B6schen (warning, that site is in German). For this I successfully managed the following steps:
1.) Installation of ADB tools
2.) Installation of ClockwordMod using Odin in order to accomplish the ...
3.) Activation of USB debugging.
4.) Rooting the phone using these instructions: androiddrole .com/how-to/how-to-easily-root-samsung-galaxy-s-plus-i9001
All these steps worked as expected. Then however, the trouble started: When trying to set the number of failed pattern attempts to 0, the following command failed: "cd /data/data/com.android.providers.settings/databases" ("can't cd to /data/data/com.android.providers.settings/databases"). Additionally I could no longer boot into android as the phone kept booting directly into CWM (This is apparently also a known problem). I proceeded to install a newer version of ClockworkMod Touch (using zip on sd card) hoping this would allow me to break the loop. It didnt. So I replaced ClockwordMod with TeamWin Recovery Project (TWRP). This did finally allow me to exit the recovery mode only to get stuck in a full-out reboot loop: Samsung logo -> black screen -> Samsung logo -> black screen. In order to get out of this reboot loop I used Odin to flash boot_loader.tar and the original version of ClockwordMod onto the device. After a number of failed attempts this suddenly worked - kinda:
The current situation is this: The phone no longer boots directly into recovery mode (good). It doesnt boot into android either though. It just reboots over and over again - this can be stopped however by using 'Volume Down' + 'Home' + 'Power' to access ClockwordMod.
My hopes of getting my phone unlocked and working as before again are rather slim at this point. I would still like to save my substantial collection of photographs from the media folders on the device, before I wipe the entire thing (or buy a new phone).
Therefore my question to you:
Is it possible to extract the photos (stored in the standard media locations of android 2.3) to a PC using only USB-Debugging/Odin/ClockwordMod (being unable to boot into android)?
I tried to pull the media files using the 'adp pull' command, but I couldnt get it to work (maybe because I didn't get the command or the file-paths correctly). Any suggestions would be GREATLY appreciated.
Click to expand...
Click to collapse

[HELP] Android not booting [URGENT]

It's a bit urgent to get solved, I'm at college, and that's the only way to talk with my parents, being 1 or 2 days without answering them would be a problem, since they will start to get worried.
Phone: Motorola Moto G 2014, XT1063
Using Team Win Recovery Project v2.8.0.1
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
DIdn't understand why, but it f**ed up.
Basically I cleaned everything, and in an act of desperation I also lost my sdcard, I've been trying to install the ROM through sideload, but it's not working, I get the error *failed to write data protocol fault no status*, and the phone keeps rebooting, and stuck in the "WARNING BOOTLOADER UNLOCKED"
I appreciate any kind of help, as I said, it's really important to solve this ASAP.
Thanks in advance!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
gouzzz said:
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
Click to expand...
Click to collapse
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Doppel u r right. follow doppel steps.
doppelhelix said:
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Click to expand...
Click to collapse
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
gouzzz said:
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
Click to expand...
Click to collapse
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
gouzzz said:
EDIT: Now it doesn't charge, or something. I connected it to charge, but it keeps appearing 0% for more than 30 minutes, I can't even access the menu from "Volume Down + Power On"
Click to expand...
Click to collapse
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
doppelhelix said:
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
Click to expand...
Click to collapse
On the MOUNT and UNMOUNT processing I don't see anything on my PC, I don't even know how to unmount it. It only appears Enable MTP and disable.
How am I supposed to load the ROMS?
Tried with sideload but got an errror : "Error executing updater binary in zip .."
Seems like the drivers aren't working properly, I have Windows 8.1, on the site it doesn't talk about it, this might be the problem? Cause I instaled motorola device manager, I scan for drivers but it doens't find anything, and the phone apperas with the yellow triangle on the Device Manager.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
EDIT: I managed to boot the Titan 5.0.2, but now it's stuck in the 4 balls moving around, i waited for about 1hour.

[Resolved]Brick in TWRP by trying to install Elite ROM

Hey,
Here's the context: I tried to install Elite ROM.
In the instructions there was this: "Wipe Everything in wipe section (dont wipe sdcard) and Change FileSystem of DATA Partition only to f2fs & FORMAT Data otherwise phone wont boot".
I was in TWRP and followed instructions.
Wipe everything: OK
Change filesystem of data partition to f2fs: OK
Format the data partition: not OK. It said me
Code:
/data : Device or resource busy.
. I couldn't do anything from there, or I thought this way at least... I think the f2fs filesystem f*cked it.
First error: I rebooted my phone. So yeah, now I'm not in TWRP anymore. I tried to boot into Recovery but Vol Up + Power brought me to Huawei eRecovery. I tried the Huawei eRecovery but it didn't work. Expected, because I installed TWRP and apparently it doesn't work anymore when you flash it. So OK.
Basically I want to get into TWRP because I could maybe solve the problem from here. I don't know how to solve this Device or resource busy, but there is a solution, like always.
Now, there is a problem. When I do
Code:
adb devices
or
Code:
fastboot device
, I get nothing. BUT, something encouraging is that I have HiSuite that shows up when I connect my phone to the PC, everytime, even if I close it. But then, HiSuite tells me to connect my phone, so I think it doesn't recognize the phone fully. Maybe it recognizes some hardware in my phone that matches Huawei phones, but still not really recognizing my phone. My phone is not appearing on the device list of Windows, I just have a "USB Mass Storage Device" in the USB controllers.
UPADTE: I managed to go into TWRP by pressing Vol Up + Vol Down + Power, so no need of ADB for now. I'm updating. Below, only for informational purpose.
UPDATE 2: As I managed to boot to TWRP, I was able to format /data and to install Kernel & ROM from my SD card! To boot in TWRP and not eRecovery, make sure you're pressing Vol Up + Vol Down + Power and not only Vol Up + Power.
The goal is to force ADB to see the phone so I can interact with it
So for now I have several theories I tried to follow, without success:
- Forcing Debugging mode on my phone (maybe it's only that)
- Find a version of ADB that can see the phone
- Find drivers that can recognize the phone fully
An other way could be to backup the partitions saved before in TWRP. But as I can't access to TWRP without ADB on this phone, for now I don't believe this is a path to explore.
Have you any other theories, and have you solutions for these 3 majors theories?
Thank you so much and see you,
Celgost
[VolUP]+[Power] - This works if the phone is turned off. When the "data" is busy, you need to reboot into the recovery mode from the TWRP.
It's true but not totally in that case. If you aren't in TWRP anymore and wiped all partitions, you cant Access TWRP neither with ADB nor with Vol UP + Power. Because Huawei added eRecovery, which coexists with other recoveries. My theory is that eRecovery is one layer below regular recoveries. You Can Access twrp only with Vol UP + Vol Down+ Power. I suppose there is a strict condition to boot into erecovery when there is not for Twrp.
It works always, you just need to release the buttons, after the appearance of the logo.

Root Lenovo Tab 10 TB-X103F

Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the .img file (if not in the same folder):
fastboot boot TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!
Stock recovery remains
RooterLeopold said:
Root Lenovo Tab 10 TB-X103F (Tested)
1. activate developer options on the Tablet
2. enable Bootloader-Unlock on the Tablet
3. download and install ADB und fastboot
4. latest usb driver on your PC
5. download TWRP TWRP-3.0.2_TB-X103F-beta.img
https://forum.xda-developers.com/showpost.php?p=70228684&postcount=65
6. download SuperSu zip file
Steps:
1.) boot to fastboot -> shutdown your device -> press on/off + "+" Volumekey → device restarts to fastboot mode
2.) connect to your pc via usb cable
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
4.) do the unlocking
"fastboot oem unlock-go"
5.) boot TWRP image file in the command line, showing the pathway to the file:
TWRP-3.0.2_TB-X103F-beta.img
6.) Put SuperSu zip file in the device memory and flash SuperSu zip with TWRP, then restart the device. Done!!!!
Click to expand...
Click to collapse
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help
That's because the above only boots TWRP to root but does not install it. To install TWRP, when in booted with TWRP, you need to transfer the TWRP img to the tablet storage and then install it while in TWRP.
it is important to show the pathway to the file TWRP-3.0.2_TB-X103F-beta.img in the command line, like:
C:\Users\Public\Documents\My Videos\TWRP-3.0.2_TB-X103F-beta.img
Sorry for this newbie question.
Which part of the above rooting steps is rooting my tablet, what is TWRP doing and why do I need to install the SuperSU app?
During my first try I didn't boot the TWRP image rather I flashed it. But that didn't help at all.
After booting the TWRP image I was able to flash the SuperSU app.
The stock recovery is still in use.
Thanks in advance.
Read the steps carefully and follow the steps, it is a tested successfull strategy. To get deep knowlege about the background processes, please read the threads elsewhere in Web.
Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option
Entering Fastboot on Lenovo TB-X103F tablet
ShottaDopey said:
Yow how do you enter Fastboot on the tablet and i haved tied avery button on the tablet and i dont see the fastboot option
Click to expand...
Click to collapse
Hi everyone. I just want to clarify something about this procedure There's a lot of people being confused on how to get into FASTBOOT on some things, and that's stopping them getting anywhere from the beginning.
The Lenovo TB-X103F tablet doesn't have a way of booting directly into FASTBOOT. Turning the tablet On while holding either volume key and the On button doesn't do it directly. . . . . Firstly, there's 3 buttons on the tablet, I call them VOL- VOL+ PWR (again, that's just to clarify things 100%)
here's what must be done (well it's this way on the 3 I have on my desk, so I assume all TB-X103F tablets are the same) . . . . .
1) Turn the tablet off completely.
2) Press & hold the VOL+ button (the middle of the 3 buttons).
3) Press & hold the PWR button, release the PWR button as soon as anything appears on screen - Keep holding VOL+ button.
4) After about 8 seconds the familiar green android lay down will appear. Then, your recovery menu will appear.
5) Release the VOL+ button anytime now.
6) Press either VOL button to select BOOTLOADER on the menu (Bootloader is the same as FASTBOOT on this menu, that's where the confusion lies for many users).
7) Got Bootloader selected? now press PWR and let the tablet reboot itself.
8) it will show the LENOVO logo, and appear to be stuck - it isn't It's in Fastboot mode.
9) Plug in your USB to PC cable, and it'll install appropriate drivers on the PC (hopefully eh?).
10) Once the drivers are installed, test it by getting a Command Prompt in your ADB/FASTBOOT folder on your PC . . . .
11) type the command FASTBOOT DEVICES It should show you that your device is connected, if it shows no devices then either it didn't install the drivers, or something
else is wrong (there's about 30 things that can have gone wrong here, too many to go through in this quick guide).
12) The tablet will stay in FASTBOOT/BOOTLOADER mode until you turn it off (or the battery goes flat lol). So stay calm, there's no rush
I've mentioned about there being no rush, because if you choose ADB connecting from the recovery menu, it disconnects automatically after about 5 minutes -
This is Important to know because it can disconnect while you're pushing/pulling files from the tablet, and cause really nasty problems. Bad design eh?
But we're in Fastboot mode, so nothing to worry about like that
Deleted
Successful root
It was hard, but I had finally had done it. I had figured it out it is easier just to go to the command prompt (I ran it under admin) and "cd C:/adb" (where you installed the adb fastboot software) while having the TWRP image file being placed there. I only wished that I had done it sooner. And for those who are new to the custom recovery it can be overwealming, but with patience and going through the files in the file explorer to find your main storage would lead you to the SuperSU file and successfully root your device.
I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.
So I did the "fastboot oem unlock-go" command and adb said ok but my tablet just went to a black screen and won't turn on now and I'm not sure why. I also heard the Windows USB disconnect sound when i did it.
Would this work with the TB-X104F running 8.1?
Since a few months my tablet is stuck with the 'password changed, wait....' message. I had hoped that I could overcome this with the steps mentioned here. But unfortunately not
I can't start it anymore, so I'm not sure if it is in developers mode or not. Also, plugging the device in my mac didn't let it download the drivers.
Too bad, because when it was working it was a great tablet, now it's just a expensive drawer filler
SynGamer said:
I flashed TWRP...now what? I can't find any instructions on how to reboot into TWRP. I got into some sort of Chinese menu (PWR + VOL-) but I'm pretty sure this is the device test menu.
Click to expand...
Click to collapse
its the vol+ not - you need to press with the power button
Steridroid said:
I have done all the steps but For some reason twrp is not installed and i still have the stock recovery. Please help
Click to expand...
Click to collapse
so what exactly do i have to type at the command prompt to run twrp?,ive put the twrp img file in the same folder as the adb stuff.
3.) start command shell (cmd) in the fastboot instalation folder on your PC and check for the device connection with the command:
"fastboot devices"
fastboot shows notting
lenovo seems to have killed these tablets from the old lady next doors experience.. no wifi, no adb, no fastboot, no qualcomm, just unknown device, which loads NOTHING, no drivers work!!!

[GUIDE][Z2 FORCE XT1789-05] Bootloader/TWRP/Custom ROMs/Root/Dirty flashing/Unbrick

First, thanks to @Uzephi and @41rw4lk for helping me to use/recover my phone. Please, read and do not underestimate the guides: our phone is tricky! We have two system partitions (slot a and b) to allow stock updates on-the-fly. This complicates the normal flashing process and if you do not follow the steps, you may bootloop. Use these guides at your own risk!
Reading this page is a good beginning to understanding the A/B partitioning scheme and how Motorola Z2 Force works:
1) Our phone has A/B partitioning, so flashing Magisk/XPosed is different
2) It does not support Project Treble (faster stock updates)
3) It does not a recovery partition, so flashing TWRP is different
Note also that the RSD Lite from Motorola has issues with Windows 10 and you’ll need to manual flash firmware if you bootloop (see Process E below). Other way is directly flashing from Qualcomm EDL mode (Emergency Download Mode) from which users can perform various tasks like unbricking, unlock bootloader, and installation of any custom ROMs.
Right now, this guide has 5 parts (maybe we can dual boot our phone in the future). If you just want to use a rooted stock ROM, please, search for other guides here on xda. These guides were written (and tested) using a Motorola Z2 Force XT1789-05 phone (Brazil), although most of it should work for other variants if you download and use proper firmware files for these other phones. For other models, better if you follow Uzephi’s guide.
A. Opening bootloader
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
C. Flashing a custom AOSP ROM + rooting
D. Dirty flashing AOSP ROM updates
E. Recovering from bricks or returning to stock
F. Oreo ROM features comparison table
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
A. Opening bootloader
With enough battery in your phone (80%), you can follow the Motorola official guide which steps are:
1. Backup everything you need. Your phone will be reseted including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options, click the OEM unlock option to enable it. Also enable USB debugging.
3. Install the Motorola drivers in your computer, but (in my personal experience) not the Android SDK suggested in the official guide. Instead, extract these adb/fastboot files in a blank folder of your computer.
3.1) Do not use other adb/fastboot binaries: I cannot guarantee they will work.
3.2) You need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Open a command line window in the adb/fastboot folder (step 3), reboot the phone into the bootloader (see adb command below or press power + volume down buttons). Plug the phone on computer (see 3.2 above). Test the connection and run the command to get the code for unlocking:
Code:
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
You’ll get:
Code:
(bootloader) Unlock data:
(bootloader) <code 1>
(bootloader) <code 2>
(bootloader) <code 3>
(bootloader) <code 4>
(bootloader) <code 5>
5. You’ll need to join 5 codes and, after logging into your own Motorola account, check by clicking the button “Can my device be unlocked” (step 6) by Motorola here. Read the text: your warranty will be void if you go ahead. Consider if you have enough knowledge, time and money to deal with a troublesome (or bricked) device. Although, it’s not that easy to hard brick this phone (see process E below).
Code:
<code 1><code 2><code 3><code 4><code 5>
6. You’ll receive back an email with the code to unlock your bootloader (if it is available for your model). Then you’ll run the following command:
Code:
fastboot oem unlock <code 1><code 2><code 3><code 4><code 5>
7. You’ll receive a warning that all your data would be erased (see step 1 above) and need to re-run the same command to confirm. At this point, your bootloader should be unlocked. As an Android restriction, each time you boot the phone you’ll see a warning. Do nothing, wait for 5 seconds and the phone boots normally. Some users bother with this warning and try to get rid of it.
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
Requirements: unlocked bootloader (see guide A) and no security lock: disable PIN, gestures and fingerprinting (because TWRP cannot read the locked/cryptographed data of the phone). Enough battery in your phone (80%).
If you do not prepare your phone to custom ROMs and if you do not have both bootloaders of the phone in the same Android version of the ROM you’ll flash, you’ll hard brick the phone and lose also the access to the bootloader! You’ve been warned: follow the guide!
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool.
1. Backup everything you need. Your phone will be reset including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options and enable USB debugging.
3. Install the Motorola drivers and the adb/fastboot files.
3.1) do not use other adb/fastboot binaries: we cannot guarantee they will work.
3.2) you need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Download the firmware of the same Android major version of the future ROM you’ll install (Oreo for Oreo ROMs, for instance). When (and if) we move to Android P, most probably we will need to follow this guide again.
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
5. Extract the zip contents to a blank folder in your computer.
6. Download the FlashAll_XT1789-05.zip file, extract the content and move all files to the same firmware folder (step 5 above). Be sure to overwrite any file (if needed).
7. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
8. Reboot the phone into the bootloader (see adb command below or power + volume down buttons). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 7.
Code:
adb devices
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
9. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
10. Reboot your phone into the system (ROM) and do a quick configuration (remember that everything will be deleted when you install TWRP further…).
11. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging.
12. Download both the .img and .zip file of the TWRP recovery from the official site. It's the same file for all models/variants of Z2 Force phone. Put the files into our firmware folder (step 5 above). Copy the .zip file to the phone internal card. Note: versions older than 3.2.2-2 does not support PIN/Password/Fingerprint, so disable them before proceed. Most probably, ROMs before July 20th, 2018 cannot be flashed in older TWRP.
13. Now boot (not flash) the TWRP .img file using a command line window in the same firmware folder (step 5 above):
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot <TWRP file name>.img
14. Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone (step 12 above).
15. Reboot into TWRP (use the main reboot menu in TWRP).
16. Now, you should reboot again into bootloader: inside TWRP, go to Reboot menu and choose Bootloader.
17. Now you will wipe all user data via bootloader. This is necessary to use an AOSP ROM when you come from stock. Using a command line window in the same firmware folder of your computer (step 5 above), run the following commands:
Code:
fastboot devices
fastboot -w
18. Now you can reboot the phone into System using the buttons volume up/down to navigate and confirming with the Power button. You’ll be with stock ROM and TWRP. If you want to move to a custom AOSP ROM, do a quick configuration: into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging and go to the proper guide (Process C).
C. Flashing a custom AOSP ROM + rooting
1. Requirements:
1.1 Motorola drivers.
1.2 Our custom adb/fastboot files (others may not work!).
1.3 USB debugging enabled into the Developer Options.
1.4 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.5 An USB 2.0 port of your computer (some users report that USB 3.0 will also work).
1.6 Two Oreo bootloaders (process B above).
1.7 Permanent TWRP
1.8 Enough battery in your phone (80%).
2. Download the AOSP ROM you want and move the .zip files to the phone. Right now, we have:
2.1 Dirty Unicorns: no need for Gapps. Official and Weeklies can be dirty flashed interchangeably. RC has a different signature. Support on Google+ page. More about DU kernel.
2.2 Lineage OS 15.1. MindTheGapps needed. OpenGapps not compatible yet. XDA thread.
2.3 Mokee: Gapps needed. Take care: online guides assume that you already have an AOSP ROM, TWRP and rooted device.
Deprecated (?)
2.4 AOSiP: no need for Gapps. XDA thread.
2.5 Invictrix. Gapps are built in. XDA thread
3. Choose the root method and download the .zip files: Magisk (suggested) or LineageOS SU Addon. Move the .zip files to phone. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk or you did not reboot between flashing ROM/Gapps and Magisk. Note: SuperSu is deprecated.
4. Reboot into TWRP:
Code:
adb reboot recovery
Then flash the ROM. It will be flashed in two steps only in the “other” slot. We have two slots, A and B. Our phone can be upgraded on-the-fly because the update is always applied to the slot not booted, the “other” slot. Then, immediately, flash the .zip TWRP or you will lose it.
5. Go to Reboot menu of TWRP and reboot into bootloader. Then, in the folder with adb/fastboot binaries (see 1.2 above), you need to wipe data (including sdcard) with the following commands:
Code:
fastboot devices
fastboot -w
6. Now you need to reboot the phone into System using the buttons volume up/down and confirming with the Power button (or typing fastboot reboot into the command line windows). You’ll be with an AOSP ROM and TWRP.
7. Once into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging if you intend to dirty flash ROM updates.
8. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved). Note: if you bootloop on Magisk, remember it is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
9. A good place to read what is not working is in the section known problems of LineageOS.
D. Dirty flashing AOSP ROM updates
1. If you follow all the processes above, you can dirty flash updates because you have:
1.1 Motorola drivers installed.
1.2 Specific adb/fastboot files for our phone and an USB 2.0 port in a Windows computer (some users report that USB 3.0 will also work).
1.3 Unlocked bootloaders (Process A above).
1.4 Permanent TWRP running and TWRP .zip file placed inside your phone and ready to be flashed again.
1.5 An AOSP ROM already running.
1.6 Developer Options and USB debugging enabled.
1.7 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.8 Enough battery in your phone (80%)
2. Download your ROM .zip update, copy it into the phone sdcard and reboot your phone into TWRP. See download links here.
3. Within TWRP you should flash (install) things in the following order:
3.1 ROM update .zip file. Remember that, at this time, the update will be flashed int the other slot and inside phone you’ll have both the system before update (in the booted slot) and updated ROM in the other slot.
3.2 TWRP .zip file (step 1.4 above) once again (do not skip this step or you’ll bootloop!).
4. Reboot to System: if you skip this step, you’ll bootloop.
5. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved) or LineageOS SU Addon .zip file. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk. I suggest v16.0 and, after you got rooted with 16.0, you can update. It is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
Note: SuperSu is deprecated.
6. Wipe Dalvik/ART cache: go to Wipe menu of TWRP > Advanced Wipe > Dalvik/ART Cache only.
7. Reboot your phone into System (ROM) will use the “other” slot, the one with the updated ROM.
8. You can use XPosed installer app (and reboot).
9. Now you can add your PIN, fingerprint, gestures back until next flashing.
E. Recovering from soft bricks or returning to Stock
If you’re reading this is because you already unlock your bootloader (see guide A) and anything went wrong, but you still can boot your phone into bootloader. Plug your phone and get enough battery (even if you do not see any charging signal).
1. Install the Motorola drivers and the specific adb/fastboot files for our phone. Remember, follow the rules because our device is tricky!
1.1) Do not use other adb/fastboot binaries: we cannot guarantee they will work.
1.2) You need to use a USB 2.0 port of your computer (some users report that USB 3.0 will also work).
2. Download the latest firmware for your model:
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
3. Extract the zip contents to a blank folder in your computer.
4. Download the FlashAll_XT1789-05.zip file (it should work for other Motorola Z2 Force models as well), extract the content and move all files to the same firmware folder (step 2 above). Be sure to overwrite any file (if needed).
5. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
6. Reboot the phone into the bootloader (see adb command below or power + volume down). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 5.
Code:
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
7. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
8. Reboot your phone into system (ROM) and do not forget, later, to enable the Developer Options and USB debugging again.
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool. Maybe these Latest 2017 Qualcomm Diag QD-Loader Windows 10 Drivers signed will help you.
F. Oreo ROM features comparison
This is a table for Oreo ROM features comparison for Motorola Z2 Force - nash.
I would like to receive feedback and updates from the users, as I can't keep changing from one ROM to another and they get new features, updates, improvements, etc.
I consider Lineage OS 15.1 our stock ROM regarding to customization. So, it's not listed there.
Legend:
Code:
X = Feature present
XX = ROM excels in this particular feature (in my opinion).
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
renanjones said:
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
Click to expand...
Click to collapse
I see two possible scenarios:
1. Your bootloader is locked (yet) (see guide A).
2. Your in a "false locked" situation that, maybe, could be solved by resetting data via recovery or in bootloader (with the command: fastboot -w).
Great tutorial, but I did not get 4g in any of the roms, only 3g
Gutto said:
Great tutorial, but I did not get 4g in any of the roms, only 3g
Click to expand...
Click to collapse
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Technical said:
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Click to expand...
Click to collapse
My cell phone and Sprint, I did every process that you indicated, but not 4G
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
shalpp said:
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
Click to expand...
Click to collapse
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
41rw4lk said:
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
Click to expand...
Click to collapse
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
shalpp said:
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
Click to expand...
Click to collapse
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
41rw4lk said:
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
Click to expand...
Click to collapse
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
shalpp said:
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
Click to expand...
Click to collapse
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
41rw4lk said:
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
Click to expand...
Click to collapse
It appears as Qualcomm 9008
It only starts the loop after starting a blankflash. That's about the only response I get out of the device, otherwise it does absolutely nothing, no combination of buttons do anything
Edit: Confirmed connect/disconnect on another machine with the same driver configuration

Categories

Resources