Honor x2 reporting emui 2.0 - Huawei MediaPad X2

Honor x2 reporting emui 2.0 an incorrect amount of RAM and the wrong resolution on the screen. I have not change the resolution and the build.prop file. And I have not done anything else other than remove the China China apps from the phone and installed official apps. What could cause this? Look at the image below.

mtyler7807 said:
Honor x2 reporting emui 2.0 an incorrect amount of RAM and the wrong resolution on the screen. I have not change the resolution and the build.prop file. And I have not done anything else other than remove the China China apps from the phone and installed official apps. What could cause this? Look at the image below.
Click to expand...
Click to collapse
When you go into the Cust folder and delete certain xml files that's what happens. It will display the wrong information in About Phone. I think it's the hw_defaults.xml file. If you delete that it will show you EMUI 2.0 etc in about phone. I had the same problem when I deleted the entire Cust folder.

I went ahead and reinstalled b015 and restore my twrp image and everything is OK. Thanks for the info.

Related

Update for l29C185Bxx

Hi all
I currently have the NXT-L29C185B162 firmware, which is specific to devices in the African region. I found at Carbontesla the firmware NXT-L29C432B170 which supposedly addresses the push notifications issue but the C432 firmware is meant for European models as far as I understand.
Would it be possible/safe to update with this firmware, or is there an equivalent update for African devices?
Unfortunately I don't seem to be able to find ANY firmware on Huawei's site for this device so its hard to know what I should be using...
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52320/f1/full/update.zip L29 C432B320
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52320/f1/full/update.zip L29 C636B320
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52321/f1/full/update.zip L29 C185B320
NaoNative said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52321/f1/full/update.zip L29 C185B320
Click to expand...
Click to collapse
NaoNative, you're a champ! Thanks mate
You wouldn't happen to know where I might find a changelog would you? I know Huawei is not exactly well known for making those public, but I'm just curious what else might have changed since B162...
This update is for system version EMUI 4.1. EMUI 4.1 optimizes the camera, battery management, and Phone Manager, and adds multi-user mode, to provide a secure and unique experience for you
[Highlights]
[Camera]
Optimized the interactive gestures, enabling you to swipe left and right to switch between the mode and settings screens
[Multi-user mode]
Added a mode, which allows multiple users to access the same app with segregated personal data and privacy protection
[Smart manager]
Added the Huawei-developed ROG power saving technology for the first time, which decreases the screen resolution to save battery power Optimized the Phone Manager, which helps you manage your device more easily and conveniently Optimized battery management, which allows you to check the battery power and battery power consumption for any period within two days Optimized traffic management to automatically add the traffic leftover from the previous month to the current month
[Home screen]
Optimized the Weather app so that it can forecast weather for each hour including the probability of rainfall Added an entry for third-party social networking apps, such as WhatsApp, eSpace, and Skype, in the contact details screen
[Communications]
Optimized the networking speed when international roaming is on Optimized the registration time when the network connection is interrupted for environmental reasons
[Update notes]
1. If some third-party apps are incompatible with EMUI 4.1, update them to their latest versions from Google Play Store 2. Your home screen layout may be rearranged slightly 3. This update will not erase your personal data, but we recommend that you back up any important data before updating. If you experience any issues during the update, please call the customer service hotline for support 4. If you are not satisfied with the new update, you can roll back to EMUI 4.0. Your personal data will be erased during the rollback. For details, please call the customer service hotline
...and thats only the changelog coming from B180
Sent from my Huawei Mate 8 NXT-AL10
NaoNative said:
This update is for system version EMUI 4.1. EMUI 4.1 optimizes the camera, battery management, and Phone Manager, and adds multi-user mode, to provide a secure and unique experience for you
Click to expand...
Click to collapse
Very nice man, I noticed a few of those after upgrading, also noticed some slight changes to the UI animations and the pop sound for volume adjustments has changed (better in my opinion)
Pity the multiuser mode doesn't work if you have SD card as default storage...
Otherwise, I like what I see so far. Did in-place upgrade using the phone dialer method for local update, so it kept all my stuff. Gonna attempt root tomorrow, will see how that goes
NaoNative said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52320/f1/full/update.zip L29 C432B320
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52320/f1/full/update.zip L29 C636B320
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52321/f1/full/update.zip L29 C185B320
Click to expand...
Click to collapse
Can I download the firmware through my phone and update it just like that or do I have to download it on a laptop first?
Skytop said:
Can I download the firmware through my phone and update it just like that or do I have to download it on a laptop first?
Click to expand...
Click to collapse
Either method would work, I used my laptop as my internet connection had been a bit dodgey so used a download manager. The file has to be stored in the root of either your internal memory or on your SD card in a folder named "dload"
You can then either do the 3 button reset (this wipes your data so make sure you have backup 1st) or you can do local upgrade (this retains your data but do a backup 1st just in case,) but that's no longer an option in the settings menu, there's a code you have to dial to bring it up. Found it somewhere around here before but can't remember it now...
Edit: code to be entered in the phone dialler is *#*#2846579#*#*
Option 4 to to update
So I finally got around to attempting root, flashed the B320 in twrp and SuperSU after, it rooted successfully but problem is now I got no Huawei Swype, no options for setting the lock screen style, and I noticed the Huawei backup app was missing (at least it's on play store though so I could restore my backup).
Anyone know where I went wrong as those things were definitely there before?
Note somewhere along the lines I did flash a decrypted boot.IMG but I don't know if flashing the rom in twrp would overwrite that or not, or even if it causes what I'm experiencing
NaoNative said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52320/f1/full/update.zip L29 C432B320
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52320/f1/full/update.zip L29 C636B320
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1076/g104/v52321/f1/full/update.zip L29 C185B320
Click to expand...
Click to collapse
Which one is for which region ? Am in Egypt...
1- I am on NXT- L29CB180B185, and would like to upgrade to B320. But I wish to read about the advantages and dis advantages of the B320 over the B185. Where can I find those notes?
2- I did not activate the finger print option untill now. I can not see any use except may b for security reasons if i loose the mobile. Does it have any other use ?
I heard it closses tha app I am using, but does this like exting with the back button, or it really close tha app, so it does not eat ou the RAM and the battery .
Thanks in advance.
mseif said:
Which one is for which region ? Am in Egypt...
Click to expand...
Click to collapse
The c185 supposidly.
But u need to check ur phone software first to check whhich version you have
mseif said:
1- I am on NXT- L29CB180B185, and would like to upgrade to B320. But I wish to read about the advantages and dis advantages of the B320 over the B185. Where can I find those notes?
2- I did not activate the finger print option untill now. I can not see any use except may b for security reasons if i loose the mobile. Does it have any other use ?
I heard it closses tha app I am using, but does this like exting with the back button, or it really close tha app, so it does not eat ou the RAM and the battery .
Thanks in advance.
Click to expand...
Click to collapse
Any response on where to read about the oldand new ROM ?
Thanks to all in advance
The link for L29C185B320 doesn't work anymore, anyone who can help with a new link?
Yo buddies
Here is the stock
Download C185B320

[HELP] Leagoo T5: why is not available any ROM ?

Hello
I've a Leagoo T5 wich use his own Nougat modifiied. TERRIFIC !!!
I'm looking for another ROM wich supporting all feature (also double rear camera and fingerprint reader) because it's impossible to use it.
T.I.A.
Paolo
You can use "MTK Extractor" to extract system.img and other files, you can then modify them, and flash them using "SP Flash".
I recently uploaded a clean stock ROM (LEAGOO_T5_OS2.1_E_20180116) to Mediafire and Needrom.
I've also uploaded a carepack if you are interested in the new ROM, or even for a custom.
The command for fast boot is: fastboot oem unlock
Ferather said:
You can use "MTK Extractor" to extract system.img and other files, you can then modify them, and flash them using "SP Flash".
I recently uploaded a clean stock ROM (LEAGOO_T5_OS2.1_E_20180116) to Mediafire and Needrom.
I've also uploaded a carepack if you are interested in the new ROM, or even for a custom.
The command for fast boot is: fastboot oem unlock
Click to expand...
Click to collapse
Do you mind sharing please? I'd love to get a working custom rom on this device.
I still can't add links yet, so you will have to Google search: "MTK Extractor". Download it, and then download the latest official ROM, which I have uploaded to Needrom and Mediafire, Google search: "OS2.1_E_20180116".
Extract the "system.img" file from the stock ROM using MTK Extractor, you can then go ahead and make your customization's. System apks are signed and locked, however they can be replaced.
When you have finished, you can use MTK Extractor to create a new system.img file with all of your modifications (including root, if you add it). The size for system.img is 4096mb.
The MTK Extractor tool uses a slider bar and text input for the partition size, the slider is limited, however enter 4096 into the text box (don't delete the text, it bugs).
Enter fastboot (Power + Volume up), third option, then using ADB with command prompt, type the command: "fastboot oem unlock", and then accept.
Now you have unlocked the phone, you can run your custom ROM. In a factory locked state, ROM's will install, but not run.
I forgot to mention my Needrom pack contains MTK Extractor. If you can make roms, there are 3 stock bugs that I would ask you to fix.
1: If the navigation bar is hidden, there is a window transition blip (bottom of the screen) if you swipe to recent apps.
2: If you select the first (bottom left) icon from the lock screen (voice, usually), you get a grey background.
3: Bluetooth scanning sometimes bugs (MAC instead of name), once paired there are no issues.*
* This may be due to my headset, but I remember my TV also displaying a MAC once.
Also, can you align or remove the 4G icon that shows even with data turned off.
Ok... So far this thread seems to be the only one on xda-dev about leagoo T5, which i just buy.
By the way thanks Ferather for pushing the rom on need rom.
Here the link :
https://www.needrom.com/category/leagoo/t5-leagoo/
Need help
Hi, could you please share the Mediafire link?
Since the last rom update (LEAGOO_T5_OS2.1_E_20180822 aka OS2.1_E_20181025) I post on needrom a moded rooted boot with magisk.
i have this leagoo t5 running this newest e_20181025 but im getting a problem with my front facing camera only displaying like an upsidedown image of the rear camera. please advise on what i can do to fix this
Maybe inconsistence between differents partitions (like boot and system)
If you know what you are doing I will advise reflashing all principal partitions.
But i don't think the phone came like this when new, so someone must have messed something.
https://www.mediafire.com/#3c2rnntnz3kw0
LEAGOO_T5_OS2.1_E_20181025.zip -- Original Leagoo T5 ROM
LEAGOO_T5_OS2.1_C_20181025.zip -- Custom Leagoo T5 ROM
No issues, other than the one I have mentioned, which is just an app default.
Enjoy!
hey cool rom bro.
Thank for sharing.
No problem, I thought I would start the ball rolling for customization of the rom, since adding ringtones does not work with the stock rom (media storage app issue I think).
You can permanently edit the rom yourself, which I found very easy. If you want to add apps, simply install them from sdcard or store, then navigate to "/data/app", you will find your installed app or update, with odex files and libs, if any.
I created a temp folder on "/data" called "Working" and copied everything into it, and then setup the correct permissions, and renames, and transferred to either "/system/app" or "/system/priv-app", depending on the app.
A better way to do it, is to use "Lubuntu" from live USB or DVD, and then mount the image and edit it as root: "sudo *file explorer*", in this case "sudo pcmanfm-qt", then create a folder in "/mnt" called "ROM".
Next copy "system.img" to "/tmp", and mount it "sudo mount /tmp/system.img /mnt/ROM", now you can do whatever you like, but make sure to "chown" and "chmod" all your modifications.
Make sure you delete anything you will replace when you transfer, else you might get old unused files (folder merged and non-replaced items remain).
----
If you make edits on the phone using an app, and want to make your own "system.img", use the readback option in "SP Flash Tool".
physical_start_addr: 0xe000000
partition_size: 0x100000000
----
Note: Most non-stock apps *do not* support the triple (3x) camera setup, and will either use the wrong camera or crash.
Yeah I encounter problems too to add custom ringtone and wallpaper but i manage to get over it by changing some files permissions
By the way I am "456456" on needrom, the boot img with magisk is from me
I know the time needed to make a custom rom and I'm glad to see that I'm not the only one trying to mess with this not-bad-at-all cheap phone
There is a possibility of an Oreo port, there is a Leagoo T8s with the the same chip that runs Oreo 8.1.0. I have checked over the rom and it looks possible (based on my basic knowledge).
Cygwin + Cmder, for Android. I made the pack myself, and thought it might help others using Windows who want various Linux tools.
I added Cmder for better console support and easy admin: ---- http://www.mediafire.com/folder/lzsf7xd2wwsm4/Commander
Quick update, will now self configure "/home", added ADB and Fastboot.
Ferather said:
There is a possibility of an Oreo port, there is a Leagoo T8s with the the same chip that runs Oreo 8.1.0. I have checked over the rom and it looks possible (based on my basic knowledge).
Click to expand...
Click to collapse
Hi, Running your ROM with no other mods, it's certainly better than original. Just curiousis there anyone working on an Oreo based ROM ?. ... J
Thanks, I did not manage to get the Oreo from the T8 to function, due to hardware changes.
Ferather said:
Thanks, I did not manage to get the Oreo from the T8 to function, due to hardware changes.
Click to expand...
Click to collapse
Ah !, C'est la vie, would have been interesting. Apologies for late reply was away from home and didn't have much spare time. ... Jack
please tell me how you can fix the inverted touchscreen Leegoo T5

[AIO] Prepare your device (and your knowledge) for any GSI

Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .​
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.​
Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.​
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.​
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)​​
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP​
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth​
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or​
adb logcat > file.txt
send file.txt to the developer
Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"​
Or simply join the telegram group.
Peace.
Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol
Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or​
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.
Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.
Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery
Update:
Added Magisk news;
Added stock PRA ramdisk
UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?
Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.
The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot
How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka

[GUIDE][TOOL] HiSuite Launcher - EMUI 10 Update

HiSuiteLauncher
EMUI 9 fix and EMUI 10 Instructions here: Post. JSON file UPDATED!!!
A Launcher for HiSuite which grabs its ssl calls and hooks them so you can update to EMUI 9.1.
What does it do?
It will launch an instance of HiSuite, Huawei Smartphone PC Manager, if installed. This instance will have a hook to ssl calls made by HiSuite to HiCloud. So we can now handle responses by editing a simple text file for a full ota update. It won't touch anything else. With an update response, HiSuite should now handle the update process including the rollback option if available and a proper imei authorization to HiCloud. This is a way to force an update to your Huawei/Honor smartphone with a standard tool.
Setup and General Info
You will need FirmwareFinder (TeamMT). If you've been around Huawei/Honor forums you should already know what it is. With FF we can track ota updates and even run an authorization test for an update. This is important because we're gonna be using the ota ID and its full link to pass to HiSuite. If you spot an update and your device is not yet authorized to install it your phone will most likely avoid it either.
!IMPORTANT!: I've been using this method since march/19 without any problems. No wipes, connectivity losses, call problems, weird behavior whatsoever. In fact, I'm running EMUI 9.1 now. I don't know how you can ensure the ID you picked is the right one for your device - considering you are using the search correctly: for my Honor 10 C636 I search for COL-L29C636. You might notice the name of the device seems a bit strange and here comes a massive confusion. Col-L29 is now COL-LGRP2-OVS (C636 is overseas) with a bunch of small step rom versions like .226 .227. 228 .229. I usually pick the very first version my phone is authorized for. So my last update was .227. After the update I tested my phone for others versions like .228 and .229 and my phone was authorized for those too. Go figure!
Since HiSuite 9+ the cust info is in the update request and I believe HiCloud suggests the right package for your phone. The reason behind this is because the ota file I get sometimes it's different in size and checksum from the one you get from FF even if it's the same ID. Total speculation here. The cust and preload info have their own json structure. Please revisit the json file below. You can find find cust and preload data in FF simply by searching <your phone model>-<cust/preload>. They both feature their own IDs and urls and they are separated by EMUI versions (Android version).
ALWAYS take note of the rollback ID suggested by HiCloud. It might look like it's just a regular version but it's not! An update and a rollback IDs are different, with different flash scripts. HiCloud will send rollback data with major updates like from EMUI 8.1 to EMUI 9; EMUI 9 to EMUI 9.1. You can spot both IDs in FF as well.
Instructions:
Just extract the zip folder to any suitable folder in your computer and run the Launcher.exe. A console window will popup and HiSuite will appear right after. You can monitor HiSuite calls in the console window.
Remove root and TWRP. You have to be full stock.
Backup data. Even HiSuite will ask you to do it.
Be prepared to download at least 4Gb of data while keeping your phone plugged to your pc.
You will need a very basic understanding of json data structure.
You have 2 files that should remain in the main folder of the launcher:
hisuite9_request_update.txt: you should add the ID to "versionID" and full link to the update ota in "url". Get those from FF.
Please notice that there is a pattern here. The "url" data doesn't include the actual file. UPDATED!!!
{
"status":"0",
"versionPackageCheckResults":[
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:41:07+0000",
"description":"COL-LGRP2-OVS 10.0.0.177",
"name":"COL-LGRP2-OVS 10.0.0.177",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<UPDATE ID GOES HERE>/f1/",
"version":"COL-LGRP2-OVS 10.0.0.177",
"versionID":"UPDATE ID GOES HERE"
}
],
"versionPackageType":2,
"checkEnd":"1"
},
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:03:11+0000",
"description":"COL-L29-CUST 10.0.0.3(C636)",
"name":"COL-L29-CUST 10.0.0.3(C636)",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<CUST ID>/f1/",
"version":"COL-L29-CUST 10.0.0.3(C636)",
"versionID":"CUST ID"
}
],
"versionPackageType":3,
"checkEnd":"1"
},
{
"status":"0",
"autoPollingCycle":"1",
"components":[
{
"componentID":1,
"createTime":"2020-06-19T03:03:11+0000",
"description":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"name":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"pointVersion":"1",
"reserveUrl":"updatessl.dbankcdn.com",
"ruleAttr":"",
"url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G5459/g1755/v<PRELOAD ID>/f1/",
"version":"COL-L29-PRELOAD 10.0.0.4(C636R1)",
"versionID":"PRELOAD ID"
}
],
"versionPackageType":4,
"checkEnd":"1"
}
]
}
IMEI.txt: add the first IMEI of your phone to the first line of this file.
Hit Update in HiSuite and you should see the red dot indicating an ota update (in fact, the update you added in the file above).
log.txt: this file holds the requests/responses during the current session.
Launcher.exe.config: here you can find a few setup options like hisuite folder.
Bugs
- Well, as far as I'm concerned you shouldn't face any bugs since it's pretty straight forward. BUT, please take my advice: if you're not sure about which update to go for avoid it altogether.
- It does not work with incremental updates. The recovery will reject it.
- In your phone, about phone page, it might not show the update changelog. Sometimes it does show, sometimes it doesn't.
- I cannot confirm this but since I always update my phone through this method I don't get incremental updates anymore. I don't know if it's because I'm always way ahead (updates usually take forever to reach my phone before and that's why I've been doing all of this) or anything else.
Notes:
- I have to thank Smaehtin (XDA) for kindly answering my request to support this tool for Honor 10 and for actually providing this method.
- Although I'm a professional developer (ERP stuff), I'm not used to C# so the code might look a bit messy and funky here and there. I'm sorry for that.
- The solution used is from a freeware compiler, SharDevelop (http://www.icsharpcode.net/OpenSource/SD/).
- Disclaimer here, I am not responsible for any damage you (your phone) might suffer from attempting this. I tested it myself several times in my phone, Honor 10 C636 (COL-L29C636). HiSuite will handle the whole update process but you still can provide wrong data as of wrong IDs or wrong url.
- We are using EasyHook (https://easyhook.github.io/) and Newtonsoft.Json (https://www.newtonsoft.com/json) libs.
Source:
https://github.com/magnot/HiSuiteLauncher
Many thanks for the instructions ??
Success update to emui 9.1.0.325 with this guide.
Same all ok ! thanks ! OFF TOPIC:anyone know how to disable suggestion on drawer ?
Thanks, works like a charm!
this made my day, many thanks superb tool
@MagnoT Thanks for your work , new version available , I change only version ID and Url link its ok to update ?
Any idea how to spoof only IMEI.txt ?
-Giving us the mean with an early device 's imei to force install the right next update or check what is latest hicloud's OVS FullOTA-MF for a device's cust region and imei.
oslo83 said:
Any idea how to spoof only IMEI.txt ?
-Giving us the mean with an early device 's imei to force install the right next update or check what is latest hicloud's OVS FullOTA-MF for a device's cust region and imei.
Click to expand...
Click to collapse
I wouldn't do that. There's no need to rush an update that way. And if you're not yet authorized for an update the recovery will just reject it.
leap_ahead said:
@MagnoT Thanks for your work , new version available , I change only version ID and Url link its ok to update ?
Click to expand...
Click to collapse
Yep, if you have FF confirmation for your device!
.326 is available in FF for quite some time. It's the August EMUI 9.1 security patch update but my device is not authorized for it just yet. The ID is 297131. I'll wait.
MagnoT said:
I wouldn't do that. There's no need to rush an update that way. And if you're not yet authorized for an update the recovery will just reject it.
Click to expand...
Click to collapse
I will do.
I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
Late 9.1 OVS build are surely/maybe cust specific now...
By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.
Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)
-But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
-Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)
MagnoT said:
Yep, if you have FF confirmation for your device!
.326 is available in FF for quite some time. It's the August EMUI 9.1 security patch update but my device is not authorized for it just yet. The ID is 297131. I'll wait.
Click to expand...
Click to collapse
You can check. 330! But still in july update
oslo83 said:
I will do.
I m speaking about getting to know myself which is the latest approved OVS builds for a specified region. (determined by spoofed/original device region)
Late 9.1 OVS build are surely/maybe cust specific now...
By the way, I'm already with a bootloader unlocked on a LYA-L29 demo C652 device which is soft-rebranded to C432 via magisk ^^
So far, I'm getting C432 OTAs ! (when time finally comes for my imei) on in-built Emui updater.
Your tool seems great. -never had to use it for now. (I did with custom FF DNS for some times)
-But I like to use it just to know what is the latest/next right C432 OVS build which is approved and actually fetched for a specified imei.
-Maybe I should get further on my magisk module which is softrebranding to spoof imei for Emui Updater process..... (just though)
Click to expand...
Click to collapse
I guess I get what you mean. In the source code there's an entry to spoof imei which I converted to read from file but that's for the authorization request. Still, I wouldn't go for it. As for knowing in advance the latest/next update roll out based on imei spoofing that would be kinda hard to accomplish imo because... well, it's random and the effort doesn't pay off. I'll have a look into it and update the tool.
leap_ahead said:
You can check. 330! But still in july update
Click to expand...
Click to collapse
.330 it's a july security patch for EMUI 9.1. I believe it's still an entry to EMUI 9.1 just like .325. That's the mess we get with this OVS thing... different versions of the same patch all approved. I'll wait for the august update.
MagnoT said:
.330 it's a july security patch for EMUI 9.1. I believe it's still an entry to EMUI 9.1 just like .325. That's the mess we get with this OVS thing... different versions of the same patch all approved. I'll wait for the august update.
Click to expand...
Click to collapse
I flash 326 over 330 all ok !
326 is approved for my device, upgrading now thx to this magic tool
leap_ahead said:
I flash 326 over 330 all ok !
Click to expand...
Click to collapse
Ing.King said:
326 is approved for my device, upgrading now thx to this magic tool
Click to expand...
Click to collapse
Thanks for the info guys! :good: I just checked FF and now I'm approved for the .326 update. I'll flash it tonight.
Just my curiosity, can i use it for the honor view 10?
Any Huawei/Honor device EMUI 9 or 9.1
chainsmkgbstrd said:
Just my curiosity, can i use it for the honor view 10?
Click to expand...
Click to collapse
Honestly it should work for any hisuite compatible device. You just have to take note of the device id, correct name tags and of course make sure the update you're going for is approved for it and set it up.

