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

[Q] HTC One M7 stuck in cyanogenmod loading screen/PC won't recognize the phone - One (M7) Q&A, Help & Troubleshooting

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

Related

(Q) Stuck at Boot screen cyanogenmod

Hey,
So I unlocked the boot-loader and installed CWM Recovery and flashed to- http://forum.xda-developers.com/showthread.php?t=2026675 but it doesn't go any where from the loading screen then I tried installing Pac-Man ROm same thing keeps loading in the boot screen doesn't go further my device is S-on and I don't know if it is rooted ? I'm sort of a noob at rooting any ways can some one tell me why this is ?
Cheers

For a start you need to get rid of CWM. It does weird and wonderful (not in a good way) things to this phone. Try TWRP or the one from Wild Child (sorry cant remember the name of it). Second, being S-on requires you to manually flash the boot.img using fastboot or you just get bootloops. Best thing you could do is read thoroughly through the pinned post as they contain all the info you need.

Spectrejester said:
For a start you need to get rid of CWM. It does weird and wonderful (not in a good way) things to this phone. Try TWRP or the one from Wild Child (sorry cant remember the name of it). Second, being S-on requires you to manually flash the boot.img using fastboot or you just get bootloops. Best thing you could do is read thoroughly through the pinned post as they contain all the info you need.
Click to expand...
Click to collapse
WHat does this mean" manually flash the boot.img using fastboot "
Thanks

it means flashing the boot.img or boot image to the phone while in bootloaders fastboot option using fastboot in a command prompt. I suggest taking time to read all pinned post in development area several times till you understand it before doing anything more, lest you end up with a bricked phone.
Here is a link to a good start http://forum.xda-developers.com/showthread.php?t=1416836
As i said read it several times to make sure you know what you are doing is right.

Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button

Mihir1997 said:
Here is a relatively easy to follow guide. Wherever you see "something in quotes" only look at whats INSIDE the quotes. Ignore the quotes themselves.
Okay, what you need to do is this:
Replace CWM with TWRP or WCX Recovery
on your phone go to setting>developer options and click USDB Debugging to enable it
now, on your computer, set up adb
To get the HTC USB Drivers download and install HTC Sync (If you do not need the Sync application itself you can uninstall it but the drivers will remain on your system). * in some cases may be necessary to temporary disable your antivirus software during the installation of HTC Sync.
Download the attached file below
Extract the archive on your C: drive. You will have C:\android-tools folder
assuming you have flashed the PAC rom, download the EXACT SAME ROM to your computer, open the zip file, copy the "boot.img" or "boot" file. Paste it into the C:/android-tools folder
in that same folder, control+shift+right click. Select open command prompt here
now, in the window that pops up, type in "adb devices" - you should now see a code starting with HT(this is your device)
next, type in "adb reboot bootloader"
wait a few seconds. your phone will turn off, and reboot in bootloader. go into fastboot mode using volume rockers and power button
in the command prompt window, type in "fastboot devices" You should see that same HT... code from before
type "fastboot flash boot boot.img" into the command window.
on your phone, using the volume rockers and power button to select reboot. Your Rom should now boot nicely.
Hope this helps you get a ROM on your Vivid. If it does, please thank me using the Thanks button
Click to expand...
Click to collapse
Where are the attached files mate ?

Oh LOL...
http://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659

Mihir1997 said:
Oh LOL...
http://forum.xda-developers.com/attachment.php?attachmentid=1764898&d=1361948659
Click to expand...
Click to collapse
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Why is this ?

dinukap4 said:
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Why is this ?
Click to expand...
Click to collapse
Is ur phone plugged in? is USB debugging on in the dev options menu?

Mihir1997 said:
Is ur phone plugged in? is USB debugging on in the dev options menu?
Click to expand...
Click to collapse
ok did that now waiting to load fingers crossed

About 5 min passed still loading :/ Should I wipe anything ?
Edit- Tried with both CM and pac same :/ did everything correctly btw what does "now, on your computer, set up adb" Mean ?
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1AXVJ00209 recovery
C:\android-tools\android-tools>adb reboot bootloader
C:\android-tools\android-tools>fastboot devices
HT1AXVJ00209 fastboot
C:\android-tools\android-tools>fastboot flash boot boot.img
sending 'boot' (3570 KB)...
OKAY [ 0.796s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.350s
C:\android-tools\android-tools>

that is like the thing that the next steps explain.
so, did you fastboot flash the boot img?
it has to be the boot from the rom you want.

Mihir1997 said:
that is like the thing that the next steps explain.
so, did you fastboot flash the boot img?
it has to be the boot from the rom you want.
Click to expand...
Click to collapse
When I try to do the CMD stuff on this screen
{
"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"
}
It tells me -
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android-tools\android-tools>
Click to expand...
Click to collapse
And if I give this command -adb reboot bootloader
C:\android-tools\android-tools>adb reboot bootloader
error: device not found
Click to expand...
Click to collapse
But if i go to recovery and enable Debugging it passes, But I cant enable it and come back to the Fast boot screen because debugging will be disabled and I get the same thing-
If done with recovery debugging-
C:\android-tools\android-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT1AXVJ00209 recovery
Click to expand...
Click to collapse

Bump!!

BUMP! Please help me out

Is this an HTC vivid ? screenshot doesn't look like one...

Lol, wrong forum. This is NOT an HTC Vivid. You have to atleast know what phone you have. Go to the forum for your device. but either way. This image suggest you have not plugged a UDB into the phone. If you had, it would say "fastboot USB"

esloan said:
Is this an HTC vivid ? screenshot doesn't look like one...
Click to expand...
Click to collapse
Mihir1997 said:
Lol, wrong forum. This is NOT an HTC Vivid. You have to atleast know what phone you have. Go to the forum for your device. but either way. This image suggest you have not plugged a UDB into the phone. If you had, it would say "fastboot USB"
Click to expand...
Click to collapse
I got that off google images lol not my phone anyways I got it to work, but it doesnt have play store and my memory car isn't accessible ? I tried with 2 mem cards both the same cant download anything

dinukap4 said:
I got that off google images lol not my phone anyways I got it to work, but it doesnt have play store and my memory car isn't accessible ? I tried with 2 mem cards both the same cant download anything
Click to expand...
Click to collapse
Play store Fix: flash Gapps (google apps) - you can do a search on google. Download the correct one. if you have a rom with Android 4.2.2, use a Gapps for 4.2.2
Memory card: What rom are you using? go into the Rom forum and post there for help.

Help! Infinite bootloop, can't enter Recovery, and Fastboot usb doesnt work

Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!

First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013

Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"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"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.

Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.

Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"

Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need

Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.

Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910

clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?

Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse

OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...

Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.

Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA

Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot

Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?

Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery

Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push

More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1

Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.

[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/

[GUIDE]-[Unlock Bootloader+TWRP+Root] Huawei MediaPad M3 8.4 [BTV-W09, BTV-DL09]

{
"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"
}
The official Huawei bootloader unlock program has been shut down! This guide describes how to use DC-Unlocker which will cost you about $5 USD. I am NOT affiliated with DC Unlocker in any way!!. This is simply the cheapest and easiest method I could find...
I have only tested this method on BTV-W09 running Android 7 and EMUI 5.0.3.,
If you have a BTV-DL09 device, please reply and let me know how everything goes...
You need ADB and Fastboot installed on your PC.
This will FACTORY RESET your tablet!!! and as always: Don't blame me for Bricks & FOLLOW THIS GUIDE AT YOUR OWN RISK!!
-Unlock Bootloader-
0. Enable USB Debugging and OEM Unlock in developer options.
1. Download DC Unlocker and extract it on your PC.
2. Open the program and choose 'Huawei phone' under manufacturer and 'Auto detect' under model.
3. Plug your device into your PC and put it into 'manufacturer mode'.
3.1 Open the Calculator app in LANDSCAPE mode
3.2 Enter this code: ()()2846579()()=
3.3 Tap on 'Project Menu' - 'Background settings' - 'USB ports settings' - 'Manufacture mode'.4. Click the search button in DC Unlocker and make sure your tablet is detected.
5. Click on 'Buy Credits' under the About section.
6. Use the website to buy 4 credits for a new account.
7. Click on 'Server' in DC Unlocker and log in using info obtained in step 6.
8. Once your logged in click 'Unlocking' then select 'Read Bootloader Code'
9. Wait until your code is displayed then copy and save the code.
10. Turn off manufacturer mode.
11. Open a CMD Prompt and type the following commands.
Code:
adb devices
//make sure your device is listed.
adb reboot-bootloader
//Wait for your device to reboot (white screen)
fastboot oem unlock XXXXXXXXXX
//replace XXXX with your code
12. Wait... your device should now reboot and do a Factory Reset...
13. After reset, boot your device and go through android setup.
Congrats your bootloader in now unlocked.
-Flash Greatslon TWRP-
0. Download TWRP for your device.
TWRP - BTV-W09 EMUI 5 (This is the only Model & Version I have tested)
TWRP - BTV-W09 EMUI 4
TWRP - BTV-DL09 EMUI 5
TWRP - BTV-DL09 EMUI 4
1. Enable USB Debugging
2. Plug your device into your PC.
3. Open a CMD prompt in the same folder as TWRP image.
4. Enter the following commands.
Code:
adb devices
//make sure device is listed
adb reboot bootloader
//wait for device to reboot
fastboot devices
//make sure device is listed
fastboot flash recovery XXXXXX
//replace xxxx with your TWRP file name
5. Completely shut down your device and unplug any USB cables. (some devices have problems booting TWRP when a USB cable connected)
6. Boot into recovery (PWR+VolUP).
Congrats You have flashed TWRP.-Root Device-
0. Download the latest Magisk release.
1. Download Magisk Manager APK file.
2. Open a CMD prompt in the same folder as files
3. Type the following commands
Code:
adb devices
//make sure your device is listed
adb push Magisk-v20.4.zip sdcard/
//change name if needed
adb push MagiskManager-v7.5.1.apk sdcard/
//change name if needed
adb reboot recovery
//wait for device to reboot
4. Install Magisk | 'Install' -> Select: Magisk zip -> Swipe to confirm.
5. Wipe Cache/Dalvik.
6. Reboot to Android.
7. Install Magisk Manager to confirm root..
Congrats your device is now Unlocked and Rooted running a custom Recovery.
:: EDIT ::
LienageOS 15.1 now available on this device., Visit the following thread for my install guide.
[GUIDE]-[ROM][8.1][LineageOS 15.1 - Huawei Mediapad M3 8.4][BTV-W09, BTV-DL09]

Thanks very much for the write up! All worked perfectly and using this to prep for lineage os.
One thing I had to do using Windows 10 is install hisuite to get the USB drivers so adb/DC unlocker could recognize the device.
Thanks again!

Phone not found!
4. Click the search button in DC Unlocker and make sure your tablet is detected.
After I click search button that warning "Phone not found!" I don't know why Help me, plz

traihams said:
4. Click the search button in DC Unlocker and make sure your tablet is detected.
After I click search button that warning "Phone not found!" I don't know why Help me, plz
Click to expand...
Click to collapse
Does you already connected USB cable between your tablet & desktop ? Does you already installed Huawei Drivers on your desktop ? Does you already enabled Android debugging inside Developer options on your tablet ?
EDIT:
From what you see there are many reasons why you do not see the tablet connected there ... unfortunately we don't have any prophet here to guess what you did or didn't do there

i follow those steps to root my d-01j, thanks so much

iFilae said:
i follow those steps to root my d-01j, thanks so much
Click to expand...
Click to collapse
Hello, could you show your unlock code? I want to see some examples for d-01j unlock code. Thank you.

baobinhday said:
Hello, could you show your unlock code? I want to see some examples for d-01j unlock code. Thank you.
Click to expand...
Click to collapse
unlock code is different for each imei

Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!

Moving on to next step (flashing greatsIon TWRP)...
There seem to be no download mirrors for TWRP - BTV-DL09 EMUI 5 at the moment, so I have to retry later.
I though noticed a strange thing: looking at the greatsIon M3 download list, it seems that there are 2 versions of the TWRP for the BTV-DL09 with EMUI 5: the one linked in this thread, and another one, having same name ("twrp_BTV-DL09_5_greatslon.img") which has been uploaded earlier (March 2 vs August 7 2017) and its quite larger (35.4 vs 24.7 MB). Now the funny thing is that this file actually has mirrors available right now, but I don't want to flash something unless I'm quite sure it's the right one. Plus I'm quite a noob, so that gives me another minus...
For all other BTV-DL09 users out there: did you try flashing this one? Why are there 2 versions hanging around?
EDIT:
Now it seems that there are again mirrors for the DL09 TWRP linked in this post. After downloading it, I extracted both versions (the smaller and larger .img files), and by doing a byte-per-byte compare of the extracted payload, it seems that the two images are identical. One is just packed in a bigger IMG file, if I got it right.
Anyways: After flashing via fastboot, I cannot eventually directly boot into TWRP recovery using the "Power+ Volume Up" combination. It boots every time in the warning screen stating "your device has been unlocked", giving me two options: Pressing "Power" will boot normally, whereas pressing "Volume Up" for at least 3 secs will boot into recovery. If I then press "Volume Up", it goes in the "Huawei eRecovery" instead of going into TWRP. Is that expected? The only way to reach TWRP for me is via adb by entering "adb reboot recovery". Why?
EDIT 2:
Sorry guys, I'm such a noob at this. I evenutally was able to boot directly in to TWRP by pressing "Power + Volume Up" a bit longer. If I press it and release when I feel the vibration, it will take it as a "Power" only command and it'll boot into the warning screen with normal boot / Huawei eRecovery options, but if you continue pressing it until you see the LCD turn on, it will boot into TWRP.
All right, seems that I'm slowly moving on. Sorry for this exhaustive reports :cyclops:

I found the calculator (my bad) but now the problem is this message in Twrp "failed to mount '/3rdmodem" and "failed to mount '/cust" Whay can i do? Please, help me.

I've just created an account, to say thank you bro.
Your guide works also perfectly fine on a BTV-DL09 device.
I also can confirm the necessarry additional steps which "the wing" mentioned. Also a great guy
A little note from me: In the windows powershell, I had to start the code lines with a "." expample ---> .\adb.exe fast boot reload
Now I am taking a sip of my coffee, lean back and simply enjoy my taken of handcuffs of my MediaPad. Twek8 is now a free elf.
Thanks a lot for your great guide and stay gangsta.

Hi Guys,
Hoping someone has had some luck with this point as I am getting really frustrated....
I have the MediaPad M3 Lite 10 (BAH-W09). I am trying to get DC_Unlocker to recognize my device. No matter what combination I try and do things (from the points above), I continue to get 'Phone not found'. If I select MTP mode, manufacture mode changes, if I change to manufacture mode, it changes to 'charge only'. I also thought I would fool the system and set 'allow adb debugging in charge only mode' but this still is not working. Of note, ADB does recognize my device and I have also installed the drivers (should that help troubleshoot).
Frustrating when you are stuck on Step 1 of so many!!
Click to expand...
Click to collapse
Just following up on this...finally got things moving along, a bit. I was finally able to unlock the bootloader, install TWRP and attempted installation of MAGISK. I have ran into a couple of problems...
1. TWRP, I installed the version that is meant for EMUI5.1 (3.2.0.0?)
2. Via TWRP, I attempted to install MAGISK.
During step 2 above, though it was running, it clearly was not succeeding and gave a long list of permission errors; thus failing.
On top of that, when I try and reboot the warning comes up that I have an unlocked device, if I continue with the boot, it gets to the Huawei logo and then reboots; over and over. The other option is to enter into Huawei's recovery system.
Anyone have any thoughts on what could have gone wrong that would have caused TWRP to fail?

Hi! Thanks so much for this guide, I've got my M3 up to the point where I flashed TWRP and rebooted into recovery.
Unfortunately, the TWRP BTV-W09 EMUI 5 image put it me into a boot-loop. I also tried both of the twrp 3.3.1-2 and 3.3.1-3 images from here. These images both got it stuck on the TWRP 'Teamwin' screen and doesn't boot into recovery. Any ideas on where to go with this issue?
Edit: I found a post stating I needed twrp 3.2.0-0, this worked for me.

Eilermoon said:
Hi! Thanks so much for this guide, I've got my M3 up to the point where I flashed TWRP and rebooted into recovery.
Unfortunately, the TWRP BTV-W09 EMUI 5 image put it me into a boot-loop. I also tried both of the twrp 3.3.1-2 and 3.3.1-3 images from here. These images both got it stuck on the TWRP 'Teamwin' screen and doesn't boot into recovery. Any ideas on where to go with this issue?
Edit: I found a post stating I needed twrp 3.2.0-0, this worked for me.
Click to expand...
Click to collapse
I don't understand why you flashed a TWRP for Kirin devices on your Qualcomm device

Bootloader unlocked but TWRP does not work, flash ok but does not start, advice?
Huawei mediapad M3 Lite 10
I need to ROOT:

It also works on BAH-W09 version?

GiammyA7X said:
It also works on BAH-W09 version?
Click to expand...
Click to collapse
NO, this is only for Huawei MediaPad M3 8.4 and not for Huawei MediaPad M3 Lite ... and it's stated clearly in the title !

surdu_petru said:
NO, this is only for Huawei MediaPad M3 8.4 and not for Huawei MediaPad M3 Lite ... and it's stated clearly in the title !
Click to expand...
Click to collapse
Yes, but I'm a bit confused about the "compatibility" between models (m3 lite 10/8, WiFi only/data). For the TWRP i've seen that it's compatible BAH-W09, but is possible make root on it?
Thanks

GiammyA7X said:
Yes, but I'm a bit confused about the "compatibility" between models (m3 lite 10/8, WiFi only/data). For the TWRP i've seen that it's compatible BAH-W09, but is possible make root on it?
Thanks
Click to expand...
Click to collapse
Unfortunately I did not test TWRP 3.2.0-0 in stock EMUI firmware Android N ... so I created that TWRP just with the intention of installing LOS 16.0 !
Basically after I installed TWRP, I formatted /data, and installed LOS 16.0 - so I can't guarantee that it works properly with android stock EMUI !
My advice is to use TWRP only if you want to update to LOS 16.0 and later to LOS 17.1 - and after installing LOS there is no way to downgrade to android stock EMUI .

Hi,
Thank your for your job but currently I'm a little bit frustrated. I can't unlock my BTV-W09 bootloader.
In step 4, DC Unlocker does not seem to find my device. It does not show any data after, "Found Applications port COM5".
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM5
===================================================================
- The ROM version is BTV-W09C100B308
- I use windows 10
- I installed hisuite
- USB debugging, OEM Unlock and manufacturer mode are enabled
- In device manager, I see "Android Composite ADB Interface" and "Huawei HDB Interface" under "Android Phone" and "Android Adapter PCUI (COM5)", "DBAdapter Reserved Interface (COM4)", "HUAWEI Mobile Connect - Fake Acm Interface (COM3)" under "Ports (COM and LPT)"
- After many tries, I uninstalled hisuite because it was started automatically after each usb connection. After uninstall, device manager still shows interfaces and ports.
Any idea about this issue? Do I need to buy credits before step 4?
Best regards,
EDIT: Sorry, I was expecting more verbose from DC Unlocker like, model, serial, firmware. In the end I succeeded. Thanks.

Device not detected in Fastbootmode.

SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?

TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?

reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw

TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done

reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"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"
}

TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.

reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:

TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....

reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty

TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...

Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!

Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...

TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)

See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution

reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.

Also I got this from continually trying to boot:

TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?

TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc

reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.

Database Develop

welcome