Database Users

[Q] Problem updating Lenovo Yoga 2 10"

Hey there
Today I got a message that I could update my Yoga 2 Tablet via the System Updater, but it doesn't quite work.
First of all about the device:
Lenovo Yoga 2 Tablet 1050F
Running current version: YT-1050F_USR_S0000198_1504220313_WW21_ROW
New version I wanna update to: YT2-1050F_USR_S1000031_1506111400_WW52_ROW
The problem:
I can download the update and when I press the install button, the tablet reboots into recovery mode. The update process begins and reaches 100% pretty quickly. After some time, it says the update failed though.
What I tried so far:
Downloading and updating again, it didn't work.
Download and starting the update on my PC with Lenovo Smart Assistant, didn't work.
Change the country code with the easyimage.zip file and the ####6020# code. I changed it to de (which is my usual country code) and us, but both did not help with the software update.
So... I really do not have any knowledge about android and can't seem to find another clue what to do next. Maybe someone of you can help me with this issue.

bjorr said:
Hey there
Today I got a message that I could update my Yoga 2 Tablet via the System Updater, but it doesn't quite work.
First of all about the device:
Lenovo Yoga 2 Tablet 1050F
Running current version: YT-1050F_USR_S0000198_1504220313_WW21_ROW
New version I wanna update to: YT2-1050F_USR_S1000031_1506111400_WW52_ROW
The problem:
I can download the update and when I press the install button, the tablet reboots into recovery mode. The update process begins and reaches 100% pretty quickly. After some time, it says the update failed though.
What I tried so far:
Downloading and updating again, it didn't work.
Download and starting the update on my PC with Lenovo Smart Assistant, didn't work.
Change the country code with the easyimage.zip file and the ####6020# code. I changed it to de (which is my usual country code) and us, but both did not help with the software update.
So... I really do not have any knowledge about android and can't seem to find another clue what to do next. Maybe someone of you can help me with this issue.
Click to expand...
Click to collapse
I posted the same issue already within the root thread. My device is rooted and after the download it started to upgrade and after reaching 100% it says it failed. I even did a factory reset - but SuperSu stays present and no upgrade is possible. I do not want to flash it via flashify - as bricking might be possible with that methode.
Maybe anyone has an idea how to proceed!?

Thanks for the reply.
I forgot to mention, my tablet isn't rooted and I tried a factory reset aswell, but nothing worked.
/E: So if anyone has the same problem: The solution is to flash the tablet to stack rom with PhoneFlashTool and update it afterwards. No problems since.

I flashed to stock rom downloaded from Russian Site with Phoneflashtool and tried to update. Update went to 100% then "failed". Any ideas anyone?

bowyerv said:
I flashed to stock rom downloaded from Russian Site with Phoneflashtool and tried to update. Update went to 100% then "failed". Any ideas anyone?
Click to expand...
Click to collapse
You missed presumably one important step after flashing the original rom, changing the country code prior OTA - which was posted already in another thread:
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update

Thanks. Will give that a go.
/E After the above it now tells me that I already have the latest version at YT2-1050F_USR-S000198_1504220313_WW21_ROW and that there is no update. Surely they have not taken the update offline??!
/EE I used the Update.zip I had previously downloaded (when the update first failed).
Placed this on the SD card and installed it via the update tools.
Thank you for those who helped me

Is there any chance You can upload this update.zip file? Thanks

Link to Lollipop Update.zip for YT2-1050F
worek555 said:
Is there any chance You can upload this update.zip file? Thanks
Click to expand...
Click to collapse
The storage I use wont let me link to my uploaded file! I have provided you the link by PM

Exactly the same problem. The ####6020# not work. Before m'y tablette was rooted but now after flash with easyimage, the stock ROM is OK but no update. I'm verry disapointed. Can you help me?
Thanks

1050F. Update fails.
Hi people, new guy here. I got redirected by some friendly dude.
Anyway, I apparantly have the same problem. Device has never been rooted. Tried the update as is, tried after a factory reset, tried #### contact hocus pocus, did not try anything involving a PC since I don't have one with that still has Windows and I can't seem to figure out Wine dependencies on my Debian box.
So, yeah, I guess I'll call the 1 euro a minute Lenovo support desk now. :laugh:
Anyway, thanks for having me, I'm subscribed to the thread . If I find out something before you guys do I'll let you know, but by all means don't stay up for it.

AgentAmsterdam said:
Hi people, new guy here. I got redirected by some friendly dude.
Anyway, I apparantly have the same problem. Device has never been rooted. Tried the update as is, tried after a factory reset, tried #### contact hocus pocus, did not try anything involving a PC since I don't have one with that still has Windows and I can't seem to figure out Wine dependencies on my Debian box.
So, yeah, I guess I'll call the 1 euro a minute Lenovo support desk now. :laugh:
Anyway, thanks for having me, I'm subscribed to the thread . If I find out something before you guys do I'll let you know, but by all means don't stay up for it.
Click to expand...
Click to collapse
I run Arch on all my machines. I was able to use my virtualbox windoze 8.1 (It came on my laptop but never booted it... ) vm to use the intelphonetool. I flashed this stock rom here and then took the ota lollipop update. If you want to root this works in Linux.
BTW... temporary Windows vm's can be found here

Guichinga said:
I posted the same issue already within the root thread. My device is rooted and after the download it started to upgrade and after reaching 100% it says it failed. I even did a factory reset - but SuperSu stays present and no upgrade is possible. I do not want to flash it via flashify - as bricking might be possible with that methode.
Maybe anyone has an idea how to proceed!?
Click to expand...
Click to collapse
Guichinga said:
You missed presumably one important step after flashing the original rom, changing the country code prior OTA - which was posted already in another thread:
If system update fails do the following:
1. Flash stock firmware
2. Optionally you can wipe user data (I never did that) from DROIDBOOT
3. Go to contacts manager. Create some dummy contact if list is empty.
4. Go to Search / Find Contacts and enter ####6020#. It will ask you to select country code (first two latin letters, ignore Chinese).
5. Select what you want, then reboot.
6. Go to System Update
7. Install OTA update
Click to expand...
Click to collapse
workdowg said:
I run Arch on all my machines. I was able to use my virtualbox windoze 8.1 (It came on my laptop but never booted it... ) vm to use the intelphonetool. I flashed this stock rom here and then took the ota lollipop update. If you want to root this works in Linux.
BTW... temporary Windows vm's can be found here
Click to expand...
Click to collapse
i have same problem and i don`t know what can i do

semsem81 said:
i have same problem and i don`t know what can i do
Click to expand...
Click to collapse
I don't know which problem you have...
Rooted and go back to stock to take OTA?
Return to stock KK firmware - Yoga Tablet 2 1050F
1) Download - This - AFH - kitkat-YT2-1050F_S0198_150422_ROW.7z
2) Extract the zipfile to a directory on PC somewhere
3) Goto "tools" folder and install the exe's in this order
__a)PhoneFlashTool_4.4.4.1_external_win32.exe
__b)iSocUSB-Driver-Setup-1.2.0.exe
__c)IntelAndroidDrvSetup1.5.0.exe
4) Start PhoneFlashTool and select settings (Upper left corner)
5) Tick "force sparcing" and change size to 500mb
6) Power off tablet and connect with usb
7) From off, hold volume up and power until tablet vibrates and release power (still holding volume up)
8) Tablet should now be in "Droidboot" and PhoneFlashTool should list it on the top
9) In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
10) WAIT!!! until you see "Result okay" on tablet AND "Flash Sucess" in PhoneFlashTool
11) Reboot
12) When Android starts skip all dialogs (tablet is going to factory reset anyway)
13) Select Contacts from desktop and make 1 dummy contact
14) In the search bar type "####6020#" and then select your country
15) Tablet reboots and you are on stock KitKat again and should receive an update notice for Lollipop
Click to expand...
Click to collapse
Stuck on bios after FAILED Lollipop to Kitkat downgrade?
Repair Lollipop to KitKat bios error
1) Get the firmware kitkat-YT2-1050F_S0198_150422_ROW.7z - https://www.androidfilehost.com/?fid=24052804347778640
2) Extract the firmware on PC
3) Download LtoKKxml.7z - https://www.androidfilehost.com/?fid=24052804347783496
4) Extract or copy the content of this zip to where you extracted the firmware, so that the flash_*.xml are located next to all the image files of the firmware
5) Edit the file flash-LtoKK_PVT_810.xml and remove the the "command" tags which contain "format data" and "erase data" (the XML tag from <command> to </command>)
6) Reboot your tablet into fastboot mode (hold power up, down and power buttons)and use PhoneFlashTool to flash this flash-LtoKK_PVT_810.xml
7) Wait for it to finish and when the tablet restarts make sure it goes back to fastboot. If not then power off and restart into fastboot
8) Flash the flash.xml which is located in the folder. This will flash all the KitKat firmware components. That's it.
Be careful if you do something wrong then a brick is very likely. Hope this helps
Originally posted by [email protected]
These are links to other variant firmwares (not my hosting):
830F: YT2-830F_S0195_150422_ROW.7z - https://cloud.mail.ru/public/Z2US9gd6f2ei/YT2-830F_S0195_150422_ROW.7z
830L: YT2-830L_S0209_150422_ROW.7z - https://cloud.mail.ru/public/2hrDmzneLDLY/YT2-830L_S0209_150422_ROW.7z
1050L YT2-1050L_S0225_150422_ROW.7z - https://cloud.mail.ru/public/2GFji3ub9JdG/YT2-1050L_S0225_150422_ROW.7z
1380L YT2 -1380L_S0216_150428_ROW.7z - https://cloud.mail.ru/public/CGZs/Nt8NE1pit
1380F YT2-1380F_S0219_150428_ROW.7z - https://cloud.mail.ru/public/8s5Q/dfuSXn7oi
Click to expand...
Click to collapse
Root Lollipop or Kitkat?
Root Lollipop or Kitkat on 1050F - 8/4/2015
Windows PC:
Thread by [email protected] - http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
Lollipop - Trigger 4
Kitkat - Trigger 3
Linux PC:
Thread by [email protected] - http://forum.xda-developers.com/showpost.php?p=61067755&postcount=1
Lollipop - Trigger 4
Kitkat - Trigger 3
Click to expand...
Click to collapse

