EMUI 9 / Pie (Beta) update for C432 available at FF - Huawei P10 Guides, News, & Discussion

Hey guys,
On TeamMT's firmware finder is EMUI for VTR-L09 and VTR-L29 International (C432) available.
Post here if you tried to update and if it's works or not.
Edit: Updated B381 with a modified version of my guide. I'll release it today for testing purposes. I didn't do a factory reset, all my files are still there. But I noticed that the system works slowly.

Did you update through e-recovery in ff?
If you do factory reset, it will probably fix the slow performance.
Does the device show as official in play store/about? Is it beta or official release? Did you upgrade from B384?

skolebolle said:
Did you update through e-recovery in ff?
If you do factory reset, it will probably fix the slow performance.
Does the device show as official in play store/about? Is it beta or official release? Did you upgrade from B384?
Click to expand...
Click to collapse
I updated with my own script I released here (tutorial 4)
It's not slow anymore, I did a reboot and now everything works fine.
I upgraded from B381.
There's no information by Huawei if it's beta or stable.
And what do you mean with official in play store? Couldn't find anything like that.

He talks about 'certified device' under settings in google play.

Firicel69 said:
He talks about 'certified device' under settings in google play.
Click to expand...
Click to collapse
There's nothing about that, I googled some screenshots and the part with "Device certification" is completely missing. Play Services updated directly after I launched Pie for the first time.
See the attached screenshot.

Jannomag said:
I updated with my own script I released here (tutorial 4)
It's not slow anymore, I did a reboot and now everything works fine.
I upgraded from B381.
There's no information by Huawei if it's beta or stable.
And what do you mean with official in play store? Couldn't find anything like that.
Click to expand...
Click to collapse
Works just fine, tnx.
I doubt that beta fw would be up to c432. Besides a day ago Oreo downgrade popped up there was no fw update this month.

Jannomag said:
There's nothing about that, I googled some screenshots and the part with "Device certification" is completely missing. Play Services updated directly after I launched Pie for the first time.
See the attached screenshot.
Click to expand...
Click to collapse
It should come after some time. Try reset phone and wait. If it says uncertified it's bad. If it says certified, it's safe for us to upgrade before official release.

skolebolle said:
It should come after some time. Try reset phone and wait. If it says uncertified it's bad. If it says certified, it's safe for us to upgrade before official release.
Click to expand...
Click to collapse
I'm on Pie now for 10 hours and installed some apps via Play Store. Still nothing to see there.
EDIT: I removed the data and cache from play store app. Now it's saying "Not certified". So I checked some guides and on the official Google page to enable custom roms for using Googles services there's the command "adb root".
My output is "adbd cannot run as root in production builds", so maybe it's still in beta. I don't know what this means for me but I hope there will be any problems with Google in the future for me.
EDIT2: I followed this tutorial and added my device to the device list. Play Store still shows uncertified but I'm hoping, that this won't affect me. At the moment I can use everything as before.

Jannomag said:
I'm on Pie now for 10 hours and installed some apps via Play Store. Still nothing to see there.
EDIT: I removed the data and cache from play store app. Now it's saying "Not certified". So I checked some guides and on the official Google page to enable custom roms for using Googles services there's the command "adb root".
My output is "adbd cannot run as root in production builds", so maybe it's still in beta. I don't know what this means for me but I hope there will be any problems with Google in the future for me.
EDIT2: I followed this tutorial and added my device to the device list. Play Store still shows uncertified but I'm hoping, that this won't affect me. At the moment I can use everything as before.
Click to expand...
Click to collapse
Unfortunately, this happens when the firmware still is not "approved for installation". That the device is not certified can make it hard to install bank apps, Netflix, Spotify and more. Also I think you will not receive any more ota. I would go back to b384 and wait to get official update.

skolebolle said:
Unfortunately, this happens when the firmware still is not "approved for installation". That the device is not certified can make it hard to install bank apps, Netflix, Spotify and more. Also I think you will not receive any more ota. I would go back to b384 and wait to get official update.
Click to expand...
Click to collapse
I always installed firmwares which aren't approve for installation (checked with FF). Never had any issues with banking, netflix, spotify and other apps.
But I never checked this, because I didn't know this.
Is this the same as SafetyNet?

