Database Develop

[Q] HTC One M7 stuck in cyanogenmod loading screen/PC won't recognize the phone

Hi guys! I need help with my HTC One (M7)
I’m not sure what was the cause, non-HTC charger or something I did, but my HTC One is softbricked, stuck during the loading screen with cyanogenmod on it AND my PC won’t recognize the phone. I searched these forums, but nobody had quite the same issue as I do and nothing helps so far. Here’s a step-by-step list of what I did:
- I was given a phone with cyanogenmod installed and it worked well for a month
- I used two different chargers, neither of them original
- after a month, the phone started going into Car Mode from time to time, not letting me speak without speakerphone turned on
- in order to have it repaired, I decided to put back the original ROM on the device since it is still under warranty, which was void after the cyanogenmod was installed, but the process is reversible from what I gathered
- I followed instructions here (basically downloading SDK, HTC Sync Manager, locking bootloader and running the ROM update utility):
ok, so I can't share the link with you, but it's instructions for uninstalling cyanogenmod and installing stock sense rom at wonderhowto site. It can easily be found by searching "How to Uninstall CyanogenMod & Revert Back to Stock Sense on the HTC One"
- at step 8, i locked the bootloader as instructed
- when I tried to update the original ROM found in these forums, it didn’t work, possibly wrong ROM
- when I turn on the phone, cyanogenmod start-up screen keeps loading but never loads, but I can still access bootloader
- in the whole process, team win recovery project (TWRP) backup application was deinstalled from the phone because of the factory reset
- after unsuccessfully trying to install multiple stock ROMs (that should work with my phone according to their description), i decided to try to transfer ROM file onto the device and install it with TWRP
- i managed to unlock the bootloader and reinstall TWRP
- by that time, my PC stopped recognizing my phone. I can still charge it, but PC wont recognize it when in bootloader
- tried reinstalling drivers, tried other PCs, nothing
- friend had a similar problem (charging, but can’t be recognized) and his phone was swapped at the HTC store, but it won’t do me any good until I put back original ROM on it
So, my question is - is my problem still software related or am I beyond that? PC stopped recognizing my phone at the worst possible moment, so it got me wondering if it was something I did or was it just bad luck that it gave up in that one hour window when I was left with the phone with no functional software on it. I wouldn’t mind being stuck with a phone that can’t connect to PC and cyanogenmod on it, but now I have a phone that I can neither use nor turn in for repairs. Any help is much appreciated!

Slingshot12 said:
Hi guys! I need help with my HTC One (M7)
I’m not sure what was the cause, non-HTC charger or something I did, but my HTC One is softbricked, stuck during the loading screen with cyanogenmod on it AND my PC won’t recognize the phone. I searched these forums, but nobody had quite the same issue as I do and nothing helps so far. Here’s a step-by-step list of what I did:
- I was given a phone with cyanogenmod installed and it worked well for a month
- I used two different chargers, neither of them original
- after a month, the phone started going into Car Mode from time to time, not letting me speak without speakerphone turned on
- in order to have it repaired, I decided to put back the original ROM on the device since it is still under warranty, which was void after the cyanogenmod was installed, but the process is reversible from what I gathered
- I followed instructions here (basically downloading SDK, HTC Sync Manager, locking bootloader and running the ROM update utility):
ok, so I can't share the link with you, but it's instructions for uninstalling cyanogenmod and installing stock sense rom at wonderhowto site. It can easily be found by searching "How to Uninstall CyanogenMod & Revert Back to Stock Sense on the HTC One"
- at step 8, i locked the bootloader as instructed
- when I tried to update the original ROM found in these forums, it didn’t work, possibly wrong ROM
- when I turn on the phone, cyanogenmod start-up screen keeps loading but never loads, but I can still access bootloader
- in the whole process, team win recovery project (TWRP) backup application was deinstalled from the phone because of the factory reset
- after unsuccessfully trying to install multiple stock ROMs (that should work with my phone according to their description), i decided to try to transfer ROM file onto the device and install it with TWRP
- i managed to unlock the bootloader and reinstall TWRP
- by that time, my PC stopped recognizing my phone. I can still charge it, but PC wont recognize it when in bootloader
- tried reinstalling drivers, tried other PCs, nothing
- friend had a similar problem (charging, but can’t be recognized) and his phone was swapped at the HTC store, but it won’t do me any good until I put back original ROM on it
So, my question is - is my problem still software related or am I beyond that? PC stopped recognizing my phone at the worst possible moment, so it got me wondering if it was something I did or was it just bad luck that it gave up in that one hour window when I was left with the phone with no functional software on it. I wouldn’t mind being stuck with a phone that can’t connect to PC and cyanogenmod on it, but now I have a phone that I can neither use nor turn in for repairs. Any help is much appreciated!
Click to expand...
Click to collapse
Try to follow this guide by alray and put ARHD 84.0 or MaximusHD on the phone.
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone any ways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didn't install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Step by Step guide to unlock bootloader and root Huawei P8 lite ALE-21

