Related
A WARNING: IN THE EVENT OF A BRICKED DEVICE, I AM NOT RESPONSIBLE! YOU DO THIS AT YOUR OWN RISK. KDZ UPDATER WILL BRICK YOUR PHONE IF NOT USED PROPERLY. SO FOLLOW THESE INSTRUCTIONS CAREFULLY!!!
So, you want to install custom recovery and custom ROMs? Well, you're in the right place. Follow this guide to it's exact instructions, and you will be fine.
You will need:
A computer running Windows (Sorry Mac & Linux users!)
Your phones USB cable. (If you don't have one, you can see a list of them here on Amazon)
We will need a couple of downloads first, so download these files:
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio).
KDZ Updater
Also, make sure you have your drivers installed. If you don't, get the .zip from here and install all 3 .exe files that are in the zip.
Now to install the Fastboot ROM!
First of all, extract KDZ Updater to the desktop. Then run the msxml.msi file to install the MSXML Parser that is needed to run KDZ. A window should then pop up that 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"
}
^^Select install now.
But if this comes up:
It is already installed, and you can close the window.
Once that is sorted, open up KDZ_FW_UPD.exe (Windows Vista/7 users, make sure to right click and select RUN AS ADMINISTRATOR!)
Change the type of flash by selecting the 'Type' dropdown box and select 3GQCT (SUPER IMPORTANT!)
And make sure PhoneMode is set to DIAG.
Click the
icon and select the KDZ file you downloaded earlier.
Prepare the phone by enabling USB Debugging by going to Settings>Applications>Development>Enable USB Debugging, also go into Settings>SDCard & Phone Storage and make sure 'Mass storage only' is unticked. Then connect the phone to the computer via USB cable and let Windows install any drivers it needs.
Click 'Launch software update' and do not use your computer until the update is complete. The update will take roughly 10-20 mins to complete. Your phone should reboot automatically.
Installing recovery:
You have multiple choices to choose from.
ClockworkMod Recovery 2.5.1.8 (Recommended)
ClockworkMod Recovery 4.x (Recommended but you may run into incompatible .zip files, download the recovery_clockwork_x.x.x.x_swift.zip file)
Amon RA 2.2.1 (Recommended)
Amon RA 1.7.0.1 (Not recommended due to incompatibility with zip files and recovery backups. Also .zips must be signed)
Download the recovery image of your choice (I strongly recommend Clockwork 2.5.1.8)
Next put your phone in Fastboot mode by rebooting then holding Camera+Power, make sure USB Cable is plugged in. Also let Windows search Windows Update for drivers.
Download fastboot.exe from here: http://adf.ly/2M8Hi and extract it to the desktop. Also put the recovery image you downloaded onto the desktop too.
Be sure to have your fastboot drivers installed, if you use Vista/Windows 7 then the driver should be auto-downloaded from Windows Update, if you use XP or the drivers won't install from Windows Update, then look at this.
Open a command prompt and type the following:
Code:
cd Desktop
fastboot devices (if you see ? fastboot then your device is recognized)
fastboot flash recovery name_of_recovery.img
fastboot reboot
When fastboot says rebooting, hold down HOME and wait. You should see clockwork pop up. Recovery is now on your phone. You can delete the fastboot, kdz and recovery file from your pc because we won't be needing them again. Unless you need to use fastboot.exe again, but just download the fastboot.zip again if you need it) The other files, we don't need.
(NOTE: If your phone reboots with no boot logos (LG logo and animation), or when you flash recovery and it doesn't come up, follow the steps found here. Thanks to fishears for the post!)
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Recovery backups usually contain some .img files and a nandroid.md5 file. The folder containing these files will need to go in the sdcard\clockworkmod\backup folder. Flash them by going to Backup/Restore>Restore>Then pick the backup folder.
Recovery update.zips contain three (or four) files/folders:
boot.img (file)
install-busybox.sh (file, only appears in SOME ROMs)
system (folder)
META-INF (folder)
DO NOT EXTRACT THESE, just put the .zip file on your sdcard, then go into recovery and go to install .zip from sdcard>choose .zip>pick the .zip you downloaded. (NOTE FOR SWIFTDROID: You MUST put the update-cm-xxxxx.zip file found in the SwiftDroid_x.x.x.x_Recovery.zip on your sdcard for it to install!!!)
If you need any help, PM me or reply to this thread.
Don't forget to say
if I helped!
Enjoy!
Want to go 'advanced'? Check out this guide resizing your partitions so you can have more app space!
(Also, if a mod could sticky this thread I would be very thankful. Cheers!)
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
scribbclubber said:
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
Click to expand...
Click to collapse
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
effortless. said:
...
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio)....
Click to expand...
Click to collapse
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
nutterbg said:
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
Click to expand...
Click to collapse
It is meant to include a fix for calling while connected to 3G. Me and many other users encountered a problem where we could not recieve calls on 3G. I flashed this and my problem was gone. Also, i'm unsure how to check the baseband firmware, in 2.2 ROMs, this is visible, but I looked in the build.prop, and it was a set text (under ro.ril.baseband I think) but yes, you could flash this KDZ, restore backup and all would be well. But if you needed the modified partitions, just use the tutorial that is in my signature, then flash backup.
Good idea
effortless. said:
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
Click to expand...
Click to collapse
yep well said, when they appear and post without using search bar...lol think that i've did it myself but i used to save improtant notes and like that no need to search again and again, the thread should be stuck for noobs..
the guides are already here but posted on different threads and not at start, so agree that pics alongside instruction is a good idea.
Do I need recovery_clockwork_4.0.1.4_swift, that is on Mur4ik's site, to install SwiftDroid_v2.0_RC4, or I can use recovery clockwork 2.5.1.8 that I already have on my phone?
EDIT:Nvm, fixed it.
Added info on making sure 'Mass storage only' is unchecked before using KDZ to solve some peoples issues with the phone not being detected.
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
DamDSx said:
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
Click to expand...
Click to collapse
Obviously if you needed to root then I would have included the steps. Also around 99% of custom ROMs are rooted anyway.
I have a rooted and already updated to 2.1.
Would this still work?
KenifJambo said:
I have a rooted and already updated to 2.1.
Would this still work?
Click to expand...
Click to collapse
Of course, you would have to do this anyway if you want to install custom ROMs
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Danzano said:
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Click to expand...
Click to collapse
It already has been lol
In 2.1, you can check baseband in hidden menu.
Sent from my GT540 using Tapatalk
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Aktivehate said:
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Click to expand...
Click to collapse
As far as I am aware, it works perfect, GO is just some branding from some providers.
^^ Could someone back me up on this,
Thanks
Well that's good to know, i had one with 1.6 but made some things go wrong with the drivers, and the usb settings in android, but know i have this guide so i am gone try it.
When I tried it i had some trouble with the kdz flasher, but i did'nt knew of the msxml stuff and it was with windows 7.
Could someone upload another fastboot rom,preferably a version v20a or v20b
Sent from my GT540 using XDA App
This Model is even Older than the Galaxy S SHW M110S but still in the market in third world countries .
The Flashing Procedure for this Korean Galaxy A is similar to the Korean Galaxy S But this model has limited ROM's and Rooting Kernels as it was not that popular once the Galaxy S was revealed three months later.
Downloads
You Can download an Instructions manual from Here
You need to use Odin3 version 1.32 (Attached below)
You need USB Drivers (Attached below)
ROMS Currently Available
Stock ROM DB19
DF27
Galaxy A 2.2.1
EB25
EG04
EG04 Custom
EG04 Jackos
EI08
KyuHyuk 2.0.1 (Rom 2.2.1 Cooked)
Johyengho
Aprime GBV02
MiRu ROM PE 2.5
GA ROM 1.5
How to Root?
You can use Framaroot app or Unlockroot from your PC or Cydia Impactor from PC
or
Flash Rooted ROM EG04
Download Mode : Press and hold vol up + vol down + Power button
Recovery Mode : Press volume up + power button
General advice prior to Flashing any phone
Its always best to do a "clean" install. meaning you should remove any old scripts, data, cache, junk before flashing a new ROM, this is like taking a bath before using new clothes. For some models it is a must do, for others it may not be a major problem or can be resolved by flashing the dbdata.rfs to clear out the remaining junk that you failed to remove before flashing . But if you had "lagfix" and did not undo it, it can cause internal SD card unavailable situation, which can be difficult to resolve.
Hence before flashing its advisable to
a) undo lagfix, IF you had any.
b) Do a factory reset by settings>Privacy> factory reset ( erase SD Card - optional , as formatting SD card could be too)
c) And even going into recovery to wipe everything is also good.
d) Removing SIM Card and External SD card ( makes it easier for phone to boot up initially after flashing a new ROM)
Doing this will give you a "Clean" install or fresh start for your phone.
Make sure your Battery Charge is more than 50%, Samsung requires you to have 100% charge when using KIES to upgrade.
Reminder, What you do with your Phone is your own responsibility, so do it at your own risk
Flashing Procedure
1). You need to Factory Reset Phone first go to settings >Privacy> factory reset also can be done in recovery
2) Power Down and Enter Recovery Mode and wipe data and wipe cache
3) Power down and remove battery, Then reinsert the battery and Enter Download Mode
4) Fireup Odin3 ver 1.32 on PC and Connect phone with USB cable to PC
5) Now select the ROM you had downloaded in Odin under PDA ( do not tick or press anything else ) and DON'T Interrupt flashing unless stuck for some time
6) Press Start Button on Odin3 and wait till is completed
7) Once phone has booted up and everything is working, power down and enter Recovery Mode, here you "factory Reset" phone one more time
That's it Now you will be using the new ROM you just flashed.
Any problem, just check My Android Solution's for relevant solution
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Its been 3 months & no one Replies to this thread ..
Really man ... This is a million $ thread ... I can just say WOW ...
Thanks
I am very thankful that i found this thread! At last! i am able to find roms for my phone. The sad part is, this phone was given to me, and i didn't know what they did because i found out that my Storage settings states Unavailable, and Available storage 0.00b. I tried flashing it with the stock rom you provided but an error that says like "the file is to large than tha target partition" something like that. Could please kindly direct me what to do? please! I would be very very thankful!
xggwarchildxx said:
I am very thankful that i found this thread! At last! i am able to find roms for my phone. The sad part is, this phone was given to me, and i didn't know what they did because i found out that my Storage settings states Unavailable, and Available storage 0.00b. I tried flashing it with the stock rom you provided but an error that says like "the file is to large than tha target partition" something like that. Could please kindly direct me what to do? please! I would be very very thankful!
Click to expand...
Click to collapse
You need to strictly follow the flashing guide , remove eveything including SIM card and Ext SD card, and format Internal SD card ( If possible) in the phone. After that following the guide flash the DB 19 Stock ROM, to see, if you can recover from the corrupt partitions problem.
Check this out! Links to useful Guides and " Banned " Documentaries
Sir, i did follow the flashing guide, but flashing the stock rom still say the same error: The file is too large than the target partition. BTW, there is no sd card in the phone while flashing. But still the same, stock rom say the same error, the other rom (custom?) succeed but still the same problem. Thank you!
Edit:
I think formatting the internal storage is impossible as there is 0.00b available in the phone storage status also the Format Storage cannot be clicked. Thanks!
xggwarchildxx said:
Sir, i did follow the flashing guide, but flashing the stock rom still say the same error: The file is too large than the target partition. BTW, there is no sd card in the phone while flashing. But still the same, stock rom say the same error, the other rom (custom?) succeed but still the same problem. Thank you!
Edit:
I think formatting the internal storage is impossible as there is 0.00b available in the phone storage status also the Format Storage cannot be clicked. Thanks!
Click to expand...
Click to collapse
The thing is , you need a PIT FILE to repartition, unfortunately, I cannot locate one, so you need to search for it. also I do not have this phone, for me to try extracting a PIT File or help you with other methods.
Alternatively, you can try to switch SD Cards, and that needs a modified CWM kernel as ell as an Ext SD card partitioned into two partitions.
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
The thing is , you need a PIT FILE to repartition, unfortunately, I cannot locate one, so you need to search for it. also I do not have this phone, for me to try extracting a PIT File or help you with other methods.
Alternatively, you can try to switch SD Cards, and that needs a modified CWM kernel as ell as an Ext SD card partitioned into two partitions.
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
OK sir.. i will try and find if there is any existing PIT file for this. Thank you!
samsung galaxy a shw m100s
i buy samsung galaxy A shw m100s with firmware 2.3.4. this is my first android phone i am intrested in learning new things i download odin3_v1.3.2.exe with a tar.md5 file named {SHW-M100S_HOME_EB25_8G_REV08_user.tar} i connect my android with power+vol down+vol up key download mode and open the odin and upload the tar file i change the firmware 2.3.4 to 2.2.1. now it is hang when i turn on hotspot sheild opened i want to back in 2.3.4 and a stable operating system
please help me please
bhailogs121 said:
i buy samsung galaxy A shw m100s with firmware 2.3.4. this is my first android phone i am intrested in learning new things i download odin3_v1.3.2.exe with a tar.md5 file named {SHW-M100S_HOME_EB25_8G_REV08_user.tar} i connect my android with power+vol down+vol up key download mode and open the odin and upload the tar file i change the firmware 2.3.4 to 2.2.1. now it is hang when i turn on hotspot sheild opened i want to back in 2.3.4 and a stable operating system
please help me please
Click to expand...
Click to collapse
Follow the guide above step by step and after that flash the EG04 or EI08 ROM, it comes in custom, rooted etc or the other after EG04 , will get you back to 2.3.4, remember to do all the wipes and steps.
Check this out! Links to useful Guides and " Banned " Documentaries
Brother Is TheRe Any Jelly Bean Rom?????
flashing not starting
xsenman said:
This Model is even Older than the Galaxy S SHW M110S but still in the market in third world countries .
The Flashing Procedure for this Korean Galaxy A is similar to the Korean Galaxy S But this model has limited ROM's and Rooting Kernels as it was not that popular once the Galaxy S was revealed three months later.
Downloads
You Can download an Instructions manual from Here
You need to use Odin3 version 1.32 (Attached below)
You need USB Drivers (Attached below)
ROMS Currently Available
Stock ROM DB19
DF27
Galaxy A 2.2.1
EB25
EG04
EG04 Custom
EG04 Jackos
EI08
KyuHyuk 2.0.1 (Rom 2.2.1 Cooked)
Johyengho
Aprime GBV02
MiRu ROM PE 2.5
GA ROM 1.5
How to Root?
You can use Framaroot app or Unlockroot from your PC or Cydia Impactor from PC
or
Flash Rooted ROM EG04
Download Mode : Press and hold vol up + vol down + Power button
Recovery Mode : Press volume up + power button
General advice prior to Flashing any phone
Its always best to do a "clean" install. meaning you should remove any old scripts, data, cache, junk before flashing a new ROM, this is like taking a bath before using new clothes. For some models it is a must do, for others it may not be a major problem or can be resolved by flashing the dbdata.rfs to clear out the remaining junk that you failed to remove before flashing . But if you had "lagfix" and did not undo it, it can cause internal SD card unavailable situation, which can be difficult to resolve.
Hence before flashing its advisable to
a) undo lagfix, IF you had any.
b) Do a factory reset by settings>Privacy> factory reset ( erase SD Card - optional , as formatting SD card could be too)
c) And even going into recovery to wipe everything is also good.
d) Removing SIM Card and External SD card ( makes it easier for phone to boot up initially after flashing a new ROM)
Doing this will give you a "Clean" install or fresh start for your phone.
Make sure your Battery Charge is more than 50%, Samsung requires you to have 100% charge when using KIES to upgrade.
Reminder, What you do with your Phone is your own responsibility, so do it at your own risk
Flashing Procedure
1). You need to Factory Reset Phone first go to settings >Privacy> factory reset also can be done in recovery
2) Power Down and Enter Recovery Mode and wipe data and wipe cache
3) Power down and remove battery, Then reinsert the battery and Enter Download Mode
4) Fireup Odin3 ver 1.32 on PC and Connect phone with USB cable to PC
5) Now select the ROM you had downloaded in Odin under PDA ( do not tick or press anything else ) and DON'T Interrupt flashing unless stuck for some time
6) Press Start Button on Odin3 and wait till is completed
7) Once phone has booted up and everything is working, power down and enter Recovery Mode, here you "factory Reset" phone one more time
That's it Now you will be using the new ROM you just flashed.
Any problem, just check My Android Solution's for relevant solution
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Click to expand...
Click to collapse
after i enter in to the download mode nothings gonna happen :'( :'( my device is not showing in the connection status :/
flashing not starting :'(
any solutions plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
my shw m100s is stuck at the upgrade screen i dont know what to do
Khizar hayyat said:
Brother Is TheRe Any Jelly Bean Rom?????
Click to expand...
Click to collapse
Sorry mate, This Phone was only sold in Korea and only a few countries. Few month later, Galaxy S came out and died. I remember many many developers back in Korea cooking ROMs but in about 2011, all the development completely stopped and the Galaxy A community closed. Gingerbread and Froyo ROMs are all we've got.
Thank you very much for the ROM
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
masterpointer said:
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Hi masterpointer,
You can almost always un-brick S3 with MTK SP Flash tool, but then, you need a firmware (with scatter file) to flash, and, you need to decide to flash KK or LP. If previously you ran KK and go LP (or, for some reason, other way around), you must use "upgrade firmware" instead of just "download" in tool. That's because KK and LP partition layout differ. You can find S3 firmwares and MTK SP Flash tool instructions in various places. Personally, I would perhaps recommend RC5 jiayu.de until a much anticipated MM upgrade arrives.
Just curious: what firmware did you run that would allow/suggest to upgrade/install resulting in getting stuck? Of course, some upgrade/install procedures may expect stock, not custom, recovery.
TWRP should give you adb, and you can always restore stock recovery put on SD card from there with 'dd'.
Dior DNA said:
Hi masterpointer,
You can almost always un-brick S3 with MTK SP Flash tool, but then, you need a firmware (with scatter file) to flash, and, you need to decide to flash KK or LP. If previously you ran KK and go LP (or, for some reason, other way around), you must use "upgrade firmware" instead of just "download" in tool. That's because KK and LP partition layout differ. You can find S3 firmwares and MTK SP Flash tool instructions in various places. Personally, I would perhaps recommend RC5 jiayu.de until a much anticipated MM upgrade arrives.
Just curious: what firmware did you run that would allow/suggest to upgrade/install resulting in getting stuck? Of course, some upgrade/install procedures may expect stock, not custom, recovery.
TWRP should give you adb, and you can always restore stock recovery put on SD card from there with 'dd'.
Click to expand...
Click to collapse
Thanks for trying to help.
However, I'm no expert so, for a start, I don't know what "KK" and "LP" refer to.
I do have a firmware (20150205-141543 (unzipped)) complete with a scatter file and I also have the MTK SP Flash Tool. I can copy the firmware to the external SD card (unzipped or zipped?) but how do I proceed from there? Please
masterpointer said:
Thanks for trying to help.
However, I'm no expert so, for a start, I don't know what "KK" and "LP" refer to.
I do have a firmware (20150205-141543 (unzipped)) complete with a scatter file and I also have the MTK SP Flash Tool. I can copy the firmware to the external SD card (unzipped or zipped?) but how do I proceed from there? Please
Click to expand...
Click to collapse
KK=KitKat aka Android 4.4.4
LP=Lollipop aka Android 5.1.1
20150205-141543 for sure will be KitKat.
Where did you get firmware?, it seems very old, older than anything I can find on needrom.
Are you sure you do not want to flash something newer? I suggest Lollipop RC5 from Jiayu.DE (to be found there).
You need to have unpacked files on PC for MTK SP Flash Tool to load the scatter file.
If you upgrade KK->LP then use "upgrade firmware" instead of "download".
Good luck!
I managed to flash my S3 Plus using Flash Tools in order to replace the useless rom published on Feb this year.
Having downloaded TWRP 3.0.0.0 on my pc I'm trying to install it on my phone using Flash Tools but I don't know how to open the .img file.
Can anyone help me please?
I tried many times following the process for TWRP but I got the answer
FAILED (remote: download the partition "recovery" is not allowed)
What is wrong?
Please HELP ...
masterpointer said:
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Apparently you tried to perform an OTA update (over the air). Unfortunately, this will only work with Stock revovery. So - flash the original recovery.img with Sp flash Tool. Power on the phone again. Perform the OTA again.
Gesendet von meinem Telekom Puls mit Tapatalk
Blackcrown said:
Apparently you tried to perform an OTA update (over the air). Unfortunately, this will only work with Stock revovery. So - flash the original recovery.img with Sp flash Tool. Power on the phone again. Perform the OTA again.
Gesendet von meinem Telekom Puls mit Tapatalk
Click to expand...
Click to collapse
Sorry for the delay with my response. I have been away the last 2 or 3 weeks.
I'm afraid no luck.
I copied the raw zip files (JY-S3-2 and JiayuS2-5.1_20160121-212346_PC)) both from NeedRom. In TWRP I click on Install, select ext. card and click on one of the zip files and then when I swipe to "flash the screen" it starts processing, then shows some error messages and finally a red "Failed" message appears. The same thing happens when I click on other rom.
I have also tried to copy all the unzipped files from an old rom i had (20150205-141543) to the external card, but that doesn't seem to do anything.
I'm obviously doing something wrong. Is it possible to get a step-by-step instructions of how to flash a rom via TWRP? I'm fairly certain that the phone is ok if I can only get the system reinstalled.
Hoping you can help
@masterpointer: Ok, so I got it wrong. You don't try OTA but want to flash a zip from recovery. The steps you've taken seem fine to me, except: do not unzip the files because TWRP will take care of that.
I suspect that you use the wrong version of TWRP recovery. I will get back to you later in the evening (Central European time), when I can access my home PC, and tell you the name of the TWRP recovery file I used.
Blackcrown said:
@masterpointer: Ok, so I got it wrong. You don't try OTA but want to flash a zip from recovery. The steps you've taken seem fine to me, except: do not unzip the files because TWRP will take care of that.
I suspect that you use the wrong version of TWRP recovery. I will get back to you later in the evening (Central European time), when I can access my home PC, and tell you the name of the TWRP recovery file I used.
Click to expand...
Click to collapse
Thanks, looking forward to hearing from you. I really would like to fix it. I loved that phone...!
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
masterpointer said:
I copied the raw zip files (JY-S3-2 and JiayuS2-5.1_20160121-212346_PC)) both from NeedRom. In TWRP I click on Install, select ext. card and click on one of the zip files and then when I swipe to "flash the screen" it starts processing, then shows some error messages and finally a red "Failed" message appears. The same thing happens when I click on other rom.
Click to expand...
Click to collapse
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Many thanks for the explicit explanation. That should keep me busy for a while! I'll have a go and let you know how I fare...
Once again, thank you!
Blackcrown said:
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Click to expand...
Click to collapse
Ok, here's what I've done:
1. downloaded and installed the drivers (as per the Windows site) and the Rom you recommended (Jiayu_S3_5.1.1_rc5_flashtool.rar. Please note the ".RAR" extension!!! - No problems
2. I also downloaded the latest flashtools file. However, that needed a password (which was shown) to unzip it, but the shown password does not work! However, I have Flashtools_v5.1452.00 already installed so I used that.
3. opened flash-tool.exe, clicked on Scatter-loading and then on the MTK6752_Android_scatter.txt
4. opened the Download only box and selected "Firmware upgrade"
5. clicked on Options/Download and ticked "DA and DL with checksum.
6. clicked on Download...
...and this is where the story ends! The screen simply greys out and stays like that until I click on Stop. No yellow progress line appears. Nothing happens.
Am I doing something wrong?
masterpointer said:
Many thanks for the explicit explanation. That should keep me busy for a while! I'll have a go and let you know how I fare...
Once again, thank you!
Click to expand...
Click to collapse
Blackcrown said:
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Click to expand...
Click to collapse
Hi again.
Just realised that the following screen appears in the tutorial (after the "Options/Download/check DA and DL"). The items on my screen stay the same
Preloader
MBR
EBR1
UBOOT
Those items (apart from the "Preloader") do not appear on my screen at any stage. I assume that has got something to do with the lack of further progress?
masterpointer said:
6. clicked on Download...
...and this is where the story ends!
Click to expand...
Click to collapse
This is, where the flashing begins! AFTER clicking download, connect the phone to your computer. Phone must be switched OFF. As soon as you connect it, Windows will recognize the switched-off phone (provided that you successfully installed the preloader VCOM driver) and start the flashing indicated by the yellow bar. If the phone is not recognized, start Windows again, then use another USB port and/or try another USB cable.
masterpointer said:
Hi again.
Just realised that the following screen appears in the tutorial (after the "Options/Download/check DA and DL"). The items on my screen stay the same
Preloader
MBR
EBR1
UBOOT
Those items (apart from the "Preloader") do not appear on my screen at any stage. I assume that has got something to do with the lack of further progress?
Click to expand...
Click to collapse
No. The person who made the tutorial used some screenshots from another phone. That's all. However, you should untick the "Preloader" image in SP Flashtool before hitting Download. The preloader is working (that's why you can connect to the phone) and should not be flashed again for safety reasons.
Blackcrown said:
This is, where the flashing begins! AFTER clicking download, connect the phone to your computer. Phone must be switched OFF. As soon as you connect it, Windows will recognize the switched-off phone (provided that you successfully installed the preloader VCOM driver) and start the flashing indicated by the yellow bar. If the phone is not recognized, start Windows again, then use another USB port and/or try another USB cable.
No. The person who made the tutorial used some screenshots from another phone. That's all. However, you should untick the "Preloader" image in SP Flashtool before hitting Download. The preloader is working (that's why you can connect to the phone) and should not be flashed again for safety reasons.
Click to expand...
Click to collapse
No luck, I un-ticked the preloader but as soon as I hit the download button, everything simply greys out. I have attached a screenshot for your perusal. I'm stuck!
{
"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"
}
masterpointer said:
No luck, I un-ticked the preloader but as soon as I hit the download button, everything simply greys out. I have attached a screenshot for your perusal. I'm stuck!
Click to expand...
Click to collapse
more info: Initially I had set the "download only" box to "firmware upgrade", but when I unticked the "preloader" as you suggested, the "firmware upgrade" automatically reverted to "download only" (I hadn't noticed). Same end result, though.
masterpointer said:
more info: Initially I had set the "download only" box to "firmware upgrade", but when I unticked the "preloader" as you suggested, the "firmware upgrade" automatically reverted to "download only" (I hadn't noticed). Same end result, though.
Click to expand...
Click to collapse
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
1testi said:
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
Click to expand...
Click to collapse
It works!!!!!!!
I thought I had to wait until being told by SP-FT to connect the phone. You last message made me think that maybe it should be connected BEFORE hitting the download button. So I did that and...Bob's-your-uncle.
I can't thank you enough for all your help. Wish I would get the opportunity to reciprocate. Many, many thanks.
1testi said:
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
Click to expand...
Click to collapse
It works!!!!!!!
I thought I had to wait until being told by SP-FT to connect the phone. You last message made me think that maybe it should be connected BEFORE hitting the download button. So I did that and...Bob's-your-uncle.
I can't thank you enough for all your help. Wish I would get the opportunity to reciprocate. Many, many thanks.
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.