Database Develop

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"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"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers

tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.

Won't this wipe everything?

jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.

coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk

This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.

So 6.23.651. 10 is not patched for "stagefright"?

Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk

links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on

santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)

chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk

I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.

santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!

yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

Ale-ul00c00b551

Hi. I know, that this is not entirely a new topic, howewer for complete workaround, here is a solution to install B551 chinese firmware. (thanks Sokoban for packages)
1. First install firmware b052 via fastboot.
2. then install firmware b230 via fastboot.
3. install b535 package.
4. then THIS IS THE TRICK: change phone model name by editing build.prop (from: ro.product.model=hi6210sft Change to: ro.product.model=ALE-UL00) -Thanks to Sokkoban
5. IF you registered for beta testing you will receive b551 update via ota. (i dont know if this works for those that doesnt registered at beta testing)
p.s. - now im downloading the update, i will post after downloading is finished.

that would be great! please check if there is a light painting mode on the camera.

here it is:
ALE-UL00C00B551
p.s. i dont manage how to install. Because the local update option doesnt show, and the force update dont work, the service code update just the kernel version updates...

tamaskurti said:
here it is:
ALE-UL00C00B551
p.s. i dont manage how to install. Because the local update option doesnt show, and the force update dont work, the service code update just the kernel version updates...
Click to expand...
Click to collapse
Hello,
I moved to hw/eu B550. But if you want use another way to try install B551 CN
1. Change location to unicomelectric/cn (WIPE)
2. Install B220 via fastboot (WIPE)
3. Use system updater to receive OTA update to B230
4. install and use VPN software like HideMyIP to enter in Huawei account
5. Use System updater to receive OTA update to B535
6. Use my tutorial to recover local update in EMUI 4.0
7. Copy and replace local.prop but write string for B535 firmware
8. And finally try to install B551
I wish you success!

Thanks i will try.

tamaskurti said:
Hi. I know, that this is not entirely a new topic, howewer for complete workaround, here is a solution to install B551 chinese firmware. (thanks Sokoban for packages)
1. First install firmware b052 via fastboot.
2. then install firmware b230 via fastboot.
3. install b535 package.
4. then THIS IS THE TRICK: change phone model name by editing build.prop (from: ro.product.model=hi6210sft Change to: ro.product.model=ALE-UL00) -Thanks to Sokkoban
5. IF you registered for beta testing you will receive b551 update via ota. (i dont know if this works for those that doesnt registered at beta testing)
p.s. - now im downloading the update, i will post after downloading is finished.
Click to expand...
Click to collapse
Great !! Thanks for this!! Do you have installed this update? There are remains special effects in camera - Light painting, etc. from B535?

Please need chinese camera apk, and relative files/folders in system/etc/camera/
i wanna try on eu firmware, thanks.

Unfortunately i didnt have succes with those steps. I got Balong after editing local.prop - and for that the remaining steps doesnt worked.
Note:
- dont forget: this b551 from chinese fw is BETA (Android 6.0)!!! (kernel version from 27. febr.)
- the latest official chinese fw B240 (Android 5.0.1) (kernel version from 23 march) HAS the light painting camera functions.
- Compared the 2 above: the B240 build has more polished options, but beta 535 and probably beta 551 builds has more experimental features. (the commom ones from european fw, but has many more unique features too)

danvo01 said:
Great !! Thanks for this!! Do you have installed this update? There are remains special effects in camera - Light painting, etc. from B535?
Click to expand...
Click to collapse
Yes my friend I installed all Chinese firmware except 551. There are much more best from European firmware. So for me the best firmware for P8 Lite is B240 or B535(Beta 6.0)
This functions didn't present in European firmware
Touch Plus
{
"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"
}
Driving Mode
Hardware Diagnosis
Camera Functions

sokkoban said:
Yes my friend I installed all Chinese firmware except 551. There are much more best from European firmware. So for me the best firmware for P8 Lite is B240 or B535(Beta 6.0)
This functions didn't present in European firmware
Touch Plus
Driving Mode
Hardware Diagnosis
Camera Functions
Click to expand...
Click to collapse
Thanks, I have installed B535, so I want to know if all great camera features are in B551 too.