After seeing lot of scams on rooting of this phone i wrote this little guide which can be used to unlock and root P8 lite ALE-21 without much effort successfully. Whenever i found something about rooting this device it took me to some survey scam or ad-wares. I used this method personally and it worked for me very well.
Below is step by step guide to root huawei p8 lite ALE-21.
A- Method for obtaining bootloader code is changed by huawei. Now you can get it online immediately by filling out their form. All you need is a huawei ID.
Request unlock code from huawei, to do so send email to [email protected] containing following lines.
In subject write bootloader unlock code request
body of email should contain
> IMEI-1: __________________________
> IMEI-2:__________________________
> S/No. _____________ (Can be found in settings/About phone/Status/Serial number)
Once you sent this email you need to wait from few hours to 48 hours.
B- Unlock boot loader on your device.
1- Download this zip file, unzip it and install in your PC (See attached pdf file).
2- Connect your phone via data cable to PC.
3- Switch it off and then by pressing volume down and power together make it in fastboot mode (in this mode you will see "Phone locked" in red color at bottom of screen)
4- Click icon on desktop for "Minimal ADB and Fastboot"
5- (A command terminal will open indicating directory where adb is installed)
6- Type in command without quotes "fastboot devices"
7- If you can see serial number of your phone you are going right.
8- In the command prompt, enter “fastboot oem unlock ****************”, where * refers to the 16 digit unlock password, e.g. fastboot oem unlock 1234567812345678”
9- Now you have unlocked bootloader, and you can see it on fastboot mode screen at bottom.
C- How to root P8 lite ALE-21
1- Download this zip file on your desktop and unzip it (see attached pdf file).
2- Open folder ROOT/data and install "UniversalAdb Driver Setup6"
3- Remove all passwords from phone and simple a swipe could unlock phone.
4- Now open folder named ROOT on your desktop and double click INSTALAR-ROOT-P8-LITE and follow instructions shown by batch file.
5- Once process is finished you will get a unlocked rooted huawei p8 lite phone.
I checked this procedure on my P8 lite ALE-21 and translated to English, also added more instructions to make it easier for a newbie.
UPDATE-1 : Root by using command line manually.
The root process is simple and achieved by adb and fastboot commands. See the attached screen shot for commands if you intend to do it manually. Make sure you have installed UniversalAdbDriverSetup6.msi from Root/data and unlocked bootloader before following steps below.
Instructions:
1- Connect phone with PC.
2- Open folder Root/data
3- Press Shift + Right click
4- Click “Open command window here”
5- Then execute commands in a sequence you can see in attached file "commandline.jpg"
UPDATE-2: Error Fix "Stuck on Installing SuperSu"
Very few users experienced that process get stuck on terminal displaying “Installing SuperSU” or copying SuperSU
Fix in my opinion: Restore stock recovery, boot in recovery and wipe cache partition and start the process again.
1- Remove data cable of phone and press power button (a bit longer) to restart it.
2- Connect phone with PC when you see home screen.
3- Open folder Root/data
4- Press Shift + Right click
5- Click “Open command window here”
6- Type in terminal “adb.exe reboot-bootloader”
7- Type or paste this command to restore stock recovery “fastboot.exe flash recovery stockrecovery.img”
8- Type “fastboot.exe reboot”
9- When your phone is completely started execute command “adb.exe reboot recovery”
10- Wipe cache partition only and reboot device.
11- Install UniversalAdbDriverSetup6.msi from Root/data folder.
12- Restart PC and Plug in Phone and restart batch file or follow UPDATE-1 above.

thanks
thanks

A thank you and some notes for future users
The original Spanish version uses the same files and works for my Dutch P8 Lite ( v100r001c432b046 )
You can find the link to the zip file in the pdf file from smchohan.
UNLOCKING
Huawei answered quite quickly (7 hours) (I also mentioned my Product ID) and I used my own Android SDK executables to unlock the bootloader.
Contrary to what I found online I didn't lose any user data while unlocking.
ROOTING
The bat file wouldn't run for me, so I manually executed the commands to see what was going on.
I used my own executables (Android SDK) and decided not to install the Google drivers (UniversalAdb Driver Setup6) (stupid me).
So when Windows start looking for Nexus drivers it couldn't find them. Solved it by installing them, unplugging my phone and re-executing adb.exe reboot recovery
After this I got an error while transferring the SuperSU binary. Solved it by using the executables delivered in the zip file instead of my own adb.exe
I created an account just to share my experiences and to thank the original author and OP for translating.