Downgrade from 9 to 8
Jannomag said:
Hey guys,
On TeamMT's firmware finder is EMUI for VTR-L09 and VTR-L29 International (C432) available.
Post here if you tried to update and if it's works or not.
Edit: Updated B381 with a modified version of my guide. I'll release it today for testing purposes. I didn't do a factory reset, all my files are still there. But I noticed that the system works slowly.
Click to expand...
Click to collapse
Hello,
How downgrade my VTR-L09C432 from android 9 to android 8 or how relock bootloader on android 9?

coabog said:
Hello,
How downgrade my VTR-L09C432 from android 9 to android 8 or how relock bootloader on android 9?
Click to expand...
Click to collapse
If you're willing to test it, you can try my script. Please use tutorial #3 and this TWRP.
The reason for tutorial #3 is this guide I've found. The linked script works the same as my script does.
Just follow tutorial#3 but first completely remove any device lock like pin and fingerprint.
Otherwise, there's no official method for the P10. I'll try my own when I have time, maybe today's afternoon.

How's the phone compared to oreo? Any difference in terms of daily performance? Smoother?

Firicel69 said:
How's the phone compared to oreo? Any difference in terms of daily performance? Smoother?
Click to expand...
Click to collapse
No issues, the animations feel a bit smoother I think.
I noticed that gboards haptic feedback failed sometimes which is kinda annoying. Mostly I type very fast and it feels like I missed a key when I'm in a flow. That's the only bug I noticed.
Face unlock is way faster btw

Did they change the camera app or is it still the same? Thanks .

Camera app is a bit different, has adittional slider to switch functions, more convenient imo.

@Jannomag do you have 'Game Suite' app on pie? I am confused if it disappeared or I've missed some update with gpu turbo patch.

On Pie, there is something like Apps assistant. You can find this in Settings > Apps.

lukastob said:
@Jannomag do you have 'Game Suite' app on pie? I am confused if it disappeared or I've missed some update with gpu turbo patch.
Click to expand...
Click to collapse
If I remind correctly it was there, yes. But I never used it.

So we can get it in about one or two weeks?
https://bit.ly/2H9FM3W

Related

the brush EMUI3.0 B008] split-screen multitasking | real-time speed, etc. | HRT_KangV