workdowg
I don't know which problem you have...
My device is rooted and after the download it started to upgrade and after reaching 100% it says it failed. I even did a factory reset
i don't know how to flash firmware and i wanna to update to 5.0
my device is yoga tablet 2-1050L

Deleted. Will update
---------- Post added at 02:34 PM ---------- Previous post was at 02:30 PM ----------
semsem81 said:
workdowg
I don't know which problem you have...
My device is rooted and after the download it started to upgrade and after reaching 100% it says it failed. I even did a factory reset
i don't know how to flash firmware and i wanna to update to 5.0
my device is yoga tablet 2-1050L
Click to expand...
Click to collapse
I'll post files for you. You were able to root your device, so I'm sure you can handle flashing back to stock. I need to sleep right now before work.
Sent from my YOGA Tablet 2-1050F

workdowg said:
Deleted. Will update
---------- Post added at 02:34 PM ---------- Previous post was at 02:30 PM ----------
I'll post files for you. You were able to root your device, so I'm sure you can handle flashing back to stock. I need to sleep right now before work.
Sent from my YOGA Tablet 2-1050F
Click to expand...
Click to collapse
thx for ur replay but i don't have experience to flashing stock and i rooted my device with luck
so its okay you can go to sleep and sorry to bother you

Some info, probably well known, but have a question about it.
Hi,
I found a folder 'lenovoota' om my tablet. It contains a file called YT2-1050F_USR_S000198_1504220313_WW21_ROW_TO_YT2-1050F_USR_S100067_1507101258_WW52_ROW.zip
and one called packages.xml.
Both can't be opened / are corrupt. 0 bytes each.
So, correct me if I'm wrong, the update fails at download already, right? Would it be of any use to get these two files somewhere and replace the corrupted ones, then trigger the updating process again? Or is that a bit optimistic?
Thanks.
I'm a bit reluctant about the instructions above btw. I know what's what, but, you know, *very* old machine running debian, not sure how VM would perform. Apart from that I am certainly going to be overly focussed on getting the details right and brick my tablet by forgetting a whole major step or something. THanks anyway, though, appreciate the effort.
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
AgentAmsterdam said:
Hi,
I found a folder 'lenovoota' om my tablet. It contains a file called YT2-1050F_USR_S000198_1504220313_WW21_ROW_TO_YT2-1050F_USR_S100067_1507101258_WW52_ROW.zip
and one called packages.xml.
Both can't be opened / are corrupt. 0 bytes each.
So, correct me if I'm wrong, the update fails at download already, right? Would it be of any use to get these two files somewhere and replace the corrupted ones, then trigger the updating process again? Or is that a bit optimistic?
Thanks.
I'm a bit reluctant about the instructions above btw. I know what's what, but, you know, *very* old machine running debian, not sure how VM would perform. Apart from that I am certainly going to be overly focussed on getting the details right and brick my tablet by forgetting a whole major step or something. THanks anyway, though, appreciate the effort.
Click to expand...
Click to collapse
EDIT: ah wait I think I get it, the row / version thing. I'll check my current version and see what the linux thread has to offer...

AgentAmsterdam said:
Hi,
I found a folder 'lenovoota' om my tablet. It contains a file called YT2-1050F_USR_S000198_1504220313_WW21_ROW_TO_YT2-1050F_USR_S100067_1507101258_WW52_ROW.zip
and one called packages.xml.
Both can't be opened / are corrupt. 0 bytes each.
So, correct me if I'm wrong, the update fails at download already, right? Would it be of any use to get these two files somewhere and replace the corrupted ones, then trigger the updating process again? Or is that a bit optimistic?
Thanks.
I'm a bit reluctant about the instructions above btw. I know what's what, but, you know, *very* old machine running debian, not sure how VM would perform. Apart from that I am certainly going to be overly focussed on getting the details right and brick my tablet by forgetting a whole major step or something. THanks anyway, though, appreciate the effort.
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
EDIT: ah wait I think I get it, the row / version thing. I'll check my current version and see what the linux thread has to offer...
Click to expand...
Click to collapse
Yes, it shows as 0 bytes when it fails.
I captured the OTA file from the 1050F. It is usable only on a non-rooted stock device and those devices should take the OTA successfully anyway... But it had the files I needed to repair the bios error from trying to downgrade from Lollipop to KitKat.
And I feel your pain with using a VM. My laptop is pretty new and I have my OEM copy of Windows on an external SSD so it works good enough.
I tried to port the Linux version of the Intel Phone Tool to Arch and it fails because of Ubuntu specific depens. You could certainly try it. If you get it installed and it see's your tablet you should be good. Let me know if it works.
See this thread: http://forum.xda-developers.com/thinkpad-tablet/general/how-to-one-guide-yoga-tablet-2-t3174597

workdowg said:
Yes, it shows as 0 bytes when it fails.
I captured the OTA file from the 1050F. It is usable only on a non-rooted stock device and those devices should take the OTA successfully anyway...
Click to expand...
Click to collapse
Well, mine is unrooted and it still fails... Ill check out that thread.

Hi there
So, im here because i got problem with my Yoga 2 10" 1050L
Well, i was trying to update my Yoga to 5.0.1 but my tablet says that there is no update.
I was tryin to use Lenovo Smart Assistant - same, no update.
Then i do hard reset (power button + vol+), fresh install, and... kitkat do not recognize any new updates to lollipop.
Then i contact with Lenovo Poland, they was tryin to turn on update from servers for my device - nothing happens.
I got 2 devices, both from Poland, second one (i got two same Yogas, both 1050L) is running 5.0.1 without any problems (it update itself instantly after 1st boot).
So, what can i do now?! Is it any possibilities to get update *.zip file from anywhere, to do it manualy from settings menu in tablet?
Sorry for my bad english, its still not my main )

So, the YotaPhone 2 is officially dead?

Hey guys,
I have the YotaPhone 2 and it's stuck on lollipop 5.0 for ages.
It feels like they ditched this phone completely.
What do you think guys?
Someone has some different info?

I hope not, some marshmallow would be nice and i am about do start an cyanogenmod port (if if find the time...)

fies76 said:
I hope not, some marshmallow would be nice and i am about do start an cyanogenmod port (if if find the time...)
Click to expand...
Click to collapse
good news!

TopTomy said:
Hey guys,
I have the YotaPhone 2 and it's stuck on lollipop 5.0 for ages.
It feels like they ditched this phone completely.
What do you think guys?
Someone has some different info?
Click to expand...
Click to collapse
I've spoken to them a couple of times, both their Facebook page and their customer service indicated their won't be a move up to Marshmallow, very doubtful over a move to 5.1 even. Any more updates will be focussed with optimising the existing software, adding slight features for the EPD etc.
Sad but they are a small company, seems they can only focus on 1 model and a time.

zute333 said:
I've spoken to them a couple of times, both their Facebook page and their customer service indicated their won't be a move up to Marshmallow, very doubtful over a move to 5.1 even. Any more updates will be focussed with optimising the existing software, adding slight features for the EPD etc.
Sad but they are a small company, seems they can only focus on 1 model and a time.
Click to expand...
Click to collapse
Thanks for sharing!

New Update .
Still Lollipop 5.0, but brings some useful improvements and enhancements. I'll take it.

I hope, with the release of the Yota 3 and 2c, that the price of the YD201 falls down. They can't update neither Yota 1 and 2. I still got the first one, but just because I live in Brazil and got from a nice guy that agreed to sell and send his Yotaphone 1 to me from India.
Anyone inclined to sell your Yota2 please talk to me.

zute333 said:
New Update .
Still Lollipop 5.0, but brings some useful improvements and enhancements. I'll take it.
Click to expand...
Click to collapse
Woot??
You got a new firmware OTA?
mine shows nothing!

TopTomy said:
Woot??
You got a new firmware OTA?
mine shows nothing!
Click to expand...
Click to collapse
It's for the RU (russian) firmware, if you check the other threads there are methods to flash the previous version. I have been using it for a few iterations now, the new one worked as an OTA, even with TWRP (they added something to reflash the stock recovery, Yota noticing the significant root community using this phone in Russia at least).

zute333 said:
It's for the RU (russian) firmware, if you check the other threads there are methods to flash the previous version. I have been using it for a few iterations now, the new one worked as an OTA, even with TWRP (they added something to reflash the stock recovery, Yota noticing the significant root community using this phone in Russia at least).
Click to expand...
Click to collapse
Thanks for the info!

I only believe it when it is real, but according to info from tech support, also the EU firmware will get an update this month...
BTW, lollipop isn't too bad, I switched back from marshmallow on my nexus 7 - too much battery drain. if Google could get it right the first time, you wouldn't need monthly bug fixes. not saying that an update for the yota isn't overdue...

Is just me that can't update? I have no OTA and flashing manually gives me "no MD5 file found" error

TKPL said:
Is just me that can't update? I have no OTA and flashing manually gives me "no MD5 file found" error
Click to expand...
Click to collapse
More info please .
firmware version? software version?
can you skip the md5 checksum?
you're rooted, so can you download the russian (RU) firmware and flash that?

zute333 said:
More info please .
firmware version? software version?
can you skip the md5 checksum?
you're rooted, so can you download the russian (RU) firmware and flash that?
Click to expand...
Click to collapse
Yes, thanks
Sorry what you mean with firmware and software version? Phone was running Kitkat 4.4.2 or 3 (now is bricked).
I cannot skip the checksum, no such option in my TWRP (2.8.5). There are others option about checksum on backup but no skipping during install.
I am rooted (and bootloader is unlocked) but I cannot install the RU version. Here I don't understand why you ask me if I am rooted: I can install from recovery or TWRP without root
I downloaded all RU versions and the last EU version from the ftp and I got the MD5 error with all, both Lollipop and KitKat.
Then I tried with Yota Flasher utility: I saw that for flash ROM it was seeking for "firmware" path, so I created "firmware" path and put there the ROM.
I started to flash and it took only some seconds... I understood immediately phone has gone bricked.. and so it is...
Then I tried to download the firmware through Yota Flasher: it arrived to 100% and got stuck in there...
I'm trying to redownload it and hope to flash the system, phone is here in downloading mode waiting...

Provide you my flash method, manually. Use the fastboot.exe in cmd, and type command line below
****************************************************************************
fastboot.exe flash aboot firmeare/emmc_appsboot.mbn
fastboot.exe flash boot firmware/boot.img
fastboot.exe flash -S 512M system firmware/system.img
fastboot.exe flash recovery firmware/recovery.img
fastboot.exe flash cache firmware/cache.img
fastboot.exe flash modem firmware/radio/NON-HLOS.bin （flash the radio）
fastboot.exe flash sbl1 firmeare/radio/sbl1.mbn
fastboot.exe flash rpm firmware/radio/rpm.mbn
fastboot.exe flash aboot firmware/emmc_appsboot.mbn （flash again, just do it.）
fastboot.exe flash userdata firmware/userdata.img （notice this is for the user data, including app data and SD）
fastboot.exe reboot (reboot and wait, about 20 min stuck on logo, it's ok.)

Thank you xingshi.
I'll try.
How long does the entire process take?

TKPL said:
Yes, thanks
Sorry what you mean with firmware and software version? Phone was running Kitkat 4.4.2 or 3 (now is bricked).
I cannot skip the checksum, no such option in my TWRP (2.8.5). There are others option about checksum on backup but no skipping during install.
I am rooted (and bootloader is unlocked) but I cannot install the RU version. Here I don't understand why you ask me if I am rooted: I can install from recovery or TWRP without root
I downloaded all RU versions and the last EU version from the ftp and I got the MD5 error with all, both Lollipop and KitKat.
Then I tried with Yota Flasher utility: I saw that for flash ROM it was seeking for "firmware" path, so I created "firmware" path and put there the ROM.
I started to flash and it took only some seconds... I understood immediately phone has gone bricked.. and so it is...
Then I tried to download the firmware through Yota Flasher: it arrived to 100% and got stuck in there...
I'm trying to redownload it and hope to flash the system, phone is here in downloading mode waiting...
Click to expand...
Click to collapse
UPDATE
Via Yota Flasher I download succesfully the 4.4.3 and flashed the phone. Now it's back
I tried to download again the 5.0 EU but no way: arrives at 100% and stops. If I check file's dimension I see it is a couple of kbytes below the size of the other package I downloaded from web browser and in fact it's impossibile to open the zip.
I'll try to download other version of Lollipop through the Yota Flasher.

TKPL said:
UPDATE
Via Yota Flasher I download succesfully the 4.4.3 and flashed the phone. Now it's back
I tried to download again the 5.0 EU but no way: arrives at 100% and stops. If I check file's dimension I see it is a couple of kbytes below the size of the other package I downloaded from web browser and in fact it's impossibile to open the zip.
I'll try to download other version of Lollipop through the Yota Flasher.
Click to expand...
Click to collapse
NEW UPDATE
I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet. I open a thread for this...

TKPL said:
NEW UPDATE
I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet. I open a thread for this...
Click to expand...
Click to collapse
Same here , have just bought the YOTA 2 too, Vod branded. I wanted to upgrade to to EU 1.60 (rom which seems to be pretty stable): Can I ask you if you have the 1.60 actually or the 1.9x (Russian one)?.
The bug you describe seems to be a real pain, do not want to risk.
Will appreciate any help.
Thx mate

lexman941 said:
Same here , have just bought the YOTA 2 too, Vod branded. I wanted to upgrade to to EU 1.60 (rom which seems to be pretty stable): Can I ask you if you have the 1.60 actually or the 1.9x (Russian one)?.
The bug you describe seems to be a real pain, do not want to risk.
Will appreciate any help.
Thx mate
Click to expand...
Click to collapse
I have the 1.60 EU.
You can make a NAND backup and then flash the newest firmware, trying maybe the 1.99 RU. Even if you flash the 1.60 EU, is not sure that you'll have my same problem, there's people who flashed without issues...

[GUIDE] Everything you need to know - YotaPhone2

This thread aims to provide every useful information about YotaPhone2 YD201 & YD206. I would like to make this post as the REFERENCE for what a user should know about this device and all the possible guides available. Unfortunately we don't have a dedicated forum for the second model of YotaPhone, so all the threads are still in Yotaphone1's forum. The guide is divided into sections hidden in the spoilers.
NOTE: I suggest to read the post entirely, because some sections depend on previous ones.
1. Overview​
{
"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"
}
Hardware specifications:
Front-display: Samsung 5.0" 16M-color 1080p AMOLED touchscreen, 442ppi. Back-display: Always-on 4.7" 16-level grayscale e-Ink display (540 x 960 px, 235ppi). Gorilla Glass 3 on both screens.
144 x 69.5 x 8.9 mm, weight: 140g. CPU: Snapdragon 801, Adreno 330, 2GB RAM, 32GB ROM, 2500mAh battery, QuickCharge 2.0, Wireless charging
8MP autofocus camera, LED flash; HDR, panorama; [email protected] video capturing, jack 3.5mm
Bluetooth 4.0, NFC, OTG, USB 2.0, Wi-Fi a/b/g/n/ac dual-band. SAR: Head -> 0.49 W/kg. Body -> 0.96 W/kg. Simultaneous transmission: 1.16 W/kg. Nano-sim, LTE cat.3, supported bands differ between YD201 and YD206. The first is sold internationally while the second only in Asia. To see the supported frequencies and to check if your mobile operator works with YD201 & YD206, click here -> Comparison -> FrequencyCheck. UPDATE: unlocking additional bands is possible! Check the last section for more details.
Software: Android 6.0.1 Marshmallow. Previous software: Kitkat and Lollipop. More detailed specification can be found on the official website.
2. Getting to know your Yotaphone 2​
YotaPhone 2 is based on stock Android, meaning that YotaDevices developed some apps and functionalities and integrated them to the stock Android OS. Hence, there are no personalied UI like TouchWiz (Samsung), EMIUI (Huawei), MIUI (Xiaomi), Flyme (Meizu), etc. YotaDevices adopted a cleaner approach, like Motorola-Lenovo style, and this keeps the devices fast and with less bloatware. On the other hand, YotaDevices, for example, is not able to implement a black settings theme because of this.
Regarding the additional software, I highly suggest you to open the app "YotaHelp" and learn what are the main features of the YotaPhone 2, its main YotaApps and what can be accompished with the back screen. Clearly, open that app once you have the latest OS version that you want (MM, LP, KK).
This is the link to the presentation of the device with some of its features shown off: MainPage. Remember to read the manual, too; choose your language accordingly.
How to check if you have a YD201 or YD206
Don't look at the info section in your phone because those values can be overwritten when flashing a different firmware or even by yourself with a simple edit of build.prop file. The best way to distinguish between YD201 and YD206 is looking at the IMEI:
First 8 digits of Chinese model: 35969406 -> YD206
First 8 digits of International model: 35643106 -> YD201
The Chinese YD206 version seems to work better with its own baseband modem ("radio"), expecially on 2G band, see the the next sections for more details. UPDATE: a hybrid RU-CN baseband has been created, permitting to YD206 users to have strong singal, fully working 2G on RU firmware and without the always blinking proximity sensor issue. More details below.
3. Changing/Updating/Flashing firmwares​
Depending where you have bought your device, it may come with different firmwares. Generally, it is advisable to install manually the latest firmware, except if you bought a YD201 (check IMEI to verify) which comes already with RU or EU version of Lollipop and will be automatically updated to Marshmallow. If this is your case you can skip this section. If, for some reason, you have a YD201 with HK or other firmware, it is advisable that you flash manually RU or EU firmware following the procedure below. Personally I advise those with EU firmware to flash the RU one, the are no differences in terms of language (except stock dialer letters), thus the latest updates will surely come as soon as possible.
The process of flashing, rooting, etc is very similar to other Android devices, hence those who have already done this modifications, will have no big issues. There are different firmwares for different markets.
UPDATE: Official FTP servers are down and can't be accessed neigher by browser nor by YotaFlasher. To download firmwares use the yotaphone.torrent file provided at the end of the post, big thanks to Alfonso in the International Telegram group. Please keep the torrent alive, for those who can, let's help each other . There is also another torrent of the full FOTA package of Marshmallow update (About MM, more information can be found in its dedicated thread). Please note: FOTA packages can't be installed using YotaFlasher, but only with adb sideload command, putting the phone into recovery mode.
The official list can be found on the YotaDevices FTP server, from where I suggest you to download firmwares for your use. [In these weeks the link doesn't work, this is an alternative: ftp://5.200.42.210/YotaPhone2/. Thanks ercicalone.]
Be aware that the access to that server is limited to 50 users simultaneously. When the limit is reached, downloads can be unsuccesful or interrupted (Try again in another moment). There you can find the official program to flash the firmware, called "YotaPhone2Flasher.exe" and all the firmwares ever released. Moreover, ftp://yota.hi-p.com/ is where Singapore firmwares for China market can be found, but it isn't useful for our purposes.
The flasher can download the firmwares, too, but sometimes it gets stuck or it doesn't tell you when it has finished. Since that program is really basic and I discourage you to use it because of its problem of flashing big .img files (due to lack of available RAM). Instead, a better option is the reworked version released by a 4pda user, which flashes system with -S 512M command (this solves RAM problem) and makes you choose whether to flash: system, radio, userdata. This version is attached here in the post at the end. Using this version covers you from a lack of physical memory, as the system.img is sent to the phone with 512MB blocks.
ReworkedYotaFlasher, hence, is better with respect to the official one. How to use it? Just download the official flasher, install it and then copy the files found in the reworked flasher into the folder of installation of the official one, substituting the old files. Basically you perform the normal installation and then just put the reworked files into the main folder.
Of course all the flashing process can be done via manual fastboot commands (because this is exactly what the flasher does in the background). To understand how the flasher works, a good starting point is learning more about fastboot here.
Step-by-step procedure to flash a firmware.​
[Linux users please refer to this post]. Set-up your PC. adb and fastboot packages must be on your computer, but you don't need to install the whole Android SDK to get them, just install this. Next step is installing the drivers for Yotaphone 2 and getting it recognized properly when connect to Windows. You can find them on this site: http://gsmusbdriver.com/yotaphone-2 with video-instructions included. Another source of getting the drivers is the YotaPhone2Flasher folder. Once you download and install it, you will find the .inf file in the drivers folder. Right click on it and choose install. NOTE: If you have Windows 10, you must disable driver signature verification prior to installing the .inf file. Another way of installing it is to install drivers from C:\Program Files (x86)\yotaphone_flasher\Driver\Google (the folder where you have probably installed your YotaPhoneFlasher).
To do so, go to Device Manager control panel, right click on the start button and select "Device Manager", then right click on your "Computer name" choose "Add Legacy Hardware".
Next -> Install the hardware manually -> Show all devices (Next) -> Have Disk and select the C:\Program Files (x86)\yotaphone_flasher\Driver\Google\android_usb. inf -> "OK" -> "Next" -> "Next.
Set-up your YotaPhone2. Go to settings/About phone, and tap 7 times on the build number, you will activate the developer options which now can be found in settings. Go there and enable USB-Debugging. Charge your phone at least at 70%.
Now you need the firmware files. Download via ftp-server the desired firmware (5.0.0-RU1.1.134.zip or 5.0.0-EU1.1.124b recommended as those are the only firmwares still officialy updated; RU versions receive updates faster), check its integrity using 7-zip or WinRar, and extract the various files in it to a new folder called firmware in the root of YotaPhone2Flasher directory. You will have there drivers folder, firmware folder, adb.exe, etc. files. The firmware folder must be exactly in the root directory of yotaphone_flasher. In the firmware folder you must have: radio, system.img, userdata.img, etc..
Turn off your device, press and hold VOL DOWN + POWER buttons until the you see on the screen "Downloading". Connect the phone to the USB cable, and connect it to the PC. Wait a few seconds to see if Windows install some additional drivers. To check if the device is recognized properly, open the YotaFlasher folder, press and hold SHIFT and right click an empty space inside that folder, then select "Open window command here". Once the black window has opened, type:
Code:
fastboot devices
Some numbers must appear, like:
Code:
56614627 fastboot
In case nothing appears, then it means that the fastboot drivers aren't installed correctly and the procedure WILL NOT WORK. There are many solutions to this: if you are sure you have installed the drivers, try to change usb port, reboot your PC or check if you installed them properly going back in this topic. (Another way you can try installing the drivers is letting Windows recognize them: remove any drivers you already installed, connect the phone in "downloading mode" and let the PC install the drivers when it sees the device connected, then check if everything is ok running the command above).
Then, open YotaFlasher running it as an administrator, and press 1. Remember that for a clean and complete flash you have to answer Y to all the question prompted within the flasher.
Look if the flasher writes some errors during the flashing process, if everything went smoothly, wait until it finishes and reboot the device. Keep in mind that the flasher needs up to 1 minute generally to flash any partition (system.img, userdata.img, etc), so if your flashing process completes itself within few seconds, it means that it wasn't able to load the necessary files into your RAM. Try to close every program on your PC and/or expand virtual memory using your hard disk or a usb-stick.
After a clean flash you HAVE TO WAIT A WHILE. You should see its beautiful bootanimation for 10-30mins, until it finally boots up. To clarify, the boot-animation is the "Yotaphone" writing in the center of blue-grey-white animation. In case it is stuck to "Powered by Android", then something went wrong. Download and verify the integrity of the firmware again, make sure that you selected "Y" in YotaPhoneFlasher and make sure you used the reworked version of it.
That's it! You succesfully flashed the firmware. When you connect to Wi-Fi the phone might download a few OTA updates (it depends of what firmware has been chosen).
How to adb sideload an update (no data loss)​ @hpnhannghia created a video-guide to update to latest MM build starting from latest RU Lollipop 134, using adb sideload. If you find it useful, you may thank him in this post.
4. Changing only the radio&modem part​
YD206 users are advised to change their modem components to the hybrid RU-CN baseband version created by unkernet, in order to have all the available bands working (2G mostly) with a RU firmware. [PLEASE NOTE: a YD206 with CN firmware works perfectly, no modification needed]. RU modem can also be used, but with the existence of the modified version, it performs worse in the reception and 2G availability. The modem version is written in "About Phone", under "baseband version". The list of all existing official baseband-radio versions is in the spoiler, and they can be found in each downloaded firmware in the "radio" folder, composed by 4 files each.
Code:
S01_003_3034_RU1_M11_P2 found in : 4.4.3-S01-003-APC.0.3.56C ; 4.4.3-S01-003-HK1.0.3.56A ; 4.4.3-S01-003-EU1.0.3.56A; 4.4.3-S01-003-RU1.0.3.56A
S01_003_3034_RU1_M15_P2 found in : 4.4.3-S01-003-EU1.0.3.61A ; 4.4.3-S01-003-HK1.0.3.61A ; 4.4.3-S01-003-ME1.0.3.61A
S01_003_4240_RU1_M05 found in : 5.0.0-APC.1.65 ; 5.0.0-RU.1.1.112 ; 5.0.0-HK.1.1.66
S01_003_4240_RU1_M04 found in : 5.0.0-APC.1.44; 5.0.0-EU.1.1.39 ; 5.0.0.-ME.1.1.45
[B]S01_003_3034_CN1_M05 found in every CN firmware, in the oldest there's the 3032 version.[/B]
There are many ways for installing official basebands using YotaFlasher. If the phone you bought, already has the baseband you need, before flashing the entire RU firmware you can just delete the "radio" folder in the firmware folder of YotaPhoneFlasher, once you copied your downloaded and extracted firmware to this folder. In this way the flasher will not change your baseband. Please note that future OTA updates might change your baseband, I'm talking about big OTAs like the one which upgrades from 4.4 to 5.0. If this is your case there is a simple solution below.
During the flashing process you will see some errors due to the fact that the flasher can't find the radio files, this is expected behaviour and proceed without fear. NOTE: Using the reworked YotaPhoneFlasher, just say N when it proposes you to flash radio.
If you are using actively your phone and have set-up all your things or you already flashed the firmware you needed and now you want to change just the radio, do the opposite process. That is, download a CN firmware, extract it, put just its radio folder inside firmware folder, open the flasher and press 1. Within a few seconds you're done because you have flashed only the radio part. No wipes/erases needed. You can change the radio as much as you want without loosing anything. If you use the reworked flasher, answer Y when "flash radio" is prompted and N to every other questions.
IMPORTANT UPDATE FOR YD206 ​Hybrid RU-CN modem makes the use of CN baseband on RU/EU firmwares obsolete. With CN baseband it has been registered battery drain, proximity sensor blinking, and other connectivity problems. Moreover, a RU baseband on the RU/EU firmware made unavailable most 2G bands and a low signal. The new baseband created by unkernet solves all this! Hence, YD206 users with a firmware different from CN are advised to use his baseband to restore full signal funcionalities of their phone. The hybrid baseband can be downloaded here TWRPHybridModem and flashed like other zips in TWRP; Instead, YotaFlasherHybridModem is designed to be installed with YotaFlasher like any other baseband (extract the .zip and place the radio folder inside the firmware folder, as usual). This baseband will be displayed as S01_003_3034_CN1_M05 in the "About Phone" menu.
5. Root, custom recovery (TWRP), unlocking bootloader, xposed​
In order to root your device, you must first unlock your bootloader. This process will WIPE ALL YOUR DATA.​Unlocking bootloader:
Go back in the downloading mode using VOL DOWN + POWER, connect the phone and open the command prompt windows (shift + right click in the yotaflasher folder).
Type:
Code:
fastboot devices
to be sure that the phone is recognized.
Then, the command to unlock is:
Code:
fastboot oem unlock
To confirm the operation, the phone will reboot in the stock recovery, there you have to select "Yes" using VOL UP and DOWN to navigate and POWER to confirm. Then, let the phone boot up again (it will take a while).​Once unlocked, a custom recovery can be installed. You can also lock it back again.​Install or boot TWRP Recovery:
I suggest you the latest TWRP recovery which is attached to this post. Download the zip, extract the .img file in the YotaPhoneFlasher folder along drivers, firmware, adb.exe, etc. you should have twrp-v5.img.
Go to downloading mode, same command window as above, and type the below code to install TWRP upon the stock recovery:
Code:
fastboot flash recovery twrp-v5.img
Moreover, TWRP can be used without its installation, booting it without overwriting the stock one, with the following code:
Code:
fastboot boot twrp-v5.img
Once flashed (or booted), you have to enter the recovery, otherwise it won't stick. You can turn off the device and press VOL UP + POWER, or better: right after the flashing process type this command while pressing and holding the VOL UP button on your device:
Code:
fastboot reboot
It will reboot into the recovery! From here you can root the device, sooner or later. The recovery is always accessible pressing VOL UP + POWER when the phone is turned off.​How to root:
Download the latest SuperSU (attached at this post), copy it into the internal storage of your phone (when it is connected normally or when it is into recovery mode, it's the same).
Once copied, enter TWRP (POWER + VOL UP), go to "install", select SuperSU-v2.79-201612051815.zip and swipe right to flash, then reboot. Done! If SuperSu app is not present in the phone after the process, there is a lack of system space and the .zip can't be installed. Continue reading to solve the problem.​Xposed Framework:
To install xposed, you can simply flash it the same way you rooted the device. Copy xposed-v87-sdk23-arm.zip (this version is for Marshmallow 6.0.x) attached to this post and flash it in the TWRP recovery. After that, install XposedInstaller_3.1.1.apk on your phone, which is also provided here. (KitKat 4.4.x users must download this version, Lollipop users must install xposed-v87-sdk21-arm.zip available here).
An error that usually occurs during flashing is the lack of space in /system partition for xposed to be installed. To solve this issue, a good choice is the guide of @TurbanGuy (link), starting from point 19. For convenience, I will quote it here in a spoiler:
Code:
19. in TWRP: Mount>System>Back
20. Do backup of system+data+boot (to be sure), going to Backup>Select>Swipe
21. There is nto enough space in system (<10MB). We need to remove application which will be updated anyway to latest version from Google Play. Will have >300MB
22. Click: Advanced>File manager
23. go to /system/app
24. Find Books click on it. Now you see apk file for built-in "Google Play Books application"
25. Click bottom (Google Play Books) icon, then delete, then swipe, then back.
26. Continue with these folders:
/Books
/CalendarGoogle (Calendar)
/Chrome (Chrome)
/CloudPrint (Cloud Print)
/Drive (Drive)
/Galaxy4 (some animated wallpaper)
/Hangouts (Hangouts)
/HoloSpiralWallpaper (...)
/Keep Keep
/Lingvo-release (ABBYY Lingvo)
/Maps (Maps)
/Music2 (Google Play Music)
/Newsstand (Google Play Newsstand)
/OfficeSuite_Free (OfficeSuite)
/Videos (Google Play Movies & TV)
/YouTube (Youtube)
27. Go to main menu in TWRP, click Install
28. Find your prepared files and install them (xposed or supersu and xposed).
29. Reboot to System
30. Install XposedInstaller_3.1.1.apk
31. Update SuperSu in Play store
32. Run SuperSu, it will try to update its binary by script in TWRP
33. Later find Xposed application, download your programs and use
If you already have root permission, you can also free system space by using this app or this one to remove some applications from /system partition which you don't need. Moreover, a file manager with system access can do the job, too: in this case you have to find the apps manually. [Be careful of what you remove using the apps or file manager]. A simple option is just removing some basic apps from there (like those pointed out by TurbanGuy) and then reinstall the same app from Play Store. (For example: removing Chrome from system apps and then reinstalling it from Play Store; it will be installed into /data partition). Xposed doesn't need many MBs in /system, so removing a few apps is enough. (Root is advised to use the installed Xposed)​
6. Various tips & topics​
Official topic about Android Marshmallow MM 6.0.1.
Suggestion to mitigate the memory leak in Android 5.0 with xposed: just install FixLollipopMemoryLeak using the xposed app.
Discussion about unlocking band, frequencies and improving modem signal can be found clicking here. In particular, now it is possible to UNLOCK B20 LTE 800MHz of YD206 by following this procedure.
Useful tools and SDK for who wants to develop an app for the e-ink screen: SDK 2.0 for MM.
Grey EPD or too much ghosting? There are several solutions. This is one: Battery discharging. Another possibility is entering the YotaHub app, and delete all the panels, then putting them back again. Eventually, a solution (if flashing firmwares doesn't work) is to heat the EPD screen for some minutes using a hairdryer for example. Be careful not to heat the phone too much!
How to get out from hard-brick [code 9008 or 9006] situation: Download the files from this 4pda guide, use QFIL as described in the screenshot in that link, then flash with yotaflasher your firmware.
How to use custom fonts with stock e-reader app YotaReader: XDA thread
Android hidden codes available through the dialer app, useful to diagnose and change many parameters, are listed in this website.
GPS issues? Refer to this thread, post #11 in particular.
Telegram users who want to join the discussion about YotaPhone2, here are the groups:
Russian group (Russian and English languages used): YotaPhone Club
Italian group (Italian & English languages used): YotaPhonisti Or in telegram search function: @yotauser
Spanish group: YotaUsuarios
International group created by @Planx66 : YOTA Users
Portuguese/Galician group: Invite link
Sources:
rovo89 xposed / various xda threads in the YotaPhone 2 section / 4pda / ChainFire for SuperSu

If someone update their yota using this guide from 206 to 201 Ru build on windows 10 x64, please confirm that works, I don't want to brik the phone after 2 months of delivery time.

queser.info said:
If someone update their yota using this guide from 206 to 201 Ru build on windows 10 x64, please confirm that works, I don't want to brik the phone after 2 months of delivery time.
Click to expand...
Click to collapse
I updated my YD206 using Win10x64. To be sure install the .inf file when you have the verification signature disabled, and then check with
Code:
fastboot devices
if it is recognized.

No way to flash anything. It stucks on "powered by android"
edit: usin the reworked version does the trick

The reworked flasher link is not working on 4pda.ru, thank you for uploading it here.

"(5.0.0-RU1.1.124.zip recommended as it is the only firmware still officialy updated)"
That meens that not RU versions (EU version for example) will not be updated?

Just used this to flash a black chinese YD206 to latest RU firmware, without doing a userdata wipe and it seems to be working very well (much to my girlfriends relief not having to setup her phone again). Thank you for writing this guide, it worked for me.

problem with step 5 !
Hi guys,
I am carefully & slowly progressing through the whole process of "Step-by-step procedure to flash a firmware". Everything went really fine until step 5. :
I launched the flasher as an administrator, but I didn't have the time to "press 1." : I just had a very brief command window that opened and then....nothing.
So I am stuck here with my Yotaphone connected, and still showing "Donwloading". What should I do ?
Thanks for your help.
Edit : hoooo, what a day...
But I think I'm on the good path. So after what I mentionned above, I decided to install the russian rom from the official flasher I found at the official ftp. This time it worked but.....the screen of my Yota was blocked for an hour at "POWERED BY ANDROID".
I searched, I searched through the forum and...found the light, thanks to CVZALEZ :
https://forum.xda-developers.com/showpost.php?p=70743395&postcount=100
Yes, there was a conflict with the ADB drivers. Now I've got the Yota working like a charm ! It even performed an OTA update.
I also managed to put back the CN radio, which is better for the 4G network in France. Hope this experience can help other yotaphoners.

I'm not 100% sure on this but I figured I'd post to make sure I'm right about it and to inform others if I am. In the guide it states:
TheArt. said:
There are multiple ways to do this process. If the phone you bought already has this baseband, before flashing the entire RU firmware you can just delete the "radio" folder in the firmware folder of YotaPhoneFlasher, once you copied your downloaded and extracted firmware to this folder. In this way the flasher will not change your baseband.
Click to expand...
Click to collapse
If you flash the RU firmware without the RU radio you won't be able to perform OTA updates as they will fail because it expects the RU radio folder. How I've decided to approach this is to install the RU frimware, then flash the CN radio folder only. Then if there is an OTA update in future I will have to re flash the RU radio folder, perform the update and then flash the CN radio folder again.
I don't wish to spread misinformation so please correct me if I am wrong about this.

Omega Xi said:
I'm not 100% sure..
[...]
I don't wish to spread misinformation so please correct me if I am wrong about this.
Click to expand...
Click to collapse
The OTA which updates the phone from RU 124 to RU 134 is about 350MB and doesn't change your radio. Only full-update OTA packages usually change it. For example if you are on RU Kitkat and RU Lollipop pops-up as OTA, then it will change it.
For OTA failing procedure issue, it doesn't work as you explained, because I saw people upgrading flawlessly with OTA having RU firmware and CN radio.

Ah, I must have made a mistake somewhere then, the OTA I got was around 1Gb and has left me on Lolipop rather than Marshmallow. I will start again and see if I can get it right this time ^^; Thanks for the help. Also thanks for the awesome guide. ^_^

Omega Xi said:
Ah, I must have made a mistake somewhere then, the OTA I got was around 1Gb and has left me on Lolipop rather than Marshmallow. I will start again and see if I can get it right this time ^^; Thanks for the help. Also thanks for the awesome guide. ^_^
Click to expand...
Click to collapse
I don't know the starting firmware which you flashed, because OTA packages depend on the initial "firmware situation". It also happened that people with RU 124 have received OTA of 350MB to upgrade to RU 134 (the latest stable version available as of now), but this OTA failed to install and thus the phone downloaded the full Lollipop ROM (an OTA of more than 1GB) and then the installation was succesful. In this case the radio files were substituted by RU files. (Meaning that CN radio must be flashed after this OTA, for YD206 users)
PS: It is correct that your phone is on Lollipop, as this is the last version available. Marshmallow is still in beta as you can see on the dedicated thread. Once it will be released, it will arrive as OTA to those who have RU 134 firmware.

TheArt. said:
PS: It is correct that your phone is on Lollipop, as this is the last version available. Marshmallow is still in beta as you can see on the dedicated thread. Once it will be released, it will arrive as OTA to those who have RU 134 firmware.
Click to expand...
Click to collapse
Ah, sorry, I managed to get that mixed up somehow. In that case I'll probably just flash the CN radio into the firmware I have now Sorry if my ramblings confuse anyone who visits this thread ^^;

TheArt. said:
Xposed Framework.
If you want to take advantage of the potential of xposed, you can install it the same way you rooted the device. (Root is mandatory to use Xposed). Copy xposed-v87-sdk23-arm.zip attached to this post and flash it in the TWRP recovery. After that install XposedInstaller_3.1.1.apk on your phone, which is also provided here.​
Click to expand...
Click to collapse
"SDK21 is Android 5.0 (Lollipop), SDK22 is Android 5.1 (also Lollipop) and SDK23 is Android 6.0 (Marshmallow)."

spinecki said:
"SDK21 is Android 5.0 (Lollipop), SDK22 is Android 5.1 (also Lollipop) and SDK23 is Android 6.0 (Marshmallow)."
Click to expand...
Click to collapse
You're right, I attached the wrong version. Now it is correct, thank you for the tip.

Stuck at Powered by - Problem
I want to mention one thing for people who may had this problem too while flashing from KitKat 4.4.3 to 5.0.
When i first followed this guide i had the problem that only the powered by Android screen appeared for a long time but nothing changed and it seemed that the flash-procedure was not succesfoul.
So at first i had to POWER OFF the phone to try it again. Pressing Vol+ and Power button for about 10sec opened the Recovery Menu i guess, and there i could select Power off with the Volume keys and entered it with the power button.
Now that the phone was powered off i tried to flash it again, and this time i saw that yotaflasher could not load the system.img file on the phone. i could read this message within the flashing procedure.
So i found a solution for this. It seems that the system.img file is too big, so that some computers are having problems to load and upload this file onto the yotaphone. You have to power off and then starting in Download Mode again and connect the sphone to the pc before the next attempt.
The solution is that you have to go to the folder where the yotaflasher is installed and open there a command prompt holding the shift key and then you have to type
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 that it will boot again, but this time after a short while it will change its screen into the Yota Video for about 10 minutes and after that it will start Lollipop but then it will also take much time till the apps become ready.
I did not invent this solution, just repeating it and hope it will be shown in the guide just to prevent panic.
https://forum.xda-developers.com/showpost.php?p=69258840&postcount=8

GetSAS said:
Stuck at Powered by - Problem
(...)
I did not invent this solution, just repeating it and hope it will be shown in the guide just to prevent panic.
https://forum.xda-developers.com/showpost.php?p=69258840&postcount=8
Click to expand...
Click to collapse
Long story short : it's already been written in the OP, section "Changing/Updating/Flashing Firmwares" ...

GetSAS said:
Stuck at Powered by - Problem
I want to mention one thing for people who may had this problem too while [...]
Click to expand...
Click to collapse
The reworked YotPhoneFlasher that I attached to OP does exactly the same and I explained it in the guide. Flashing using the new flasher will use that fastboot command you mentioned.

TheArt. said:
The reworked YotPhoneFlasher that I attached to OP does exactly the same and I explained it in the guide. Flashing using the new flasher will use that fastboot command you mentioned.
Click to expand...
Click to collapse
Yes i know now. But in the flashing procedure when the powered by Android screen appeared i was not sure what was causing the problem. Also i did not know what to do in this moment, e.g. to go into the recovery mode just to power off.
So i just want people who have the same experience don't panic at this moment. There is a way to get out of this.

Guys I think I would need some help here, I have flashed a lot of phones over the years, but this one is just refusing to do it. I am getting the attached message every time I try to connect the phone, I did install and reinstall the drivers step by step as instructed on the first page, but still nothing. Does anyone have an advice, thank you?
In addition, I tried different cables and different USB ports, also computers (2 on Win 10 and 1 on Win7).
Update: Never mind fellas, finally it worked, not sure what the issue was, but after the 15th time, just worked. Thank you again.

P9 Lite wont turn on

Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...

fr4nk32 said:
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
Click to expand...
Click to collapse
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck

Dadditz said:
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Click to expand...
Click to collapse
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.

fr4nk32 said:
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
Click to expand...
Click to collapse
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery
(name.of.recovery).img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added

Dadditz said:
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery.img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Click to expand...
Click to collapse
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.

fr4nk32 said:
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
Click to expand...
Click to collapse
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...

Dadditz said:
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Click to expand...
Click to collapse
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!

fr4nk32 said:
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
Click to expand...
Click to collapse
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.

Dadditz said:
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Click to expand...
Click to collapse
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.

fr4nk32 said:
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
Click to expand...
Click to collapse
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards

Dadditz said:
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Click to expand...
Click to collapse
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....

fr4nk32 said:
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
Click to expand...
Click to collapse
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )

Dadditz said:
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Click to expand...
Click to collapse
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:

fr4nk32 said:
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
Click to expand...
Click to collapse
Ok i'm glad to see that worked..
I wish to thank in a special way Firmware Finder TEAM that with their
programs gave us the chance to solve many problems, THX guys. :good:
See you

Huawei P9 lite not starting

Hi, this is my first post here so Hello everyone!
I tried to root P9 lite using below steps:
1. Get unlock code from DC-unlocker.
2. "fastboot oem unlock XXXXXXX..."
3. Phone was reset to factory default sow raw Android 7 was installed.
4. "fastboot boot twrp-3.1.1-0-eva.img" was not working (unknown or forbidden command, don't remember exact message)
5. fastboot flash recovery twrp-3.1.1-0-eva.img
6. After restart with recovery mode still Marshmallow recovery was running so I assumed flash failed.
7. I tried several time put other versions (twrp-3.0.2-0-eva and twrp-3.1.0-0-eva) but if I remember well last one was again installing twrp-3.1.1-0-eva again.
8. As that didn't helped I decided to give up and restore phone to previous state so locked bootloader using SRKToolHuawei-STABLE-V1.3-20160619
9. System restarted and restored to factory default and after running I saw message informing that password is needed to unlock mass storage (or mass memory). There was no onscreen keyboard so no possibility to type anything.
10. Restarted in recovery mode (volume up + power) and tried to recover system from Marshmallow recovery option (using WiFi) but it didn't helped.
11. During next restart I accidentally hold both volume up, down with power so phone tried probably to install system from SSD, but as there was no UPDATE.APP it just stopped at 5%. I left it as it is and after some time (around 5min) phone restarted.
12. Now after restart I see only info that "Your device is booting now...". All key combinations are causing phone restart and same message.
Please advise if there is anything what I can do now.
Will appreciate any help.

After discharging the battery phone started responding properly.
With connected USB cable, volume down and power buttons fastboot&rescue mode is working.
Phone unlocked
FRP unlocked
There is still EMUI recovery in place.
So looks like recovery partition was not replaced and bootloader was not locked again.
I can't tell what is in bootloader now.
System is cleared and can't reinstall it using Marshmallow recovery as it is probably end of maintenance.
My goal is to recover system now and I don't want to root it anymore.
How should I proceed?

JimiLincoln said:
After discharging the battery phone started responding properly.
With connected USB cable, volume down and power buttons fastboot&rescue mode is working.
Phone unlocked
FRP unlocked
There is still EMUI recovery in place.
So looks like recovery partition was not replaced and bootloader was not locked again.
I can't tell what is in bootloader now.
System is cleared and can't reinstall it using Marshmallow recovery as it is probably end of maintenance.
My goal is to recover system now and I don't want to root it anymore.
How should I proceed?
Click to expand...
Click to collapse
Hello,
it seemed that android 7 was your latest working OS.
Can you confirm it ?
If yes what was you complete firmware ?
(example: VNS-L31C432B418/VNS-L21C185B392, etc...)
note: 'EVA' stuff is for P9 variant, not P9 lite..
that's why you f***ed your phone...

Thank you Dadditz for your reply.
Dadditz said:
Hello,
it seemed that android 7 was your latest working OS.
Can you confirm it ?
If yes what was you complete firmware ?
(example: VNS-L31C432B418/VNS-L21C185B392, etc...)
Click to expand...
Click to collapse
It was 7 installed there for sure. And this is VNZ-L21.
Probably latest possible firmware version but can't be sure about this.
Can it be somehow checked now (guess not but not losing hope )?
Dadditz said:
Hello,
note: 'EVA' stuff is for P9 variant, not P9 lite..
that's why you f***ed your phone...
Click to expand...
Click to collapse
I took TWRP from here: twrp.me/huawei/huaweip9.html
When I look at devices list there is not P9 lite here: twrp.me/Devices/Huawei/
Which one should I use then?
P.S. sorry for no links or pictures but as new here I can't add them for now.
EDIT: I found TWRP in SRKToolHuawei-STABLE-V1.3-20160619\recovery\p9\p9.zip\twrpp9mm.img.
Guess I should load this one.
What do you think?

JimiLincoln said:
Thank you Dadditz for your reply.
It was 7 installed there for sure. And this is VNZ-L21.
Probably latest possible firmware version but can't be sure about this.
Can it be somehow checked now (guess not but not losing hope )?
I took TWRP from here: twrp.me/huawei/huaweip9.html
When I look at devices list there is not P9 lite here: twrp.me/Devices/Huawei/
Which one should I use then?
P.S. sorry for no links or pictures but as new here I can't add them for now.
EDIT: I found TWRP in SRKToolHuawei-STABLE-V1.3-20160619\recovery\p9\p9.zip\twrpp9mm.img.
Guess I should load this one.
What do you think?
Click to expand...
Click to collapse
I don't think firmware can be checked now...
Firmware may depend on where you live...
If you live in Europe it can be a branded one
(ex. vodafone: VNS-L21C02B345/6) or unbranded one(VNS-L21C432B505/6).
You cannot flash one of them if you have the other one.
You have to flash an OEMinfo file...
Anyhow you may try a factory reset first and let's hope it will restore the device.
Boot your phone with vol+and power till the e-recovery appear,
do the reset and report back how it went.
P.S.: P9 lite doesn't have an OFFICIAL TWRP.
Available unofficial versions can be founded searching into P9 lite XDA threads.
P.S.2 : A LITTLE SARCASM...
When you tinker with the phone you're not cooking
a plate of spaghetti with tomato sauce.
As you can see bricks are beyond the corner... and not always they can be solved...
Generally it is always better to ask before do, specially
if you don't know what you're doing ... but ... yes,
phone is yours and you can do anything you want...

Dadditz said:
Firmware may depend on where you live...
If you live in Europe it can be a branded one
(ex. vodafone: VNS-L21C02B345/6) or unbranded one(VNS-L21C432B505/6).
You cannot flash one of them if you have the other one.
You have to flash an OEMinfo file...
Click to expand...
Click to collapse
VNS-L21C22B383
Dadditz said:
Anyhow you may try a factory reset first and let's hope it will restore the device.
Click to expand...
Click to collapse
I don't have such option in Huawei eRecovery, only 3 below:
Download latest version and recovery
Reboot
Shutdown
When I used first option and connected trough WiFi I got error "Getting package info failed".
I tried that several times previous days but today this phone again surprised me.
After over 24 hours with discharged battery it became even more responsive (or maybe I just treated it different today).
Today I tried Huawei eRecovery again, it tried to download latest version trough WiFi and "Getting package info failed".
After restart I saw recovery wizard.
Went trough it and I got 7.0 working.
There was no screen keyboard but after recovering backup from HiSuite keyboard is was installed.
I'm also missing some other default android applications like file explorer, mirror, voice recorder, calc.
I'm wondering if it wasn't corrupted during my activities (eg "fastboot flash recovery twrp-3.1.1-0-eva.img").
Dadditz said:
P.S.: P9 lite doesn't have an OFFICIAL TWRP.
Available unofficial versions can be founded searching into P9 lite XDA threads.
Click to expand...
Click to collapse
When I mentioned about SRKToolHuawei-STABLE-V1.3-20160619.zip in my previous post it was one from:
forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Would you recommend it?
Dadditz said:
P.S.2 : A LITTLE SARCASM...
When you tinker with the phone you're not cooking
a plate of spaghetti with tomato sauce.
As you can see bricks are beyond the corner... and not always they can be solved...
Generally it is always better to ask before do, specially
if you don't know what you're doing ... but ... yes,
phone is yours and you can do anything you want...
Click to expand...
Click to collapse
I fully agree with you.
I was searching for many instruction how to do it properly and my mistake was that I stopped fallowing them at point where I tried to installed manually TWRP.
My general conclusion is that even if system was recovered I'm not sure if everything will be ok.
I was totally surprised how my phone reacted during last days so still everything may happen.
I see also some corruption in restored system as some apps are missing.
Any advise how this could be cleaned?
Maybe I should install this system again from some trusted package like from below topic?
forum.xda-developers.com/huawei-p9lite/development/huawei-p9-lite-firmware-compilations-t3517124
What about unlocked bootloader? Should I leave it with annoying screen during phone startup or lock again?

JimiLincoln said:
VNS-L21C22B383
Click to expand...
Click to collapse
This is a good new !!
JimiLincoln said:
I don't have such option in Huawei eRecovery, only 3 below:
Download latest version and recovery
Reboot
Shutdown
When I used first option and connected trough WiFi I got error "Getting package info failed".
I tried that several times previous days but today this phone again surprised me.
After over 24 hours with discharged battery it became even more responsive (or maybe I just treated it different today).
Today I tried Huawei eRecovery again, it tried to download latest version trough WiFi and "Getting package info failed".
After restart I saw recovery wizard.
Went trough it and I got 7.0 working.
There was no screen keyboard but after recovering backup from HiSuite keyboard is was installed.
Click to expand...
Click to collapse
Also a good new !!
JimiLincoln said:
I'm also missing some other default android applications like file explorer, mirror, voice recorder, calc.
I'm wondering if it wasn't corrupted during my activities (eg "fastboot flash recovery twrp-3.1.1-0-eva.img").
Click to expand...
Click to collapse
Yes, surely.
JimiLincoln said:
When I mentioned about SRKToolHuawei-STABLE-V1.3-20160619.zip in my previous post it was one from:
forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
Would you recommend it?
Click to expand...
Click to collapse
No, this recovery isn't for nougat (android 7) version.
If you want, you can flash the one you find into HassanMirza01 TWRP thread.
Do not use 3.2.1, instead choose the 3.1.1-1 version, it's the most stable one.
JimiLincoln said:
I fully agree with you.
I was searching for many instruction how to do it properly and my mistake was that I stopped fallowing them at point where I tried to installed manually TWRP.
Click to expand...
Click to collapse
I agree too, it happen when process aren't properly followed...
JimiLincoln said:
My general conclusion is that even if system was recovered I'm not sure if everything will be ok.
I was totally surprised how my phone reacted during last days so still everything may happen.
I see also some corruption in restored system as some apps are missing.
Any advise how this could be cleaned?
Maybe I should install this system again from some trusted package like from below topic?
forum.xda-developers.com/huawei-p9lite/development/huawei-p9-lite-firmware-compilations-t3517124
What about unlocked bootloader? Should I leave it with annoying screen during phone startup or lock again?
Click to expand...
Click to collapse
Dude,
system can be fully recovered, especially now you're sure about
your latest firmware...
There was a thread with a list of stock apps, but it's been closed
because links are dead...
First thing, eliminate all safeties (fingerprints/pattern/pin)(you can add at the end of process)
You should try to reinstall your current firmware using Firmware Finder app,
download it from the big G store. Use dns/vpn method
and choose VNS-L21C22B383 FULLOTA-MF.
Also all info are inside the app. Using this method
the bootloader will be relocked.
If you wont succeed then i can tell you how to use twrp recovery
providing your stock full firmware.
Cheers

Dadditz said:
No, this recovery isn't for nougat (android 7) version.
If you want, you can flash the one you find into HassanMirza01 TWRP thread.
Do not use 3.2.1, instead choose the 3.1.1-1 version, it's the most stable one.
Click to expand...
Click to collapse
Thanks for that info. I will try it in a while when my wife will have new phone.
Dadditz said:
First thing, eliminate all safeties (fingerprints/pattern/pin)(you can add at the end of process)
Click to expand...
Click to collapse
Done
Dadditz said:
You should try to reinstall your current firmware using Firmware Finder app,
download it from the big G store. Use dns/vpn method
and choose VNS-L21C22B383 FULLOTA-MF.
Also all info are inside the app. Using this method
Click to expand...
Click to collapse
I fallowed instructions and choose first VNS-L21C22B383 FULLOTA-MF from the top (each version appear 2 times on this list).
Tried downloading trough DNS but got below message.
"Due to changes in the data exchange protocol between the Huawei server and the device, this function stopped its correct operation, but still works on older software that allows you to upgrade to one of the latest software if it has not already been done."
I tried with all FullOTA-MF versions on the list and same situation for all.
Because no other option I choose Download from last section (Other) and now I have 3 files on my phone:
update.zip
public/update_data_full_public.zip
VNS-L21_polkomtel_pl/update_full_VNS-L21_polkomtel_pl.zip
Should I install them manually?
If yes then how?
Vol+Vol-Power with those files on SD card or by TWRP?
Dadditz said:
the bootloader will be relocked.
If you wont succeed then i can tell you how to use twrp recovery
providing your stock full firmware.
Cheers
Click to expand...
Click to collapse
Many thanks for your help so far! Really appreciate that.

JimiLincoln said:
I fallowed instructions and choose first VNS-L21C22B383 FULLOTA-MF from the top
(each version appear 2 times on this list).
Tried downloading trough DNS but got below message.
"Due to changes in the data exchange protocol between the Huawei server and the device, this function stopped its correct operation, but still works on older software that allows you to upgrade to one of the latest software if it has not already been done."
I tried with all FullOTA-MF versions on the list and same situation for all.
Because no other option I choose Download from last section (Other) and now I have 3 files on my phone:
update.zip
public/update_data_full_public.zip
VNS-L21_polkomtel_pl/update_full_VNS-L21_polkomtel_pl.zip
Should I install them manually?
If yes then how?
Vol+Vol-Power with those files on SD card or by TWRP?
Many thanks for your help so far! Really appreciate that.
Click to expand...
Click to collapse
Dude, sorry if i wrote this.
I'm pretty sure you done everything correct,
but before attempt using the TWRP it's better if you
try again using Firmware Finder this way...
1 - connect to the internet, open the app, accept the disclaimer;
2 - add your complete firmware (add model) - VNS-L21C22B383;
3 - tap on your firmware;
4 - select the one with fullota-mf;
5 - tap check firmware access;
6 - tap check availability, accept disclaimer;
7 - you should have an 'availability of firmware' popup, tap ok;
8 - go back and tap 'get update through dns';
9 - a popup 'alert' you already faced will apper, tap ok;
10 - a new popup 'select dns method' will appear, tap 'auto',
then tap run vpn service and 'accept' the new connection request popup;
11 - you should now have the running vpn service in the notification panel...;
12 - minimize Firmware Finder;
13 - open settings > tap system updater,
you should find the VNS-L21C22B383 update (check multiple times);
14 - tap on it do download and apply the update;
15 - when the download reach 5%, stop the vpn service and continue doing the process...
It's something like THIS VIDEO.
Let me know...

Hi, your directions as well as movie you provided is giving much more details than application itself.
(In below description I had to use links without https as still I don't have enough posts to make them working.)
Dadditz said:
1 - connect to the internet, open the app, accept the disclaimer;
2 - add your complete firmware (add model) - VNS-L21C22B383;
3 - tap on your firmware;
4 - select the one with fullota-mf
5 - tap check firmware access;
6 - tap check availability, accept disclaimer;
7 - you should have an 'availability of firmware' popup, tap ok;
8 - go back and tap 'get update through dns';
9 - a popup 'alert' you already faced will apper, tap ok;
10 - a new popup 'select dns method' will appear, tap 'auto',
then tap run vpn service and 'accept' the new connection request popup;
11 - you should now have the running vpn service in the notification panel...;
12 - minimize Firmware Finder;
Click to expand...
Click to collapse
Done
Dadditz said:
13 - open settings > tap system updater,
you should find the VNS-L21C22B383 update (check multiple times);
Click to expand...
Click to collapse
No such option in my Phone. It looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ibb.co/Zf4k0fX
when it should look like this
ibb.co/C0NfpJd
I found it using search menu
ibb.co/SDSYdjR
but when I tap it nothing is happening
Dadditz said:
14 - tap on it do download and apply the update;
15 - when the download reach 5%, stop the vpn service and continue doing the process...
It's something like THIS VIDEO.
Let me know...
Click to expand...
Click to collapse
I wish I could do that

JimiLincoln said:
Hi, your directions as well as movie you provided is giving much more details than application itself.
(In below description I had to use links without https as still I don't have enough posts to make them working.)
Done
No such option in my firmware finder
ibb.co/DYkBGVH
ibb.co/rsNTvdb
so i tried to proceed without checking.
Done
No such option in my Phone. It looks like this
ibb.co/Zf4k0fX
when it should look like this
ibb.co/C0NfpJd
I found it using search menu
ibb.co/SDSYdjR
but when I tap it nothing is happening
I wish I could do that :
Click to expand...
Click to collapse
Thank you for all your feedbacks dude.
Yep, it's clear the firmware is completely f***ed...
Tomorrow i will tell you how to use TWRP
and completely restore the device.

@JimiLincoln
You can restore the exact same rom you had on your smartphone ...
(I'm not sure, it seems it's a sort of firmware branded by vodafone)
but if I can afford, if it were you
i would install the European non-brand version (C432),
without bloatware and should also have the most updated security patch.
Is the phone single or dual sim?
Also, let me know if you want to have all stocks or
have the bootloader unlocked for future manipulations ...

Hello @Dadditz,
Dadditz said:
You can restore the exact same rom you had on your smartphone ...
(I'm not sure, it seems it's a sort of firmware branded by vodafone)
Click to expand...
Click to collapse
It is branded by Polkomtel (plus.pl).
Dadditz said:
but if I can afford, if it were you
i would install the European non-brand version (C432),
Click to expand...
Click to collapse
European non-brand version would be the best.
Dadditz said:
Is the phone single or dual sim?
Click to expand...
Click to collapse
Dual (hybrid)
Dadditz said:
Also, let me know if you want to have all stocks or
have the bootloader unlocked for future manipulations ...
Click to expand...
Click to collapse
I have bootloader unlocked and if future modifications will not erase phone data then we could start with minimal version.
Thanks

JimiLincoln said:
Hello @Dadditz,
It is branded by Polkomtel (plus.pl).
European non-brand version would be the best.
Dual (hybrid)
I have bootloader unlocked and if future modifications will not erase phone data then we could start with minimal version.
Thanks
Click to expand...
Click to collapse
You must use a twrp to rebrand your phone.
Download and flash the one i suggested you (3.1.1-1 by HassanMirza01)
When you done, come back for the files and the guide...

TWRP 3.1.1-1 For P9 Lite by HassanMirza01 installed.
I can enter it only by holding Power + Vol Up without USB connected.
When I hold Power + Vol Up with USB connected Huawei eRecovery is launched.
Is it normal?

JimiLincoln said:
TWRP 3.1.1-1 For P9 Lite by HassanMirza01 installed.
I can enter it only by holding Power + Vol Up without USB connected.
When I hold Power + Vol Up with USB connected Huawei eRecovery is launched.
Is it normal?
Click to expand...
Click to collapse
Yes, normal, you have both
stock and custom recovery now...
Ok, i will post a list of file you have to download:
1 - HuRUpdater04.zip file (will do the job);
2 - L21C432OEMinfo.zip file (dual sim);
THE FIRMWARE:
3 - update.zip ;
4 - update_data_full_public.zip ;
5 - update_full_VNS-L21_hw_eu.zip ;
Let file 3 the same name, rename file 4 from
update_data_full_public TO update_data_public,
rename file 5 from update_full_VNS-L21_hw_eu TO update_all_hw.
Names must mandatory match the ones I wrote to you, otherwise it won't work.
This is the procedure:
Use your PC, make a folder and rename it L21C432B506.
Copy files 3-4-5 (renamed) and HuRUpdater04.zip file into that folder.
(if you want you can keep the TWRP copying the .img file into that folder too).
Copy the folder into the SD.
Copy the OEMinfo file wherever you want into the SD.
Put the SD into the device...
Reboot into recovery and format DATA
(wipe>advanced wipe>tick data and tap format in the bottom right> type 'yes').
Reboot again recovery and wipe everything except SD
(wipe>advanced wipe>tick everything except sd).
Go in main menu, tap install, find and select OEMinfo file, let it flash...
When finished go in main menu and select REBOOT then Bootloader.
Once booted, connect the phone to your PC and
unlock again the bootloader. (quickly disconnect it from PC)
Device should automatically reboot into the recovery otherwise you can do
holding vol + and power button.
Now tap install, find your L21C432B506 folder,
select (only) HuRUpdater04.zip file and let it flash...
Your device should reboot into the system correctly,
if not (if passes over 15 mins) reboot into the e-recovery and
do a factory reset + wipe cache.
Done !!

Hello Dadditz,
Everything installed and working fine
Only bothering thing is message that device was unlocked and can't be trusted.
I will keep this for now as it may be useful at some point.
Many thanks Dadditz for your great help!!!
I will probably come back to this topic when my wife will have new phone, so I will play more with this P9 lite, customize system and learn more.

JimiLincoln said:
Hello Dadditz,
Everything installed and working fine
Only bothering thing is message that device was unlocked and can't be trusted.
I will keep this for now as it may be useful at some point.
Many thanks Dadditz for your great help!!!
I will probably come back to this topic when my wife will have new phone, so I will play more with this P9 lite, customize system and learn more.
Click to expand...
Click to collapse
Amazing polite guy,
i was very pleased to be able to help you, obviously, for what I know ...
It's not a big deal to have that 'annoying' message at boot.
Re-lock the bootloader is the only way to remove it.
You have more than one method:
Flash a previous version of your current firmware
and use Firmware Finder to update to the latest;
or wait untill a new version of your current firmware comes out
and use Firmware Finder to update to;
or use fastboot commands but it's seriously risky;
Keep it as is..
Cheers dude. :highfive:

help
i have a similar problem BUT i can't restart my p9 lite in recovery mode. I tried vol+ & power; vol - & power; vol +, vol - & pwer; only power. The result is always the same: "your device as been unlocked and can't be trusted....... Your device is booting now....". I try also to wait to descharge battery. After descharging, when i connect usb cable to recharge, the smartphone wake on with the same message..... Someone can help me?

Dadditz said:
Amazing polite guy,
i was very pleased to be able to help you, obviously, for what I know ...
It's not a big deal to have that 'annoying' message at boot.
Re-lock the bootloader is the only way to remove it.
You have more than one method:
Flash a previous version of your current firmware
and use Firmware Finder to update to the latest;
or wait untill a new version of your current firmware comes out
and use Firmware Finder to update to;
or use fastboot commands but it's seriously risky;
Keep it as is..
Cheers dude. :highfive:
Click to expand...
Click to collapse
Hello Dadditz,
thank you for your warm words.
I can only comment that still being polite is much easier than spending your private time on helping stranger
Also thanks for warning about locking bootloader by fastboot.