Not sure if all root apps will work currently on this phone
Thankyou pietjpuk92 for sharing your experiences.
Surely this is translated and recompiled from huawei website and a spanish forum.
After rooting my device i installed key to supersu free to make it supersu pro, all root apps work fine, tested root explorer and flashify but titanium backup latest and few old version does not work with full functionality, especially when i tired to convert a user app to system or a system app to user it just stuck in processing. Its not problem with root but few apps needs to updated for this device.

Hi Guys
Newb here. I got hold of the bootloader unlock code from Huawei Mobile and am trying to root my P8 Lite.
Having difficulties with step B. When I execute "fastboot devices" nothing happens. Phone is connected and "phone locked" is displayed.
Any ideas?
Cheers

maxpowers410 said:
Hi Guys
Newb here. I got hold of the bootloader unlock code from Huawei Mobile and am trying to root my P8 Lite.
Having difficulties with step B. When I execute "fastboot devices" nothing happens. Phone is connected and "phone locked" is displayed.
Any ideas?
Cheers
Click to expand...
Click to collapse
These are the steps I followed to unlocked the bootloader:
1. Make sure USB debugging is enabled / HiSuite is able to make a connection
2. Check if you see your device with "adb devices"
3. Reboot into fastboot mode with "adb reboot bootloader". If you see "phone locked" than the bootloader is still locked.
4. Unlock the bootloader with "fastboot oem unlock ****************"
5. Wait. If the phone doesn't reboot by itself execute "fastboot reboot"
The "devices" command is used to see if your computer has a connection to your device.

maxpowers410 said:
Hi Guys
Newb here. I got hold of the bootloader unlock code from Huawei Mobile and am trying to root my P8 Lite.
Having difficulties with step B. When I execute "fastboot devices" nothing happens. Phone is connected and "phone locked" is displayed.
Any ideas?
Cheers
Click to expand...
Click to collapse
First switch on usb debugging in developer options. you will be able to access developer option in this phone by going in settings/about phone and then tapping build number several times. after enabling developers mode connect your phone to PC. once you connect your phone to PC switch it off, and then switch it on by pressing volume down and power key together for few seconds, a white screen should appear at bottom of which phone lckoed is written.
now write in command fastboot devices and press enter you should see serial number of your phone in terminal. If still not working message here again i will write down more detail on it.

PietjePuk92 said:
These are the steps I followed to unlocked the bootloader:
1. Make sure USB debugging is enabled / HiSuite is able to make a connection
2. Check if you see your device with "adb devices"
3. Reboot into fastboot mode with "adb reboot bootloader". If you see "phone locked" than the bootloader is still locked.
4. Unlock the bootloader with "fastboot oem unlock ****************"
5. Wait. If the phone doesn't reboot by itself execute "fastboot reboot"
The "devices" command is used to see if your computer has a connection to your device.
Click to expand...
Click to collapse
Thanks for the headsup, working now.
Started the process, runs through, install the drivers and gets stuck.
At this point the phone screen is black and the bat says "Installing SuperSU...."
Hangs here for some time and nothing happens. Restart the phone manually and nothing has changed. The bat file continues after the manual restart, it restarts the phone into the fastboot "phone unlocked". Restarts again, starts up normally, bat file finishes and phone is not rooted.
Can anyone push me in the right direction?
Thanks