while surfing huawei china forums I found this custom Rom (http://cn.club.vmall.com/thread-2182114-1-1.html)
Did any one tried it .. and if yes what is your feedback about it ?
I haven't tried his newest ROM B008, but I have tried several of his older modded ROM for the X1. Issue I have is that I can't get google play store or google services to work. I've tried varies version of goole play store and google service framework, but never could get it to work. Split view is nice...but it isn't automatic, you have to manually select the windows; not as good as Samsung implementation, but better than nothing.
Ahmed.ragab said:
while surfing huawei china forums I found this custom Rom (http://cn.club.vmall.com/thread-2182114-1-1.html)
Did any one tried it .. and if yes what is your feedback about it ?
Click to expand...
Click to collapse
it is sweet, i m using it, only 2 points to note before flashing it:
1) u need to be already on the official B008 rom (otherwise u will get the write to cust error)
2) the bootloader of your X1 must be already unlocked (if not u cannot flash via ADB)
for those using non china 4G sim, u may also get android.phone.com FC-ing during initial boot, no amt of wiping DATA or Cache (of phone itself or apps e.g. contacts, phone etc the usual sugg when u google the problem) will work, in this instance, simply switch to airplane mode, proceed to connect the X1 to your wifi and go abt dong all the updates via Huawei app store, i m not sure which update cured the problem, but when I switch off airplane mode after that, the FC disappears .. YMMV
---------- Post added at 05:17 AM ---------- Previous post was at 05:07 AM ----------
acuratlsfan said:
I haven't tried his newest ROM B008, but I have tried several of his older modded ROM for the X1. Issue I have is that I can't get google play store or google services to work. I've tried varies version of goole play store and google service framework, but never could get it to work. Split view is nice...but it isn't automatic, you have to manually select the windows; not as good as Samsung implementation, but better than nothing.
Click to expand...
Click to collapse
there is actually a very simple workaround for google services (other than google+, which there is another solution), and it doesnt involve 'hacking' or meddling with system files, rooting is not even needed (although KangVIP rom comes pre-rooted)
because even on china roms, Huawei has actually implemented the google framework within, all we need are the correct apps, simply launch the default Huawei Store (App Centre) and search for Google Play, GoogleCalendarSyncAdapter and GoogleContactsSynAdapter. After installation of Play, just launch it and install other Gapps u need from there.
Hi all,
Small point to note, somehow Google always translates the Chinese word "shua" literally as the verb "brush" but it actually means the verb "flash" in this context.
Note that translations of "shua ROM" will end up being "brush ROM" instead of "flash ROM".
FC ing with non china sim card
potatohead said:
it is sweet, i m using it, only 2 points to note before flashing it:
1) u need to be already on the official B008 rom (otherwise u will get the write to cust error)
2) the bootloader of your X1 must be already unlocked (if not u cannot flash via ADB)
for those using non china 4G sim, u may also get android.phone.com FC-ing during initial boot, no amt of wiping DATA or Cache (of phone itself or apps e.g. contacts, phone etc the usual sugg when u google the problem) will work, in this instance, simply switch to airplane mode, proceed to connect the X1 to your wifi and go abt dong all the updates via Huawei app store, i m not sure which update cured the problem, but when I switch off airplane mode after that, the FC disappears .. YMMV
Click to expand...
Click to collapse
this method is won't work for me.
even updated everything but my phone still get com.android.phone FC.
what can I do??
sampei said:
this method is won't work for me.
even updated everything but my phone still get com.android.phone FC.
what can I do??
Click to expand...
Click to collapse
Sorry, I really have no idea what I had done to result in the FCs disappearing. In fact, I wasnt expecting it to be.
My original intention was to play around with it and conduct some experimental tweaks since I was already on it before reflashing to get rid of the FCs.
One other thing that may have caused the FCs to go away is Xposed framework, you can try installing it.
The attached file below is an old version, install it then update to version 2.5.1 via the Xposed app; I also installed the App Settings module (version 1.8) for per app DPI setting. In fact, this is the tweak I wanted to try on EMUI 3.0 B008, it worked on EMUI 2.3 B010 and I was hoping for the same favorable result on EMUI 3.0. It did.
It was after the above that I re-enabled mobile/data and discovered to my surprise the FCs were gone.
YMMV.
Unfortunately I couldn't make it so I'm back to use EMUI 2.3 B010.
Thank you for suggest me some methods.
ps / I got sme results. with Australian Boost sim is worked but Japan Softbank and Singapore StarHub SIM is won't work.
@potatohead
Today I try fix again then suddenly your method is work for my phone. I carefully follow methods then work.
Thanks.
sampei said:
@potatohead
Today I try fix again then suddenly your method is work for my phone. I carefully follow methods then work.
Thanks.
Click to expand...
Click to collapse
can you tell me to do this step by step?
i don't understand chinese
thank u
Well anyone please upload that file on any other websites, I i have tried to download it with many ways but no way succeed
Edit : thank you all, I downloaded it by changing my IP with Psiphon app
1. Install KangVip rom.
2. then switch on airplane mode. (For stop to show phone FC )
3. Install above xposed for Huawei apk.
4. Update xposed to 2.5.1 ( version is very important any other versions are won't work )
5. Install xposed framework then reboot.
6. After rebooted, turn off airplane mode. FC IS GONE ALREADY.
Sent from my X1 7.0 using XDA Free mobile app
hopeless with this, always stop in the middle of download
anyone have another link?
Try it ! hopefully you can install.
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v29_665be7.apk
alexkarimovic21 said:
hopeless with this, always stop in the middle of download
anyone have another link?
Click to expand...
Click to collapse
if you are referring to problematic download of kangvip's mod, try this
http://www.mediafire.com/download/04izc31qkkl4d2q/X1-EMUI3.0-B008_img.rar
potatohead said:
if you are referring to problematic download of kangvip's mod, try this
thanks for the link, and done flashing but for me its feel laggy and the phone become so hot
i try to back to official B008 with flash update.app via sd card but not success, anyone have solution?
Click to expand...
Click to collapse
alexkarimovic21 said:
potatohead said:
if you are referring to problematic download of kangvip's mod, try this
thanks for the link, and done flashing but for me its feel laggy and the phone become so hot
i try to back to official B008 with flash update.app via sd card but not success, anyone have solution?
Click to expand...
Click to collapse
have u tried the 3-buttons method of flashing?
this method shd work for flashing of any full ROM
http://forum.xda-developers.com/showpost.php?p=58123000&postcount=25
Click to expand...
Click to collapse
potatohead said:
alexkarimovic21 said:
have u tried the 3-buttons method of flashing?
this method shd work for flashing of any full ROM
I did that method too but unsusccesfull, but after many reboot my phone start running well, now i use this ROM as a daily (without lockscreen)
thank you very much
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hi Potoatohead, after I installed the Xposed apk, I couldn't install the framework. I just got a hang (4.4.2 Emui 3.0). Downloading the 2.5.1 update and trying to install that result in install failed. Any clues?

Android 7.1.1 now available --- [Dead Thread about Preview]

[Dead Thread about Preview]
See this thread for discussing rooting 7.1.1 : -
Root Android Nougat 7.1.1 -- [NMF26F] -- SuperSU v2.78 SR5
Factory Image!
Successfully used flashfire to flash above factory image, along with SuperSU v2.78 SR4 ( instead of everroot) and ElementalX 5.05
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Tapatalk on Nexus 9
ritchea said:
Flashed with Flashfire. Root intact. Haven't looked at anything else yet.
Click to expand...
Click to collapse
Did you use everroot option of flashfire? Which is still using su v2.78 SR1? I thought we would have needed SR4 for 7.1.
I need to make some backups and probably will flash this version on Thursday!
Made backups today (23/11) and successfully flash it! OP update with links!
Yes.
Tapatalk on Nexus 9
I flashed it a few minutes ago over stock 7.0 without wiping data and it seems to be the fastes and smoothest experience I ever had with this device. Can't say much more and didn't try to root, but I switched a few times between my two users und it's still fast and smooth. After switching between my users for two times with 7.0 a reboot was much needed! :fingers-crossed:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
jaju123 said:
Mine is stuck at booting animation. No idea why first time this has happened to me before. Or does it just take like 20 minutes on first boot or what?
I flashed it manually through fastboot like normal.
Click to expand...
Click to collapse
20 minutes is too long. Have you tried to just power off then on? Sometimes, that's all it takes. It's happened to me but not for this flash.
Tapatalk on Nexus 9
seems way faster than 7.0 so far.... I just did a full reset on 7.0 a week ago and experience immediate lag after I installed my apps. I flashed the 7.1 dev image today and went through the same process. So far so good. I'll report back after a couple of weeks of usage.
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Had to post. Clean flashed new preview , temp boot of twrp to flash latest SU (SR4) for root and set up as new device. Best google effort yet! No problems adjusting build prop to enable assistant and both Pixel and Nova Launchers are go as is new systemless option adaway. Couldn't help notice how responsive UI is and chrome is stable for me 4-5 tabs in using sites like fark.com and no/very few redraws after pushing the tablet with moderate demands. Looking forward to the December release, noticed USB charging was still fairly slow still, hopefully the batt life is ok too. Go Google, they might just catch up to Craig's AOSP version/kernel performance if they're not careful !
Completed clean flash this preview
Rootless with supersu 2.78 sr4
Disable some app not use, very smooth
the.teejster said:
Did anyone enrolled in the beta program get the OTA yet ?
Previously I got it the same day an announcement was made. Nothing received yet. As a matter of fact, I didn't even receive the November security update this month.. Never rooted, never modified.
Click to expand...
Click to collapse
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
I never flashed a custom rom on my N9 nor has it ever been rooted. Still haven't received Nov update nor the Beta program update.
If you flash a factory image then you are fully stock and you should receive all updates from google.
Gold Ribbed said:
Same here. My device is enrolled but no update. I had to manually flash the November update. I did wonder if it was anything to do with flashing custom Roms. I am on full stock Google image but no update yet.
Click to expand...
Click to collapse
Has anyone received the ota yet? Or is google only doing a factory image this time for some reason?
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Gold Ribbed said:
Just manually flashed the stock preview. Much better than the stock 7.0 which is virtually unusable . This preview is solid and stable..
Click to expand...
Click to collapse
the.teejster said:
One of the main benefits of enrolling in the beta program was to be able to get OTA updates and not lose your data. Other devices in the program have received the OTA. Disappointing that the N9 hasn't to this date.
Click to expand...
Click to collapse
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Flashfire
Click to expand...
Click to collapse
is the most advanced on-device firmware flasher available for rooted Android devices.
Click to expand...
Click to collapse
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
corkiejp said:
You can flash factory images without affecting your data partition. It is called "dirty flashing" for a reason.
My device has been through loads of updates, + the previous Preview images, by that method!
Checkout "Flashfire" app!
Click to expand...
Click to collapse
the.teejster said:
I realize this is the wrong thread for this discussion but to conclude. I'm not rooted and choose not to go down that path. My last comment still stands.
Click to expand...
Click to collapse
It is also possible to flash factory images with fastboot without wiping data.
Flashfire is just a convenient app for doing it (with needing a computer) for people who are rooted.

The Nexus 6P May build has been pulled?

The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.

[App] AsusUpdater v1.0.4 - WW System updates for Tencent/Unlocked phones

Hi everyone,
I recently bought a Tencent edition of the ROG Phone 2, and was a bit annoyed to see that automatic system updates no longer worked after converting it to a WW ROM. I did some digging and found out that ASUS uses the IMEI of the device to track what updates the device is entitled to, including the region. So a CN IMEI would only be entitled to CN firmware updates.
That's what led me to write this app that interacts directly with the ASUS servers to look for updates, but using a spoofed IMEI that makes the server think it's WW. It was a bit of work to figure out how it all works, but I have managed it, and it seems to work as it should - I successfully upgraded from .44 to .64 just a short while ago using the app.
Download
v1.0.4:
- Allow input of custom IMEI
- Fix issues on Android 10 beta
- Other fixes
https://github.com/HomerSp/AsusUpdater/releases/download/v1.0.4/AsusUpdater-v1.0.4.apk
v1.0.3:
- Enable downloading updates via mobile data
- Several UI fixes
https://github.com/HomerSp/AsusUpdater/releases/download/v1.0.3/AsusUpdater-v1.0.3.apk
v1.0.2:
- Fix updates not working when on CN fingerprint (for real this time)
https://drive.google.com/open?id=1IgDM9T6u4z4LLLudHYIg3hb6OPw7Qz29
v1.0.1:
- Fix updates not working when on CN fingerprint
https://drive.google.com/open?id=1_hYwPi3Q_8tW6gaBnQvNmohWR4Q4wP2o
v1.0:
- Initial release
https://drive.google.com/file/d/1KVh8OmgMxMg-jQfpF2LmIW4cqBDKXtyz/view?usp=sharing
Instructions
The app is very basic, but it does what it should. It will check for updates every hour, and send you a notification if it has found an update - or you can force a check by opening the app and pressing the button.
Once the update is downloaded (the updater will notify you when it's done), you will need to restart the device, and upon booting again you will be notified by the system that a system update has been found and be asked if you want to apply it or not.
That's really it, the system will handle the updating from there.
Note 1:
You need to be on completely stock firmware for the update to apply properly. The bootloader can be unlocked, but you can't be rooted or such.
Note 2:
For the updater to work correctly you'll have to allow it to auto-start by going to System settings -> Battery -> PowerMaster -> Auto-start manager and make sure ASUS updater is ticked. Not doing this means you will have to run the app once each boot for notification to work correctly.
Note 3:
If the update fails (after rebooting and starting the update), I will need a log to be able to figure out what's wrong. The relevant tag is UpdateLauncher.
Source code:
AsusUpdater - Github
Do let me know if it's working for you, or if you can think of any improvements I can make.
Wow great work mate I will download the app when the next update will be available.
I wish you can develop something for volte and vowifi.
avivv said:
Wow great work mate I will download the app when the next update will be available.
I wish you can develop something for volte and vowifi.
Click to expand...
Click to collapse
+1 for VOWIFI
Sent from my ASUS_I001DE using Tapatalk
---------- Post added at 12:24 AM ---------- Previous post was at 12:22 AM ----------
Hope you can get some more app for our lovely ROG 2 like this. Keep it up...
Sent from my ASUS_I001DE using Tapatalk
This is awesome and quite helpful! I appreciate your time and effort in making this!
HomerSp said:
Hi everyone,
I recently bought a Tencent edition of the ROG Phone 2, and was a bit annoyed to see that automatic system updates no longer worked after converting it to a WW ROM. I did some digging and found out that ASUS uses the IMEI of the device to track what updates the device is entitled to, including the region. So a CN IMEI would only be entitled to CN firmware updates.
That's what led me to write this app that interacts directly with the ASUS servers to look for updates, but using a spoofed IMEI that makes the server think it's WW. It was a bit of work to figure out how it all works, but I have managed it, and it seems to work as it should - I successfully upgraded from .44 to .64 just a short while ago using the app.
Download
https://drive.google.com/file/d/1KVh8OmgMxMg-jQfpF2LmIW4cqBDKXtyz/view?usp=sharing
Instructions
The app is very basic, but it does what it should. It will check for updates every hour, and send you a notification if it has found an update - or you can force a check by opening the app and pressing the button.
Once the update is downloaded (the updater will notify you when it's done), you will need to restart the device, and upon booting again you will be notified by the system that a system update has been found and be asked if you want to apply it or not.
That's really it, the system will handle the updating from there.
Note 1:
You need to be on completely stock firmware for the update to apply properly. The bootloader can be unlocked, but you can't be rooted or such.
Note 2:
For the updater to work correctly you'll have to allow it to auto-start by going to System settings -> Battery -> PowerMaster -> Auto-start manager and make sure ASUS updater is ticked. Not doing this means you will have to run the app once each boot for notification to work correctly.
Do let me know if it's working for you, or if you can think of any improvements I can make.
Click to expand...
Click to collapse
Hats off for you Senior.
I'm on WW_ZS660KL-16.0622.1906.19-0, was never able to update this phone that I imported from China to EU, and your tool doesn't find new updates available to install either. Could it be that I'm on ww firmware but cn fingerprint? (seller's doing, not mine). I'm 100% on stock everything (meaning, I haven't tinkered with the software one bit). Would appreciate some clarification, thank you.
Juraviel said:
I'm on WW_ZS660KL-16.0622.1906.19-0, was never able to update this phone that I imported from China to EU, and your tool doesn't find new updates available to install either. Could it be that I'm on ww firmware but cn fingerprint? (seller's doing, not mine). I'm 100% on stock everything (meaning, I haven't tinkered with the software one bit). Would appreciate some clarification, thank you.
Click to expand...
Click to collapse
As it turns out, the CN fingerprint does affect it; I didn't think it would, but one of the props that the app uses to send to the server actually changes based on the fingerprint.
I've fixed it, so please try this, and let me know if it works:
https://drive.google.com/open?id=1_hYwPi3Q_8tW6gaBnQvNmohWR4Q4wP2o
For me it's the same, unfortunately. Not sure what I could be doing wrong.
Juraviel said:
For me it's the same, unfortunately. Not sure what I could be doing wrong.
Click to expand...
Click to collapse
Sorry, I had completely missed another reference to the CN fingerprint. Try this latest one (tested and working for me with fingerprint changed to CN):
https://drive.google.com/open?id=1IgDM9T6u4z4LLLudHYIg3hb6OPw7Qz29
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Just change the fingerprint to WW, having a WW rom with CN fingerprint will cause more issues.
Juraviel said:
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Click to expand...
Click to collapse
A log would say what's wrong, most likely one of the partitions isn't completely stock - they probably botched something when they flashed the WW ROM on it. Feel free to send me a log and I can have a look.
avivv said:
Just change the fingerprint to WW, having a WW rom with CN fingerprint will cause more issues.
Click to expand...
Click to collapse
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Juraviel said:
It found and downloaded this time, but the update process itself fails, I tried twice. May be because my version is too old? It's the same if I download the update file manually and put it on root, phone detects it after reboot but unable to flash the update.
Click to expand...
Click to collapse
Juraviel said:
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Click to expand...
Click to collapse
Sure you can, it's easy just follow this guide, no need to root or to wipe and it takes 5 minutes
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
Juraviel said:
I can't 'just change it' without rooting the phone, unless there's a way in unaware of. I was planning to do that once android q releases. Otherwise, it's just too much hassle with currently available untested methods.
How do I do that @HomerSp
Click to expand...
Click to collapse
I would indeed recommend changing the fingerprint to WW as having a CN fingerprint causes a whole bunch of issues, although that most likely won't fix your upgrade issue. The EDL method is really easy, and can be done in a couple of minutes - and does not require rooting.
As for the log, have you used adb and such? I just need a logcat. There are plenty of guides on how to do that, so I won't go into that here.
You were right it was fairly easy, although the original tutorial should have a warning that entering in edl mode causes the screen to go black and the phone completely unresponsive! Other than that it went smooth. You did an amazing job.
Edit: well, actually, it still fails I'll keep at it
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
---------- Post added at 10:41 PM ---------- Previous post was at 09:45 PM ----------
kashif31 said:
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
Click to expand...
Click to collapse
Nvm there was an error with the file which was downloaded by your app .. i download the file again n it worked
kashif31 said:
Hey I changed my fingerprint from cn to ww now I am fully covertred I download the update from your app the update size is 128mb I rebooted my device it detected the update but when I click on update it says update failed any idea what's wrong ?
---------- Post added at 10:41 PM ---------- Previous post was at 09:45 PM ----------
Nvm there was an error with the file which was downloaded by your app .. i download the file again n it worked
Click to expand...
Click to collapse
If you get this again I would need a logcat to be able to help you. The update dialog you see on reboot isn't from my app, but it's a system app that I have no control over - so there's no way of telling what's causing it to fail, except for a log.
HomerSp said:
If you get this again I would need a logcat to be able to help you. The update dialog you see on reboot isn't from my app, but it's a system app that I have no control over - so there's no way of telling what's causing it to fail, except for a log.
Click to expand...
Click to collapse
How to open logcat
Thanks so much for this app, I was thinking I would just need to apply the updates manually as they came out. It doesn't seem to be downloading the update when I tap the button though, my data usage stays in the KB/s range or lower. Anything I might be doing wrong?