Damn... this chineese version is really wonderfull , but why don't we also has same features ? :/

Update to v551 is not working due to changes in software - it said: try to download full update. Maybe is problem in rooted phone? Here on B535 is for me probably everything working so for now i will stay at this version.

sokkoban said:
Hello,
I moved to hw/eu B550. But if you want use another way to try install B551 CN
1. Change location to unicomelectric/cn (WIPE)
2. Install B220 via fastboot (WIPE)
3. Use system updater to receive OTA update to B230
4. install and use VPN software like HideMyIP to enter in Huawei account
5. Use System updater to receive OTA update to B535
6. Use my tutorial to recover local update in EMUI 4.0
7. Copy and replace local.prop but write string for B535 firmware
8. And finally try to install B551
I wish you success!
Click to expand...
Click to collapse
hi, what was the country that you changed your ip? I did everything as you say but when I try to update the system updater not appear to b535 but the B240 ...

velosa said:
hi, what was the country that you changed your ip? I did everything as you say but when I try to update the system updater not appear to b535 but the B240 ...
Click to expand...
Click to collapse
here you are OTA B535:
ALE-UL00C00B535

It is important to use OTA update! DO NOT USE these links!
For that chage you IP to Hong Kong and check for B535

managed to install the B551, but always with the model problem...

velosa,How did you manage to do?

armendeo said:
velosa,How did you manage to do?
Click to expand...
Click to collapse
follow the tutorial Sokkoban

Hi, velosa. I tried to follow the tutorial written by sokkoban, but without succes.
1. I dont have the b220 package, but the b230 via fastboot.
2. I cannot receive b535 via updater, but i have the b535 package so i installed from local update.
3. Editing lines:
a. I modified build.prop to showing ALE-UL00. effect: the b551 ota update appear.
b. I modified local.prop --- BUT: witch lines? all showing b551 to modifying to B535, or what. And after that witch permission to set, because i observed, that the original local.prop has rw - r -r, and the posted by sokkoban rwx - r - , maybe.

tamaskurti said:
Hi, velosa. I tried to follow the tutorial written by sokkoban, but without succes.
1. I dont have the b220 package, but the b230 via fastboot.
2. I cannot receive b535 via updater, but i have the b535 package so i installed from local update.
3. Editing lines:
a. I modified build.prop to showing ALE-UL00. effect: the b551 ota update appear.
b. I modified local.prop --- BUT: witch lines? all showing b551 to modifying to B535, or what. And after that witch permission to set, because i observed, that the original local.prop has rw - r -r, and the posted by sokkoban rwx - r - , maybe.
Click to expand...
Click to collapse
Here is B220 fastboot
About the local.prop
This is for B551
Code:
ro.product.CustCVersion=C00
ro.product.CustDVersion=D001
ro.build.display.id=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]
ro.build.version.incremental=C00[B][COLOR="Red"]B551[/COLOR][/B]
ro.build.description=ALE-UL00-user 6.0 HuaweiALE-UL00 C00[B][COLOR="Red"]B551[/COLOR][/B] release-keys
ro.build.fingerprint=Huawei/ALE-UL00/hwALE-H:6.0/HuaweiALE-UL00/C00[B][COLOR="Red"]B551[/COLOR][/B]:user/release-keys
ro.confg.hw_systemversion=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]_SYSTEM
ro.confg.hw_fastbootversion=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]_FASTBOOT
ro.confg.hw_bootversion=ALE-UL00C00[B][COLOR="Red"]B551[/COLOR][/B]_BOOT
ro.fackInfoForCmccIot=false
Replace bold and colored symbols to B535 with following rights RW- R-- R--

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released

Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.

Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse

ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro

Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page

there is already something new on this topic?

not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse

some good news
good news

Rooted on 9.0
{
"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"
}
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls

mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash

mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.

purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent

mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button

otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help

It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone

deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)

Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...

[GUIDE] How to install early Android Pie build on Nokia 5

