Database Users

[ALL-IN-ONE][HOW-TO][D5803] Bootloader Unlock/Relock/Flash firmware/CWM Recovery/Root

Hello
I have done this on two Xperia Z3 Compact phones this weekend in Bulgaria, bought from local mobile operator. I wanted the latest Sony firmware, so I did the following:
How to install the newest Android 4.4.4 for Sony XPERIA Z3 Compact D5803
CAUTION
There is information, that users who have unlocked the new Xperia Z3 Compact have found that low-light camera performance drops considerably. It turns out to be because of DRM in Sony's image signal processing.
When the bootloader is unlocked, the device loses certain DRM security keys. That means you can't purchase content from Sony's storefronts and a few licensed features won't work, but it apparently also means basic features of the phone are negatively affected. A Sony rep has confirmed that some advanced camera algorithms on the new generation of devices like the Z3 and Z3 Compact are protected by DRM. If you unlock the phone, those features stop working. Apparently that causes photos in low-light to be noisier and poorly balanced.
This isn't the first time Sony's bootloader unlock has come with some major drawbacks—unlocking past devices could actually break camera functionality (this was technically a bug). There have always been a few proprietary features that stop working, but the difference in image quality this time is allegedly noticeable.
Update: Sony has updated the text of the bootloader unlock warning on its website to be clear about the camera impact. It reads, "...the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected."
Relocking your device bootloader will NOT get back the lost DRM Keys... Once locked, they will be lost forever! More info cant be found HERE
More detailed info and explanations can be found HERE
Click to expand...
Click to collapse
1. PREPARATION
1) First of all, check your firmware version (if you already have the newest one, you do not need to download it, so skip step 3) and step 4), that are below. Just proceed with step 2) -> 5) from the PREPARATIONS (this) tutorial . Steps in the other tutrials are absolutely needed! Dont skip any of them!)
2) Download and install latest Flashtool from here (Latest Flashtool for Xperia Devices)
3) Download also latest Sony Original Firmware - 23.0.A.2.105 - Android 4.4.4 ( Mega Download ) for Sony XPERIA Z3 Compact
4) Paste the .ftf file downloaded in step 3 in folder „Firmware“ in your Flashtool installation folder. (for example for me is C:/Flashtool/Firmware)
5) Go on Sony Mobile site and download the Sony PC Companion. You must install it, because it installs some important drivers for your device. Since Sony stopped the Update Service application, now all the job is done from PC Companion.
a) After you installed the PC Companion, you must launch it and download the "Support Zone" addons from the main menu.
b) After that you must go in your Flashtool installation folder and find the Drivers folder. Go in it and install the Flashtool drivers for your device.
IMPORTANT
It is important to install Flashmode and Fastboot drivers with the driver for your device! Otherwise it will cause some problems during the flash procedure.
So now we're going into the real part of the things
2. BOOLADER UNLOCK
1) Go on Sony Mobile Developers website, register, enter your device IMEI and it will generate an unlock key for your device. Write it down!!!
1) Start Flashtool application and click on BLU button on the top
2) Turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
3) Copy the unlock key, that was given to you earlier from Sony Website to Flashtool window and than click unlock button
4) When you are prompted, disconnect your phone and connect the phone again, but this time with holding volume up button when Flashtool shows pop up window
5) Wait the unlock process to finish
6) Disconnect your phone and start it up. If it boots normaly, than all is DONE. Congratulations! You have unlocked your bootloader!
3. BOOTLOADER RELOCK
1) Download and install latest Flashtool from here (Latest Flashtool for Xperia Devices)
2) Start Flashtool and click on BLU button on the top
3) Turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
4) Just click on relock button and your bootloader is locked again
4. Flash Sony XPERIA Z3 Compact Latest Firmware - 23.0.A.2.105 - Android 4.4.4
1) Ensure yourself that you have the .ftf. that you downloaded in the PREPARATION process into the Firmwares folder of your Flashtool
2) Do not connect the phone to the computer yet. You must first open the Flashtool application, click on flash (the thunder) and choose Flashmode, than choose the firmware that you have downloaded and click ok.
3) Now turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
4) After few minutes of flashing, all is done!
IMPORTANT
The process is pretty slow! DO NOT DISCONNECT your phone during the proccess! Leave it still and for it to finish the flashing process! When it is DONE, Flashtool will say Disconnect and turn on your device (not a pop-up, just a line at the bottom of the other lines of words)!!!
If the device boots normaly, it should be factory reseted and it will boot slowly. Much slowly than normal.
Congratulations! You have the lates firmware from Sony!
5. Flashing ClockWorkMod Recovery
1) Download the kernel image with integrated CWM Recovery from HERE
2) Save the boot.img to folder of your choice
3) Open Flashtool, click on the Flash (thunder) and choose Fastboot. Choose "Choose file to flash" under the DooMLoRD "side" of the opened window. Then choose the folder, that you have saved the boot.img in and then choose the .img file itself.
4) Follow the instructions. There are two posibilities - the phone will reboot itself and go into Fastboot mode without you touching it OR you must turn-off the phone, hold the volume up key and connect phone to computer.
5) The flashing will finish verry fast. Wait for it and when it is done, disconnect you phone and turn it on. When Sony logo appears, start pressing the volume down button rapidly, until it enter the recovery mode. And you're ready to go!
6. ROOT
IMPORTANT
You must ensure yourself, that you have falshed the kernel boot.img WITH the CWM Recovery!
1) Once you have flashed the kernel boot.img WITH the CWM Recovery download the latest SuperSU update.zip from: HERE
2) Save the downloaded .zip file on sdcard of device
3) Reboot into recovery and choose "Install ZIP from sdcard" and then "Choose ZIP file to install" (moving thru options is vol up / volume down keys; choosing an option is power button)
4) Choose the .zip file that you have downloaded on your sdcard and the installing should begin
5) After a while the installing should be finished you the recovery will bring you into the menu, that was just before the installation begin. You must choose "Go back" and then "Reboot"
6) The recovery will say you, that the root permisions must be fixed befor rebooting - choose ok / accept or fix (don't remeber what was the opiton really...)
7) If all is OK the phone must boot normaly ( the first time it will say "Upgrading Applications") and after that in the applications menu you must have an applicaion, named SuperSU. If you have it - Congratulations! You have rooted you phone successfully!
7. Installing BusyBox
It is highly recommended to install busybox after rooting!
You must just go to andorid play store and download the busybox installer. Once the installer is downloaded start it and choose to install busybox in /system/xbin. After the installation is done, reboot the device and you're done!
-------
Special thanks (and apologize for using their files) to:
DoomLoRD - CWM Kernel, CWM Kernel Flashing and Rooting / BusyBox installing guide! - Sorry for using your files man, but I think that the users deserve at least one ALL-IN-ONE tutorial! Please, forgive me!
Unknown User from other website - Bootloader Unlock / Relock / Latest Firmware flash (with some additional explanations from me and my expirience! )