Please Help with beta firmware downgrade of CMR-AL09

Hello guys, my device has a locked bootloader so my flashing options are limited. I wanted to upgrade to Android 9 and I think I may have flashed a beta wrong firmware (dload method) meant for the WiFi only version. Although my device boots normally and looks like its upgraded to Android Pie, the play store does not have a lot of apps I want to use especially Netflix does not work.
I've been trying to flash the stock firmware using the force dload update method for the past two days but nothing works, it just fails. I've downloaded and tried like 10 different firmwares but nothing is recognised.
Does anyone have any suggestions?
I have no idea but.. did you ever try "HiSuite"? Well for my P30 Pro phone I downgraded using it. That was from Beta 10 to 9. When Beta 10 had just came out.
Zeblade said:
I have no idea but.. did you ever try "HiSuite"? Well for my P30 Pro phone I downgraded using it. That was from Beta 10 to 9. When Beta 10 had just came out.
Click to expand...
Click to collapse
Yeah, Hisuite didn't work. Looking at the build number, It seems to be the M5 Pro firmware but the very first version of Android 9. It seems some people had the issue of Google Play not being certified which was resolved with subsequent updates. None of the updates I tried has applied without an unlocked bootloader.
However, the solution I came with was to transfer my apps from my phone to it using phone clone app, so at least I have all the apps and Netflix works. Play store is still showing as uncertified.

Categories

Resources