General ROG Phone 5 Ultimate | New Firmware WW-18.0840.2109.188 | WW RAW & ROOT Images

Model - ROG Phone 5 Ultimate (Possibly ROG Phone 5 as well see here )
2021/11/05
Version Name - WW-18.0840.2109.188
Release Date - 2021/11/05
OTA Download Link - Download
RAW Download Link - PENDING
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image:WW-18.0840.2109.188 for WW/JP/EU/RU only*
This firmware is only for ROG Phone 5 WW/JP/EU version use and not applicable to ROG Phone 5S/5S Pro series models.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1. Optimize the charging experience function
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
Spoiler
2021/08/24
Version Name - WW-18.0840.2107.151
Release Date - 2021/08/24
OTA Download Link - Download
RAW Download Link - Download
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image:WW-18.0840.2107.151 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed issue with sending MMS messages on Optus Australia
3.Fixed an issue where some videos played through apps would get stuck and without response.
4.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
For JP SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed an issue where some videos played through apps would get stuck and without response.
3.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
*********************************************************************************************************************
2021/07/22
Version Name - WW18.0840.2106.86
Release Date - 2021/07/22
OTA Download Link - Download
RAW Download Link - Waiting
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image:WW-18.0840.2106.86 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Improved Item:
1. Updated Android security patch to 2021-06
2. Fixed an issue where the game would crash when using multiple windows to open the settings and change the system navigation
3. Fixed the problem of broken sound when using screen recording
4. Fixed the problem of low notification sound when using Bluetooth headsets in standby mode
5. Fixed an issue where blocking notifications in the game could not block Facebook messenger notifications
6. Fixed the problem of reduced call volume
7. Fixed the problem of using a microphone to record the voice of a team in the game, and the problem of not being able to record your own voice
8. Fixed the problem that the 5G network cannot be detected when connected to the GT-AX11000 router
9. Fixed a serious delay in the screen when entering the game with Geforce Now
10. Optimize touch experience
11. Fix sound effect for speaker playback.
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
twistedumbrella said:
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
Click to expand...
Click to collapse
It is the same, I'm looking for the RAW File.
JazonX said:
It is the same, I'm looking for the RAW File.
Click to expand...
Click to collapse
Wouldn't it also be the same then?
twistedumbrella said:
Wouldn't it also be the same then?
Click to expand...
Click to collapse
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Well... I can at least take some of your worries... OTAs won't be a thing after you unlocked your bootloader. You need to manually install them via magisk again. So there is no chance these automatic updates will break your phone.
Furthermore you don't have to worry about root + TWRP as well because there is no twrp for this phone and I doubt there will be one in the next time.
But applying updates and keeping root access without loosing your user data should be no problem. Magisk has special options for this and many people here update that way without bootloops and soft bricks.
JazonX said:
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Click to expand...
Click to collapse
I think you completely misunderstood my comment. I was saying that if the firmware for both models is the same, it is likely the raw files for both are the same (but still separate from the firmware).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to be a low-level rebuild. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
twistedumbrella said:
I think you completely misunderstood my comment, but I am sure someone new will appreciate the explanation (with a few corrections).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to wipe your data, while the regular firmware upgrades are not. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Click to expand...
Click to collapse
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
JazonX said:
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
Click to expand...
Click to collapse
Then apparently it has changed. I didn't have a ROG II, but I have the ROG 5 in hand. I couldn't tell you what has changed, though.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
twistedumbrella said:
Then apparently it has changed. I didn't have a ROG II, but I actually have my ROG 5. Couldn't tell you what else has changed.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Click to expand...
Click to collapse
Ohh .. In that case I was super wrong, and apologies over my misinformation.
Yeah, Actually ROG II Raw files had a Flash-all file which installs the full firmware, and reboots.
I even had a source (A Persian website) to get these when the OTA releases.
I was on windows, and usually after a RAW installation, the cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before.
Guess we gotta stick to ASUS OTA files from the support site then.
Thanks a lot ! : )
These updates come with a flash_raw script that looks more or less harmless. There is no visible wipe command included, but the phone did appear wiped after installing.
The flash_all, on the other hand, has a rather obvious section to opt in or out of an erase that opting out on Linux and Windows. I think the wipe isn't as much a wipe as it overwrites the partition.
I typically install my firmware with fastboot using a slightly modified version of the flash_all script and an unpacked payload. Somehow I broke the installer, which gives me a chance to test the raw again.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
JazonX said:
The cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before
Click to expand...
Click to collapse
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Anubarak16 said:
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Click to expand...
Click to collapse
I think Art broke that. If I remember the explanation, the idea was to create something like the old odex layout that was less sloppy. The code that used to be cached is now broken out into a physical file alongside the application. It's also how apps like *that one everyone remembers for IAP* are able to modify code without breaking signatures.
Successfully rooted using the same commands from here and the root images in the OP.
JazonX said:
Successfully rooted using the same commands from here and the root images in the OP.
Click to expand...
Click to collapse
Any word on the raw firmware? What about the existing boot images?
twistedumbrella said:
Any word on the raw firmware? What about the existing boot images?
Click to expand...
Click to collapse
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
JazonX said:
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
Click to expand...
Click to collapse
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
twistedumbrella said:
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
Click to expand...
Click to collapse
Patching own images are always reliable...
SafetyNet Passed with this fix !
JazonX said:
Patching own images are always reliable...
SafetyNet Passed with this fix !
Click to expand...
Click to collapse
Glad you found it. Good luck.
I flashed the raw firmware. It was a downgrade and my device was already set up and in use, but it included the scripts and commands to install without a wipe (finally). Moving the latest firmware to the sdcard allowed me to update almost immediately after finishing the flash.
I would assume it works on the Ultimate, since everything else has been identical and the date on that package is the same as the software image.
New update !

Categories

Resources