nowhere you mention that unlocking loses DRM keys and relocking will not get it back - you really need to include this vital info!

Bäcker said:
nowhere you mention that unlocking loses DRM keys and relocking will not get it back - you really need to include this vital info!
Click to expand...
Click to collapse
Yes, you're right. I've added the info at the begining of the post! Thanks for fast reply!

Moderators, please consider to make this thread an important one! Thank you!

up ^

Is the only downside of missing the DRM keys the camera?? How bad does it actually get?

crxmax said:
Is the only downside of missing the DRM keys the camera?? How bad does it actually get?
Click to expand...
Click to collapse
There is a topic that compares pictures with and without an unlocked BL.
The problem is if you unlock your BL and you send your phone back for repairs, chances are very big that they will refuse to repair your device.
Hence being able to re-lock it and regaining the keys is almost a must.

Thanks!! It works a lot!

Dsteppa said:
There is a topic that compares pictures with and without an unlocked BL.
The problem is if you unlock your BL and you send your phone back for repairs, chances are very big that they will refuse to repair your device.
Hence being able to re-lock it and regaining the keys is almost a must.
Click to expand...
Click to collapse
Well since you unlock your BL through Sonys website they'll know If its been unlocked...regardless If you relock it.

For a guide which details unlocking bootloader, you should probably include backing up TA partition using this tool
Do it after root, before unlocking bootloader. Then if you want DRM stuff back, you can restore the TA backup using the same tool; this automatically relocks the bootloader, then flash a stock kernel (& rom if you need) & it will be in 'factory' condition

Hi, I followed the steps exactly and everything went perfect. However, I downloaded CM nightly and when i try to install it, i get an error msg that says that the nightly zip file is for zc3, while my phone is aries (which i believe is Xiomi MI2). The model number of the phone still says d5803, so I am not sure why its recognized incorrectly.
Any ideas, anyone?

@ThunderBird891 Where did you get the boot.img from under " 2) Save the boot.img to folder of your choice" of flashing cwm ?
Also, the "choose file" option in flashtool isn't there in fastboot mode. There is "select kernel to flash" but it's looking for .sin files and not .img files, am i missing something here ?
I've flashed with cm12, but i'd like a proper recovery and root.

flintfirewalker said:
Hi, I followed the steps exactly and everything went perfect. However, I downloaded CM nightly and when i try to install it, i get an error msg that says that the nightly zip file is for zc3, while my phone is aries (which i believe is Xiomi MI2). The model number of the phone still says d5803, so I am not sure why its recognized incorrectly.
Any ideas, anyone?
Click to expand...
Click to collapse
I believe that, by now, you got the answer to this question... Yeah, I don't know why this is happening, you won't have this issue after flashing CM12 / CM12.1 the first time since all the upgrades will be done through Cyanogen Recovery which seems to work ok for updates.
Anyway, you need to remove the first line (pretty long one, so be careful) in the updater-script. You can find the updater script in the CM12/ CM12.1 zip archive, under META-INF/com/google/android/updater-script. If you're running Windows, please, make sure you edit this script using Notepad++, not Notepad.

Hi guys, i have a problem.
I need to prepare my xperia z3 compact to be stock cause i will carry my telephone for repair my glass.
I had tried to relock the bootloader with flashtool but without success.
When i click on "BLU" button, there is the popup, i power off my z3c and then i plug the usb with the volume button down pressed. The pop up with the instructions disappear for 2 seconds and device seems connected.
But after 2 seconds apear another popup:
{
"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"
}
I've tried to plug the usb cable when i press the menu button (power button, yes?) but device remain powered off and no changement on flashtool.
What is wrong?
Another question: after (i hope) bootloader relocked, how can i restore the drm keys and how can i have a full stock device?
Thank you so much and sorry for my bad english sometimes...
EDITED:
Guys, i am so confused, my bad: i have never unlock the bootloader, so for this i can't reblock it...
So sorry guys

Hiya, when I flash using that boot.img, my phone goes into a restart loop and I have to reflash firmware to have it functional again, losing CWM in the process. Is there another .img file I should be using? I've used both this method and the command line, both causing the same issue, so it's got to be this particular image. Or does this image only work with this firmware? I am updating to 5.1.1....26.

No way to relock bootloader on 6.0 at Z3+ Ivy

Hello guys, I tried to go back to stock today. I relocked the BL using flash tool and flashed 23.5.A.1.291 from https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706. After that the phone stucks in the Blue-wave starting animation.
Any hints how to get this work? I also like to patch the DRM fix. When should I do that?
Edit: Never mind: Just forgot to wipe appslog in Flashtool ^^