maxpowers410 said:
Thanks for the headsup, working now.
Started the process, runs through, install the drivers and gets stuck.
At this point the phone screen is black and the bat says "Installing SuperSU...."
Hangs here for some time and nothing happens. Restart the phone manually and nothing has changed. The bat file continues after the manual restart, it restarts the phone into the fastboot "phone unlocked". Restarts again, starts up normally, bat file finishes and phone is not rooted.
Can anyone push me in the right direction?
Thanks
Click to expand...
Click to collapse
You may have the same problem as me with the bat file not working correctly.
Open the bat file with a text editor and look for the commands that are executed (TASKKILL, adb.exe & fastboot.exe). In Notepad++ these will be light blue instead of dark blue.
Open a commandline window in the same folder as the bat file and manually execute the commands. The comments in the file (echo's) will be your guidance.
If you still have a problem, please mention at which command the error occurs.

maxpowers410 said:
Thanks for the headsup, working now.
Started the process, runs through, install the drivers and gets stuck.
At this point the phone screen is black and the bat says "Installing SuperSU...."
Hangs here for some time and nothing happens. Restart the phone manually and nothing has changed. The bat file continues after the manual restart, it restarts the phone into the fastboot "phone unlocked". Restarts again, starts up normally, bat file finishes and phone is not rooted.
Can anyone push me in the right direction?
Thanks
Click to expand...
Click to collapse
Make it sure that you installed UniversalAdbDriverSetup6.msi file present in ROOT/data folder before starting step C. First install and then begin. when it shows black screen first time, on PC you will see installation of some drivers let it complete, then continue.

News for working twrp for this model?
Thanks in advance

Hi! I wrote an e-mail to Huawei but they didn't reply after 4 days. Is there another solution please?

YuYu_Man:P said:
Hi! I wrote an e-mail to Huawei but they didn't reply after 4 days. Is there another solution please?
Click to expand...
Click to collapse
Could not say any thing about it, as it depends on huawei they have to provide unlock code, in my case it came after a day, but due to weekend they might have delayed. Wait for a day more, hopefully you will get code, or mail them again.

GABRIPOSI said:
News for working twrp for this model?
Thanks in advance
Click to expand...
Click to collapse
Still no news but have to wait for a while, it will be there soon.

Thanks, everything went perfectly.
Sent from my ALE-L21 using XDA Free mobile app

Thank you!
Edit: But will they ever reply me even it will take a long time?
(Sorry for my bad English)
---------- Post added at 09:32 AM ---------- Previous post was at 09:24 AM ----------
And I have a question but it is NOT related to this thread but I'm writing here cuz I couldn't find any other general Q&A thread. So can I use a theme on my Huawei P8 Lite EMUI 3.1 with lollipop 5.0 a theme that is only for Huawei P8 EMUI 3.0 ? Will it work? Here is the link: http://www.huaweithemes.cf/2015/05/newborn-theme-p8-built-in-for-emui-30.html

YuYu_Man:P said:
Thank you!
Edit: But will they ever reply me even it will take a long time?
(Sorry for my bad English)
---------- Post added at 09:32 AM ---------- Previous post was at 09:24 AM ----------
And I have a question but it is NOT related to this thread but I'm writing here cuz I couldn't find any other general Q&A thread. So can I use a theme on my Huawei P8 Lite EMUI 3.1 with lollipop 5.0 a theme that is only for Huawei P8 EMUI 3.0 ? Will it work? Here is the link: http://www.huaweithemes.cf/2015/05/newborn-theme-p8-built-in-for-emui-30.html
Click to expand...
Click to collapse
Hopefully you will get code or send them email again with correct serial number.
About your question answer is yes you can use any hwt theme, for that;
First download this theme, it will be downloaded in /download folder of internal storage, copy it from downloads to /HWThemes folder. Now open themes app and you will see it there, apply it.

So it doesn't matter if I use that theme even it's for Huawei P8 EMUI 3.0 ? Will it brick my phone?
Sent from my ALE-L21 using XDA Free mobile app

YuYu_Man:P said:
So it doesn't matter if I use that theme even it's for Huawei P8 EMUI 3.0 ? Will it brick my phone?
Sent from my ALE-L21 using XDA Free mobile app
Click to expand...
Click to collapse
I am using all p8 themes on p8 lite, no problem at all.

Ok THanks
Sent from my ALE-L21 using XDA Free mobile app

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus Player Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}

Hello Nexus Player users. NRT has supported this device for a little while but I never had a dedicated thread.
This device is definitely the most unique of the Nexus lineup - so lets try and keep the posts in this thread specific to this device alone.
Enjoy!

Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin

haeffnkr said:
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
Click to expand...
Click to collapse
You don't need a mouse, the root is fully automated in this release.
Sent from my Nexus 5X using Tapatalk

I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin

haeffnkr said:
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
Click to expand...
Click to collapse
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.

WugFresh said:
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
Click to expand...
Click to collapse
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin

haeffnkr said:
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
Click to expand...
Click to collapse
Very nice software indeed, thanks WugFresh, had that issue multiple times, when you get the screen that adb doesn't detect device, give it a minute or two and hit continue and it should redetect it. hope it helps. I think installed driver is fine.

confirmed adb doesn't see device once you hit the temporary twrp.

worked really well, thanks for the software!
I had issue initially connecting to the player it took me couple of tries/toggles of adb (developer tools) to get the USB to recognize, and one time of hard boot while unlocking for no reason it just hung there but the device was unlocked.

upsame problem exactly as people above.i can unlock my nexus player but says adb device recovery was not found.and i have android device in device manager working properly.i've tried everything and not new to rooting phones,tablets or any device that can be rooted and romd.
update switched to another pc and worked fine.thanks

Thanks so much for this application! Worked like a charm on Windows 8.1 and Windows 10. Flawlessly installed TWRP after i flashed the purenexus recovery which is bad.. It got stuck after installing the flash for some reason.

twrp 3.0 not available and it wont proceed with out it.. can you help?

yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link

serpentxx said:
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
Click to expand...
Click to collapse
Any luck finding the twrp 3.0.0.0 recovery?

unfortunately not, i ended up using SkipSoft toolkit which installed an older TWRP for the latest official rom, seemed to work without issue, and once installed apparantly the twrp recovery can self update itself

Now that twrp is available again, I have a question.
I was having some success using this tool to root when I was interrupted by the lack of recovery image and that's a good thing I think because it gave me time to look into things a bit more. When rooting do I need to be able to navigate the twrp recovery? I ask because the instructions I've seen say a OTG cable and mouse are needed in twrp, which I don't have and I will need to order one online since there don't seem to be any retail stores in my area with one. I'd just hate to get stuck half way through this thing when I'm really just trying to root so I can get my ouya games running on the Nexus player.
EDIT: Have tried again and was unsuccessful. Downloaded the latest TRWP from the other section of the Nexus Player forum and it rejected it as a bad hashcode. Looks like the app will need an overhaul to deal with changes in where files are located before it will continue to be useful. Frustrated. I was under the impression the Nexus line of Android devices were supposed to be easy to root and unlock--so far they've been anything but for me.

Where can I download the file TWRP-3.0.0.0-fugu.img ?
Where can I download the file TWRP-3.0.0.0-fugu.img ?
The file on the twrp site dont work.

I just got it working with the current TWRP-3.0.0.0-fugu.img.
Download "3.0.0-0" from the TWRP site.
Rename the file to "3.0.0.0" (remove that "-").
Copy file to (program path)/Nexus root toolkit/data/Recover_custom/TWRP.
Then run the tool. It'll think it already downloaded the file.
BTW, I had a LOT of issues with the ADB drivers. Easiest fix I found, was delete the driver in device manager, then unplug/plug in device. Didn't think I'd ever get past that first TWRP screen.

Here's the link to download the 3.0 TWRP.img for nexusplayer.
https://dl.twrp.me/fugu/

Google play protect problem

Hi. Tried to install lineage yesterday (didn't go well at all). After that car crash I did a factory reset to get back to scratch. However, I cannot reinstsll Netflix now. Google play protect seems to be fine so I'm not sure what is wrong now.
Edit: Google pointed me in the wrong direction. I seen to have lost the certification when I tried to install lineage. What do I need to do to fix this?

Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?

Eggstones said:
Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?
Click to expand...
Click to collapse
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.

Dirk said:
Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?
Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.
Click to expand...
Click to collapse
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.

Eggstones said:
I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).
So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.
Not rooted so I don't I can use magisk.
Click to expand...
Click to collapse
Magisk is the root method, and also used to fix Safetynet issues. You would need TWRP installed though.
Locking the Bootloader right now will fix the issue you are having. It will also factory reset your phone again, so be prepared for that.
That said, installing TWRP is easy if you follow the guides carefully and avoid the obvious pifalls, or simply trying to use the wrong TWRP is a common issue.
In case you still want to try LOS:
This TWRP:
Download twrp-3.3.1-0-oneplus3.img
Follow this guide from funkwizard:
Flashing TWRP Recovery
Adjust the following settings on the phone:
{
"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"
}
USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Place TWRP image in the Platform Tools folder in C:\adb
Then boot into fastboot/bootloader mode on your phone by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the platform tools folder and run the following command:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead unplug your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed, or you can also use the command:
Code:
fastboot boot recovery.img
/Guide.
Just to be clear, when you fastboot flash the TWRP image i linked you to, the command will be:
Code:
fastboot flash recovery twrp-3.3.1-0-oneplus3.img
Make sure your phone is actually in fastboot mode when you do this. Just follow the guide. (On Windows 10 a command prompt window can be opened in the platform tools folder by typing 'cmd' in the Address Bar in that folder, using Windows Explorer).
Once you have flashed TWRP, you do need to boot straight into that Recovery. If you boot into the OS, the stock Recovery will overwrite TWRP again. (follow the guide).
Once you are in TWRP, swipe to 'allow modifications'. (If you decide to go down the custom ROM path you will need to Format /Data and Wipe Partitions, then connect to your PC and transfer any zips you need to install to Internal Storage).
You will have to decide for yourself whether you want to be rooted with Magisk. While it can be used to fix Safetynet issues, it's not needed for that. If you want root access, flash Magisk. If you don't want root, don't. Simple.
Let's say for arguments sake you don't want to be rooted and have sucessfully installed TWRP. Next step would be to install LOS. Assuming you want a stable ROM, it would be LOS 16 you install. So you would flash the latest build of that along with Gapps and the second Zip in this post:
https://forum.xda-developers.com/showpost.php?p=78433987&postcount=3 which is:
https://drive.google.com/open?id=1Yy...2YSyxEXNXWolH5 (sec-patch-2019-08-01.zip)
That zip takes care of one Safetynet problem. (CTS Profile).
Once you have LOS setup you can relock your Bootloader. That then takes care of the remaining Safetynet issue.
Clear Cache/Data on the Play Store App and reboot. Use the 'Root and Safetynet Checker' App to test Safetynet status. Once it shows 'Passed', Netflix and Banking Apps (Including Google Pay) that rely on Safetynet will all work.
Or stay on OOS and relock your Bootloader. Only you know what you want, although it seems that after our previous discussions you are ready to dip your toes into the custom ROM scene. Don't let some early setbacks deter you. You're almost there.

