Related
Welcome to my first tutorial! Please make suggestions in this thread on how to improve it. I will try to be a comprehensive as possible but also as general as possible since flashing firmware to Motorola phones is a pretty consistent process.
Disclaimer:
Please note, like almost everything else on XDA-Developers.com doing this process without fully understanding it can possibly brick the phone (although if it probably already is) thus, I cannot be held liable for any damages caused by following this process.
In other words, the person performing the work performed in this post is fully responsible for their actions on this phone.
/Disclaimer
Before starting with the flashing a Motorola phone, please review the following information:
In most cases firmware versions CANNOT be downgraded
Firmware from other regions can sometimes be flashed, but not always, this is why it is always recommended to stick with the same firmware branch that is already on the phone
The phone that will be flashed should be fully charged, the fastboot flashing process only allows for phones that are over 50 or 60% to be flashed.
If the phone that is trying to be flashed is under 50 or 60%, purchase a "factory adapter" - http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make one - http://forum.xda-developers.com/showthread.php?t=1077414
Use a USB 2.0 port that is directly connected to the motherboard of the computer (preferably on the back of a desktop, or internal ports on a laptop)
Now, prepare the computer for the flashing process
Download the latest Motorola USB & Charging Drivers from http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Download the latest available RSD Lite software (~6mb) - As of March 4th 2013, it is 6.1.4 and can be downloaded from here : http://d-h.st/KNN
Ensure the computer can detect the phone in fastboot mode (I have seen a number of problems with different versions of Windows, if it doesn't work on one PC, try a different one). To perform the test, power off the phone completely and boot it into fastboot mode. Unfortunately since Motorola phones are all built uniquley, this tutorial cannot cover all of the different methods to boot a phone in fastboot, but the most common method is to hold the VOLUME UP button and VOLUME DOWN button while pressing POWER. A menu will most likely appear, use the VOLUME DOWN button and navigate to "AP Fastboot", now press the VOLUME UP button. The phone should say it is OK to Program like in the following screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, connect the USB cable to the computer, it should detect and install a driver. Check in device manager for a "Mot Single ADB Interface" under ADB Interface. If it is not listed, try to force the drivers to look in the "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" folder.
Once the driver is loaded, open up RSD Lite and the internal codename should be listed under one of the ports. In RAZR HD (GSM) it says Fastboot VANQUISH_U S.
At this point, I would recommend to download the firmware to the computer that will be used for the flashing (once the phone is detectable in RSD Lite, that is a good indication the computer can detect the phone, navigate to http://motofirmware.center and locate the correct firmware and version that should be loaded on the phone. If the firmware is not listed there, please put a request into the firmware team (supply the default.prop and build.prop files). They are pretty good with locating firmware! The firmware files are generally large (ranging anywhere between 200mb and 1500mb) so now would be a good time to top-up that phone charge (if possible). If it isn't possible to charge the phone, don't worry, the phone will automatically turn off if it doesn't detect a flashing process after a few minutes.
Flashing Time!
Once the preparation has completed, flashing is very straightforward. Extract the downloaded firmware files to a folder on your hard disk, then use RSD Lite to load the XML file up. Power on the phone into fastboot mode again, and plug in the phone into an internal USB port on the computer, then press the start button. If everything is successful the phone should begin booting into the stock system. The flashing process usually takes 10-20 minutes depending on the size of the files and the power of the phone. If there are any failures, be sure to read the "Before getting started" section again, and hopefully someone on the forum can help recover the phone with you!
Re: [TUTORIAL] How to Flash Stock Motorola Fastboot & SBF files
danifunker said:
Welcome to my first tutorial! Please make suggestions in this thread on how to improve it. I will try to be a comprehensive as possible but also as general as possible since flashing firmware to Motorola phones is a pretty consistent process.
Disclaimer:
Please note, like almost everything else on XDA-Developers.com doing this process without fully understanding it can possibly brick the phone (although if it probably already is) thus, I cannot be held liable for any damages caused by following this process.
In other words, the person performing the work performed in this post is fully responsible for their actions on this phone.
/Disclaimer
Before starting with the flashing a Motorola phone, please review the following information:
In most cases firmware versions CANNOT be downgraded
Firmware from other regions can sometimes be flashed, but not always, this is why it is always recommended to stick with the same firmware branch that is already on the phone
The phone that will be flashed should be fully charged, the fastboot flashing process only allows for phones that are over 50 or 60% to be flashed.
If the phone that is trying to be flashed is under 50 or 60%, purchase a "factory adapter" - http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make one - http://forum.xda-developers.com/showthread.php?t=1077414
Use a USB 2.0 port that is directly connected to the motherboard of the computer (preferably on the back of a desktop, or internal ports on a laptop)
Now, prepare the computer for the flashing process
Download the latest Motorola USB & Charging Drivers from http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Download the latest available RSD Lite software (~6mb) - As of March 4th 2013, it is 6.1.4 and can be downloaded from here : http://d-h.st/KNN
Ensure the computer can detect the phone in fastboot mode (I have seen a number of problems with different versions of Windows, if it doesn't work on one PC, try a different one). To perform the test, power off the phone completley and boot it into fastboot mode. Unfortunatley since Motorola phones are all built uniquley, this tutorial cannot cover all of the different methods to boot a phone in fastboot, but the most common method is to hold the VOLUME UP button and VOLUME DOWN button while pressing POWER. A menu will most likley appear, use the VOLUME DOWN button and navigate to "AP Fastboot", now press the VOLUME UP button. The phone should say it is OK to Program like in the following screen
Next, connect the USB cable to the computer, it should detect and install a driver. Check in device manager for a "Mot Single ADB Interface" under ADB Interface. If it is not listed, try to force the drivers to look in the "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" folder.
Once the driver is loaded, open up RSD Lite and the internal codename should be listed under one of the ports. In RAZR HD (GSM) it says Fastboot VANQUISH_U S.
At this point, I would recommend to download the firmware to the computer that will be used for the flashing (once the phone is detectable in RSD Lite, that is a good indication the computer can detect the phone, navigate to http://sbf.droidevelopers.org and locate the correct firmware and version that should be loaded on the phone. If the firmware is not listed there, please put a request into the firmware team (supply the default.prop and build.prop files). They are pretty good with locating firmware! The firmware files are generally large (ranging anywhere between 200mb and 1500mb) so now would be a good time to top-up that phone charge (if possible). If it isn't possible to charge the phone, don't worry, the phone will automatically turn off if it doesn't detect a flashing process after a few minutes.
Flashing Time!
Once the preperation has completed, flashing is very straightforward. Extract the downloaded firmware files to a folder on your hard disk, then use RSD Lite to load the XML or SBF file up. Power on the phone into fastboot mode again, and plug in the phone into an internal USB port on the computer, then press the start button. If everything is sucessful the phone should begin booting into the stock system. The flashing process usually takes 10-20 minutes depending on the size of the files and the power of the phone. If there are any failures, be sure to read the "Before getting started" section again, and hopefully someone on XDA can help recover the phone with you!
Click to expand...
Click to collapse
Would be best to download the files before entering the bootloader... I heard some nasty stories bout battery emptying out in BL/recovery and it messed up while flashing.
Charge up the phone before flashing and have the files ready prior to flashing.
Sent from my XT925 using xda app-developers app
saloums7 said:
Would be best to download the files before entering the bootloader... I heard some nasty stories bout battery emptying out in BL/recovery and it messed up while flashing.
Charge up the phone before flashing and have the files ready prior to flashing.
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
danifunker said:
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
Click to expand...
Click to collapse
Works like a charm. Thank you.
danifunker said:
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
Click to expand...
Click to collapse
Good point good thing I have unlimited bandwidth so that doesn't affect me too much
Sent from my XT925 using xda app-developers app
If you have "battery low" during flashing, and you can't make the phone boot, just discharge it completely and then plug the phone into charger (it will charge in "emergency mode" without booting).
Thanks for this post....after issues with CM 10 and no GPS....I flashed back to Rogers/Fido 4.1.2. very happy....here is hoping if there are any future updates this ROM will auto update. Or I can wish for a working CM 10.1 some day
Sent from my XT925 using xda app-developers app
shredrex said:
Thanks for this post....after issues with CM 10 and no GPS....I flashed back to Rogers/Fido 4.1.2. very happy....here is hoping if there are any future updates this ROM will auto update. Or I can wish for a working CM 10.1 some day
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Hi shredrex, I am also having the same problems and I want to flash back to rogers/fido 4.1.2. May I know where you got your files from? I would really appreciate it!!
taeotut said:
Hi shredrex, I am also having the same problems and I want to flash back to rogers/fido 4.1.2. May I know where you got your files from? I would really appreciate it!!
Click to expand...
Click to collapse
I posted the wrong link in the original tutorial, thanks for flagging it.
Check this site : http://sbf.droid-developers.org/
Good luck!
i´m trying to install the telcel firmware and also used 2 different computers with the lastest drivers and rds lite 6.1.4
I followed all the steps and doesn´t work for me I´ve got the next error
failed flashing process. unknown fastboot command getvar
Help me please
Hi danifunker, I am new to Motorola and I have the RAZR i (XT890). I'm making two guides related to helping new people to Motorola phones here . May I link your guide here, of course giving full credit? I basically would like to recommend new users to the RAZR i to read good guides like this before they brick their phone. We get about 5 bricks a day over there!
gorefrausto said:
i´m trying to install the telcel firmware and also used 2 different computers with the lastest drivers and rds lite 6.1.4
I followed all the steps and doesn´t work for me I´ve got the next error
failed flashing process. unknown fastboot command getvar
Help me please
Click to expand...
Click to collapse
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
elcacho said:
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
Click to expand...
Click to collapse
Thanks, now I´m installing the firmware
elcacho said:
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
Click to expand...
Click to collapse
Can we have this put into the tutorial please.
Also, as for the OP in general, thanks for putting this here; its not so clear elsewhere on this section of the forum and everything that is useful to a Motorola noob is specifically for the XT926... even the blog posts linked to. I had a lot of anxiety over trying this in the past because things as fundamental as this, concerning Motorola and these phones in particular as well, are scattered and disorganised in various places on the internet. Its frustrating and makes one want to shy away from trying things out for fear of not being able to return to stock or bricking their device. I come from an SGS2 which had no fastboot to worry about, for example, and even though the RAZR HD forum had few participants when I first got mine, there was still a lot to be confused about and to shy away from.
Im trying to flash the filmware to my phone cause my camera stopped working shortly after i updated my droid razr to 4.1.2, and when i did the ap fastboot filmware update, everything comes back like it already was should i remove everything from my phone and try again?
Edit: My Safestrap is gone, and now i have no service..
Edit Again: Service restored after i removed everything, another problem tho. Camera still wont initialize now
Firmware Motorola V9 bootloader 04.C1
Dear XDA members, need firmware in Portuguese with the Motorola V9 bootloader 04.C1. I thank you.
Thanks for detailed instuctions! Worked perfectly for Motorola XT862.
Ok to program option
I have been running 4.2.2 aokp unofficial, and its been awesome.. i need to flash back to stock because im going to be selling my phone soon, when i try to use mattlgraf's utility i always get the unable to mount error message.. im going to be trying this option aswell, but I have a feeling it wont work because i dont get the "OK to program" in AP Fastboot, if you have any idea why this is happening just reply to this post, thanks for all the material guys.
---------- Post added at 11:05 AM ---------- Previous post was at 10:58 AM ----------
thetigerag said:
I have been running 4.2.2 aokp unofficial, and its been awesome.. i need to flash back to stock because im going to be selling my phone soon, when i try to use mattlgraf's utility i always get the unable to mount error message.. im going to be trying this option aswell, but I have a feeling it wont work because i dont get the "OK to program" in AP Fastboot, if you have any idea why this is happening just reply to this post, thanks for all the material guys.
Click to expand...
Click to collapse
I got an error message that said "Failed flashing process. Unknown fastboot command" im not sure if this is due to the new firmware because of running 4.2.2 or what.. any information would be appreciated - Thanks.
Use MATT's utility v1.2
Look for the v 1.2 and give it a try.
I was able to go back to stock ICS on the xt925 (Rogers)
itzik_man said:
Look for the v 1.2 and give it a try.
I was able to go back to stock ICS on the xt925 (Rogers)
Click to expand...
Click to collapse
Yes, 1.20 was the utility i originally used.
I get the error message 'fastboot' is not recognized as an internal or external command, operable program or batch file. multiple times, then it takes me back to the main screen.
---------- Post added at 10:45 PM ---------- Previous post was at 10:04 PM ----------
Got it all worked out, thanks guys.
Well I found the latest official firmware for ZTE Open C.Maybe it is helpful to you guys.
Before doing anything,read the introduction carefully.
Instruction of ZTE OPEN project SD card upgrade
Ⅰ Cautions：
The software version and pictures in this document are just for reference only. Please use ZTE handset support website provided version to download software, moreover, SD card upgrade only allows upgrading between the same version and from low version to high version.
1) Before you begin:
a) Please back up all user data of mobile phone, including Phonebook, Messages and so on;
b) Please make sure the mobile phone can be normally powered on. Otherwise it may cause download failure;
c) Take out SIM card and check whether update.zip of SD card is in accordance with to be upgraded mobile phone; copying update package to update.zip file before upgrade.
d) Please check whether the battery power is enough (2 cells more), if the battery power is not enough, please charge the mobile until the battery power is enough; Do not execute SD card upgrade while charging in case losing data or the mobile phone crashes during downloading.
2) Do not do other operations and do not take out battery by force during upgrading.
3) It will take 1-2 minutes to finish SD card upgrade. If the upgrade is invalid, you can contact local ASC.
Ⅱ Steps of SD card upgrade:
1. Download upgrade package and copy the software to sdcard
a) Open the SD card upgrade package which is downloaded from ZTE website, check whether there is a update.zip file( The picture and file name are just for reference only), as picture 1-1 shown below:
{
"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"
}
b) Copy whole update.zip file to root directory of micro Sd card (TF Card)
2. Power off mobile phone, and then hold the power key and volume up key simultaneously to enter into firefox OS recovery mode, as picture 1-10 shown below.
3. Press side down key to move down until move to “apply update from sdcard”, as picture 1-11 shown below:
4. Press power key Choose the downloaded update package update.zip after entering into directory of T card,, as picture 1-12 shown below.
5. The upgrade will be completed after 1-2 minutes
6. Select reboot system now
Here is the download address:
http://www.mediafire.com/download/sczh3w7x2m8ketg/OPEN_C(European_Standard)_SD_card_upgrading_instruction_&_software_package-251920B0788FFOS_OPENCV1.0.0B05.rar
The unzip code is geekbuying.com
The original source is from http://blog.geekbuying.com/index.php/2014/06/10/latest-official-firmware-for-zte-open-c-firefox-smartphone/#.U5q6N3KSyzQ ,contributed by Mike.
Apirl said:
Well I found the latest official firmware for ZTE Open C.Maybe it is helpful to you guys.
Before doing anything,read the introduction carefully.
Instruction of ZTE OPEN project SD card upgrade
Ⅰ Cautions：
The software version and pictures in this document are just for reference only. Please use ZTE handset support website provided version to download software, moreover, SD card upgrade only allows upgrading between the same version and from low version to high version.
1) Before you begin:
a) Please back up all user data of mobile phone, including Phonebook, Messages and so on;
b) Please make sure the mobile phone can be normally powered on. Otherwise it may cause download failure;
c) Take out SIM card and check whether update.zip of SD card is in accordance with to be upgraded mobile phone; copying update package to update.zip file before upgrade.
d) Please check whether the battery power is enough (2 cells more), if the battery power is not enough, please charge the mobile until the battery power is enough; Do not execute SD card upgrade while charging in case losing data or the mobile phone crashes during downloading.
2) Do not do other operations and do not take out battery by force during upgrading.
3) It will take 1-2 minutes to finish SD card upgrade. If the upgrade is invalid, you can contact local ASC.
Ⅱ Steps of SD card upgrade:
1. Download upgrade package and copy the software to sdcard
a) Open the SD card upgrade package which is downloaded from ZTE website, check whether there is a update.zip file( The picture and file name are just for reference only), as picture 1-1 shown below:
b) Copy whole update.zip file to root directory of micro Sd card (TF Card)
2. Power off mobile phone, and then hold the power key and volume up key simultaneously to enter into firefox OS recovery mode, as picture 1-10 shown below.
3. Press side down key to move down until move to “apply update from sdcard”, as picture 1-11 shown below:
4. Press power key Choose the downloaded update package update.zip after entering into directory of T card,, as picture 1-12 shown below.
5. The upgrade will be completed after 1-2 minutes
6. Select reboot system now
Here is the download address:
http://www.mediafire.com/download/sczh3w7x2m8ketg/OPEN_C(European_Standard)_SD_card_upgrading_instruction_&_software_package-251920B0788FFOS_OPENCV1.0.0B05.rar
The unzip code is geekbuying.com
The original source is from http://blog.geekbuying.com/index.php/2014/06/10/latest-official-firmware-for-zte-open-c-firefox-smartphone/#.U5q6N3KSyzQ ,contributed by Mike.
Click to expand...
Click to collapse
That's the European Standard version, There are two versions one European Standard other America Standard both on ZTE site.
http://www.ztedevices.com/support/s...cc0-42d6-8f23-8834b4a6849c.html?type=software
vampirefo said:
That's the European Standard version, There are two versions one European Standard other America Standard both on ZTE site.
http://www.ztedevices.com/support/s...cc0-42d6-8f23-8834b4a6849c.html?type=software
Click to expand...
Click to collapse
It is a little bit snapper, still 1.3 though, anyway I got my dual boot set up, I am running rooted kitkat from sdcard, and rooted firefox from phone.
B04?!
Hello,
I have an european version of the ZTE Open C.
To update the firmware to version B06 and to root the device I downloaded the "Open C Upgrade Tool" and the latest firmware from comebuy.com
After successful flashing I was wondering that the recovery mode showed B04 instead of B06. So there went something defenitly wrong - probably the firmware file is the wrong one even if the filename says B06.
But my Problem is that I'm not able to update the OS using the integrated updater or to flash any other firmware. I tried B05 from this thread, B06 directly from ZTE and another version I found on the internet.
The update routine of the recovery mode always aborts and the veryfication process of the update.
So the update via the recovery menu fails and the Upgrade Tool also.
Is there any way to flash a version with the possibility to update to my device?
Thanks in advance!
-nr23730
nr23730 said:
Hello,
I have an european version of the ZTE Open C.
To update the firmware to version B06 and to root the device I downloaded the "Open C Upgrade Tool" and the latest firmware from comebuy.com
After successful flashing I was wondering that the recovery mode showed B04 instead of B06. So there went something defenitly wrong - probably the firmware file is the wrong one even if the filename says B06.
But my Problem is that I'm not able to update the OS using the integrated updater or to flash any other firmware. I tried B05 from this thread, B06 directly from ZTE and another version I found on the internet.
The update routine of the recovery mode always aborts and the veryfication process of the update.
So the update via the recovery menu fails and the Upgrade Tool also.
Is there any way to flash a version with the possibility to update to my device?
Thanks in advance!
-nr23730
Click to expand...
Click to collapse
You aren't going to be able to update from zte site, firmware is completely different than "Open C Upgrade Tool" firmware. you could upgrade, but you need a backup and custom recovery.
Anytime you update or flash firmware not from zte, then you can no longer upgrade from zte firmware, zte's firmware isn't rooted, it's locked down, once you flash another firmware that gives you root, you have to either continue using from that branch or use custom recovery and re-install your backup of stock firmware, if you never made a backup, then you have to get a backup from another user or phone.
Hi,
I'm in the same situation with the same hardware. Have you found a solution?
Thanks in advance.
vampirefo said:
You aren't going to be able to update from zte site, firmware is completely different than "Open C Upgrade Tool" firmware. you could upgrade, but you need a backup and custom recovery.
Anytime you update or flash firmware not from zte, then you can no longer upgrade from zte firmware, zte's firmware isn't rooted, it's locked down, once you flash another firmware that gives you root, you have to either continue using from that branch or use custom recovery and re-install your backup of stock firmware, if you never made a backup, then you have to get a backup from another user or phone.
Click to expand...
Click to collapse
thebeach555 said:
Hi,
I'm in the same situation with the same hardware. Have you found a solution?
Thanks in advance.
Click to expand...
Click to collapse
Simply not possible without unlocking bootloader, rooting phone and installing USA update via custom recovery. I know most people quickly followed the video below. but the author didn't warn USA users the files are EU Not US files, so once USA users flash them they have lost any chance to upgrade to any ZTE Official USA releases.
https://www.youtube.com/watch?v=axOYIfo7y2s
vampirefo said:
It is a little bit snapper, still 1.3 though, anyway I got my dual boot set up, I am running rooted kitkat from sdcard, and rooted firefox from phone.
Click to expand...
Click to collapse
Hi I rooted my open c and I am running kitkat 4.42. I would like to know how I can dual boot with firefox please. Can you help me?
garryc10 said:
Hi I rooted my open c and I am running kitkat 4.42. I would like to know how I can dual boot with firefox please. Can you help me?
Click to expand...
Click to collapse
I no longer have this phone.
Sent from my Venue 8 3830 using Tapatalk
I know this is a few years too late, but maybe I still can get some help...
So I still have a ZTE Open C in working state (battery a bit inflated, but if I can get it in proper shape software-wise, I'll probably get a replacement) but I don't seem to be able to flash it (the idea was to put LineageOS 14.1 on it, I recently discovered what appears to be a stable build for this phone by Konstakang). Now...
1. The phone has the latest Firefox OS Nightly build that I was able to get - Boot2Gecko 2.6.0.0-prerelease.
2. I can use ADB to connect to it (Windows), phone is unlocked, but fastboot is not enabled.
3. I have no backups.
... ideas?
KodrutZ said:
I know this is a few years too late, but maybe I still can get some help...
So I still have a ZTE Open C in working state (battery a bit inflated, but if I can get it in proper shape software-wise, I'll probably get a replacement) but I don't seem to be able to flash it (the idea was to put LineageOS 14.1 on it, I recently discovered what appears to be a stable build for this phone by Konstakang). Now...
1. The phone has the latest Firefox OS Nightly build that I was able to get - Boot2Gecko 2.6.0.0-prerelease.
2. I can use ADB to connect to it (Windows), phone is unlocked, but fastboot is not enabled.
3. I have no backups.
... ideas?
Click to expand...
Click to collapse
It is in French, but it works https://blog.mossroy.fr/2018/11/21/passer-un-zte-open-c-sous-lineage-os/ . There are a lot of source links in there. Enjoy!
Thank you very much, Nico. Sadly, I wasn't able to enable fastboot. The LineageOS installation part - or any other ROM installation - requires fastboot to be enabled. I will try again as soon as I find the time and the phone itself...
KodrutZ said:
Thank you very much, Nico. Sadly, I wasn't able to enable fastboot. The LineageOS installation part - or any other ROM installation - requires fastboot to be enabled. I will try again as soon as I find the time and the phone itself...
Click to expand...
Click to collapse
This command below does not work?
Code:
adb reboot bootloader
Does anyone still have a working link for the latest FirefoxOS firmware (and Android->FirefoxOS script, IIRC there was one)?
Hello, my name is Chris and I was beeing stupid.
I accidentaly started the latest OTA System Update (in Germany) on my rooted 830L.
After that, it was stuck in Bootloop.
I thought I was being smart and tried to go back to stock Kitkat so start over from there.
So i used the tool from this post http://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-830-1050-1380-to-kitkat-t3240487 whichh seemed to work.
Afterwards i tried to flash Stock Kitkat using this firmware http://forum.xda-developers.com/showpost.php?p=62237392&postcount=9 and according to a german how to. That seemed to go well, too. But now the tablet starts in strange mode:
It is not recognized by the PC in this mode. I still can enter fastboot mode though. In Fone flash tool it is shown as INT1503... and not as Bayflie or whatever it was before.
Ist there anything i can do to repair this? Thank you very much in advance!!
Chris
UPDATE: Fastboot Screen
[UPDATE 2]
heineken123 said:
Hello, my name is Chris and I was beeing stupid.
Chris
Click to expand...
Click to collapse
go in fastboot mode and take a picture
try flashing the lollipop stock rom , maybe you are still on the lollipop bios.
1. download and extract someplace on your pc
2. uninstall your existing Phone Flash Tool and from the drivers folder install both files (Intel Phone Flash Tool and Android Driver accepting defaults) reboot pc when finished
3. place your tab in DNX mode (from power off press and hold both volume keys then press pwr to start, in a few you screen will show "Fastboot starting..." message and hang on that. you must get that message on your tab screen, restart from power off until you have it)
4. start the installed Phone Flash Tool and load flash.xml from the extracted YT2-830L... folder then Start Flashing, it will reboot when done
I just realized that I was even more stupid than I thought.
I flashed a 830F KitKat Rom to my 830L!!!! Is there a way to revert that?
I have added a picture of the fastboot screen above, since i couldnt link it here.
Thank you!
heineken123 said:
I just realized that I was even more stupid than I thought.
I flashed a 830F KitKat Rom to my 830L!!!! Is there a way to revert that?
I have added a picture of the fastboot screen above, since i couldnt link it here.
Thank you!
Click to expand...
Click to collapse
already instructed you with some stuff (also, that one is the DNX mode, fastboot mode is the one with the Droidboot menu etc). it is likely that your bios is still a lollipop one, the rom i linked is for lollipop. if it does not work just download the kitkat stock rom for your model and flash it
Ok, I am a step forward. At least there seems to be something.
Flashing your image with the tool did not work. It lead to the same screen as the first picture above.
However, when i tried to flash the KitKat Rom with your tool it startet and it went into Droidboot.
Flashing did not finish thoug. i get this error, see UPDATE 2 Above.
heineken123 said:
Ok, I am a step forward. At least there seems to be something.
Flashing your image with the tool did not work. It lead to the same screen as the first picture above.
However, when i tried to flash the KitKat Rom with your tool it startet and it went into Droidboot.
Flashing did not finish thoug. i get this error, see UPDATE 2 Above.
Click to expand...
Click to collapse
go in File->Options check the Force sparsing box and input 500MB in there (if is not already) then repeat the whole flashing procedure
i asked you to flash lollipop first just in case you were still on the lollipop bios (for the future so you should know, you can flash a stock rom matching your existing install if you brick, for eg you could have flashed a stock lollipop rom from the beginning) no longer the case as now you have downgraded the bios to kitkat. after you flash kitkat rom remember to set your region code before you start to update through ota's.
ionioni said:
go in File->Options check the Force sparsing box and input 500MB in there (if is not already) then repeat the whole flashing procedure
i asked you to flash lollipop first just in case you were still on the lollipop bios (for the future so you should know, you can flash a stock rom matching your existing install if you brick, for eg you could have flashed a stock lollipop rom from the beginning) no longer the case as now you have downgraded the bios to kitkat. after you flash kitkat rom remember to set your region code before you start to update through ota's.
Click to expand...
Click to collapse
Excellent, Tab is booting and seems to be working!!! Region code is changed to de. Thank you very much.
From your other post that i have seen there it seems possible to flash the LC Formware to enable Calling?
Would i proceed by updating to Lilipop, all ota updates and then flash the lolipop 830LC firmware as sugested in the other post? Will it work with region code de and is it rootable?
Thank you very much again!
heineken123 said:
Excellent, Tab is booting and seems to be working!!! Region code is changed to de. Thank you very much.
From your other post that i have seen there it seems possible to flash the LC Formware to enable Calling?
Would i proceed by updating to Lilipop, all ota updates and then flash the lolipop 830LC firmware as sugested in the other post? Will it work with region code de and is it rootable?
Thank you very much again!
Click to expand...
Click to collapse
yes, yes and yes
Hello there,
I'm facing pretty much of the same issues.
Having the 1050l Version, tried to update the ota while having the device rooted. So after that, it just booted until the "those who do"-sign.
I followed the "get back to kitkat" thread, downgraded the bios (might have worked i think) and flashed YT2-1050L_S0225_150422_ROW to it.
Right now it is just coming to the very first "powered by Android"-screen and aborts rebooting, booting again, and so on and so on.
Might it be that theres sill the lollipop bios on it?
Thought about flashing yoga_tab_2_osc_android_to_lollipop_201505.rar (Official stock rom) on it, but dont want to make any further stepp before having your advice.
I hope for you help,
Thank you.
Pikku said:
Hello there,
I'm facing pretty much of the same issues.
Having the 1050l Version, tried to update the ota while having the device rooted. So after that, it just booted until the "those who do"-sign.
I followed the "get back to kitkat" thread, downgraded the bios (might have worked i think) and flashed YT2-1050L_S0225_150422_ROW to it.
Right now it is just coming to the very first "powered by Android"-screen and aborts rebooting, booting again, and so on and so on.
Might it be that theres sill the lollipop bios on it?
Thought about flashing yoga_tab_2_osc_android_to_lollipop_201505.rar (Official stock rom) on it, but dont want to make any further stepp before having your advice.
I hope for you help,
Thank you.
Click to expand...
Click to collapse
this is the 1050L kikat stock rom and this is the lollipop one
if you are sure that you downgraded the bios when using the restore kitkat bios tool then flash the kikat one
Thank you very much.
It just appeared to me that i flashed the "erase" image, so i might try to flash the "blank factory" one.
Pikku said:
Thank you very much.
It just appeared to me that i flashed the "erase" image, so i might try to flash the "blank factory" one.
Click to expand...
Click to collapse
do not use other files than flash.xml, you can erase the imei for eg or even worse some xml files are writing a bios that will hard-brick. always use a known stock rom and never use other files than flash.xml unless instructed otherwise!
Oh boy... ye i will keep that in mind definately!
Is there btw any possibility to charge the device in the current status?
---------- Post added at 02:44 PM ---------- Previous post was at 02:35 PM ----------
Ok, so after your hint with the bios i went to reexecute your kitkat-bios-reset, and i'm in the same bootcycle, the programs i preparing for pushing files all the time. Hardbrick confirmed?
Pikku said:
Oh boy... ye i will keep that in mind definately!
Is there btw any possibility to charge the device in the current status?
---------- Post added at 02:44 PM ---------- Previous post was at 02:35 PM ----------
Ok, so after your hint with the bios i went to reexecute your kitkat-bios-reset, and i'm in the same bootcycle, the programs i preparing for pushing files all the time. Hardbrick confirmed?
Click to expand...
Click to collapse
if you used the 'restore kitkat bios' tool once there's no need to use it again (you already have the kitkat bios)
download the kitkat stock rom i linked, extract it and flash using intel phone flash tool (flash.xml file) from dnx mode (from pwr off, press and hold both vol keys then pwr on, screen will stay on a 'fastboot starting...' message, you must have this message on your tab when you click the 'start flashing' on the intel phont flash tool)
Ok, 7m of dl left, tho many thanks to you already, really appreciate your effort!!
---------- Post added at 03:22 PM ---------- Previous post was at 02:59 PM ----------
ionioni said:
if you used the 'restore kitkat bios' tool once there's no need to use it again (you already have the kitkat bios)
download the kitkat stock rom i linked, extract it and flash using intel phone flash tool (flash.xml file) from dnx mode (from pwr off, press and hold both vol keys then pwr on, screen will stay on a 'fastboot starting...' message, you must have this message on your tab when you click the 'start flashing' on the intel phont flash tool)
Click to expand...
Click to collapse
Ok i flashed the kitkat, now im facing "E: cannot remove cache/fastboot.tmp".
Any advice?
EDIT: Sorry it just toook a few times!
Pikku said:
Ok, 7m of dl left, tho many thanks to you already, really appreciate your effort!!
---------- Post added at 03:22 PM ---------- Previous post was at 02:59 PM ----------
Ok i flashed the kitkat, now im facing "E: cannot remove cache/fastboot.tmp".
Any advice?
Click to expand...
Click to collapse
ignore it... in the intel phone flash tool log window (in the boottom) is it reporting as finished? if so just reboot the tab
It worked!
Oh man, really thank you, glad you were up to help me Thanks!
Hi, unfortunately I got the IMEI changed/reset (probably due flashing other than flash.xml)... would you pls know about any solution to change it back so that LTE starts working? Thanks a lot!
ionioni said:
ignore it... in the intel phone flash tool log window (in the boottom) is it reporting as finished? if so just reboot the tab
Click to expand...
Click to collapse
Hi, hi hope you can help me. Yesterday I tried to flash the 830lc rom but it stopped at 16% so I turn it off and tried again but it didn't recognize the tablet. If I turn it on it show 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"
}
And when I put it in fastbot mode and try again to flash phone flash tool give me this error.
Any idea? I really don't know what to do.
Thank you
I can't post pic from iPad...
I don't know how to show it
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.
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.