UPDATE: ND1-612E released. If you have already installed ND1-612D or 558K, you can download it from https://androidfilehost.com/?w=files&flid=287909 and install it manually by dialing *#*#874#*#*.
I strongly recommend you to unlock the bootloader before proceed - I won't tell how to unlock the bootloader in this guide.
Take a look to this video first if you want to know the experience of Android Pie: https://youtu.be/ay6CeonzoD8
Click to expand...
Click to collapse
In this guide, I'll provide two different methods to get Android Pie on your Nokia 5.
Both methods will erase your userdata.
I only tested it on TA-1024, but it should also work on TA-1053.
Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
So the TWRP ported for Nokia 6 can be also used on Nokia 5.
If you want to experience fully customized Android Pie (CN) on your Nokia 5, read this guide:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-install-android-pie-build-t3879899/
To confirm your current firmware revision, please dial *#*#227#*#*.
If you're running ND1-558*-0-00WW-B01, you can use both methods.
If you're running ND1-560*-0-00WW-B01 or ND1-563*-0-00WW-B01, you can only use method 1.
Click to expand...
Click to collapse
Method 1: Use OST LA to flash my homebrew firmware
You should be familiar with this method.
1. Download "ND1-612C-0-00WW-B01.7z" from following site:
Or, you can also download ND1-558K-0-00WW-B01.7z instead then perform method 2.
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=287885
https://fih-firmware.hikaricalyx.com/index_en.html
2. If you have Android 8.x running with LOCKED bootloader, please downgrade bootloader back before processing. If you have unlocked bootloader, you needn't to downgrade the bootloader.
3. Open OST LA or NOST and load the mlf file, in download options, only choose "Normal Download" and "Erase userdata".
If your phone boots suddenly when flashing splash, close OST LA and force power off your phone then flash again.
You can download NOST from https://github.com/StollD/NOST
4. All done, enjoy Android Pie.
Method 2: OTA Update from ND1-558J or ND1-558K
1. Download packages from here:
https://androidfilehost.com/?w=files&flid=287909
https://tpedutw-my.sharepoint.com/:...1BsF1FoPk--uIBfiMbYurDs7NCwOHd05fanA?e=MToYsb
2. Place both packages to root directory of internal storage.
5. Dial *#*#874#*#* to update.
6. After update installed, it will tell you "Encryption failed", click "Factory Reset".
If your phone encountered boot loop, you can enter recovery to perform factory reset manually.
Here's how:
1. Press and hold both volume keys and power key.
2. When you see "shutdown device:" on the left up corner of the screen, release these keys.
3. Connect your phone to a charger.
4. When you see a charging animation, press and hold volume up key and power key.
5. When you feel the phone vibrates, release the power key but only hold the volume up key.
6. When you see Android Robot lying and "No command", press the volume up key with power key holding to get the recovery menu.
7. I needn't to mention what to do next.
Click to expand...
Click to collapse
7. Enjoy Android Pie.
FAQ:
Q1: Can I root it?
A1: Yes, but you must have unlocked bootloader, and Magisk 18 seems unusable.
Q2: How to downgrade bootloader in case I want to roll back without unlocked bootloader?
A2: Rename existing Android 7.x or 8.x OTA package for your model to ND1-9999-0-00WW-B09-update.zip. Then you should know what to do next.
Q3: When will you unlock Nokia X7 / Nokia 8.1?
A3: I don't know!
Q4: When will you get Nokia 9 Penta Camera Phone?
A4: I don't know, don't ask.

How to use method 2 if unlocked bootloader and updated to December security patch
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
And which file download for india android pie

I can watch your video!

Jitender Baloda said:
How to use method 2 if unlocked bootloader and updated to December security patch
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
And which file download for india android pie
Click to expand...
Click to collapse
You still need to check if you're running ND1-558J. If yes, download both packages and follow the guide.
You'll need to update twice.

How to check which version is running on my phone

Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
So the TWRP ported for Nokia 6 can be also used on Nokia 5.
Click to expand...
Click to collapse
Anything else, guy? except stock firmware, please!

Installed on TA-1053
{
"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"
}