Still Can't unlock bootloader
Hello, I've done that, but, my bootloader still says "no" in * # * # 7378423 * # * # how to solve it? Please help ...
of course,I have flashed the kitkat version like the above method.

[HOWTO] Unbrick Hardbricked (stuck onUSB Logo) MeMo Pad ME170CX (and others)

This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"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"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool

Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated

Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.

Thanks
I shall keep going at it until it works or I find another solution.

PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?

Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.

korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore

Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?

korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."

Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.

korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well

Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.

korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload

Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.

korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help

Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck

Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??

Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.

is this solution applicable to non-intel memopad? (e.g. me172V)

playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.

[CLOSED]Yoga Tab 2 (830, 1050, 1380) - get back to KitKat

@MikeChannon removed OP. please close
what? lol

Yeeha! You are the magic man....

workdowg said:
Yeeha! You are the magic man....
Click to expand...
Click to collapse
He truly IS the man. Helped me out BIG style.

ionioni said:
READ CAREFULLY AND BE WARNED BEFORE ANYTHING:
THIS CAN HARD-BRICK YOUR DEVICE AND I TAKE NO RESPONSIBILITY FOR THAT!
use it only if you must or not at all
you can read this for some details about what bricks are so you understand what you can get into
this is for all Yoga Tab 2 models 830, 1050, 1380 (regardless of the submodel F,L,LC)
it restores(downgrades) your bios firmware from whatever Lollipop version to the original/genuine one from the latest KitKat stock rom released by Lenovo (and all the latest KitKat stock rom's have 150422 in the rom filename, ie April 15, 2015 and nothing not even minor OTA's were released after this date for KitKat, next ones upgraded KitKat to Lollipop)
useful to:
1. those who want to return back to the KitKat stock rom from Lollipop (if you simply flash back the KitKat stock rom files and you are still on Lollipop bios firmware you will softbrick as the Lollipop bios is a x64 version while the KitKat loader/kernel are ia32 so you will get stuck at efi shells, bios screen etc)
2. those who took the Lollipop OTA, succeded, but had in time problems (bricked their device) and cannot flash a Lollipop stock rom as they don't have one (not being released by Lenovo/available yet and at least some 830 and 1380 models are in this situation), so they must flash back KitKat stock rom and after take the OTA to Lollipop (and the KitKat flashing part put's them in the same situation as those from p1.)
3. those who tried to take the Lollipop OTA and had problems and they tried to flash KitKat stock rom and yet they are failing (this could be due to problems in the updating while OTA was applied, yet could be that their bios firmware was updated to Lollipop version)
4. those who want to test stuff (going down/up between versions) ... you name it...
how to use it:
1. first download and extract the corresponding tool for your device (830 and 1050 models share the same bios firmware so they have a common tool), while at this you can watch the little attached recording i made with the tool restoring the bios for my 1380F tab so you know what to expect when you run it. USE THE TOOL THAT MATCHES/CORRESPONDS TO YOUR MODEL, you can hard-brick if for eg you use the 1380 one on a 1050 model (didn't even tried but nothing good can happen)
2. place your tab in the DnX mode: power off (by force if you have to), press and hold both VolUp and VolDown butons, keep them pressed, now press Pwr to start and release Pwr when it turns on/buzz (but keep holding pressed Vol buttons), in a few seconds your screen will display "Fastboot starting..." and it will hold on that, now you can release the Vols (you are in DnX mode). you must get that message, try again the whole sequence until you succed, don't move on until you have that "Fastboot starting..." on your screen.
3. run the tool (you must have the intel drivers installed, if you flashed to your tab at some point you should have them already), follow the messages i think it's quite easy and straightforward, in a few minutes you will be done and having a brand new kKitKat bios firmware on your tab
(3) if while running it hangs on the "Preparing to push files..." message, and your tab starts to the whatever error message you had before it means that you already have a KitKat bios (the tool works only with the Lollipop bios firmware) so you don't need to restore the bios, you can flash stock KitKat rom directly (in this scenario the tool doesn't modify anything on your tab)
4. when it finishes the tool will automatically reboot your tablet, leave it for a few seconds to start (it will most likely go ninto some efi shell, or bios screen whatever your old files were) afterwards turn it off (long press Pwr) and that's it
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
i must warn you again, while i tested this tool (i think i moved from KitKat to Lollipop and back at least 20 times and never had any issue with it) you are the only responsible if something bad could happen, this is playing with bios (and any mistake will hard-brick your tab so you will have to send it to a service for fixing). make sure you have enough battery (while i used the tool even when i was with 5% on my battery i would not recommend, i say at least a 30-40%, the process runs only for 2-3 minutes so that should not be an issue). and of course once it started the flashing DO NOT EVEN THINK OF INTERRUPTING! (you could close other software on your PC that maybe can hang your computer while flashing.. you got the point)
Good Luck!
edit: i already have messages about successful bios restoring (as expected no? ) but failing on completing the OTA to Lollipop update after flashing anew the KitKat stock rom. to them and to all of you people who are going to Lollipop from your newly flashed stock KitKat: SET YOUR COUNTRY CODE!!! after you flash back stock kitkaton the first boot input ####6020# in your contacts and a dialog will pop from which you MUST choose a country (no matter which one, preferably yours or a close one), then after the tab reboots for updating the region and comes back to Android check that you have a country code set by entering #### 59930# and it should show the code you chosed. if you take the OTA without a country set you will FAIL! if you failed on your OTA to Lollipop flash anew the stock KitKat rom and set the country code
also do not take an OTA if your device is rooted, always UNROOT first then take the update, and you can root back after or just don't root until you finished the whole Android installing and OTA updates
Click to expand...
Click to collapse
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.

