Related
But I want the exact same sprint image thats on there... is this possible? Can't I get the recovery image off the phone? I'd rather not use an image off the interwebs..but a sprint image of sorts. Is this doable? Thanks!
Yes go to settings and then "About phone" and tell us exactly the versions. (Kernel etc...).
Then I will tell you if you need to downgrade or just root it
Firmware: 1.5
Kernel: 2.6.27
Build Number: 1.56.651.2
Software Ver: 1.56.651.2
Hardware Ver: 0002
I want to root it but am nervous. I don't want to jack up my phone. I'd like to root it, and then goto some sort of recovery console like I've seen and take a default basic image of my phone. Can I do this?
What if you Update your phone and then root it ?
Because your version is old and when you update you will be able to see much improvment.
Don't be nervous when rooting it, its nearly impossible that you can brick it.
Are you on Europe ?
I'm in US (Michigan) CDMA network. How do I update it? I've already downloaded the latest sprint firmware that was just released. What other updates are you referring to? If you mean 1.6, I thought they were skipping 1.6 and waiting for 2.0 as far as HTC was concerned?
No I was meant updates from the original HTC website but I don't know about your phone. Have you installed this firmware that you downloaded ?
Yes its already been installed a week ago.
Weird...
Just go to the CDMA Hero subforum and check what you can do. I don't know about your model
If you are worried about messing up your phone, I would recommend you be at ease. It's pretty damn difficult to brick your phone as long as you stick to the instructions.
I'm assuming you want to stick with the original Sprint rom simply because you want to remove stock apps... otherwise, you'd be sorely mistaken to think you can add themes and other third party rom features to your phone (such as installing apps to your sd card).
The phone can always be reverted back to bone stock with a rom updating utility install file that sprint has made available to their users.
Why exactly, may I ask, do you want to root the phone whilst keeping the phone completely stock?
Check out this VZW PDF document -
http://support.vzw.com/pdf/system_update/eris.pdf
It seems to have been authored only 6 days ago (Mon 21 Feb), and mentions a hitherto unknown Eris release - 2.41.605.6 (same radio as the July 2010 OTA, but different/newer ROM version number)
Anybody want to run stock 2.1 for a couple of days to see if they can capture an OTA download link?
I suppose it could be meaningful not only for 2.1/Sense dev ROMs, but also to Froyo/GB if there are any changes to any of the vendor hardware libraries (e.g. gps, rild, etc).
It does seems kind of odd though for HTC/VZW to be doing an OTA on a discontinued device - and no mention of 2.41.605.6 OTAs yet from non-rooted users. I wonder if this is real, or just a simple mistake on VZWs end of things.
??
bftb0
I think i will go back to stock and see if mine tries to update.
Sent from my Ginger Tazz using XDA App
It is a fact.
verison support site said:
Verizon Wireless recently released a software upgrade to the DROID Eris by HTC. All Verizon Wireless cell phone plan holders are encouraged to download this update for their HTC Droid Eris to improve the phone’s performance. The following instructions explain how to upgrade your phone’s software:
You will be notified that a system update is available via your notification bar. Select “system update available” to view the update details.
Read update details and when ready, select “Restart & Install”. Your device will power off and back on and the installation process will begin.
To manually update your phone or to check for updates to make sure you are running the most current software, go to Home > Menu > Settings > About phone > System updates. If an available update is shown, press “Restart & Install”. The device will power off and back on and the installation process will begin.
Note: If you have received and installed the update on your phone, you may experience delays in restoral of personal data, such as contacts, while the data is being re-synced. Data is normally re-synced within about 30 minutes after the update is complete. If for some reason the sync stalls or does not start, you can force a sync via “Sync Now” in Accounts and Sync menu or turning your phone off/on may help expedite the sync process. To see the order of sync and the sync status press Menu -> Settings -> Accounts & sync.
System Update While You Are Roaming
If you are roaming you will not receive a system update notice. You will need to enable Wi-Fi and wait for the update notice to appear.
To enable Wi-Fi, go to Settings > Wireless Controls and press Wi-Fi to enable.
To connect to an available Wi-Fi network, select “Wi-Fi settings” and choose an available Wi-Fi network or manually add a Wi-Fi network that has had security settings established.
Follow directions above to ensure proper installation of the updated software.
Click to expand...
Click to collapse
http://community.vzw.com/t5/Other-Android-Devices/HTC-DROID-ERIS-OS-UPDATE/ta-p/346372
There you go. The modified date is 1-24-2011.
Super_Dork_42 said:
http://community.vzw.com/t5/Other-Android-Devices/HTC-DROID-ERIS-OS-UPDATE/ta-p/346372
There you go. The modified date is 1-24-2011.
Click to expand...
Click to collapse
Except for the fact that not a single person has reported receiving a v 2.41.605.6 OTA. I suppose that rooters are the minority of users - so it would seems like somebody might have let out a peep if it was already being rolled out by VZW. Time will tell, I guess.
Super_Dork_42 said:
http://community.vzw.com/t5/Other-Android-Devices/HTC-DROID-ERIS-OS-UPDATE/ta-p/346372
There you go. The modified date is 1-24-2011.
Click to expand...
Click to collapse
That was last month?
Sent from my HTC Eris using XDA App
I was OTA 2.1 unrooted till last week and didn't get it.
Just ran the RUU, waiting for the phone to boot up.
Edit: System Updating
Would froyosense be nice. But I doubt it.
Sent from my GSBv1.7-ERIS using XDA App
spc_hicks09 said:
Just ran the RUU, waiting for the phone to boot up.
Edit: System Updating
Click to expand...
Click to collapse
I'm assuming the RUU gives you 2.36.605.1; let us know if you get anything besides 2.37.605.4 as a result of the OTA.
Changed nothing that I can see.
Firmware Version
2.1
Baseband Version
2.42.00.04.12
Kernel Version
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.37.605.4 CL185970 release-keys
Software Number
2.37.605.4
Browser Version
WebKit 3.1
PRL Version
2.11_002
ERI Version
5
Afterwards I got "Your system is up to date"
Well, now to reroot.
I am kinda excited for this...I checked the HTC Developer site and at the top of the list is "Droid Eris by HTC - Eclair MR - 2.6.29 kernel source code" not sure when this was published and don't know the difference but this is all very interesting... the only difference is that earlier they released another one but is says Droid Eris by HTC (Verizon) - Éclair MR - 2.6.29 kernel source code....no Verizon in the newest one...
spc_hicks09 said:
Changed nothing that I can see.
Firmware Version
2.1
Baseband Version
2.42.00.04.12 <-- That is unexpected
Kernel Version
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.37.605.4 CL185970 release-keys
Software Number
2.37.605.4
Browser Version
WebKit 3.1
PRL Version
2.11_002
ERI Version
5
Click to expand...
Click to collapse
Everything above seems like what would be expected from the July 2010 OTA - except the radio version. ( see here. )
spc_hicks09 said:
I don't think the update took or something. Phone is showing the wrong radio version and software number.
Click to expand...
Click to collapse
But something DID take - the RUU is 2.36.605.1, and you ended up with 2.37.605.4 (... and some strangeness involving the radio...)
All of the OTAs have been "incremental", not cumulative - they perform binary PATCHING of existing files, so they are highly sensitive to the starting version of the software. I would think that if VZW was really doing another OTA, the starting point would be 2.37.605.4. (There was a time when Google's servers simultaneously had two OTAs available: one that converted a Cupcake Eris @ 1.17.605.1 to 2.37.605.4, and one that upgraded the "Leak-V3/RUU" Eclair Eris @ 2.36.605.1).
bftb0
bftb0 said:
Everything above seems like what would be expected from the July 2010 OTA - except the radio version. ( see here. )
But something DID take - the RUU is 2.36.605.1, and you ended up with 2.37.605.4 (... and some strangeness involving the radio...)
All of the OTAs have been "incremental", not cumulative - they perform binary PATCHING of existing files, so they are highly sensitive to the starting version of the software. I would think that if VZW was really doing another OTA, the starting point would be 2.37.605.4. (There was a time when Google's servers simultaneously had two OTAs available: one that converted a Cupcake Eris @ 1.17.605.1 to 2.37.605.4, and one that upgraded the "Leak-V3/RUU" Eclair Eris @ 2.36.605.1).
bftb0
Click to expand...
Click to collapse
Could the radio just be because I flashed a radio when rooted ? I would think that the radio would have changed though when I ran the RUU. So the update itself, changed my radio ?
HaRdC0r3 said:
I am kinda excited for this...I checked the HTC Developer site and at the top of the list is "Droid Eris by HTC - Eclair MR - 2.6.29 kernel source code" not sure when this was published and don't know the difference but this is all very interesting... the only difference is that earlier they released another one but is says Droid Eris by HTC (Verizon) - Éclair MR - 2.6.29 kernel source code....no Verizon in the newest one...
Click to expand...
Click to collapse
Thanks for pointing that out - there are a LOT of files in there that have dates of 2011-02-23.
Maybe there is something to this after all.
They're probably just updating us to Honeycomb.
spc_hicks09 said:
Could the radio just be because I flashed a radio when rooted ? I would think that the radio would have changed though when I ran the RUU. So the update itself, changed my radio ?
Click to expand...
Click to collapse
The July 2010 OTA flashed a new radio as part of the update package.
The only way to know for sure what happened is for you (or someone else) to repeat the experiment you just went through, but make sure to capture the OTA download link. Then we can look into the update package and see what it is doing. It would be a surprise if HTC/VZW changed the radio version.
However - the 2.37.605.4 (July 2010 OTA) is old news - this thread is about something which is apparently more recent than that.
ONE MORE THING - there is a chance that the Android 2.1 (Evo/Unrevoked/wag3slav3) rooting exploit will be patched in a new update - there is a risk that if you roll back to capture a new OTA, you might end up with a phone which can not be re-rooted, as every OTAs has also replaced the recovery partition. If you are going to take that risk, you probably ought to have the S-OFF bootloader installed on the phone.
bftb0
I'll give it a try, after the update I was already able to reroot and flashed Ginger Tazz 8 again with no issues. I'll give it a try and run logcat so I can get the link.
If just the radio changed, Sprint recently updated the Hero radio to something newer than what we got in the July Update.
I wonder why Verizon would care if we rooted our Erises at this point?
Ok so the RUU i'm using says:
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver
Will update again with logcat and phone info in about 10 minutes.
@ stonent .I was talkin to Verizon yesterday .. the guy told me I should look into.rooting lol I said I already have and running gb lol
sent from my invisable htc thunder bolt
Hi,
I recently updated my Mozart to Mango via the beta invitation.
The reason being that I was unable to force the Mango update via Zune and was not included in the first update wave.
So I activated the beta invitation that I had received several months ago (I'm a registered developer) and set up a PC with the old beta versions to flash my Mozart.
After going through all the updates (I was on 7392) including ISV, I am now on 7720.
However, my phone did NOT update the firmware.
I am therefore currently stuck with:
Firmware revision number: 2250.09.12803.111
Radio software version: 5.52.09.16_22.33a.50.10U
Bootloader version: 1.28.2250.3(113810)
But my OS version is: 7.10.7720.68
Do you know of any way to get the new firmware revision and the new radio software? (I would like to keep my data on the phone and would therefore be happy, if I don't have to reflash a Mango-rom that has these updates included)
Thank you very much in advance
Best regards,
FrozenLord
little info
The only words I can say is that after offical update (free phone in france,)
figures are:
Firmware : 22.50.21.40.600.401
Radio: 5.69.09.05a_2250_50_50_21U
spl; 4.6.2250.0 129193
i have the same later radio and firmware version numbers as well, after tricking the update with the Zune and Local Area Connection disable method.
Hi,
I do know that you receive these updates when updating via the regular way (even if it's tricked).
Unfortunately, this way was not possible for me - for a reason I don't know.
So I used the approach I explained above and am NOT able to do the regular update.
Does anybody know of any way to update these components separately?
Best regards,
FrozenLord
I updated my wife's Mozart to Mango 7720 via the 'leaked' MS employee release. Her phone still had the original firmware after the Mango update like yours. I was beginning to anticipate having to reflash her phone with the Stock ROM when two days ago she got a message of an update in Zune. Sure enough it was an HTC update that brought the firmware up-to-date, the same as mine updated via the public release. You just may need to wait a bit longer.
Sent from my T8697 using XDA Windows Phone 7 App
Hi,
I have the same problem. My carrier is also t-mobile germany. Maybe it is a problem from them??? If you find a way to tricker the firmware update. please let me know.
I finally found a way
Hi there
After a lot of fiddling around, I have finally found a way to upgrade the radio rom without losing the private data.
You will need at least the following applications:
- A modified RUU so the flash is not erased after the update (which is a standard procedure in the standard RUU, so use the modified one and ignore the HD7-part - it works!) http://forum.xda-developers.com/showthread.php?t=1204733
- The actual radio update (5.71.09.02a from the HTC Mozart Europe ROM) https://rapidshare.com/files/1216711649/RUU_unsigned.nbh
Now, before you start doing anything that you might regret or wonder about later, I suggest that you read the complete post
I've tried to explain all the pieces and posted my experience too.
Just for security (better safe than sorry!), you should create a complete backup of your phone to fall back to if anything goes wrong.
A great tool is provided here: http://forum.xda-developers.com/showthread.php?p=14258464#post14258464
Now for the instructions
I am not responsible for your actions or any consequences that are caused by this mod! You do all this on your own and can hold no one responsible but yourself!
Download both files and extract them into the same folder.
Reboot your phone and keep the VOLUME DOWN button pressed, while turning it on
You should see the SPL-screen (a strangely colored screen like this one: http://forum.xda-developers.com/showpost.php?p=16189686&postcount=3)
Connect the phone via USB to your PC
(Windows should install a driver - if not, install Windows Mobile Device Center if you're on Windows Vista/7)
Fire up the modified RUU and click through
You should be ready to go
By the way:
I almost killed my phone in the testing procedure because I created an invalid nbh (had no idea what I did and started fiddling without tutorials ), which seemed to have killed parts of my SPL...
The process was easily fixed (fortunately) by applying the HSPL by DFT, which fixed the problem (which was that my phone always booted back into the SPL-screen, unable to boot into WP7).
But since that moment, I've got HSPL installed.
So if the above procedure does not work for any reason, install HSPL and try again
HSPL can be found here: http://forum.xda-developers.com/showthread.php?t=1195647
Also, I updated the ROM using a standard RUU and found out about the FLASH-format after applying the update the hard way (resulting in a totally clean mobile...).
Fortunately, I had created a complete backup before and was easily able to restore it via the same application.
Should you happen to run a normal RUU for who-knows-what-reason, just restore the update. (the radio rom is NOT downgraded in the restoring process, so you're good to go, even if you chose the wrong RUU)
Just out of curiosity (and knowing that I had a backup to fall back to) I reran the update process using the modified RUU (see link above) and the flashing went fine - and the phone did not format itself afterwards
Therefore: Ignore the HD7 in the name, it works for the HTC 7 Mozart too.
I used this tool to extract the Radio-rom (and the including customisation) and repacked it using the same tool: http://forum.xda-developers.com/showthread.php?t=1260757
Thanks a lot, ted973 for providing it
Additionally, I am glad that DFT had released the HSPL for my phone, else I would have had a problem
Thanks a lot guys!
Now have fun with the updated radio and feel free to comment
My versions are now:
OS version: 7.10.7720.68
Firmware revision number: 2250.09.12803.111 (unchanged to before)
Radio software version: 5.71.09.02a_22.51.50.21U
Bootloader version: 1.32.2250.1(119496) which is because of the DFT HSPL
Best regards,
FrozenLord
@ FrozenLord
did you debranded your mozart or did you have an unbranded device in the first place ?
i'd like to figure out a way to get the latest radio on a debranded mozart. seems like zune doesn't update the bootloader and radio on a debranded device.
I've got a T-Mobile branding.
But the procedure should work for an unbranded mobile as well
thanks a lot. will try to get my debranded phone to the normal update route with your tip.
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.
UPDATED TOPIC! 02.08.2017
ASUS has released the NEWEST Nougat Update for ZF3U:
Newest Release: Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
Previous Version: Version WW_14.1010.1705.49 Release Date: 21.06.2017
Here is the official Update for Manual Install. DIRECT from ASUS Servers. Version WW-14.1010.1706.50 Release Date: 2017/08/01 Size: 1.71 GBytes
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/UL-ASUS_A001-WW-14.1010.1706.50-user.zip
Via:
http://https://www.asus.com/Phone/ZenFone-3-Ultra-ZU680KL/HelpDesk_Download/
If the link is expired Get it from the Asus ZenFone 3 Ultra Support and Firmware Website under Drivers and Tools-ANDROID Section. It is for the WW Version:
UPDATE! :OTA Update Working ONLY with phones with LOCKED Bootloaders. The Manual Update will work with both LOCKED and UNLOCKED Bootloaders. I have tested the OTA Update and after I unlocked my ZF3U's bootloader, I can no longer get update notification (on my previous ZF3U-I am on my 2nd one). From what I have read, ASUS servers block any devices with unlocked bootloaders from accessing automatic system updates. My only option is to find a way to RELOCK the bootloader or use the Manual Update file.
Enjoy!
Changelog:
Android 7.0 Nougat comes with handful of features such as App Shortcuts, Multi Window support, restart setting to power menu, Launch the camera by pressing the power button twice, Image Keyboard support, 100 emoji added, GIF Support, Quick Reply via Notification, Notification Redesigned panel, Notifications prioritization, Enhanced Doze Mode, System UI Tuner, Customizable Quick Settings, Don Not Disturb, New Settings Panel Redesigned, Data Saver per App, seamless updates and New Emoji Support.
-----------------------------------------
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
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, .
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_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
ctorbaoglu said:
AWFRONT said:
The Asus Zenfone 3 Ultra is now receiving the Android 7.0 Nougat update with software version 14.1010.1702.36. The update is rolling out over-the-air.
Check for it from Settings > About > System Updates on your Zenfone 3 Ultra. If you’ve got the update, go ahead and download/install it.
It appears to be currently available for the WW (Worldwide Version)
Currently no manual install file is available but I guess this will be available very soon. I also think this may be the first and last final update from ASUS for the ZF3U before they launch another version but it is nice to have the newest version after all and I very much look foreard to making use of multi-window on the device.
--------------------------------------------------------------------------------------------------
Mine is WW version but couldn't receive the update yet. Why?
Click to expand...
Click to collapse
It may be because your Bootloader is unlocked. If it is you will not receive the update. My ZF3U's bootloader was locked when I received the update. However, when I unlocked the bootloader, rooted and then decided to wipe everything through TWRP to do a fresh install of everything to reinstall Android 7.0 the trouble started. Now, I cannot do firmware update using the system Update menu (notification of update availability is not there). This is because the bootloader is now unlocked and I don't know if it is possible to relock it. I guess I have to wait for the full manual package of Android 7 to become available or see if anyone can help me to relock the bootloader and then update from Android 6.0 original firmware. I was excited to be finally getting Android 7.0 but only managed to use it for 1 day. Oh well, you live and learn.:crying:
Click to expand...
Click to collapse
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
AWFRONT said:
UPDATE! As some of us have found out. ASUS has now removed the Nougat firmware (MANUAL Update file) for the ZF3U. As my device's bootloader is unlocked I can no longer receive OTA updates. Perhaps someone could give us an update on the status of the OTA release of Nougat for the ZF3U. I have downloaded the file before removal and successfully installed it. I don't mind uploading it to a file sharing website. However, I am currently using it and I am still having the same issues I had when I used the OTA update, so my advice is for everyone to wait for a confirmed final version of the firmware as the version we have may still be buggy. This may be the reason why they removed it and lets hope they fix and reupload soon. Here are quick my observations of the firmware;
-Fingerprint scanner still not registering when device is setup for the first time or under settings later,
-Screen Rotation is not functional on some of my apps that were able to use it previously with Android 6.0
-My device serial nunber has changed to 111111111111111 (15x1s)( I tried lots of things to put it right but all attempts failed)
-Dual Sim settings access from the notification menu shortcuts is no longer there (it was very useful for me),
-Multi-Window is not operating on all the apps for some reason. On the OTA that i had installed I was able to use it but on the manual firmware file this does not seem to work properly.
-My device is no longer showing under my ASUS account as a registered device (I don't know if this is a firmware issue or not as bootloader does show the correct serial no)
Also, does anyone know how or where in the firmware I can extract the boot.img, recovery.img and all the othr essential .img files to restore stocj recovery after root/twrp installation?
If anyone has any ideas as to why the serial number and fingerprint issues are there, I would like to hear from you. Other issues are tolerable. Thanks.
Click to expand...
Click to collapse
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
doctahjeph said:
After some thought on your issue, do you now which version of the device you have? Maybe you have an China(CN) device and not World Wide(WW)? Just trying to think about your issues and it seems to possibly be that your firmware may not working correctly. This very well maybe because ASUS dropped a faulty firmware on you/us, or maybe because you tried WW firmware on a CN device? Or vice versa? Have you looked into what would happen if a firmware for a different region was installed on a device?
As for the images, I believe you can get the boot.img inside the firmware zip files you download from ASUS. Just unpack it and the boot.img should be in the root of that folder. I can't find the recovery.img from anywhere, other than from Shaka's megadownload page. I was able to get that one working on my Zenfone though and successfully put my Zf3U back to stock.
Click to expand...
Click to collapse
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
doctahjeph said:
hhhmmm, I had a similar issue with a corrupted cache partition that was causing boot loops. I was able to get it fixed. Try this. Download the latest WW firmware from the website, MM no nougat. Then flash the original boot.img and recovery.img from Shaka's megadownload page. Boot into stock recovery and do a factory reset. They should wipe all the partitions and format them again. After that install update from SD card and choose the latest WW firmware zip you just downloaded. Profit??
Click to expand...
Click to collapse
I have tried your suggestion numerous times and;
-it appears that when I boot to Android M, I don't have any sound in calls, fingerprint and other issues fully remain.
-when I upgrade to Android N, then Iam able to hear call sounds but fingerprint scanner still does not register and other issues still remain.
I have a feeling that somewhere along the process my device has enabled some sort of encryption and this is preventing the device from enabling all the features. No matter how many times I install/reinstall/wipe using stock or TWRP no change.
Does anyome know how I could disable encryption either using some sort of google service or through root etc... In settings device reports that it is encrypted. Also when I first booted the device after firmware update encrypting device message was shown. Not sure whats going on with my device. Hope to find out/fix soon though.
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
AWFRONT said:
ASUS Releases new update to fix the previously faulty update that was withdrawn.
Latest Version WW-14.1010.1703.42
Previous Version [Withdrawn due to faults] WW-14.1010.1703.36
I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Click to expand...
Click to collapse
???? Thank you!!!
ASUS has released the NEWEST Nougat Update for ZF3U.
Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes
ASUS ZenFone 3 Ultra=ZU680KL(A001) software Image:V14.1010.1706.50 for WW SKU only*
Improvement Item：
1.Modify strings in several apps
2.Google security patch update
3.Update FR E-label
For more information please refer to：
TW：http://www.asus.com/zentalk/tw/ReleaseNotes
WW：http://www.asus.com/zentalk/ReleaseNotes
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, .
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_Z00ED
**How to know the device software version?
Path: Settings->About-> software information->Build number
Once again, I have updated my original post (First Post of the Topic) with all the latest links and the newest changelog.
Enjoy!
Never mind.
AWFRONT said:
Thanks for the reply. My version of ZF3U is the Worldwide WW version and the firmware is definitely the correct one as stated on the original changelog from ASUS as I posted above. I have not tried the CN firmware but I am tempted to give it a go to see what happens. I also noticed that everytime I go into recovery via TWRP I see this red message stating "failed to mount factory/partition [invalid parameters]"
What does this mean and could the phone be stuck between two firmwares and not sure what to do even though I have wiped every wipeable area using TWRP(like I used to with Samsung devices but not sure if this could have caused it). Could this explain why I still cannot use fingerprint scanner on neither Android 7 nor Android 6.
At one point I used the ASUS Flash Tool and I noticed a message whilst attempting to load the firmware stating something like 'encrypting device.....' does this mean anything? Has my device been encrypted somehow in the process resulting in lack of fingerprint registrations on the scanner. Coming from Samsung/Sony/Huawei devices, I am finding the update process with ASUS a bit of a hassle but lets hope they will fix this soon as I believe that currently there is no phablet better than ZF3U. Due to the fact that the firmware has now been removed from their servers, I am beginning to believe that the firmware is faulty and is not doing a clean wipe/reinstall of all parts of the device configurations.
Click to expand...
Click to collapse
Hey @AWFRONT How did u manage to go back from android 7 to 6 ...i recently updated my phone to nougat and want to go back to mm. Could u help me out I have unlocked bootloader
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
AWFRONT said:
Hi! I did not downgrade from Android 7.0 to 6.0 on my new/2nd ZF3U. If you read a post I made in another topic you will see that I am now on my 2nd ZF3U because the 1st one had some serious issues and then it powered off so I gave up and sent for repair through my insurance but they said it could not be repaired so I bought another one with the payout I received and this one I am using, I use in its factory state with Bootloader locked and unrooted and given the lack of developer support for this handset, I do not want to modify anything.
My advice would be to stick with Android 7.0 and if there are any features you are missing then write them out and send to Asus and hope thy will fix in future update. With my previous ZF3U, I did do a downgrade on the 1st ZF3U but this resulted in Fingerprint scanner failing and I could not hear the other side when making and receiving calls and the device serial number in About Phone section was incorrect (changed to all 1s).Unless you have insurance and a spare phone, I would not recommend you downgrading. Too much of a risk with this handset. If you want to do it, then go ahead and you can share yoir findings here.
Instructions to follow:
-Disable and erase fngerprint records in settings
-Prepare a microsd card with the MM manual firmware in it and reboot into recovery.
-If you are rooted then wipe cache and factory reset but do not wipe data/system partition,
-Select update from SD Card and select firmware file and wait for the process to complete.
-reboot back.into recovery, you should hopefully see the factory kernel has downgraded to I think version 1.26 from 3.11 and then do another factory wipe and reboot and see the results.
Sorry, cannot be of much help but I wish the developers could pay a little bit more attention to this device like the Samsung Note series.?
Click to expand...
Click to collapse
all of this from twrp or stock recovery
If you have TWRP installed then apply from it, if not you can use the stock recovery of Android 6.0 as posted in one of the topics of ZF3U forum sections and flash it using custom recovery and then flash the appropriate firmware file of Android MM version 6.0 and on completion wipe cache, factory data and reboot.
Due to lack of developer support for this device, I do not recommend that you rollback the firmware. When my 1st device failed I realised that ASUS devices don't have the software fixability ease of Samsung devices so I am using my 2nd ZF3U in its original factory state. I love the device as it is and don't want to mess with it and root is no longer important to me.
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
gubbilo144 said:
does anyone know if this latest firmware update Version WW-14.1010.1706.50 2017/08/01 Size 1.71 GBytes is still rootable before i update from Android 7.0 (WW_14.1010.1703.42),thanks
Click to expand...
Click to collapse
mine is
Malam
anybody updated to WW-14.1010.1711.62 is it still 7.0 or 7.1.1