Good evening, to use method 2, is it also necessary to have the bootloader unlocked?

Hiiii Sir I am not able to boot into twrp recovery give me solution
Bootloader is unlocked

Jitender Baloda said:
Hiiii Sir I am not able to boot into twrp recovery give me solution
Bootloader is unlocked
Click to expand...
Click to collapse
Flash TWRP-3.2.3-0-PLE.img to recovery partition, then power off the phone:
Code:
.\fastboot oem HALT
Pull the USB cable, connect your phone to a charger. When you see the charging animation, press and hold volume up and power key.

two things in a single post
noe zapata said:
Good evening, to use method 2, is it also necessary to have the bootloader unlocked?
Click to expand...
Click to collapse
(my device is TA-1027, and my version was ND1-558J-0-00WW-B01 before the process)
it is not necessary to unlock the bootloader of the device, in my case (I do not know if it was just good luck) but do not need to restore the phone to the factory state (keep my complete info, even some banking applications that are more delicate than usual with the updates)
-----
Installed on a TA-1027, method 2
No problems encountered after 3 hours of testing.

Does the temporary bootloader unlock method suffice for said unlocked bootloader requirements?
I can't get NOST working as it says i have to be in critical bootloader state(?)
When doing OTA update method, it says file not found

+1

One question
Would I be able to further update my phone by OTA updates or not

the link is broken
the link to download the file from nd1-558j can not be access

Looks like a great tutorial. Too bad that official version is just around the corner. On the other hand.. Are there any plans to make NOST linux-friendly? Not talking about wine.

Benderisas said:
Looks like a great tutorial. Too bad that official version is just around the corner. On the other hand.. Are there any plans to make NOST linux-friendly? Not talking about wine.
Click to expand...
Click to collapse
Yeah official update will roll out January 2019

Question, is adoptable storage feature still present in this pie build?

Respected which file is to download to upgrade Nokia 5 T-1053 to android pie

wick00750 said:
Respected which file is to download to upgrade Nokia 5 T-1053 to android pie
Click to expand...
Click to collapse
Check using *#*#227#*#* then you'll se which version you're using the files doesn't matter but the method does

Question Downgrading from Android 12 to Android 11 without adb

Hi. Is there a way to downgrade from Android 12 to Android 11 without using a computer? I have a firmware package in the root path however phone does not show the possibility to downgrade (i've read it should be in notification panel but it's not). Regards

hello
in first you need the right dongrading firmware for yoyr device :from asus server :
exemple :
{
"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"
}
firmware must be in root or sd card and follow step 3 here:
GUIDE: How to unbrick your Zenfone 6 (ZS630KL)
Hello. This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like. Note: Unlocked bootloader is not required to do any of the actions...
forum.xda-developers.com
regards

I have a correct firmware .zip file in root path however in Android Fasboot menu I have only following options:
- Reboot system now
- Enter recovery (it just takes back to the previosu menu)
- Reboot to bootloader
- Power off
How to use command adb reboot recovery without using a computer (as stated in first post)?

so maybe you have one of the lastest andoid 12 version and now you can't downgrade
if we don't know which version you have and you try to downgrade it's very hard to help you

My current firmware version is 31.1010.0410.72
I'm trying to downgrade by flashing firmware that is visible in the screenshot in post #2

I have the same problem, A12 firmware version is 31.1010.0410.72 , the phone doesn't pop up a message which detected a firmware update info.
maybe also interesting
(in recoverymode only :
Reboot system now
Reboot to bootloader
Enter fastboot
Wipe data/Factory reset
Run graphics test
Power off)
I do have a PC and adb
Can I downgrade with these instructions ? I'm scared:
Android-12-Beta | ASUS Global
www.asus.com
the bottom of the link

eboelens said:
Can I downgrade with these instructions ? I'm scared:
Android-12-Beta | ASUS Global
www.asus.com
the bottom of the link
Click to expand...
Click to collapse
Hi
yes , I did that and it worked
But keep in mind that the script used to downgrade will delete ALL files on your phone.
And as far as I know there is no other way to downgrade the OS from 12 to 11.
regards
Bernd