Works perfect! Thanks!

daWyrd1 said:
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Click to expand...
Click to collapse
yeah... the guys at Lenovo deserve a break, they have such a beautiful daadeedaadoo sound on the boot animation (that one cannot even disable it )
bisti2004 said:
Works perfect! Thanks!
Click to expand...
Click to collapse
Pentru putin

Mersi Dorin!

My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?

aerofisher said:
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
Click to expand...
Click to collapse
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting

Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
ionioni said:
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Click to expand...
Click to collapse

aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.

aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
http://bfy.tw/2gNc (just having fun) it is the one that says phone support.
ionioni said:
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
Click to expand...
Click to collapse
Yes, once i talked to them (about 5 minutes) they emailed me all i needed and i just had to find a local fedex dropoff center. They boxed it and i got it back in 6 days.... this seems to be a common thing for them....
Sent from my YOGA Tablet 2-1050F using Tapatalk

Yoga Tab 2 (830, 1050, 1380) - get back to KitKat
You are my lifesaver and I just can not thank you enough @ionioni
how can you make a file like restore-kitkat-bios-1380.zip ??!! you are such a genius !! :good:
We will never be able to flash it back to KitKat Bios without this zip file !! :crying:
But why don't we need to flash it back to Kitkat Bios on my Samsung Note 3, S5, Note 10.1 (2014 version) and Nexus 9 ?!!
thank you very much for your hard work again and keep up the good work pls

this was on my inbox and it should continue publicly maybe others can benefit
KainXSS said:
I'm wondering what your flashing to the tablet with your tool, I have a Lenovo S8-50F and lollipop is pretty abysmal on it, so I'm wondering what your flashing to downgrade the bios so I can try it on the S8, since its very very similar to the 830.
Click to expand...
Click to collapse
you should NOT use the tool unless it is made exactly for your model, or you most likely will hard-brick. moreover Lenovo uses an in-cpu module for digitally checking the authenticity of the firmware you have on your board at pwr on time and even if you have a bios that would work on your model if it is signed with another key it will cause a hard-brick (the measured boot module will refuse to load the IBB in the new bios).
for eg if one writes the 1051 windows variant of bios on the 1050 android one (they are identical in hardware) it hard-bricks (tested).
send me a link to the latest KK stock rom for your device and i will check on it.

That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.

bombolota1 said:
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
Click to expand...
Click to collapse
not so much you can do, the hardware is fine, it just got the wrong firmware in it... somehow you must rewrite the bios but you cannot do that from the outside (ie by software means) without being able to boot at least in DnX mode. you can check quickly ... if after you PwrOn (well.. after you long press Pwr button as at this moment Powered On of Off are werid concepts ) you don't get NOTHING on your display (ye not even the Lenovo -> Powered by Android white/black logo) than that's it (try maybe to see if somehow DnX didn't got hooked by entering a fastboot devices and see if by some miraccle you don't see your device there)
your device must be opened by a repairing service tech (especially if he is on warranty), you could do it yourself (i did) but you need the appropiate tools and know/how otherwise from a hard-bricked yet recoverable (the hardware is ok) you will transform it into just a paper holder

updated kitkat bios restore tool to version 2 (foolproof version). read the main thread post at the beginning.

Good morning.
Please let me introduce my situation. I use Lenovo Yoga tablet 2 Pro. On 9-th of november I updated Android to 5.0.1. Unfortunately, one of my commercial aps now can not make a connection with external device (no appropriate information about USB connection is appeared).
I am affraid the problem lies on the Android 5.0.1 system. Before that everything had worked perfect.
That is way I decided to downgrade to the Androix 4.x.
I found above treads, but have some doubts.
Is above tool downgrade my system to Android 4.x or do I need to do some additional operations, to get back to the Android 4.x?
In the section - how to use it (point 5) we can read:
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
Click to expand...
Click to collapse
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.

pawlikp100 said:
In the section - how to use it (point 5) we can read:
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
Click to expand...
Click to collapse
you must:
1. Downgrade the bios using the restoring tool (you mention "Yoga Tab 2 Pro" so you must use the 1380 version), and you must do that so you can flash KitKat stock rom on your tablet (if you try to flash directly, without the bios downgrade it will fail and you will soft-brick your tablet)
2. After restoring the bios, download from here your stock KitKat rom and extract
3. Flash using Intel Phone Flash Tool (open with it the "flash.xml" from the target_bin directory of the extracted archive). the Intel Tool can be found in the tools directory of the same extracted archive.
4. After you finished sotck KitKat flashing, remember to set your contry code (####6020# in Contacts), also it's not necessary to make your settings wifi etc before you set your country code as they will anyway going to be deleted (a factory reset is performed on country code setting operation). if you don't set a country code you will fail when upgrading to Lollipop.
5. Update using the Lollipop OTA or stay on KitKat

Thank you for explanation.
I download system, installed Phone Flash Tool, open it and chose flash.xml, but after connecting my YT2Pro I can not see device specific with "Start to flash" button in the Device list area of the program.
see below screen. Is this screen looks as it should? (ups, unfortunately I can not post images, because I am new user).
One more thing, tablet should be turned off during flashing?
Right now my tablet is connected to the laptop by USB. It is not switched off and charging is in progress (laptop does not see my tablet as an additional disc/device).
Is above status correct?

Yotaphone 2 yd206 updating issues

Just bought this from Gearbest. It is unrooted. I don't have a "check for system updates" button in Settings,About phone.
1. Is there a way of enabling this or will OTA update happen automatically?
2. I have read about manually updating with the yotaphone flasher utility but some of the posts here are scaring me off. Has anyone successfully flashed the EU firmware onto this phone using the flasher?
Thanks
John

HI, I had the same with my phone from tinydeal.
You can update it manually, but prepare to lose all you data if you don't have it backed up in some way.
Also, you need to be sure that you are prepared to try again and mess around a little if it does not work. As far as i've read nobody has actually hardbricked the device by trying to flash it.
My advise would be to download the latest firware via the yotaflasher, whichever you like but rename the radio folder in the firmware folder in the yotaflasher folder so the radio part just stays the same, this worked for me.
then choose flash the firmware in the yotaflasher tool and when it asks to flash userdata, you better press yes, otherwise it will probably bootloop, but so this also means EVERYTHING on your device is deleted
Greets and good luck!
Jblessing said:
Just bought this from Gearbest. It is unrooted. I don't have a "check for system updates" button in Settings,About phone.
1. Is there a way of enabling this or will OTA update happen automatically?
2. I have read about manually updating with the yotaphone flasher utility but some of the posts here are scaring me off. Has anyone successfully flashed the EU firmware onto this phone using the flasher?
Thanks
John
Click to expand...
Click to collapse

tomgaga said:
HI, I had the same with my phone from tinydeal.
You can update it manually, but prepare to lose all you data if you don't have it backed up in some way.
Also, you need to be sure that you are prepared to try again and mess around a little if it does not work. As far as i've read nobody has actually hardbricked the device by trying to flash it.
My advise would be to download the latest firware via the yotaflasher, whichever you like but rename the radio folder in the firmware folder in the yotaflasher folder so the radio part just stays the same, this worked for me.
then choose flash the firmware in the yotaflasher tool and when it asks to flash userdata, you better press yes, otherwise it will probably bootloop, but so this also means EVERYTHING on your device is deleted
Greets and good luck!
Click to expand...
Click to collapse
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?

Jblessing said:
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Click to expand...
Click to collapse
Nice to hear, and well you can probably het some support but I bet it will be rather useless anyways

Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but
---------- Post added at 01:29 AM ---------- Previous post was at 01:25 AM ----------
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but yotaflasher stills waiting device and the phone says cannot load volume/misc!
Now send the package to applyto the device with adb sideload(filename)
What must I have to do?????

pedropicapiedra1 said:
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but
---------- Post added at 01:29 AM ---------- Previous post was at 01:25 AM ----------
Hi I tried to do this but when I put the phone in android recovery there are four options...reboot,apply update from adb,wipe data factory reset,and wipe cache partition,I think the correct option would be 2,apply update,but yotaflasher stills waiting device and the phone says cannot load volume/misc!
Now send the package to applyto the device with adb sideload(filename)
What must I have to do?????
Click to expand...
Click to collapse
You don't need to put your phone into Android recovery mode to flash. Just hold power and volume down until your phone displays Downloading... Now run YotaFlasher on your PC to flash your phone with the firmware you like.

stuck after tried flash
I ran into trouble when trying to flash my new Yotaphone2: After the flash-process (really quick) the yotaflash-software asked if I wanted to flash user-partition also (or sometihng to that extent). I answered "no". Now the phone seems stuck, only showing "powered by android". I read all the posts, but could find no solution. Fastboot does not find the phone. I can not power it off using any buttons, so I cannot put in in the flash-mode.
Any ideas what I can do?

klettervirus said:
I ran into trouble when trying to flash my new Yotaphone2: After the flash-process (really quick) the yotaflash-software asked if I wanted to flash user-partition also (or sometihng to that extent). I answered "no". Now the phone seems stuck, only showing "powered by android". I read all the posts, but could find no solution. Fastboot does not find the phone. I can not power it off using any buttons, so I cannot put in in the flash-mode.
Any ideas what I can do?
Click to expand...
Click to collapse
It's a common problem. Try this:
- Put your phone in download mode. Just keep holding power and volume down, it will get there eventually.
- Use the YotaFlash tool to flash the latest EU or RU firmware, whichever you like.
- After YotaFlash is finished your phone will reboot and still be in a bootloop
- Put your phone in download mode again. Just keep holding power and volume down.
- Now go into the command prompt on your computer and navigate to the YotaFlash folder (for me it is in C:\Program Files (x86)\yotaphone_flasher)
- Now type the following command with your phone still in download mode: fastboot flash -S 512M system firmware/system.img This will flash the failed system.img in multiple parts.
- After the flashing of the system partition is finished reboot your phone with the command: fastboot reboot
After this your phone will restart. It may take around 10 minutes to finish and if everything went right the Android unlock screen should appear.

Finally did work. Thanks a million! What helped was pushing power off and volume up, that brought up a menu where i could select to bring up "downloading" screen. You are the best, thank you!

What I learned today about being stuck in loops -
1. Bootloop - to exit a bootloop, press up volume and on button simultaneously to enter recovery mode. DO this until you arrive at the Android symbol, normal after 2 cycles, up to 2 minutes. You are then presented with a few options (select with on button), since you are flashing, normally you would go to bootloader mode "downloading" , then change the firmware (usually a zip) file.
This is method employed in the post just above.
2 The second is stuck at Yotaphone logo at beginning. Have you waited long enough ? Be patient, maybe it is still installing , allow 10 minutes before you try the following method . To break out of the stuck at Yotaphone logo, enter the bootloader mode , by pressing the on button and volume down button simultaneously. You cannot enter recovery mode as in point 1 above. This method will restart the phone. After the reboot starts, quickly hold down the volume up (only) button before the short "buzz" then you will enter recovery mode. You only have a few seconds to do this. In recovery mode you can delete the cache , user data or reboot but not enter bootloader mode.

still stuck in
VirtuaLeech said:
It's a common problem. Try this:
- Put your phone in download mode. Just keep holding power and volume down, it will get there eventually.
- Use the YotaFlash tool to flash the latest EU or RU firmware, whichever you like.
- After YotaFlash is finished your phone will reboot and still be in a bootloop
- Put your phone in download mode again. Just keep holding power and volume down.
- Now go into the command prompt on your computer and navigate to the YotaFlash folder (for me it is in C:\Program Files (x86)\yotaphone_flasher)
- Now type the following command with your phone still in download mode: fastboot flash -S 512M system firmware/system.img This will flash the failed system.img in multiple parts.
- After the flashing of the system partition is finished reboot your phone with the command: fastboot reboot
After this your phone will restart. It may take around 10 minutes to finish and if everything went right the Android unlock screen should appear.
Click to expand...
Click to collapse
still stuck in "waiting for device" and my phone is still in dowlaoding mood. please help.

To exit downloading mode , press the yotaphone ”on/off" button for about 30 seconds . It will restart in normal mode.
You have incorrect "adb composite" drivers and your phone is not communicating with your PC. Try to get rid of any bad adb drivers in device manager on your PC.

where to get ypflasher from?
Jblessing said:
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Click to expand...
Click to collapse
where can i download the ypflasher/yotaflasher from? the yota official website no longer have it available for download! at least the downloaded zip file is empty?
thanks. in advance
Basem

basemaggad said:
where can i download the ypflasher/yotaflasher from? the yota official website no longer have it available for download! at least the downloaded zip file is empty?
thanks. in advance
Basem
Click to expand...
Click to collapse
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/

kophyo07 said:
still stuck in "waiting for device" and my phone is still in dowlaoding mood. please help.
Click to expand...
Click to collapse
go to yotaflasher folder (usually under programme files) and ensure that the individual files of the firmware you want to install are there and not zipped!

VirtuaLeech said:
- Now go into the command prompt on your computer and navigate to the YotaFlash folder (for me it is in C:\Program Files (x86)\yotaphone_flasher)
Click to expand...
Click to collapse
Hi well I have reached this point too but how to I ascertain the address to enter? Yes, yotaphone_flasher in in \Program Files but I'm told that C:\Program is not a valid command... Sorry I know this is basic PC computing 101 but after hours of trawling the net I am none the wiser. I am running XP. How can I see what the file path would be? Apparently there is a helpful utility to bring up the file path in the command prompt but of course it has been deleted because XP is no longer supported...

nutsoboy said:
I'm told that C:\Program is not a valid command... Sorry I know this is basic PC computing 101 but after hours of trawling the net I am none the wiser.
Click to expand...
Click to collapse
Did you try "cd Program Files"?
Make sure you are in the root directory C:\ (type "cd.." to go one level back through the hierarchy)
then type "cd Program Files\yotaphone_flasher" (if that is your folder path)

Jblessing said:
Thanks. I took the plunge and ran yotaflasher, downloaded the latest EU firmware and flashed the phone. It all went well, though after reboot there was a worrying 5 minutes as it stayed on the Yotaphone logo. Rebooted fine into lollipop and "about phone" now shows it as YD201. I didn't bother renaming the radio part of the firmware and, so far, it seems no worse or better than before flashing.
The system update option became available and it immediately downloaded the latest OTA update. All looks good so far.
I had contacted yotaphone support before I flashed the new firmware and they told me that as it was the Chinese version, there was no international support. I wonder if now it is showing as model yd201 whether I would get support ?
Click to expand...
Click to collapse
Hey,
Facing the exact issue of not being able to see the update option!
Planing to take the plunge my self but am a bit skeptical about the lollipop update. On facebook yotaphone page ppl have been complaining a lot about the lollipop update slowing down the phone and lot many other issues.
If I could get a little review from your side it would be very help full.
If there are any issues?
If so what are they?
Are they worth taking?
should I stick to kitkat?
ETC

tnautanki said:
Hey,
Facing the exact issue of not being able to see the update option!
Planing to take the plunge my self but am a bit skeptical about the lollipop update. On facebook yotaphone page ppl have been complaining a lot about the lollipop update slowing down the phone and lot many other issues.
If I could get a little review from your side it would be very help full.
If there are any issues?
If so what are they?
Are they worth taking?
should I stick to kitkat?
ETC
Click to expand...
Click to collapse
I have had no issues with lollipop, doesn't seem any slower or battery guzzling than kitkat

Jblessing said:
I have had no issues with lollipop, doesn't seem any slower or battery guzzling than kitkat
Click to expand...
Click to collapse
Same for me. Battery is good and I have no problem.

[GUIDE] Unlock Verizon OnePlus 8 5G UW (IN2019) bootloader

Disclaimer​While I will assist with any issues resulting from this guide, I disclaim all responsibility and cannot be held accountable for any consequences caused by the use or misuse of this tool or process. This method also will wipe your phone, so please back up your data. I also will disclaim any understanding as to why exactly this works, since this method was developed by someone else, I am just listing the instructions on how to use it. With that being said, understand your personal limits and read this entire guide before starting.
Preface​I have seen dozens of posts asking for a Bootloader unlocking method for the OnePlus 8 5G UW (IN2019) and thanks to the attributed users at the end of this post, a method has been found. I will document the most straightforward way to unlock the bootloader here so you can install custom OSes, TWRP, and Magisk.
Part I: Prerequisites and initial setup​To follow this guide you will need
A Windows PC (running 7+)
Latest MsmDownloadTool and stock firmware for the OnePlus IN2019 - Link
OnePlus 8 IN2019 with latest stock software update and USB cable
Latest version of platform-tools - Link
The bootloader unlock.ops file - Link
Plug your phone into your PC using a USB 2.0 port (this is important, USB 3.0 has given me a lot of issues and just doesn’t seem to work all the time) and ensure USB debugging is enabled.
Extract the downloaded platform-tools zip and open the platform-tools folder in a command prompt, and Run adb devices and makes sure your device appears in the list.
Next, extract the OnePlus_8_Verizon_OxygenOS_11.0.zip and open up the MsmDownloadTool V4.0.exe inside the instantnoodlev_15_O.01_210110 folder.
When the application opens, select “Others” under the User type dropdown and hit next. Leave this window and the platform-tools command prompt open.
Spoiler: Command Prompt
{
"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"
}
Spoiler: MsmDownloadTool setup
Part II: Entering Qualcomm EDL mode and installing correct QDLoader Driver​In this section we will install the correct drivers to utilize Qualcomm's Emergency Download (EDL) mode. When you are in EDL mode, your phone screen will be completely black and it will only exit if you complete a flash or unplug it from your PC and hold volume up, volume down and power. To enter EDL mode from a powered off state, hold volume up and volume down and connect your phone to your PC.​1. Return to the platform-tools command prompt, and type adb reboot edl and wait. Your phone should disconnect from the computer and then reconnect.
2. Open Device manager, and check for the device “Qualcomm HS-USB QDLoader 9008” or “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” - if you see “Qualcomm HS-USB QDLoader 9008” under Ports (COM and LPT), skip to part III. If you see “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” under Other Devices with a yellow triangle, then proceed to step 3.
Spoiler: QUSB_BULK_CID:xxxx_SN:xxxxxxxx (Proceed to Step 3)
Spoiler: Qualcomm HS-USB QDLoader 9008 (Skip to Part III)
3.
Spoiler: Windows 11
Open Settings, Go to Windows Update and Check for updates. After, Click Advanced options, Optional Updates and drop down “Driver Updates” Locate “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” in the list, and install it.
Spoiler: Windows 10
On Windows 10 - Open Settings, Go to Update & Security, Check for updates, Click “View Optional Updates” and select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager.
Spoiler: Correctly Installed Driver
Part III: Flash Stock Firmware​In this section, we will flash the stock IN2019 Android 11 firmware. If you have any trouble with this process refer to the original guide on how to do this here.​1. Return to MsmDownloaderTool and hit the Enum button. In the list, it should list the COM Port associated with the device. The status of connection should read “Connected”
Spoiler: MsmDownloadTool Connected
2. Click the “Start” button. This will flash the stock firmware, wiping your data. Make sure you have backed your data up at this point. It will take a few minutes, usually ~300 seconds. Once it completes, it will reboot into factory default android.
3. Close MsmDownloadertool and once you are back to android, unplug your phone and power it off.
Part IV: Unlock the bootloader​In this section, we will flash the unlockable firmware and unlock the device for good.​1. Inside the directory with MsmDownloaderTool V4.0.exe, there should be a file called “instantnoodlev_15_O.01_210110.ops”. Remove it from the directory, either by deleting it or moving it to another folder. Then take the unlock.ops file downloaded earlier, and drag it into the directory. It should be in the same folder as MsmDownloaderTool.
Spoiler: Directory before unlock.ops
Spoiler: Directory after unlock.ops
2. Reopen MsmDownloaderTool V4.0.exe and like before, select “Others” in the drop down, and click next. Leave the window open.
3. Hold in the Volume up and down buttons, then plug your phone back in. Keep holding the buttons until your phone connects to your PC as "Qualcomm HS-USB QDLoader 9008", like before. Check device manager to ensure that it’s connected correctly as a COM port. If it boots to android, power it off and try again.
4. Return to MsmDownloaderTool and click Enum. Make sure the phone is still displayed in the list under the associated COM Port.
5. Click start. The flashing should take about 15 seconds, and when complete, your phone should restart. It will display a message at boot saying “<!> The device is corrupt..” Do not panic, this is normal.
6. Unplug your phone and hold Volume Up, Volume Down and Power until the device reboots and let go once it shows the OnePlus Logo and “Fastboot Mode”. You should arrive at a screen that has “Start” in big green letters at the top, and “Fastboot mode” below it, with the very last item saying “Device state - Locked” in red text.
7. Plug your phone back into your computer, and open device manager. Look for the “Kedacom USB Device” category with “Android Bootloader Interface” under it. If this device is present, skip to step 9. If this device is not, proceed to step 8.
8. Go back to Windows Update, Check for updates again, go into Optional Updates and install “Google, Inc. - Other hardware - Android Bootloader Interface”
Spoiler: Optional Driver
Check device manager to ensure “Android Bootloader Interface” is present under Kedacom USB Device.
Spoiler: Kedacom USB Device
9. Return to your command prompt window open in platform-tools, and run fastboot devices and ensure your device is in the list.
10. Finally, run the command fastboot flashing unlock and on your phone, it should prompt you to confirm unlocking the bootloader. Once complete, it should reboot into Android.
11. Shut the phone off again, and then Hold Volume Up, Volume Down, and Power and let go when the OnePlus logo and “Fastboot mode” shows up on screen. If the final item in the list says “Device State - Unlocked”, Congrats! You have successfully unlocked your bootloader. You can follow your custom OS’s installation guide from here.
Part V: Troubleshooting, Notes, and Attributions​
Spoiler: If your MSM tool gets stuck on "Sahara communcation failed" when trying to flash.
Unplug your phone, and hold Power, Volume Up, and Volume Down. It should reboot into fastboot mode. Using the volume keys, navigate to the "Power off" option and hit the power button to confirm. Then holding Volume Up and Down, plug your phone back into your PC and try flashing again.
Any attempt to use MsmDownloadTool after the unlock will cause the device
to become locked again. You can unlock again by repeating the steps above.
Attempting the unlock process while running android 10 will result in a
crash at bootup. Update your phone to the latest update before starting.
USB 3.0 has thrown some obtuse errors when trying to use this process, so I highly recommend using a USB 2.0 port if possible.
If you want to flash back to stock firmware again (relock bootloader), you have to first flash this file (stock.ops) and then flash the bundled stock firmware. It will give a mismatch error if you do not.
You can only have one .ops file in the MsmDownloadTool directory at a time. You'll get an error if there are multiple files.
If for some reason, you run into an issue or skip a step by accident, leave a comment and I will try to help as much as possible. This is my first XDA guide and I just wanted to compile something that would have saved me hours of trial and error.
Attributions:​@Whoareyou for providing the method and unlock.ops to me originally. He pretty much got the ball rolling for me.
@retryfail / https://retry.abort.fail for creating the unlock.ops and providing the original guide, this would absolutely not be possible without his work.
@Some_Random_Username for the MsmDownloadTool tutorial and resources.
https://onepluscommunityserver.com (hosted by Votton, maintained by @Some_Random_Username and AnonymousWP) for providing the stock firmware and MsmDownloadTool

The unlock.ops link doesn't work?!?

7eregrine said:
The unlock.ops link doesn't work?!?
Click to expand...
Click to collapse
It does. If you already have Android 11, just save and store your phone data, factory reset, boot into EDL, connect and start the tool. If it runs an error, DONT stop the download. Press the POWER + VOLUME UP + VOLUME DOWN buttons at the same time and hold it until it reconnects. It takes a few seconds. Once it reconnects you should see it fully load. I didn't see the need for stock firmware file unless I needed to reflash my stock after ****ing up (I bricked it once or twice), and tbh it's not even the one I used to reset my phone. I just unlocked my BL a few hours ago. It works, I promise

7eregrine said:
The unlock.ops link doesn't work?!?
Click to expand...
Click to collapse
Right click the link and open in new window, than refresh the blank page it opens. That will trigger the download.

GloomyHat14 said:
It does. If you already have Android 11, just save and store your phone data, factory reset, boot into EDL, connect and start the tool. If it runs an error, DONT stop the download. Press the POWER + VOLUME UP + VOLUME DOWN buttons at the same time and hold it until it reconnects. It takes a few seconds. Once it reconnects you should see it fully load. I didn't see the need for stock firmware file unless I needed to reflash my stock after ****ing up (I bricked it once or twice), and tbh it's not even the one I used to reset my phone. I just unlocked my BL a few hours ago. It works, I promise
Click to expand...
Click to collapse
Did you follow the guide while unlocking your bootloader and if so, do you have any feedback for the guide? This is my first guide so I just wanted to hear any potential criticism.

Mason220 said:
Did you follow the guide while unlocking your bootloader and if so, do you have any feedback for the guide? This is my first guide so I just wanted to hear any potential criticism.
Click to expand...
Click to collapse
It worked for me. It was straightforward, and it was really easy to figure out. I kept getting an error during the parameter update when I used the included firmware, so I just flashed the Unlock.ops file and carried on. I had a dumb moment bc I didnt actually read it fully at first, so I freaked out and thought that I'd bricked it lmao. But all in all, it was good man. Good instructions, and you gave examples that helped me out when I was confused. Good job! Well worth the wait

This replaces the VZW abl/xbl with ones from one of the unlockable variants? Impressive that it works this way...

AndyYan said:
This replaces the VZW abl/xbl with ones from one of the unlockable variants? Impressive that it works this way...
Click to expand...
Click to collapse
From my understanding, it messes with the param essentially tricking the phone into thinking it's not from Verizon.

Mason220 said:
From my understanding, it messes with the param essentially tricking the phone into thinking it's not from Verizon.
Click to expand...
Click to collapse
Fantastic! Actually I have a OnePlus 8 T-mobile. Did you modify the Msmdownloadtool to allow this process going? Can you help allow msmdownloadtool to flash global roms to the T-mobile/ Verizon variant so that we maybe can unlock the second sim function?

dlhxr said:
Fantastic! Actually I have a OnePlus 8 T-mobile. Did you modify the Msmdownloadtool to allow this process going? Can you help allow msmdownloadtool to flash global roms to the T-mobile/ Verizon variant so that we maybe can unlock the second sim function?
Click to expand...
Click to collapse
The MsmDownloadTool did not need to be modified at all, you just had to swap the included .ops file (Stock firmware) with the unlock.ops in the directory, and it'll flash it on. As for the second question, I'm not really sure how I could help. If really would like my help, I'd be happy to assist, just contact me on Discord (Mason.#6969) or Telegram (message me on xda and i'll give it to you).

Thanks guys. I'll be trying this soon.

7eregrine said:
Thanks guys. I'll be trying this soon.
Click to expand...
Click to collapse
Please share your findings when you are successful.

Does this process replace verizon rom with global stock rom?

Does this process replace verizon rom with global stock rom?
I am on OnePlus 8 5G UW (Verizon) using a different network operator.

Zombify01 said:
Does this process replace verizon rom with global stock rom?
I am on OnePlus 8 5G UW (Verizon) using a different network operator.
Click to expand...
Click to collapse
No. It just unlocks the bootloader so installing a different ROM is possible. What you install is up to you.

Mason220 said:
No. It just unlocks the bootloader so installing a different ROM is possible. What you install is up to you.
Click to expand...
Click to collapse
+1

is there any way to change from verizon rom to global rom..?

Can we use with another Sim when flashed custom Rom?? Anyone know??

nhonpiseth said:
Can we use with another Sim when flashed custom Rom?? Anyone know??
Click to expand...
Click to collapse
Yes. As long as your device is unlocked (60 days after initial purchase from Verizon) then it will work with any SIM.

Royk504 said:
is there any way to change from verizon rom to global rom..?
Click to expand...
Click to collapse
I did this while trying to get the camera working. I think you can flash the global rom using the stuff from this guide