At the moment I'm just trying to get back to where I started. Funk wizards guide is slightly different from the one on the lineage wiki page. I got as far as installing twrp but got only an error message (something on the lines can't load image). Not sure if that's due to adb being wrongly installed or the image being in the wrong folder. Don't think the wiki page mentioned advanced boot mentioned above. Slightly surprised that my banking apps work fine but not Netflix. You would have thought they would be more 'cranky'.

Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.

Eggstones said:
Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.
Click to expand...
Click to collapse
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.
If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.
Click to expand...
Click to collapse
Sorry but I do not follow. Type where? If I right click on the folder there is nothing opening up where I can write the command in. Only the normal file options show up.
If I search for it using the windows 10 search function I can start it but it doesn't recognise ./adb as a command. So where have I gone wrong?

@Eggstones
Sorry, I meant to say shift-right-click on the folder and then select "Open PowerShell window here" from the menu.
Sent from my OnePlus 3T using XDA Labs

Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.

Eggstones said:
Thanks. That worked. I have version 1.0.41.
So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.
Click to expand...
Click to collapse
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"
And please quote my post otherwise I can't tell that you've replied.
Click to expand...
Click to collapse
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience

Eggstones said:
Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience
Click to expand...
Click to collapse
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.
Click to expand...
Click to collapse
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying

Eggstones said:
For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying
Click to expand...
Click to collapse
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Code:
On Windows 10:
Open the Start menu, and type “advanced system settings”
Select “View advanced system settings”
Click on the Advanced tab
Open the “Environment Variables” window
Select the Path variable under “System Variables” and click the “Edit” button
Click the “Edit Text” button
Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
Will post that later. When I set it up I followed that guide, but wouldn't be surprised if the pathway thing is wrong as it is a bit opaque in my view.

BillGoss said:
That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:
Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB
Click to expand...
Click to collapse
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...

Eggstones said:
I think I know what's gone wrong.
Pathway: C:\platform-tools
I'm guessing that is the line that should be in the environmental variables...
Click to expand...
Click to collapse
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).
If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.
Click to expand...
Click to collapse
That is what I did to get the path. So should C:\platform-tools replace kjien\adb to make it work?

How To Guide [GUIDE] Unbrick Lenovo Y700 tablet

Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
{
"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"
}
Your main window should look like this:
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!

For whatever reason, my devices isn't showing up when writing "fastboot devices" but shows up in QFIL. Any suggestions?

Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.

Ale_ax said:
I got one with the "GLOBAL ROM" which miss a lot of feature so I follow this tutorial to flash the stock rom and works like a charm.
The only question is why I can't get any OTA?
Due to te unlocked bootloader?
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
Yes, this one is weird. Some people are able to lock it, and some are not.
To my understanding you need to lock it to get OTA's. It's still possible to update, though, through downloading the newer update and installing the update in .zip format on stock ROM.

Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?

Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.

Joncka said:
See if you can find the right incremental updates here: https://drive.google.com/drive/u/0/mobile/folders/1BZuFF4ZwYHCjIWua-INiEFe1YItjAYz2
I'm on crDroid, I just flashed from the standard 13.0.586 ROM.
Click to expand...
Click to collapse
Thank you, btw they are for the "TB-J716F" Xiaoxin pad pro 2021n, Legion Y700 is "TB-9707F"

Ale_ax said:
Is possible to find the update package? I find 2 in the other y700 thread but they are incremental from an above version of mine and won’t install
Also searched a day on Chinese forum but no succes…
Which version do you have installed?
Click to expand...
Click to collapse
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually

Just for anyone else having trouble getting into EDL mode (my Y700 wasn't bricked, I just wanted to restore stock rom):
When the tablet is running normally, go to developer options, enable USB debugging, then go to the platform-tools folder on your PC and open a command prompt there, then type "adb reboot edl". Then you'll see the "Qualcomm HS-USB QDloader 9008 (COMxx)" Port under Ports in Device Manager.
To re-lock, I believe you can use these instructions. The command "fastboot flashing lock" brought up the menu on the Y700 screen to re-lock, but I didn't do it because I didn't want to delete my user data (I'd just spent time setting up all my apps!)
When I was in fastboot, the tablet was showing up with an exclamation point and just called, "Android device" in Device manager, I used the drivers from here to get it to show up as "Android Bootloader Interface".

Don't do what I just wrote!! I did it and now I'm stuck and it won't boot, and I can't get to EDL mode.
I don't have time to work on it now but my tablet is effectively bricked.
I'm in a bootloop to the fastboot screen, and it shows up in Device Manager as "Android Bootloader Interface". I can't flash in QFIL as described above because it just says "No Port Available". I can't get to EDL mode as I did before because I can't boot the tablet as usual to enter the "adb reboot edl" command.
"adb devices" doesn't show the Y700.
Can anyone tell me how to get to EDL mode when I can't get adb to work?

Ale_ax said:
I tried to relock it but when it's done it say "device corrupted" on bootup so I had to unlock again and reflash all again.
Click to expand...
Click to collapse
That's what happened to me! How did you get it back into EDL mode after unlocking?
Mine isn't showing the Qualcomm device under Ports in Device Manager anymore, so I can't get the port to show in QFIL!!

Got it to work getting to EDL mode, phew!
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
Click to expand...
Click to collapse
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.

shahrul5689 said:
hi, in my case after fresh flash to zui 13 official i can use ota to zui 14 even the tablet in unlocked state, someone in xiaoxin pad pro thread suggested using vpn 'returness' set to china (shanghai 11) i think... and ota did works, zui 14 is about 3 half gig so i ended up using link from y700 thread to install manually
Click to expand...
Click to collapse
Yep, I can get ota with that vpn
gnoted said:
Got it to work getting to EDL mode, phew!
This got the Qualcomm port to show up again.
So I'm now running the stock rom but still unlocked so no OTA. What a waste of time that was.
Hoping someone can work out how to re-lock.
Click to expand...
Click to collapse
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota

Ale_ax said:
Yep, I can get ota with that vpn
you have to use Chinese vpn, it’s not because of unlocked booloader, I will link you the one I used later, btw no need to relock bootloader, for getting ota
Click to expand...
Click to collapse
Haha, maybe I should read more of the comments before assuming things.

Hic, I just got a second hand Y700, it had an original Zui 13 chinese rom, and I started to OTA update upto ZUI 14. Then the Google Play disappeared, also the PC mode. I tried to downgrade to ZUI 13 with this guide WITHOUT enabling usb debugging nor oem unlock. The flashing process succeeded, but when the tablet reboots, it shows for the first time "Your device is corrupt, It can't be trusted and will not boot", after that keeps showing bootloader menu.
Please help me what to do from this step?

I'm in a different state from others here, I think; my Y700 appears to be totally bricked. It's plugged in to charge and nothing's happening at all. I originally installed crDroid on it, but ran into Widevine issues and was going to revert. I don't remember the last steps I took on it (it was a month or so ago), but when I picked it up again a few days ago, turning it on showed only a black screen (only detectable by seeing the backlight), so I let it discharge the battery entirely planning to try and fix it via reflash later. Now, however, it's doing... nothing.
I'm going to let it charge overnight and see if that changes anything, but if anybody has ideas what might have happened or things to try to get out of this, I'd appreciate it!

Hi, I'm stuck after flashing the Chinese stock rom on my legion y700. I was first successful except for upgrades which were proposed and installed but wouldn't show after reboot. I decided to flash again hoping that would solve the problem. But now my tablet remains in EDM mode and won't start. The final message in Qfil was 'download successful'. It is fully charged
Any idea on how to solve this issue?

I am in yet another state. I only run Linux (Mint 21), and have not been able to get any version of wine working, so I cannot use QPST or QFIL (windows .exe's). I CAN access my Y700 via adb or fastboot, and it is now unlocked. It was unsealed when it arrived, but does NOT have any google stuff on it.
I have downloaded all of the components needed from apkmirror, and followed instructions in the Y700 topic to activate them, to no avail.
Sadly, since I do not read Chinese, and the use requirement needs google, it might as well be a brick.
Further, despite more than 40 years doing technical support on all sorts of computers, I have never yet flashed an android device. Can it be done from adb or fastboot? If so, how do I specify which partition to flash? Does anyone have a guide to help me get started? I wish to put cdroid on it, do I use the .xz file or extract the .img?

OK, I've just found something I missed, but it doesn't work for me. My terminal is in the same folder as the .img
fastboot flash boot crDroid-8.10-arm64_bgN-Unofficial.img
Sending sparse 'boot_b' 1/15 (262088 KB) OKAY [ 8.186s]
Writing 'boot_b' FAILED (remote: 'Value too large for defined data type')
fastboot: error: Command failed
What am I missing (apart from a brain!) is this the correct partition to write crDroid to? is there an option to set the data type size? if so what?

Joncka said:
Windows guide, might work for other aswell.
I finally solved my problem with my Lenovo Y700 tablet being stuck in bootloop mode due to trying to flash Magisk boot with a mismatched firmware version. This resulted in the UI constantly crashing, and I could not connect to Wi-Fi, and other problems...
I tried flashing back to stock with QFIL, which put the device in a bootloop. I will explain why later on.
I also lost recovery mode due to trying to solve the problem, and now I was stuck with either showing the bootloader screen, or restarting the tablet, which brought me back to the bootloader.
So the tablet was now genuinely useless. This is what I did to bring back the stock ROM and later flash to crDroid 8.10.
Flashing boot.img, system.img or recovery.img was no luck.
First off, there is no need to have unlocked "USB debugging" before your tablet bricked.
Second, you don't need to have your "sn.img" file from Lenovo, you can unlock the bootloader using fastboot commands.
Fastboot commands works on the bootloader screen, without having ADB connection.
Start by downloading these four files:
Platform tools r33.0.2
QPST_2.7.496
Qualcomm_USB_Driver_v1.0
Lenovo Y700 tablet stock ROM
We'll start by unlocking your bootloader. You can do this from the bootloader screen. If you for some reason can enter recovery mode, enter fastboot.
1. Connect your tablet to your PC.
2. Open a terminal windows in the ADB folder. On Windows 11 this can be done by right-clicking inside the ADB folder and select "Open in terminal". If you don't have that option, try Shift + Right-click. If that doesn't work, you can always start the terminal by pressing Win + R, and type in "cmd" without citations. Now you have to navigate to your ADB folder by typing
Code:
cd (here you'll type in the location of your ADB folder)
Without the brackets.
3. When located, type in
Code:
fastboot devices
You should see your tablet in the list.
If not, try using another cable or USB port on your PC.
4. Now type in
Code:
fastboot oem unlock-go
Restart your tablet, and it should now say "unlocked" under "DEVICE STATE" in the bootloader.
5. Now you can start by installing the programs on your PC, QTPS, Qualcomm driver and platform tools.
6. Extract ALL files from your stock ROM to the "bin" folder in QTPS location (usually C:\Program Files (x86)\Qualcomm\QPST).
This will help with Sahara errors in QFIL.
7. Open QFIL from your QTPS bin folder, it installs with QTPS. Don't worry if it shows "No Port Available", we'll get to that. Your configuration should look like this:
View attachment 5741653
Your main window should look like this:
View attachment 5741651
Don't worry about the "status" window.
Hit "browse" in the "Programmer Path" window, and navigate to your QTPS bin folder. Select "prog_firehose_ddr.elf"
Hit "Load XML", and navigate to your QTPS bin folder. Now, select ALL of the "rawprogram" files (my first mistake, I only selected the "rawprogram_unsparse0.xml" file on first flash)
In the next window, select ALL of the "patch" files (my second mistake, I only selected the "patch0.xml file" on first flash).
Without doing this, you will only flash a portion of the ROM, and not all of the partitions needed.
8. Now it's time to reboot you tablet into EDL mode to be able to flash. Start your tablet by pressing VolUp + Power button.
If you can't turn off your tablet when connected to PC, just select "Power off", and just hold the VolUp button as soon as the device vibrates and reboots, keep holding until the screen flickers and turns off.
9. Now QFIL should detect the Qualcomm 9008 port. If not, hit "Select Port" and select the Qualcomm 9008 port.
10. Hit the now available "Download" button, and the flashing should begin. Allow it to run its course, and it should reboot the tablet when done. Might take a while.
If flashing won't start properly, you might have waited too long between entering EDL mode and hitting the "Download" button.
If so, disconnect your device, which might now be "dead".
Don't worry, you can fix this be holding VolUp + VolDown + Power button for a long time, say about a minute to be sure. Release the Volume keys some second before releasing the Power button.
Hit the power button again, and the tablet should boot to bootloader screen again.
Repeat the steps to enter EDL mode, and now hit the "Download" button in QFIL when it becomes available, don't wait too long.
You're done! ​I recommend opening "Settings", enable "Developer" option, by pressing the "Build number" on the "About tablet" screen repeatedly until a pop-up appears saying "You are now a developer".
Open "Developer options" and hit "Enable USB debugging", it will allow you to run ADB commands from your platform tools folder.
If you want, you can again open the terminal in the platform tools folder and type
Code:
adb devices
It should now show your device in the list.
Now you can uncheck the "OEM unlocking" in the "Developer options" which should let you get OTA updates when available.
There are plenty of guides on how to flash different GSI's like crDroid, so I won't cover that here.
Enjoy your tablet!
Click to expand...
Click to collapse
A lot of this does not seem to work on Linux (Mint 20.3).
fastboot flashing unlock
worked for me, and while I have no problem getting into recovery or fastboot modes on my Y700, I never see anything I recognize as EDL. On a machine with 'wine' installed and working, QTSP installs and appears to run OK, as also does QFIL. I can select the "rawprogram" and "patch" files OK, but it cannot find a port.
Both adb devices and fastboot devices report the correct device when it is in the appropriate mode, and
fastboot flash system crDroid-8.10-arm64_bgN-Unofficial.img appears to have successfully flashed correctly, but it is still unable to communicate with Google servers. All good (tear hair out type) fun!