Related
Hello everyone, today for the Honor 6 Plus is a new OTA is the C432B571 some people have jumped him via OTA and others not so you can download the update I put and upgrade to the latest version which is the PE-TL10C432B571.
Instructions: download, unzip and copy the folder dload update.app in SD.
LINK http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v55895/f1/full/update.zip
Awesome..!! This is just like the B190 OTA update for Honor 7.
So they are updating the Lollipop version for their devices too, this is the first approach like this I have seen.
This is an update improving mm is passed from the B560, B571 this new update
Does this work on honor 6 too?
Dynos said:
Does this work on honor 6 too?
Click to expand...
Click to collapse
No, it's for the plus
Damn, any word on when h6 gets this?
I'm on the PE-TL10C432B560 but when I tried to update it gave me "FAILED TO UPGRADE" and I was forced to restart my H6+.
Did you get the same error?
I placed my update.app in a dload folder, inside my External SD Card.
Thanks in advance
fefferico said:
I'm on the PE-TL10C432B560 but when I tried to update it gave me "FAILED TO UPGRADE" and I was forced to restart my H6+.
Did you get the same error?
I placed my update.app in a dload folder, inside my External SD Card.
Thanks in advance
Click to expand...
Click to collapse
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
zinko_pt said:
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
Click to expand...
Click to collapse
Thanks a lot mate!
With the link you provided I was able to successfully upgrade my H6+
Anyway I'm still official, no root, no unlocked bootloader.... strange considering that I lost my MotoG1 warranty after a week
Thanks again
I have downloaded the zip (didn't extract it) and i have created /dload file in internal memory and put that zip inside it, then i have open updater and select that zip and my 6+ enter in installing mode, but it stuck at 99% and it doesn't continue, someone knows whats wrong with it ?
You should have extracted it.
Extract the zip file unitl you have an update.app and put this into your dload folder. Then try updating again with force update method. If this doesn´t work
zinko_pt said:
Have you stock boot and recovery partitions? No root?
If you have, you must remove Supersu (select full unroot), flash stock partitions and then do the update.
If you don't have root, consider first and foremost a backup with Huawei Backup. Then download the zip file from here and follow the instructions.
Click to expand...
Click to collapse
Hello Zinko_pt,
I have the PE-TL10C900B331 and my phone shows me the PE-TL10C432B571 to update. If I run the automatic update it is not working. At 1% the installing stops and phone reboots.
I tried the german site with the zip and force installing but it is the same
Could you help me? No root phone
Thank you in advance
ofczi said:
Hello Zinko_pt,
I have the PE-TL10C900B331 and my phone shows me the PE-TL10C432B571 to update. If I run the automatic update it is not working. At 1% the installing stops and phone reboots.
I tried the german site with the zip and force installing but it is the same
Could you help me? No root phone
Thank you in advance
Click to expand...
Click to collapse
First I would try to get an update file that I could check its integrity either by MD5 or other form of verification. That would ruled out corrupted file cause.
Second, I would backup all my important things with native Huawei backup app into SD or PC. The I would perform a factory reset and setup just the Google account and Huawei ID if your ROM has one. Also setup HiCare app. Make sure all are updated. Then try to check update and if it works, great, if it doesn´t then try force update.
Only after update I would restore backup.
May I please ask what are the changes in this update? I am a huawei honor 6 plus user.
Thank you in advance for your response!
Does this work on PE-TL10C185B561 ?
As i worked on the steps but it stops at 5% although there is enough free space & battery charge
assemaskar said:
Does this work on PE-TL10C185B561 ?
As i worked on the steps but it stops at 5% although there is enough free space & battery charge
Click to expand...
Click to collapse
No, only it works in PE-TL10C432
zinko_pt said:
First I would try to get an update file that I could check its integrity either by MD5 or other form of verification. That would ruled out corrupted file cause.
Second, I would backup all my important things with native Huawei backup app into SD or PC. The I would perform a factory reset and setup just the Google account and Huawei ID if your ROM has one. Also setup HiCare app. Make sure all are updated. Then try to check update and if it works, great, if it doesn´t then try force update.
Only after update I would restore backup.
Click to expand...
Click to collapse
Thanks it works! Factory reset was needed. I think the problem was, that I encrypted the phone itself before.
ofczi said:
Thanks it works! Factory reset was needed. I think the problem was, that I encrypted the phone itself before.
Click to expand...
Click to collapse
From my experience, encrypted phones don´t go along with automatic turn on/off and updates.
oh.joan said:
May I please ask what are the changes in this update? I am a huawei honor 6 plus user.
Thank you in advance for your response!
Click to expand...
Click to collapse
If you're already on MM, it's just bug fixes and optimizations
Hi
my device run on PE-TL10C185B510, does this update work and what new features it will add?
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
EDIT: I tried to install it through firmware finder and it didn't pass the verification at the end
https://drive.google.com/open?id=0B4baHcoSeBbgY21CVjlPNk45YlE
https://drive.google.com/open?id=0B4baHcoSeBbgYTZiR1ZDeUpoWnc
https://drive.google.com/open?id=0B4baHcoSeBbgV0g3ejBlMXlzdkk
I have downloaded the 3 zips in this update and verified the md5 they are all good if someone figures out how to install this
krchi said:
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
Click to expand...
Click to collapse
I found the same... Gonna try!
Jessooca said:
How did that work out for you Jorge??
Sent from my FRD-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
JorgeCS said:
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
Click to expand...
Click to collapse
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Well the good news I see out of this even if we cannot install is that the update is finally coming after 2 months of the other versions enjoying it for that long. Hopefully it fixes the battery drain.
Sent from my FRD-L04 using Tapatalk
Received the OTA update for the B380 version on my FRD L09C185 yesterday. But no notable change in the battery life till now.
krchi said:
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Click to expand...
Click to collapse
Yep, you can't install this...
Can you install the full firmware from B162 though?
Gus194 said:
Can you install the full firmware from B162 though?
Click to expand...
Click to collapse
You can try and tell us
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Jessooca said:
So the 622mb update file is the correct B385 update file? Can i push it to the phone via adb? Or what's the best way to install it??
Click to expand...
Click to collapse
Likely you'd push both update.zip and the region specific zip to where the stock recovery is expecting, then from a powered-off state use the key combinations to force-udpate. I'm unsure why there are 3 zips this time though since B360 was only 2 zips, I haven't had time yet to look at the contents.
Telperion said:
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Click to expand...
Click to collapse
Mines was just the OTA files you have the full ota files
Jessooca said:
Did you install the update you found?
Click to expand...
Click to collapse
I tried.
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
usmcnyc said:
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
Click to expand...
Click to collapse
Tried that, compatibility error.
Telperion said:
Tried that, compatibility error.
Click to expand...
Click to collapse
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
usmcnyc said:
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
Click to expand...
Click to collapse
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Telperion said:
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Click to expand...
Click to collapse
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
usmcnyc said:
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
Click to expand...
Click to collapse
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Telperion said:
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Click to expand...
Click to collapse
There's a 1.9gb OTA on firmware finder...I'd download it here at work but the internet is too slow, it'd take hours.
This guide is for update within versions if you are rooted, if not, simply download and install de ota or with FF.
If you update to B394 from any version, downloading the last complete packet in update system, it locks the bootloader !!! be advised
If you update to B399 or B401, B402 from B394, downloading the last complete packet in update system, DO NOT LOCK the bootloader !!! good news
My first problem was when I was in B380 and rooted , the b389 ota arrived...then I unroot, put stock recovery and unistalled busybox, but ota failed at 8%
The solution to this :
1 - flash stock recovery from version you have
2 - download the last complete packet in update system , for me 2.41 Gb, not the ota
3 - (optional but useful for future) connect to pc and copy the 3 files downloaded the update in HWOUC to pc
4 - make the normal update in update system
7 - copy supersu 2.82.zip original file or Magisk to SD
8 - Flash last twrp recovery twrp-3.1.1-1-frd , enter in twrp recovery and:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
10 - Make a backup of boot (for future) if you want
11- flash supersu 2.82 original or Magisk
12 - reboot and it's done!!!!!!!!
Update to B394
if you have done all the process and you want now to update to b394, you can uninstall first supersu within options menu saying yes to all questions when uninstalling and without errors or bad uninstallation; then, delete binaries of busybox, flash stock recovery and try to install ota...for me the ota not installed and done with errors.
Then I installed b394 full and locked my bootloader, forcing me to format all because i unlocked the bootloader (remember to activate oem bootloader unlock on and usb depuration on).
After installing the same twrp recovery, I tested the magisk v14 and works perfect, but with an inconvenient, you have to disable the option of magisk manager "magisk hide" to work with fingerprint ,At version 15.3 I didn't see this error.
B394 to B399
Tried the uninstaller of magisk flashed with twrp to unroot and then put the stock recovery and failed, then I flashed stock boot and failed ....finally it worked downloading the last complete packet in update system.Then the habitual, flash twrp recovery, magisk v15.3 from twrp and magisk manager v5.5 in android...and worked perfect
B399 to B401
This time I only unistalled binaries from busybox and flashed stock recovery; then launched Full update (2.41 Gb) without problems.Then flashed twrp, magisk 15.3 from twrp as usual and nothing more...magisk manager detected all ok and I have a rooted device again.
B401 to B402
Simplified the process, now only flash the stock recovery 401 and make the full update packet (2.41Gb). Then flash twrp, enter in twrp, flash magisk 16.0, reboot and that's all. Install busybox script, adaway hosts and done.
Notes:
1 - If the system downloaded automatically the small ota update. you must to try to update with an obvious error, then you can download the full update packet.
1 - the installation of magisk is simple, in twrp flash the magisk.zip , reboot and install magisk manager to control all. This is another app to root and don't need supersu. The advantages to make this is magisk hide, it permits to work with apps that can't work if your phone is rooted.
Wow awsome guide. Thanks alot bro .+1
gopinaidu77 said:
Wow awsome guide. Thanks alot bro .+1
Click to expand...
Click to collapse
happy to help!
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
in the options of the twrp, last tab , there's a thick that says this
deadko said:
in the options of the twrp, last tab , there's a thick that says this
Click to expand...
Click to collapse
Bro , y u should mount vendor?
warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
gopinaidu77 said:
Bro , y u should mount vendor?
Click to expand...
Click to collapse
to root correctly with supersu original version
deadko said:
to root correctly with supersu original version
Click to expand...
Click to collapse
But i dont think modifying vendor part is good .
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
I didn't say nothing to modify nothing, I said thick this option on, and in my case, I did nothing because is marked by default.
deadko said:
I did nothing to modify nothing, I said thick this option on, and in my case, I do nothing because is marked by default.
Click to expand...
Click to collapse
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
gopinaidu77 said:
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
Click to expand...
Click to collapse
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
deadko said:
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
Click to expand...
Click to collapse
Ok , thanks though
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
at the tab up to the right in update system
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
Click on 3 dots on the top right corner . U will see the option.
deadko said:
4 - download the last complete packet in update system , for me 2.41 Gb, not the ota
Click to expand...
Click to collapse
My option is greyed out, what should i do?
Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
fabh2o said:
My option is greyed out, what should i do?
Click to expand...
Click to collapse
the ota is avaliable for you?
deadko said:
the ota is avaliable for you?
Click to expand...
Click to collapse
Yes i'm downloading it right now
Edit: i'm downloading the 2,41 gb update, thanks for the support.
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Snowjack said:
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Click to expand...
Click to collapse
very large process, but you make a hard reset, and my process is to preserve data and use original supersu not the modified , thanks for info
This is totally CLEAN and Typically ENGLISH (OFFICIAL) version that means no chinees APPS no issue.
Donot forget to make a backup before starting.
Steps to Follow: (FOR TWRP installed user)
1. Download 20s OTA file from here.
2. Download 21s OTA file from here. (Donot Download this ZIP file as i got an OTA update of 21S after installing 20s)
3. Goto TWRP recovery.
4. Formate everything. (Cashe, Delvik, Sysytem,Data)
5. Flash the 20s Rom (Provided in STEP 1)
6. After Installing and setting up phone, You are ready to GO BACK to official stock recovery.
Steps to Follow: (FOR already on stock recovery users)
7. Download the 21s recovery (provided in step # 2)
8. change the name to update.zip
9. put it into the root folder.
10. Goto stock updater and slect MANUAL UPDATE from 3dots on top.
11. This is will install the recovery 21s.
12. DONE
Note: you can not install 21s directly on custom recovery as it will give error 7
Can you 1. correct typos 2. move this to https://forum.xda-developers.com/le-2/how-to
Thank you
Thread cleaned up.
If you find some rule violation, please report it.
Also this is not a thread to bring up your personal vendettas. Add the annoying member to your ignore list and move on. No need to use foul language.
Consider this as the first and final warning. If this is repeated any further, there will be action taken against your accounts.
Hope I made myself very clear.
Regards
Vatsal,
Forum Moderator.
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
26s removed
as the provider stopped me to share it. correction in heading done.
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
zogu said:
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
Click to expand...
Click to collapse
As I already mentioned that I have tested these file on my x522(S3) before upload.
Nd x52x series means x520/522/526
Download 20s flash it you will receive 21s automatically
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
Original 26s is available in Chinese only. You can flash it via twrp than root nd remove all Chinese app.
Chinese twrp ?
edan lkr said:
Chinese twrp ?
Click to expand...
Click to collapse
Yes.
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Christhepenguin said:
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Click to expand...
Click to collapse
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
gtd2000 said:
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
Click to expand...
Click to collapse
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Christhepenguin said:
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Click to expand...
Click to collapse
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
gtd2000 said:
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
Click to expand...
Click to collapse
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Christhepenguin said:
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Click to expand...
Click to collapse
I note that this says it's the ROM for the S3.
I'm using the X527 which is the S2 with the Snapdragon chip (now listed as X526 after installing 21s), did you perhaps flash the incorrect ROM?
I had continual problems upgrading from 19s with TWRP - it would go through the whole process and then reboot to 19s..
Even after the replacement of the stock recovery, the first ROM I downloaded (21s) was not accepted. Had to download another one for it to finally work.
Could be a bad download?
Contact
How did you contact leeco and get this. I need all future updates. My phone is rooted and I am unable to completely unroot it and get OTAs.
---------- Post added at 02:59 AM ---------- Previous post was at 02:52 AM ----------
rodogg88 said:
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Click to expand...
Click to collapse
If you don't have TWRP or anything installed, it should work fine if you put the 20s update in the root folder (the folder with the android and download folders). Then just go to system update, press menu, press local update, go through prompts and it should update automatically. Then just repeat the process for the 21s update. If you have twrp installed, I'm pretty sure the chinese ydss version doesn't allow OTA installs. This update requires stock recovery installed because it updates through the recovery. You can find stock recovery images on google (search le s3 stock recovery and click skyneel) or, someone might have posted a recovery image on the le 2 forum. Plz reply if it doesn't work, it worked for me tho.
Is there any bugs? If yes please list. Thank you
does it work for le s3 X626 mtk?
if not, please guide me as I see that this forum support Le S3.
thanks.
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Tsun_Pooka said:
So my question is, can you lock the bootloader with TWRP installed and still access the system?
Click to expand...
Click to collapse
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Tsun_Pooka said:
Hello!
I have unlocked the bootloader of my Mate 10 lite and proceeded to flash TWRP and Magisk onto the device. But in doing so, I get an awful looking screen when I boot the device, so I thought I should relock the bootloader, now that TWRP has been flashed.
...I immediately regretted relocking the bootloader, as the system was inaccessible until I re-unlocked the bootloader and was able to access TWRP and the system again. So my question is, can you lock the bootloader with TWRP installed and still access the system?
Also, if I want to go back to full-stock, I have to download a stock ROM for the system from firmwarefinder and flash it with some tool, correct?
Click to expand...
Click to collapse
How you unlock the bootloader?
bozka1 said:
Unfortunately, it's impossible... If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
Thanks for the tips! By the way, what is dload? If it's a website, I cant find it (the fact that dload is short of "download" doesn't really help). I am now in need of that full-stock ROM.
Tsun_Pooka said:
By the way, what is dload?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/help/formatting-dload-method-t3815949/page2
Whew. I got the bootloader AND FRP locked on me, and now I don't have a usable system. So now, I have to rely on eRecovery to download a 3GBs package and hope all things go well...the problem is, I'd need to find a place that offers fast WiFi...my internet is terrible.
EDIT: Got the system back up thanks to eRecovery. I'm not sure if I want to root or install a custom recovery on the Lite. I've realized even more that I should cherish my older phone, my Samsung Galaxy Win. At least this one isn't complicated or protected by Fort KNOX.
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
usman400 said:
When u play with custom roms, u appreciate the customization/optimizations offered by developers, thanks to them. But with the time, u always feel stock ROM was best for this n that reasons. Recent 2/3 times I was able to use Huru Updater to get back to Stock ROM and it worked well (needs TWRP installed, and you may need to switch to other TWRP if u get error from existing)
You seem to be a beginner, so I would suggest to get help from some friends who can do it for you. Or obviously u can try ur self again and again, and learn good things until something finally works for u. You were able to relock bootloader so it means u have the code for ur device for locking/unlocking, save this code on at least 2 different places (email, google drive, dropbox etc.). Then u can easily unlock ur device again, and install Stock ROM etc.
Click to expand...
Click to collapse
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Tsun_Pooka said:
Custom ROMs are the best thing to happen to the Galaxy Win, even if the available choices all have their compromises. But with the M10 lite, I think it's better to stick with stock and mod it. And I'm not exactly a beginner, but rooting the Galaxy Win and modifying it was no hard ordeal. Or the Galaxy Grand for that matter, which I changed its ROM entirely. The Mate 10 lite however, oh dear (wipes sweat).
I've got the system back up and re-fitted it with TWRP and installed Magisk. And yet, when I try backing up the data partition with TWRP, I meet a peculiar error. Excerpt from recovery.log:
Code:
I:addFile '/data/misc/bluedroid' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
found policy '/data/misc/bluedroid' - '1DK' - '3c2755a577289547'
I:addFile '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' including root: 1
==> set selinux context: u:object_r:bluetooth_data_file:s0
I:Error adding file '/data/misc/bluedroid/K+hpne9pCUEHa,R422fJJA' to '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/FFY5T18328016218/2019-06-08--20-21-17/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
Searching on the internet, I found the solution was to delete the file that stops the operation from finishing. However, using MiXplorer with full root permissions, I...couldn't find the file...? There's only bt_config.bak, bt_config.conf and macbt. Nothing else. What the heck is up with all that?
I'd appreciate a solution to this.
Click to expand...
Click to collapse
I am certainly not up to what u r indicating so cant suggest a solution, earlier in my reply, I was only
indicating my experience with custom ROMs. I havent yet come across a single custom ROM for mate 10
lite that has no problems. Earlier Galaxy S4 Mini, there was custom ROM which was awsome, not a single issue
But for mate 10 lite camera problem is most common. Stock camera app often doesnt work or partially
works, restart of the app etc. You can install open camera, but it does not give u best shots, and filters.
Other issues are already discussed in every custom ROM thread, so I had to come back to Stock ROM
with magisk to remove any system apps that I dont need plus other goodies that magisk offers u (modules)
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Tsun_Pooka said:
Alright, so I am supposed to install 347, but I uhh...can't, because I don't think TWRP is able to do it. What am I supposed to do in order to carry out the update successfully?
Click to expand...
Click to collapse
Flash the stock erecovery whenever i root my phone i always stick with stock recovery not custom recovery(TWRP)
Theres another method to flash the stock recovery but... This is my method on how to flash stock recovery(erecovery)
PC ONLY!!! and MAKE SURE TO HAVE UNLOCKED BOOTLOADER AND FRP!!!
1.Download MultiTool from https://pro-teammt.ru/en/multi-tool-huawei-honor/
2.Make sure to install Huawei driver from the MultiTool
3.Download This File i provided Here https://mega.nz/#!nZxl2AwZ!6qRIIRbLK4Ub80dPMae4HQQ7e-O49_f2BZ8PhbuZTYM
4.Go to MultiTool and go to recovey Section an select file that you download earlier
5.Make sure to CONNECT USB CABLE TO YOR PC now Reboot your device into Bootloader mode by PRESSING VOLUME DOWN BUTTON and CONNECT THE CABLE TO YOUR PHONE
6.Now on the MultiTool click on Flash Recovery_Ramdisk andlet it flash...,
7.Now You Have The Stock Recovery Installed Now You Can Install Offical Firmware Update On Your Phone
8.All Done
I Hope I Help You
I will follow your guide later today or tomorrow! Thank you for the help!
Tsun_Pooka said:
I will follow your guide later today or tomorrow! Thank you for the help!
Click to expand...
Click to collapse
Np
LoneWolfz said:
Np
Click to expand...
Click to collapse
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
Code:
Software install failed!
Failed to check the update files
Please download the package again
> Reboot system now
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Tsun_Pooka said:
I just did your instructions today. All was going well up until installation of the new update. The first time, it rebooted when the progress bar was at 6%, then it rebooted again to the recovery, went up to 6% again before showing this screen:
So I'm back to square one basically.
Also, I can't install updates to the built-in Huawei apps for some reason, even after flashing the stock recovery. I'm not sure what to do with both issues now...
Click to expand...
Click to collapse
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
bozka1 said:
Unfortunately, it's impossible...
You can flash Stock ROM for the system from firmwarefinder (fullOTA-MF only!) using HwOTA, HuRupdater, Huawei Multi-tool (RUFI).
If You want to go back to full-stock with locked bootloader (not re-locked) , You have to flash Service ROM from dload (this process will erase all the data from your device!).
Click to expand...
Click to collapse
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Deathecho said:
But can you unlock the bootloader later on with the same code if you wanted or is this it?
Click to expand...
Click to collapse
Yes you can use the same unlock code again.
LoneWolfz said:
Try to download the update again
Usually when i tried to install new update(100+Mb) i will ended up what the code said but downloading a Full Update(3.49Gb) Fixed the problem
Just refresh the update in setting and install it
Click to expand...
Click to collapse
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Tsun_Pooka said:
The full update actually installed. Thanks for the tip!
I just still can't update my built-in Huawei apps.
Click to expand...
Click to collapse
Np