Thanks,
1.can you tell me when you did that that the bootloader was untouched and locked ?
2.can I do something wrong ?
3.Is it better unlock the bootloader and install twrp ?
(the basic recoverymode gives me no possibilty for use an upgrade or adb sideload)
4. I want install /e/ on it , /e/ expect A11 on it
I'm still scared:
I get an answer from Asus:
Usually, the downgrade is only intended for the first batches of Android 12. According to the data you provided, your phone is up to date and you are therefore using the most recent Android 12 version. The downgrade is not written for such a version given that it is now 4 months old and was intended for users at the time where the first upgrade to Android 12 did not suit.
I will check internally for you what the possibilities are, but keep in mind that there is a chance that we no longer offer a downgrade for this version of Android 12.

Hi
1. can you tell me when you did that that the bootloader was untouched and locked ?
Click to expand...
Click to collapse
As far as I know the bootloader is not touched (I'm not sure if downgrading via that script works with a locked bootloader - but I did not test that)
2.can I do something wrong ?
Click to expand...
Click to collapse
Well, there is always the change that something goes wrong doing this kind of stuff. But regarding the script the only thing you do is starting the script - the script will execute all neccessary steps for the downgrade without user intervention and will only ask for confirmation for the last reboot from the new installed Android 11
But if the script fails for whatever reason you should know how to fix this kind of error before using it.
3.Is it better unlock the bootloader and install twrp ?
(the basic recoverymode gives me no possibilty for use an upgrade or adb sideload)
Click to expand...
Click to collapse
As far as I know you can not downgrade using the standard installation via TWRP or any other recovery ROM (but that might be wrong - you can try it before using the script ...)
4. I want install /e/ on it , /e/ expect A11 on it
Click to expand...
Click to collapse
I never tested that OS, probably you should wait for an A12 based version of the OS.
Usually, the downgrade is only intended for the first batches of Android 12. According to the data you provided, your phone is up to date and you are therefore using the most recent Android 12 version. The downgrade is not written for such a version given that it is now 4 months old and was intended for users at the time where the first upgrade to Android 12 did not suit.
Click to expand...
Click to collapse
The installation of Android 11 here is only to prepare the phone for another Android 11 based distribution as far as I understand so this can be ignored. But if you stay on the original ASUS Android 11 you should update the OS to the latest version of Android 11 released by ASUS after downgrading.
regards
Bernd

sqfaaa said:
Hi. Is there a way to downgrade from Android 12 to Android 11 without using a computer? I have a firmware package in the root path however phone does not show the possibility to downgrade (i've read it should be in notification panel but it's not). Regards
Click to expand...
Click to collapse
Yes, the instructions state to download the zip file into the root directory and wait for a few min after rebooting preferably, no need to unzip. However, the person uploading the files seem to be mixing up the file name format for various devices. You need to check which format is compatible for your device : UL-ASUS_I006D-ASUS or UL-I006D-ASUS. The file name has to be EXACT for the update for upgrade or downgrade to TRIGGER. Hope that helps.

Downgrading to Android 11 was possible with either through PC and the developer system image zip or downloading the zip file and letting the phone detect it, though out of the box after updating to A12 the phone didn't detect the zip. I had to go through the PC and run the update_image.bat from the provided firmware.
Problem is, after starting A11, right after getting an internet connection the phone starts downloading and updating to Android 12 automatically. It can't be stopped, or disabled. God damned infuriating, makes me want to return the phone, but I know there are no other options for this kind of phone.
I have no other option than to unlock the bootloader, root, and disable the update apps through adb. At the same time I'm possibly denied warranty. F*cking senseless bull**** that if I prefer to use A11 I can't without problems. Sure the security patches are a bit older, but people make too big of a deal out of them. You aren't instantly getting hacked even with a few year old security patches.
edit:
I have managed to stop the update service permanently in android 11. You need to enable developer options, then connect usb debugging and open an adb shell, which should as for authorization on the phone.
In the shell, type
pm uninstall -k --user 0 com.asus.dm
pm uninstall -k --user 0 com.asus.UpdateLauncher (this might be just the new phone wizard for restoring files etc)
which should return "Success", even without root. I'm not sure if you need to uninstall both of them, or just dm, which is the main update process. In any case, the whole system update section in settings has disappeared. Fine by me, I can install them manually, which is all that I wanted as an option. You can uninstall other packages too, pm listpackages produces a list of them, and you can filter it like "pm listpackages facebook" to show only results with facebook in the name.

Jgruar said:
Downgrading to Android 11 was possible with either through PC and the developer system image zip or downloading the zip file and letting the phone detect it, though out of the box after updating to A12 the phone didn't detect the zip. I had to go through the PC and run the update_image.bat from the provided firmware.
Problem is, after starting A11, right after getting an internet connection the phone starts downloading and updating to Android 12 automatically. It can't be stopped, or disabled. God damned infuriating, makes me want to return the phone, but I know there are no other options for this kind of phone.
I have no other option than to unlock the bootloader, root, and disable the update apps through adb. At the same time I'm possibly denied warranty. F*cking senseless bull**** that if I prefer to use A11 I can't without problems. Sure the security patches are a bit older, but people make too big of a deal out of them. You aren't instantly getting hacked even with a few year old security patches.
edit:
I have managed to stop the update service permanently in android 11. You need to enable developer options, then connect usb debugging and open an adb shell, which should as for authorization on the phone.
In the shell, type
pm uninstall -k --user 0 com.asus.dm
pm uninstall -k --user 0 com.asus.UpdateLauncher (this might be just the new phone wizard for restoring files etc)
which should return "Success", even without root. I'm not sure if you need to uninstall both of them, or just dm, which is the main update process. In any case, the whole system update section in settings has disappeared. Fine by me, I can install them manually, which is all that I wanted as an option. You can uninstall other packages too, pm listpackages produces a list of them, and you can filter it like "pm listpackages facebook" to show only results with facebook in the name.
Click to expand...
Click to collapse
Thanks for the tip. I was laughing since I had the same exact frustration as you but unfortunately my way of disabling the update was to unlock and relock the bootloader without any changes to avoid a possible brick. Unfortunately I noticed there is a bootloader lock count and it changed to 1 after I did this so my warranty is now voided most likely since they can tell it was unlocked with the counter. Any particular reason why you choose to revert to A11? Cheers
PS
Fortunately I noticed widevine L1 was still intact after unlocking / relocking bootloader so seems to be unaffected by both instances.

maxsterling said:
Thanks for the tip. I was laughing since I had the same exact frustration as you but unfortunately my way of disabling the update was to unlock and relock the bootloader without any changes to avoid a possible brick. Unfortunately I noticed there is a bootloader lock count and it changed to 1 after I did this so my warranty is now voided most likely since they can tell it was unlocked with the counter. Any particular reason why you choose to revert to A11? Cheers
PS
Fortunately I noticed widevine L1 was still intact after unlocking / relocking bootloader so seems to be unaffected by both instances.
Click to expand...
Click to collapse
It seems wanting to root your phones is harder and more inconvenient every year. It should really be a simple process that simply allows you to decide what is running or installed on your phone. I can understand the security implications, but that should be all be dealt with a disclaimer. It is now your responsibility to make sure you don't allow shady programs root access, that's it.
With every new phone I get it's more convoluted, there are less roms available, less people on the forums. Driven to extinction because god damned the manufactures don't care about you after they get your money.
Well anyway, my reason was simply that I really really dislike the UI in 12. Doesn't sit well with me at all, and can't get used to it.
I know I'm making things difficult for me but I refuse to accept that garbage and if I want to run 11 for the time being I should be able to. It's the principle.
I'm going to have to root in the end, but just for now I wanted to test drive the phone without too much work if it's going back.

@eboelens have you received an answer from Asus?
@eboelens @bnsmb @Jgruar when trying to downgrade by method from https://www.asus.com/Content/Android-12-Beta/ I'm getting following error "Command not supported in default implementation" and since it worked for you I have a following questions:
1. You were using Recovery mode or Fastboot mode?
2. Have you enabled USB debugging in Developer options? I did.
3. Have you enabled "OEM unlocking" in Developer options? I tried, but I can''t cause it's visible in the search but not in Developer options (looks like a bug).

sqfaaa said:
@eboelens have you received an answer from Asus?
@eboelens @bnsmb @Jgruar when trying to downgrade by method from https://www.asus.com/Content/Android-12-Beta/ I'm getting following error "Command not supported in default implementation" and since it worked for you I have a following questions:
1. You were using Recovery mode or Fastboot mode?
2. Have you enabled USB debugging in Developer options? I did.
3. Have you enabled "OEM unlocking" in Developer options? I tried, but I can''t cause it's visible in the search but not in Developer options (looks like a bug).
Click to expand...
Click to collapse
Hi
the instructions from the Beta Website will only work if the phone is connected via USB and booted into the bootloader (=fastboot mode).
USB debugging on or off should be irrelevant for this action (I did the reinstallation using this method with and without USB debugging enabled)
AFAIK the phone must be unlocked to reinstall via fastboot commands . Unlocking the phone can/must be done with the Unlock App from ASUS:
https://www.asus-zenfone.com/2015/10/official-asus-zenfone-2-unlock.html
regards
Bernd

@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?

bnsmb said:
AFAIK the phone must be unlocked to reinstall via fastboot commands . Unlocking the phone can/must be done with the Unlock App from ASUS:
https://www.asus-zenfone.com/2015/10/official-asus-zenfone-2-unlock.html
regards
Bernd
Click to expand...
Click to collapse
I haven't unlocked and did the downgrade through fastboot mode with the A11 image file and instructions from ASUS beta program. If they provide the image freely and don't mention anything about voiding the warranty it has to work without unlocking. Just had to make sure my usb connection was stable, had a problem of corruption during install with one cable.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
Make sure your device is visible to the computer (fastboot devices) and is in the fastbootd mode (like in your 1st picture).
You then should be able to excecute the "update_image.bat" file from the package, but I used "update_all.bat". Not exactly sure what the difference is, but someone at some post said to use that. I think the update_image.bat would have worked fine if I had a stable usb connection at the time.
Male sure to disable the update service via the method I posted, or else the Android 11 version will force an install of A12 as soon as it gets a network connection.

sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
HI
see the other reply - it seems to work without unlocking ( I did not test this -- all my phones are unlocked)
regards
Bernd

Thanks.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
Neither of those modes is correct. For me mode from the below screenshot worked.
@Jgruar The version that we uploaded via script is a very old Android 11. How did you update from it to the latest Android 11 version since you have uninstalled update service?
Comment for other people, who just bought Zenfone 8 and are struggling like I did: Consider returning the phone. UI of Android 11 is better than 12, but it's still much worse than Android 8 with Samsung add on (Samsung Galaxy S7). Notification list has ridiculously big margins and the opacity is too big (it's hard to see what's in the background). Also view of last application is much worse (one can see name of only one application - the one which is currently open and in Samsung I could see names of last 5 apps). IMHO using pure android is a pain and it's better to buy some phone with pre installed add on or root the Asus but that's voiding the warranty and costs time.

sqfaaa said:
Thanks.
Neither of those modes is correct. For me mode from the below screenshot worked.
@Jgruar The version that we uploaded via script is a very old Android 11. How did you update from it to the latest Android 11 version since you have uninstalled update service?
Comment for other people, who just bought Zenfone 8 and are struggling like I did: Consider returning the phone. UI of Android 11 is better than 12, but it's still much worse than Android 8 with Samsung add on (Samsung Galaxy S7). Notification list has ridiculously big margins and the opacity is too big (it's hard to see what's in the background). Also view of last application is much worse (one can see name of only one application - the one which is currently open and in Samsung I could see names of last 5 apps). IMHO using pure android is a pain and it's better to buy some phone with pre installed add on or root the Asus but that's voiding the warranty and costs time.
Click to expand...
Click to collapse
>>Neither of those modes is correct. For me mode from the below screenshot worked.
That 's the bootloader (with fastboot support)
regards
Bernd