Related
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
condi said:
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
Click to expand...
Click to collapse
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Judah001 said:
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Click to expand...
Click to collapse
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
condi said:
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
Click to expand...
Click to collapse
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Judah001 said:
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Click to expand...
Click to collapse
There was small typo - bad syntax in 1.0, it will make no harm, but will exit when will arrive ota download. Just redownload - v1.1
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
zaynal said:
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
Click to expand...
Click to collapse
Great happy to kick your worries out
Judah001 said:
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
Click to expand...
Click to collapse
So in summary:
everything works correctly,
WiFi issue IS NOT related to multitool.
Im glad
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
obicom said:
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
Click to expand...
Click to collapse
hi friend,
thanks for posting this info - its very important to stay rootable..
about OTA RootKeeper - i've got it installed and got 'protected root'.
Got to check if it works ok in details.
As far as I remember - it worked, but not from the beginning.
I've already reflashed with rootkeeper,
su-backup stays, after reflash you need to reinstall Superuser app.
Will try that when I get back home later evening.
BTW - I think I could get some other, 'extra rootkeeper' for us,
as far as I remember - with some proper permissions we could get
unwritable build.prop - then we could have opportunity to reflash
older 'rootable' zip, if another ota would lock the exploit vulnerability.
I had this one time - reflashed new ota, and build.prop remained untouched
br
condi
My friend,
I guess the magic command should be 'chattri +i'.
This is the way how Root Keeper works.
It should be possible to use the same to protect the build.prop too.
But please consider, to install an older version of update.zip, we need a much lower value in the build.prob. I have two files on my sd card (update.zip) ..
For example .. if my build.prop = 123456789, I got the last version with
123456788 and a older one (e.g. 3.2) with 103456789
Therefore we should increase build.prop for the first step (download latest version) with one and should increase a higher digit for protection as a backup.
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
What do you mean with "I run the bootloop protection"?
Did you reinstall the ota firmware zip via recovery menu?
If yes and if it was successful the boot loop should be gone.
If you try do start boot loop protection script after getting boot loop ...
its to late ... :-(
rfreeman said:
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
Click to expand...
Click to collapse
Code:
pro·tec·tion [pruh-tek-shuhn]
noun
1.
the act of protecting or the state of being protected; preservation from injury or harm.
You get 1000 of viruses, hard disk damaged. And then you buy antivirus software and want pc to work?
You cant protect something, that has already been done.
Now you can FIX, REPAIR, not protect!
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
rfreeman said:
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
Click to expand...
Click to collapse
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
condi said:
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
Click to expand...
Click to collapse
I think your first assessment was correct. It sounds like he already had a bootloop and is now trying to use protection to fix it....
BTW Thanks for the awesome tool. I've had my tablet for about a week but haven't gotten up the nerve to try and root it yet lol =D
Received a Prime today, brand new. Powered on to 3.2, and almost immediately got the DMClient crash, while still going through the Android Wizard. Continually got it, tried force stopping, clearing cache and data on it, rebooting, etc. Wiped all data both via the bootloader and via settings, immediately came back. Was unable to get an update OTA - crashed immediately.
I downloaded .14 ICS update from ASUS, put it on the internal storage, and it immediately noticed it and offered to upgrade. Did the upgrade, wiped data. Again, during the step where you enter your Google credentials, started getting the DMClient crash. It clearly isn't the result of anything I've installed (since it was happening after a wipe before I was able to install anything!) I know .15 is out there, but updating via the menu is not an option. (Crash, crash, crash, crash.) I haven't seen any other complaints of it happening on a fresh clean install, where it seemed to be impossible to make it stop.
I guess I'm going to root and install .15 either from the dev section, or Virtuous Prime. But has *anyone* else had this happen? I don't understand how it can crash fresh stock install, unless there's some sort of hardware issue causing it. Not that it would be related anyway, but I do have a serial number.
Any help???
skunkiechris said:
Received a Prime today, brand new. Powered on to 3.2, and almost immediately got the DMClient crash, while still going through the Android Wizard. Continually got it, tried force stopping, clearing cache and data on it, rebooting, etc. Wiped all data both via the bootloader and via settings, immediately came back. Was unable to get an update OTA - crashed immediately.
I downloaded .14 ICS update from ASUS, put it on the internal storage, and it immediately noticed it and offered to upgrade. Did the upgrade, wiped data. Again, during the step where you enter your Google credentials, started getting the DMClient crash. It clearly isn't the result of anything I've installed (since it was happening after a wipe before I was able to install anything!) I know .15 is out there, but updating via the menu is not an option. (Crash, crash, crash, crash.) I haven't seen any other complaints of it happening on a fresh clean install, where it seemed to be impossible to make it stop.
I guess I'm going to root and install .15 either from the dev section, or Virtuous Prime. But has *anyone* else had this happen? I don't understand how it can crash fresh stock install, unless there's some sort of hardware issue causing it. Not that it would be related anyway, but I do have a serial number.
Any help???
Click to expand...
Click to collapse
What SKU are you? WW, DE, US, UK?
That really is no good. And it's odd that wipes/manual installs aren't cutting into it, usually the rewrites will help iron things like this out.
Like you said, rooting and trying other (older) updates and such would at least show us if it's consistent regardless of what you do.
Must be s/w issue though, so I'm stumped why you haven't absolved it yet
*EDIT:
And please realize that rooting and unlocking are not the same! You can root and install other updates and still keep your warranty. If you successfully unlock so that you can install Virtuous, you will not have a warranty.
US SKU, sorry about leaving that out. Is there any way a hardware issue could wreak havoc with DMClient? This is really perplexing.
Now that I think about it, though, I'm a bit reluctant to unlock the tablet and cause warranty issues while this is still happening...
EDIT: Hahaha - I realized as I was replying to you that didn't make any sense, and I shouldn't have said unlock!
buxtahuda said:
What SKU are you? WW, DE, US, UK?
That really is no good. And it's odd that wipes/manual installs aren't cutting into it, usually the rewrites will help iron things like this out.
Like you said, rooting and trying other (older) updates and such would at least show us if it's consistent regardless of what you do.
Must be s/w issue though, so I'm stumped why you haven't absolved it yet
*EDIT:
And please realize that rooting and unlocking are not the same! You can root and install other updates and still keep your warranty. If you successfully unlock so that you can install Virtuous, you will not have a warranty.
Click to expand...
Click to collapse
well technically rooting can void warranty also as it states it in there. tampering with root files or software. BUT at least we can unroot. plus hopefully Asus not to much by the books when device is rooted n sent in for warranty work. if anything, I'd remove root from device to be on the safe side n take no chances of them denying me warranty claim for something as simple as that.
but like you said though, if you unlock, kiss your warranty good bye..lmfao
demandarin said:
well technically rooting can void warranty also as it states it in there. tampering with root files or software. BUT at least we can unroot. plus hopefully Asus not to much by the books when device is rooted n sent in for warranty work. if anything, I'd remove root from device to be on the safe side n take no chances of them denying me warranty claim for something as simple as that.
but like you said though, if you unlock, kiss your warranty good bye..lmfao
Click to expand...
Click to collapse
Yeah, I'm not going to unlock until I know what's going on. I figured rooting isn't a big deal since it can always be unrooted. But I'd need to be unlocked to install another ROM, so I guess I don't see where this gets me very far. ACK! Frustrating!
skunkiechris said:
Yeah, I'm not going to unlock until I know what's going on. I figured rooting isn't a big deal since it can always be unrooted. But I'd need to be unlocked to install another ROM, so I guess I don't see where this gets me very far. ACK! Frustrating!
Click to expand...
Click to collapse
Just root. Follow my sig to PrimeTime (Root/Unroot).
Then we (that is, XDA'ers more knowledgeable than I) can get into your system files to see what's going on. You could even just try fixing its permissions and such.
If none of that works, manually blob to another update (also in my sig) and continue testing.
All of this will leave warranty intact so long as you unroot and rewrite any changed system files (probably with a reset/install).
buxtahuda said:
Just root. Follow my sig to PrimeTime (Root/Unroot).
Then we (that is, XDA'ers more knowledgeable than I) can get into your system files to see what's going on. You could even just try fixing its permissions and such.
If none of that works, manually blob to another update (also in my sig) and continue testing.
All of this will leave warranty intact so long as you unroot and rewrite any changed system files (probably with a reset/install).
Click to expand...
Click to collapse
I did root successfully after my first post. Here's what they look like currently:
-rw-r--r-- root root 167247 2012-02-14 08:51 DMClient.apk
-rw-r--r-- root root 668904 2012-02-14 08:51 DMClient.odex
That seems on par with everything else...
Does DMClient do anything other than manage OTA updates? Maybe the solution is just to remove it entirely. I have no problem manually downloading and installing updates, as long as there are no other issues!
skunkiechris said:
Does DMClient do anything other than manage OTA updates? Maybe the solution is just to remove it entirely. I have no problem manually downloading and installing updates, as long as there are no other issues!
Click to expand...
Click to collapse
This formats the internal SD card which makes this route a nuisance. It also requires hooking back up to a PC to re-root.
Again, I've no idea what to look for or what would cause this especially after wiping/resetting (I still wouldn't know otherwise lol ), but hopefully someone will come along who might know or ASUS will answer a support ticket.
Before everyone feels obligated to point this out... yes, I know this will prevent me from unlocking the bootloader. I plan to stick with stock ROM's, so that should not be a problem for me.
I've downloaded the OTA, and made a copy on me SD card.
When I try to run the update normally, it fails without any error message I can see.
When I rename the OTA file to update.zip and try to update from sdcard through recovery, I get an error message referring to build.prop. As far as I can remember, I have never done anything with build.prop on this device. In any event, I'm not sure what to do to fix this.
I would like to get the update installed. Any ideas?
Be glad, that it fails. There is something that do not match and if it would go through, your phone would be dead.
Look in the zip /meta-inf/com/android/metadata, open it and check what pre-build do you need. You must have this one in the phone without root or other changes.
peetr_ said:
You must have this one in the phone without root
Click to expand...
Click to collapse
I doubt that's true. My wife's photon was rooted and did the OTA just fine.
Ok. But after some readings here I wouldn't risk that.
friends, brothers, fellow technologically advanced people lend me your ears
yea, I "figured" it out. had the same problem, but now "at last" i'm on 2.3.5
you're going to have to flash (back to stock; unroot) as done in the qbking video here
http://www.youtube.com/watch?v=J94VcWk-CJc
but when you're choosing which sbf file to flash, dl, - pick '154'
i tried the 198_6 but that didn't work for me.
once you've flashed '154,' you'll have to do two updates before you get to the 2.3.5 one
.....note: after the first one, i lost wifi and 3g, but a quick reboot brought it back.
.............note 2: after you've flashed 154, your photono will take a while to find service, because it'll be deactivated on the phone,
but then it just gives you an option to 'activate' and you're good.
when i was rooted i got rid of some of the bloat sprint stuff; i think that's the 'root' of the problem.
alexthen said:
you're going to have to flash (back to stock; unroot)
Click to expand...
Click to collapse
Not really.
My device has never had anything but stock. It's rooted, but my wife's was also rooted and had no trouble.
I just copied her build.prop to my device and the update went without a hitch. I am fairly certain I never modified my build.prop, but I suppose it's possible. I had to use her 2.3.5 build.prop, too, since this happened after she upgraded.
I never did figure out what the problem was, so the issue that is the thread topic of figuring out what was keeping the update from succeeding is not actually solved. However, a potential solution to the failed upgrade is to copy a different build.prop.
Hi all... so, this is new to me... see the attached screenshot. Never seen that before on any phone. Yes, I'm rooted, but still stock, including recovery... only "hack" I've done is to change platform.xml to make the SD card writable... maybe that's enough... anyone else see this when checking for updates? Especially interested if you're rooted too.
Rooted devices don't receive OTA'S. That's normal
Sent from my SM-G900T using XDA Premium 4 mobile app
fzammetti said:
Hi all... so, this is new to me... see the attached screenshot. Never seen that before on any phone. Yes, I'm rooted, but still stock, including recovery... only "hack" I've done is to change platform.xml to make the SD card writable... maybe that's enough... anyone else see this when checking for updates? Especially interested if you're rooted too.
Click to expand...
Click to collapse
This also happens if you switch from Dalvik to ART as the runtime. I get this same message and I am not rooted yet. I am just playing with ART.
This wasn't the case with my S4... it was rooted and I could still take OTAs... would have to re-root afterwards but it would apply no problem... is this new for the S5? Also, I did switch to ART but then switched back... is that enough to cause the message?
fzammetti said:
This wasn't the case with my S4... it was rooted and I could still take OTAs... would have to re-root afterwards but it would apply no problem... is this new for the S5? Also, I did switch to ART but then switched back... is that enough to cause the message?
Click to expand...
Click to collapse
When on ART the device status is Custom and you will get this message I just switched it back to Dalvik and now my device status is Official and software updates works. I have not updates available. Remember I am NOT Rooted (yet)
philow said:
When on ART the device status is Custom and you will get this message I just switched it back to Dalvik and now my device status is Official and software updates works. I have not updates available. Remember I am NOT Rooted (yet)
Click to expand...
Click to collapse
Ok thanks... it appears to me that once the warranty flag is tripped you're done as far as OTAs go (at least *checking* for OTAs- they may still install from recovery, I don't know)... some tests I did:
Tried on my daughter's phone, which was rooted, with platform.xml changed but never used ART: update check failed, so switching to ART and then back appears to not matter
Tried reverting platform.xml change on my phone, leaving root: update check failed
Tried unrooting my phone as well: update check failed
Tried clearing cache from recovery (didn't expect it to work but easy and worth a try): update check failed
Tried removing busybox: update check failed
So, my conclusion is it's probably reading the warranty flag... looking in Triangle Away it says counter is 0 but system is modified, so the only other thing that *might* work is flashing the system partition only, which I'd be willing to try but I frankly forgot how to do that If anyone can remind me how to flash just a single partition, pulling the .img file out of a .tar.md5 file I'd give it a shot. I'd like to know for sure either way.
Further info: I flashed just the system partition as a last resort... figured that should revert anything I may have done regardless... well, the update check still fails even after that. So yeah, pretty strong evidence that once you trip the warranty flag you aren't getting OTAs automatically anymore... that's a change from my past S3 and S4 experience and I'm not sure if that's an S5 thing or a T-Mobile thing (same version of Android as on my Sprint S4 before I switch to T-Mobile so I don't think it's that).
I'll be interested to see if whenever the next OTA lands it can be installed from recovery manually... if it can then no big deal. If not then it's a bad situation.
Reverted MT2-L03 back to stock, bootloader unlocked/rooted -, even reflashed stock recovery to be on the safe side (with root).
Unlike other people, whom seem to be getting a push notification for system update, this phone gives no such thing. I'm on Wind mobile, doesn't notify whether on WiFi or carrier network.
Reading "How To Get Update" on other sites tells me to go to Huawei's site directly, but all I see is a download for HiSuite.
For the heck of it, I also tried to fetch an update manually through "System Update" on the phone, and through HiSuite, no dice.
Don't need a recovery image, need this elusive update app/image everyone is talking about. That said, does anyone have a clean source for this, since Huawei isn't pushing it to my device? Thanks!
Other Info:
MT2-L03
Carrier: WIND Mobile (carrier does not impose any restrictions or software, stock = factory stock)
Android 4.3 (184 is still on 4.3 with some fixes right? Some select apps have issues with later ver. of Android)
Bootloader = UNLOCKED; Rooted with KingoApp, variant of SuperSU is the only thing installed (KingoUser) for permissions.
Current build: 128
volcolm said:
Reverted MT2-L03 back to stock, bootloader unlocked/rooted -, even reflashed stock recovery to be on the safe side (with root).
Unlike other people, whom seem to be getting a push notification for system update, this phone gives no such thing. I'm on Wind mobile, doesn't notify whether on WiFi or carrier network.
Reading "How To Get Update" on other sites tells me to go to Huawei's site directly, but all I see is a download for HiSuite.
For the heck of it, I also tried to fetch an update manually through "System Update" on the phone, and through HiSuite, no dice.
Don't need a recovery image, need this elusive update app/image everyone is talking about. That said, does anyone have a clean source for this, since Huawei isn't pushing it to my device? Thanks!
Click to expand...
Click to collapse
I also have a Wind MT2-L03, and mine has never had the bootlaoder unlocked, and never rooted, yet I'm also stuck on the build B128 that it came with, with no push notification for system update. So your issue has nothing to do with anything you may have done to your device. Looks like Wind users are left out in the cold on this one.
antinerd said:
I also have a Wind MT2-L03, and mine has never had the bootlaoder unlocked, and never rooted, yet I'm also stuck on the build B128 that it came with, with no push notification for system update. So your issue has nothing to do with anything you may have done to your device. Looks like Wind users are left out in the cold on this one.
Click to expand...
Click to collapse
It would seem that way. Perhaps Wind's version works well enough that they don't need to update said devices (or maybe issues aren't as prevalent on these). So far haven't noticed any issues, but I've emailed Huawei mobile support later in their afternoon, and just about 10 minutes ago, so awaiting what they say about any later firmware updates.
_____
That said, HiSuite finally pushed a version update (of HiSuite software) then checked for Android OS updates through it (sends IMEI back to Huawei then checks their database). It says "Your device has the latest version." So that answers that, at least.