Related
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Ste_J said:
New member but long time lurker.
Hoping somebody can help with a UK Nabi issue
I have previously used nabi lab to flash, root and install gapps. This worked great until I got a mail about the UK OTA. I then started to search for my stock back up and remember losing it in a hard drive disaster.
This led to updating using what I could find and nabi lab. End result at one point being Nabi reporting US Nabi version
Long story short. Managed to find another thread with a UK stock backup v2. Got this loaded and can update to v2.1 with no issue. Then I tried to go to v2.2 and I constantly get the dead android. And back to 2.1
The nabi has been wiped several times and at one point had no OS at all. I used the stock recovery in nabi lab and now wondering if the recovery files have an influence on the OTA? I have read that the earlier forcing gapps may have wiped some files needed for the OTA although I would assume that the very action of wiping everything via TWRP would have got around this I.e restoring via stock would have put them back on?
The nabi is currently running fine on v2.1 but can't get to 2.2 despite trying to find every solution found via search. Would have posted in the nabi section but don't have enough posts yet
Thanks in advance
Ste
Click to expand...
Click to collapse
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Floralina123 said:
I posted a question 2 days ago- can't even do first update so I'm following this with interest in the hope of getting info on how to unroot and just do ota updates with no dead android.
Click to expand...
Click to collapse
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Ste_J said:
Hi,
what nabi version do you have? I have been able to unroot and get back to stock by using a UK v2 back up and a combination of nabi lab and twrp.
If you was looking for UK then I could probably point you in the right direction to get to the same point as me
Click to expand...
Click to collapse
Hi Ste_j, thanks for the reply. I unrooted it already, or so I thought using nabilabs but it looks like twrp was removed and gapps remains - which I'm happy about seeing as I can't update it using ota update with google playstore- that could have been a disaster.
Here is my question I posted -
I Apologise for my ignorance in android in general.
I have rooted a Nabi 2 successfully installing Gapps etc using Nabilab, which was a pleasure to use. Now that the new OTA update is available which includes the Googleplaystore I would like to unroot and get the OTA updates. I thought I had unrooted it - using Nabilabs (twrp would not work, can't remember why but I think the touchscreen part wouldn't work for me). I returned to stock using (option 1. -1.9.37. Android can boot.) recovery using Nabilabs. I think I did a factory reset after that -sorry but it was weeks ago. Anyway, I suspected something wasn't right when I still had Gapps. I don't have TWRP on it now.
When I do the OTA update I get the dead android on reboot. Nabi is working fine apart from that. I read a lot of pages on this website but it ended up confusing me more than helping me unfortunately as I'm not android savvy.
I just need someone to tell me exactly what to do to properly unroot the Nabi so that it is truly back to original so I can use the OTA updates. I have no need to root the nabi again as the google play store is now officially available. And I've got a UK Nabi 2.
Ste_j,
I assumed I had a Uk nabi because I'm in Ireland. I don't know how to check this as it doesn't say uk here but the
model no is NABI2-NV7A-IE
Android version 4.0.4
Kernel version 3.1.10-00298-ge08b99f
[email protected] #2
SMP PREEMPT Tue Feb 26 17:21:35 HKT 2013
Build no IMM76L
Product version: 2.0-release-keys
I don't want to unroot any further unless I can get the latest ota update that gives me the google play store. I would rather leave it as it is now(gapps still on it) until you get yours working successfully I will gladly follow your lead from start to finish then. I just hope someone in the know replies with the solution. I too had been reading the nabi forum but cannot post there.
Tnx
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Ste_J said:
Sounds like one of my recent 1am going on for 2 adventures in nabi land!
Hopefully there will be a UK stock 2.2 being uploaded tonight and if I get it working then I will let you know.
Click to expand...
Click to collapse
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
metalheadkicks said:
Did you ever sort this one out mate? If I can atleast get my hands on the 2.2 OTA update zip file then atleast I can force it to upgrade from recovery mode.
Click to expand...
Click to collapse
Not yet. Waiting on 2.2 to be uploaded on the other thread. Hopefully the guy will get chance to upload over the weekend
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
aicjofs said:
So all 3 of you have UK Nabi's that can't get to 2.2 and are stuck somewhere at 2.0 or 2.1? Is that correct?
In theory restoring either of these(2.0 stock or 2.1 stock) http://forum.xda-developers.com/showpost.php?p=50158865&postcount=67
should then allow you to take the OTA. The US version did it as a 2 part update and the first wiped the system partition and installed a base ROM which got everyone on the same page and the did the second update to 2.3(2.2 for you guys if I understand correctly). Maybe the UK version doesn't do it like that.
Where is everyone failing at? TWRP usually fails for a "assert error in some file" If the backups are truly stock then this should work fine. Sometimes people who make backups mess up and TWRP set the file recovery-from-boot.p to recovery-from-boot.bak then the update can find that file and errors. Any other files will cause the same issue. Some other issues are the addon partition, the OTA's do edit stuff on the addon partition, if you have skipped around OTA's this can cause a mismatch too.
A stock 2.2 ROM would be great but anyone on 2.1 would still be stuck with ICS bootloader which won't boot 2.2UK. You would also want an addon partion backup to restore too.
Oops I get it.. You guys don't know where you are failing at because the stock recovery(dead android) doesn't give you any info. TWRP 2.6.3 can install OTA updates. Put TWRP backon. Use it to install the OTA it will have a log that will say why it's failing.
Click to expand...
Click to collapse
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Ste_J said:
Thank you. I have restored 2.0 from that post
Am I correct in thinking that the OTA will be stored in internal memory and that TWRP should be able to locate the file? Is there anyway of repairing the addon partition if that is corrupt?
Click to expand...
Click to collapse
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
aicjofs said:
Yes the ota is stored in internal memory. On data/media(internal). Its in a folder called ota or something intuitive like that. A forum search will find it, I'm drawing a blank. Do the ota download but when it says to update, back out of settings at that point and you will have the OTA zip.
Its kind of hard to repair addon. If there was a backup of addon from an early software version you could let the otas update it properly. I didn't really think to add that ability to twrp until late in the game though. The other option is to have someone that has successfully progressed through the otas make a backup and share. Then we could cook something up where you just use a 2.2 ROM and restore, update the bootloader and restore a 2.2 add-on. The last option is a custom OTA, similar to what I did with the US Nabi, and even that hasn't went perfectly. I'm not sure if its my update or people doing it a little different then the instructions but there have been a few failures with it. Although we figure it out eventually, just like we will with the UK Nabi.
Click to expand...
Click to collapse
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Ste_J said:
TWRP installed and OTA attempted. log file attached . still not sure what is going wrong but hopefully somebody who is used to reading the logs will point me in the right direction
Click to expand...
Click to collapse
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
That was going from 2.1 to 2.2
And yes i appear to be cross threading at the moment. Grabbed the 2.2 update and just spent the last hour trying to get past the stuck nabi screen. Got back to 2.1 eventually. Fastboot and Nabilab with just enough time to fire over previous TWRP and get back to the restore
Any ideas on how to update the boot loader?
Moving back to the other thread http://forum.xda-developers.com/showthread.php?t=2041224&page=9
aicjofs said:
Looks like it fails for fuhu_nabiMD_uk.apk. Never seen it fail a vendor app before. This was going from 2.0 to 2.1?
I see the 2.2 with addons got uploaded in the other thread. That's going to be the easiest route, except like I said previously I have this thinking that if you restore that(boot,addon,system) it's going to be stuck at Nabi symbol when you reboot because the bootloader wasnt updated to Jellybean. We will have to see I guess.
Click to expand...
Click to collapse
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Uk nabi update - leaving nabi as is until it's solved
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
MattP79 said:
I get this issue also. I had rooted and added Google services - happy enough but no ability to move Apps to SD and I wanted to see if the Kernel update added this option. Anyway, I restored my backup - but the updates didn't apply cleanly. I swapped the boot loader back and things still weren't right and I didn't know then how to troubleshoot it. I was tired/had a wailing 3 year old wanting his tablet and I elected to wipe and reinstall from scratch using NabiLabFull. Initialised well enough through initial setup - completed setup and changed the recovery back to stock and it boot looped... Ugh. Reapplied stock image through twrp and changed to recovery back immediately - setup the Nabi from scratch and update 2.1 applied successfully. Update 2.2 fails however using stock everything with the error message:
Finding update package. . .
Opening update package. . .
Verifying update package. . .
Installing update. . .
Verifying current system. . ,
assert failed: apply_patch_check("/system/vendor/app/fuhu_nabiMD_uk.apk", "c4cd5edbc3f980c806a4fb8dd1d182f5c81b35f3", " eea145bf7f4a7b314ef15a3f3b0b9e8a9bc6efe7")
E:Error in /cache/nabi2-update.zip
(Status 7)
Installation aborted
So. The presence of two, what appear to be, md5 hash values makes me think the app in the system partition is not what it should be. Absent a file manager and root access I haven't delved deeper but I can only think the stock image I loaded isn't close enough to the UK stock image such that the UK specific apps correctly update in the 2.1 update (NabiMD is no longer installed after applying the 2.1 patch - dead link launcher icon on Parent home screen). My problem is I forgot to copy the pre-rooted backup before wiping - so I might have lost it. Anyway. Need to go shopping now and I'll dig more later. Long story short - I'm not sure a stock root path via NabiLab is viable for UK Nabi 2s.
Click to expand...
Click to collapse
Floralina123 said:
I'm sorry this is not helpful but I just wanted to say that until the uk nabi is restored successfully and can update normally using ota, I'm leaving mine as it is. Basically, it works fine and my 4 yr old gets endless fun out of it. In saying that, I will restore it to normal someday when it can be done. I await one of you smart nabi gurus to come up with the answer.
Click to expand...
Click to collapse
Have you tried this? http://forum.xda-developers.com/showpost.php?p=50431606&postcount=98
It has to be done manually but should get a UK Nabi to complete stock version 2.2.
In case you need to know for some reason in the future that is a SHA1 hash not md5.
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
So, about like a week ago, I made a post on XDA developers named "Well, I f**ked up. Badly.." and basically, this is what it contained.
Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Anyways, I've tried restoring the phone for 3 days straight to EMUI stock rom, so I could update it manually to Oreo 8.0 and THEN install LineageOS 15.1. However, I literally could not find ANY SINGLE ROM on planet earth for Huawei Mate 10 Lite, on EMUI 5.1. I was so desperate to fix the phone that I just gave up and installed Elemental which was based on EMUI 5.1. Sure, phone working great, but not what I wanted.
I wanted LineageOS 15.1, not a rom based on EMUI. So, my question is, how do I update it to 8.0?
In the post, people suggested to manually flash the stock rom (8.0), but I couldn't find the stock rom. Also, yes, I tried TeamMT's site, xml tree not working blah blah blah site's dead.
So, what do I do?
Here's the link to the post, if anybody wants to read the replies
https://forum.xda-developers.com/mate-10/help/fked-badly-t3868233
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
draqkin said:
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
Click to expand...
Click to collapse
I have exactly same phone (c185) never tried unlocking bootloader but I updated to emui 9 159 there are some buggy things like when you want to use third party lunchers You can't use gesture navigation and it has so many bugs so not using gesture is better
there are again some problems with third party launchers (im using nova) like sometimes when you go to "resents" its totally blank and you have to force stop "huawei home" to make it right
there are some good changes in camera like new 960 fps slow motion (but there is a huge crop in 240fps 720p and 960fps 720p I can't remember that 240fps had that crop or not) Turning off master ai and some new scene detection but it's slower than last one
there is a new performance mode that i love using it (it feels like a real flagship however it's not because of stupid SOC)
there is a new AI api that android 8 didn't have so most of apps wasn't able to use NPU
in emui 8 there is a little bit better battery
I love changes to my phone so I preferred buggy new firmware to old ones there are so many good little changes in interface (like when you take a picture you can go to gallery then scan it for QR code)
There is a way better Mira cast functionality (and new desktop mode in it)
hi touch, hi vision
These were all expensives I had with emui 9 that I can think of
How did you update @arianamirgholami ?
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Same here, although my brother and I have the same device (ALP-L29C185) and we're on the same career, he got the pie update like a month ago and nothing for me yet. I think it's a matter of time until our imeis turns.
MasterThiefGarrett said:
How did you update @arianamirgholami ?
Click to expand...
Click to collapse
I used Erecovery of firmware finder
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Fazee99 said:
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Click to expand...
Click to collapse
I finally got the OTA update from EMUI 8 to EMUI 9
curgervending said:
I finally got the OTA update from EMUI 8 to EMUI 9
Click to expand...
Click to collapse
Thats great. Means you got more luck. Mine is still on 9.0.0.159 and no update. Please also confirm one thing. What is android security patch in this version?
Finally grab the update today morning...
Another update today. Woww
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks