Database Develop

Installing Android 4.2.2 CM10.1

Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar

PetarHolland said:
Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar
Click to expand...
Click to collapse
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.

Thanks, i will read this, then i'll post here if i still need some information The entire process seems to be very hard ^^
soupmagnet said:
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.
Click to expand...
Click to collapse

I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
{
"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"
}
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance

Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
ed! said:
I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance
Click to expand...
Click to collapse
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.

Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1

Indeed... The entire process is hard, i'm trying to organize the information. SO the step are:
-Fastboot
-Installing bootloader
-Cleaning the system/exporting img
-Installing the rom
-Wipe
-Reboot
android :victory:
Right?
Some questions:
I read about a special cable, i can't do the process with the standard miniusb cable?
I read about downgrade the firmware of my kindle... I have the 7.3.0.3 version, i need to downgrade before install the bootloader right?
ed! said:
Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1
Click to expand...
Click to collapse

@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!

Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
E_Zatopek said:
@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!
Click to expand...
Click to collapse

PetarHolland said:
Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
Click to expand...
Click to collapse
Just a note of caution, as with all flashing of rom's. Whilst the fastboot cable is not 'required/essential' if you do mess it up , there is a potential that you 'could' brick, and depending to what extent your at, the cable becomes vital. In a nutshell if you can get your hands on a cable its recommeded as the earlier thread stated its a kind of insurance!
Good luck
kgyuszko

Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?

Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse

from ondom
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
PetarHolland said:
Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
Click to expand...
Click to collapse

ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
PetarHolland said:
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
Click to expand...
Click to collapse
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.

How can i test if my fastboot work? if i type fastboot on cmd i have the entire instruction of fastboot, so the command is recognised....
seokhun said:
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.
Click to expand...
Click to collapse

fastboot -i 0x1949 getvar product

<waiting for device>
but when i plug my kindle fire and reboot, no fastboot, still <waiting for device>
I previously installed the sdk developer tool and changed the PATH adding the skd folder path to the windows shortcut for the cmd.
soupmagnet said:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse

You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.

Nope, i tryed every possibility, plugging turned off, plugging turned on and reboot, leaving to "waiting for device" for 2 hours, and nothing happened. soupmagnet suggested me to use the kindle first aid script to reinstall the adb drivers, seems the best option atm....
seokhun said:
You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.
Click to expand...
Click to collapse

Cyanogenmod logo all the time
seokhun said:
Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.
Click to expand...
Click to collapse
I did exactly this and now i get the cyanogenmod logo all the time after reboot. been this way for 40 mins already. Can someone suggest what to do next?

[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

Can't seem to get past the stuck at 50% Bootloader unlock issue.

In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.

vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.

Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))

stefipant said:
Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Click to expand...
Click to collapse
You still have problem, unlocking your device?
Sent from my Xiaomi Mi 5 using XDA Labs

vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.

abelmaster said:
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.
Click to expand...
Click to collapse
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Sent from my Xiaomi Mi 5 using XDA Labs

harish15 said:
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Click to expand...
Click to collapse
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?

abelmaster said:
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?
Click to expand...
Click to collapse
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.

vgdoc said:
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.
Click to expand...
Click to collapse
Thanks for posting your link, this helps me find it quick. Now one last question (I hope . Where can I find/download the version 9 driver?

"Google USB driver" in the SDK tools application. That is the version 9 driver.

vgdoc said:
"Google USB driver" in the SDK tools application. That is the version 9 driver.
Click to expand...
Click to collapse
When I type SDK tools application into windows menu bar nothing pops up, so i guess you mean the android sdk manager?
{
"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"
}
But where in the SDK manager can I "google" (or do you mean "search") for something?

In SDK manager did you install tools > Android sdk tools and tools > Android sdk platform-tools ?
If not try to install them, then check you can detect your device with adb tools :
connect your phone with usb
windows key + r
in prompt enter cmd
go to your adroid sdk platform-tools directory with "cd" command
then type "adb devices"
Your device should be find
Here an example :
Code:
cd /D F:\android\sdk\platform-tools
F:\android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
74a9b5b5 device <<<<<<<<<<<<<<<<<<<
If you do not see your device there is something wrong, try to install this pack from xda :
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It worked for me.
If it still not work after installation usb driver from xda have a look in the miFlashunlock log directory, open the MiFlashUnlock.log file and check the error.

What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.

I'm convinced it's impossible.
I've done a clean install of all the drivers (either via SDK or the minimal adb packs), tried doing what crim did... Still stuck on 50% error. Mind boggling stuff.

vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
same problem guys plz help me
---------- Post added at 02:43 AM ---------- Previous post was at 02:04 AM ----------
dkmsn8 said:
same problem guys plz help me
Click to expand...
Click to collapse
ok i did it guys thanks

Crim Soukyuu said:
What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.
Click to expand...
Click to collapse
I dont know why this worked, but it did. Finally! I tried this method a couple of times and the fourth time it works. Have to say that mi unlock did not install the driver for me, I searched for it online with the built in windows driver update. It gave me the kedacom one again, but it worked!

vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
eros1on said:
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
Click to expand...
Click to collapse
and i believe other guys with this problem can also solve it via this method.

i solved it by;
1.disable internet coonection cause of auto update driver
2.uninstall kedacom driver, select delete files.
3.update driver manually and select let me pick driver.
4. choose usb composite device than try "fastboot oem-devices" command .
if it shows your device. unlock wont be stuck at %50.

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