Related
So I did a stupid thing and flashed SuperSU after updating to Android Nougat (UK) in TWRP, the phone won't boot, both of my TWRP backups will not restore my data (bootloop at untrusted device page).
Fastboot won't flash the stock MM anymore either and I get a FAILED every time after validating it says security version downgrade, (attached image).
Any help in getting my phone to boot would be much appreciated, I've never seen anything like this before.
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Prfndhatrdofman said:
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Click to expand...
Click to collapse
Thank you that's a relief, I just flashed Rogers -45 but get "No command." at recovery when I go to sideload nougat, do I flash TWRP again? I followed your easy flash guide, was I right in doing that? Thanks for your help
Edit: after flashing TWRP again and clicking ADB Sideload it gets stuck at "starting ADB sideload feature" not sure where i've gone wrong. Its 2am here so i'll try again tomorrow, appreciate all your help.
supacrazyguy42 said:
Thank you that's a relief, I just flashed Rogers -45 but get "No command." at recovery when I go to sideload nougat, do I flash TWRP again? I followed your easy flash guide, was I right in doing that? Thanks for your help
Click to expand...
Click to collapse
Don't flash TWRP.
When you are at No command, hold the power button for like 2-3 seconds (I sometimes press the volume key too) and you should see some commands!
Prfndhatrdofman said:
Don't flash TWRP.
When you are at No command, hold the power button for like 2-3 seconds (I sometimes press the volume key too) and you should see some commands!
Click to expand...
Click to collapse
Thanks, when running the flashfile.bat is it normal for it to say "not found" on each? I tried holding power, and again with volume after starting from scratch flashing Rogers -45 but still get No command. and then a bootloop Completely lost
It also has no baseband and says Console null but i'm not sure if that's relevant. Just can't seem to get into recovery at all now, tried flashing recovery again separately too.
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Prfndhatrdofman said:
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Click to expand...
Click to collapse
Brilliant! That worked to get commands, thank you. Time to try sideloading
Prfndhatrdofman said:
Not Found error is fine, ignore that.
Also Baseband will be blank until after the first boot of nougat. Trust me!
OK so go back to recovery. You need to get the commands for recovery to appear.
Try again. Go back to Recovery, hold power button at the No Command and press Volume Down then power Up then let go of everything. The commands should show up. Try again! Ill see if i can record a video of me doing it shortly.
If you need to, re run the RSD Batch and try again.
Click to expand...
Click to collapse
Yet another problem, sorry, but now in recovery i'm on "apply update from ADB" any idea why i'd get "cannot read Filename.zip " when trying to sideload? I tried mfastboot v2
supacrazyguy42 said:
Yet another problem, sorry, but now in recovery i'm on "apply update from ADB" any idea why i'd get "cannot read Filename.zip " when trying to sideload? I tried mfastboot v2
Click to expand...
Click to collapse
Also had the same problem. Reboot your computer, rename the zip to something like update.zip or something. If that doesn't work, reinstall your ADB drivers.
Prfndhatrdofman said:
Also had the same problem. Reboot your computer, rename the zip to something like update.zip or something. If that doesn't work, reinstall your ADB drivers.
Click to expand...
Click to collapse
Finally worked on a fresh start with another PC You're a life saver man :good:
supacrazyguy42 said:
Finally worked on a fresh start with another PC You're a life saver man :good:
Click to expand...
Click to collapse
Cheers!
please help phone bricked
i have the same problem and tried reflashing the stock rogers 45 firmware but i get these lines in terminal and it doesntwork. fastboot flash partition.. writing partition (bootloader) validating gpt.default.xml (bootloader) security version downgrade image primary_gpt failed validation preflash validation failed and some other lines basically saying the same thing. am i doing something wrong?
dchitolie said:
i have the same problem and tried reflashing the stock rogers 45 firmware but i get these lines in terminal and it doesntwork. fastboot flash partition.. writing partition (bootloader) validating gpt.default.xml (bootloader) security version downgrade image primary_gpt failed validation preflash validation failed and some other lines basically saying the same thing. am i doing something wrong?
Click to expand...
Click to collapse
Sent PM, I can only walk you through how I fixed it but it sounds similar. Is it saying downgrade error for every single file or just the first two? If just the first two I'd follow the easy flash to Nougat guide step by step.
Also I'm curious, is it possible to downgrade to MM from this? Flashing stock MM will just result in bootloops and downgrade errors again I assume.
Prfndhatrdofman said:
It's OK! Don't panic. I did this too.
Reflash Rogers -45 firmware then adb sideload nougat again. You'll be back up and running.
From my experience with Nougat these last few days, do NOT flash SuperSU and do not try to modify the system partition in anyway or you will soft brick.
Also there error you're seeing is expected. You can't flash MM GPT over Nougat it won't let you (or then you'd really be bricked)
Just flash all of MM again so that Nougat can be sideloaded again
Click to expand...
Click to collapse
You saved my ass! Thank you so much!
supacrazyguy42 said:
Also I'm curious, is it possible to downgrade to MM from this? Flashing stock MM will just result in bootloops and downgrade errors again I assume.
Click to expand...
Click to collapse
You can reflash 45 only so you can sideload Nougat again. Thats why you might see errors when flashing 45 because some of those items cant be downgraded anymore. Theres no going back to MM once you flash nougat.
Prfndhatrdofman said:
You can reflash 45 only so you can sideload Nougat again. Thats why you might see errors when flashing 45 because some of those items cant be downgraded anymore. Theres no going back to MM once you flash nougat.
Click to expand...
Click to collapse
Thanks for clearing that up :good:
I flashed Nougat in my phone, but the built quality of the rom is not stable. Is there any way to get back my stock MM 6.0. My device is Moto Z Play.
aniket1311 said:
I flashed Nougat in my phone, but the built quality of the rom is not stable. Is there any way to get back my stock MM 6.0. My device is Moto Z Play.
Click to expand...
Click to collapse
Assuming it's the same as with the Moto Z, if you're on the Nougat bootloader (from using OTA or by flashing everything including the new bootloader) there's no way back to android MM currently.
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
BACKUP YOUR DATA FIRST
Only for zs570kl 2.15ghz CPU; NO zs570klPRO 2.4ghz device.
Hi all,
official image to flash Android 8 Oreo.
HOW TO:
Method fast 1
1.Extract ZIP
2.Go into the fastboot (key vol + and power on)
3. On the folder extract open update_image.bat
Wait to done 2/3 minut and ENJOY android Oreo
Method 2
Flash using Asus Flash Tool
to download and info
https://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html?m=1
Update file Android 8 Oreo 15.0210.1804.47:
https://drive.google.com/open?id=1U5SBXDpezUIIxisDPY8qm85LoGNfS5i6
I take no responsibility for brick device.
Have testeted the rom and work fine.
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
tecnicopascoal said:
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
Click to expand...
Click to collapse
official Asus, no only in fastboot mode
Has anyone suffering battery drain? I've updated my ZS570KL to 8.0 with Asus official but phone became hot and battery drain is dramatical…. obvious reset many time to factory default and wipe all…. The problem appears from the beginning…. starting the initial setup. Thanks.
grean said:
official Asus, no only in fastboot mode
Click to expand...
Click to collapse
So is this rootable or is it pre-rooted? I also am wondering if this Oreo update fixed the Quickcharge limit (where QC is disabled)?
It is the only way to update?? Except ota
EDIT. Guys, the other way you can update to oreo is flashing oreo stock recovery and then install the firmware
Wheres the MAGIC
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Aussiewaterdragon said:
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Click to expand...
Click to collapse
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
BahaStriker said:
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
Click to expand...
Click to collapse
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
karlnorth said:
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
Click to expand...
Click to collapse
Tried all means, I just gave up
I'm happy to say that I got it working. It appears the Unlock tool gives the "Can't unlock your phone right now" error if your phone is already unlocked.
Previously, I was running the Turbo ROM 6.01 found in the ZF3 Deluxe thread. My phone was BootLoader unlocked and Rooted. I upgraded to 8.0 by running the very straightforward "Update_Image.bat" command found in the 8.0 ROM folder. I figured the update would re-lock my BootLoader, so I ran the 8.0 version of the Unlock tool. Then I ran into the previously mentioned error. In my frustration I just said 'screw it, I have 4 of these phones'. So I booted the phone into fastboot mode and flashed TWRP 3.2.2. I expected it to fail; however, it WORKED! I then booted the TWRP 3.2.2 image and flashed SuperSU v2.82 SR5. That worked! I then flashed the Xposed v90-sdk27-arm64-beta3 zip and THAT worked! I rebooted the phone and it loaded up pretty as you please.
I've followed this procedure with all 4 of my ZF3 Deluxe phones and they are all happily on 8.0.0, Rooted, and have Xposed running
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)
Note: This process is shown for OnePlus Nord 2 and work for any MTK device just replace files as per your model you need to Serch for that)
Credits @Raygen @TheWing
After relocking bootloader you can do safety net pass check to confirm by using following app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettes
Download Re LiveDVD mtk. Client ( this is ready mtk client ubuntu os no need to Install python, drivers ready to go iso)
re_livedvdV3.iso
drive.google.com
Download Rufus for windows 32/64bit)
https://github.com/pbatard/rufus/releases/download/v3.17/rufus-3.17.exe
Note:Relocking has been done on OOS 11.1 v13 so stock boot img of v13, vbmeta from update zip of v13 is required, recovery must be given below.
Your need to replace files as per oxygen os version you are using.
FOLLOWING are images of DN2101 A13 OOS UPDATE IMAGES EXCEPT RECOVERY IMAGE IT WILL WORK IN ANY PHONE, U NEED YOUR AS PER YOUR REGION I WILL UPDATE THREAD AFTER COLLECTING ALL HERE
Boot img (This is stock A13 indian, other regions must use there current OOS version boot img)( other mtk devices must use there boot img here)
https://forum.xda-developers.com/attachments/boot-img.5460945/
Stock recovery(in zip unzip it you will get img file this will work for any region)( other mtk devices must use there recovery img here)
https://forum.xda-developers.com/attachments/recovery_stock-zip.5464685/
Vbmeta:must have correct vbmeta of current OOS Rom. Version (from stock A13 indian update.zip if U r using EU, OR GLOBAL region NORD replace it with the current OOS version you are for which you want to relock)(other mtk devices must use there vbmeta img here)
vbmeta.img
drive.google.com
All files for EU DN2103 ON A12 UPDTAE :
EU varient v12 files:
Boot. Img:
https://forum.xda-developers.com/attachments/boot_stock_a12-img.5461083/
Vbmeta. Img/
vbmeta.img
drive.google.com
Recovery same link for all)
recovery_stock.zip
drive.google.com
Terminal emulator commands :
1) BOOT TO FASTBOOT connect phone to pc in on condition)
adb reboot fastboot
2)to relock bootloader in terminal emulator connect phone to pc in fastboot mode and type)
fastboot flashing lock
MTK client commands:
1)Flash boot img:
python mtk w boot boot.img
2) Flash recovery img:
python mtk w recovery recovery.img
3) Flash Vbmeta :
python mtk w vbmeta vbmeta.img
wifi is not working. everything working after relock bootloader but wifi is not working
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
Factory reset u r phone and reboot see
pankspoo said:
Factory reset u r phone and reboot see
Click to expand...
Click to collapse
i did it. but it's not working
farhansaeeddnp3021 said:
i did it. but it's not working
Click to expand...
Click to collapse
Update yourbphone to latest v14
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
NetSoerfer said:
Is there any way to relock the phone just through fastboot? After installing an OTA update, the partitions should match the vbmeta partition, right? So could just relock the bootloader using fastboot flashing lock or would the phone not start then?
Click to expand...
Click to collapse
Your device will go in to boot img corrupt after that.......
PLEASE NOTE: This isnt working if you are on a custom rom! My Bootloader ist broken and locked and I have to figure out how to fix this ****.
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
7tyjupiter said:
Hello Pankspoo.
I reset my Nord 2 again with an A11 image.
Now I wanted to lock the bootloader again. I have implemented your instructions one to one.
After that, the Nord 2 will boot normally and start.
But in the developer options I can still unlock the bootloader. So the option is not greyed out. The OTA cannot be installed but does not lead to a bootloop either.
I used the appropriate boot.img recovery & vbmeta.img.
Do you have any idea?
Best regards
Click to expand...
Click to collapse
Check YASNAC app from play store if it's showing safety net check passed your locked.
While installation of OTA what's errors u r getting.
After locking OEM unlock not grates off actually now it's available to unlock again with switchable tab
Sorry for crossposting a lot today, but I am really stuck and it seems that this may be the tool I need. I am on A15, cannot lock bootloader and cannot update.
So, to be sure, for this to work I need the boot.img, recovery.img and vbmeta.img for A15 stock rom? If yes, where can I get those files?
I found the files! Thank you for this guide! It worked perfectly. I really thought my phone was completely bricked. Coming from a Pixel, the root/restore process on this thing is a complete nightmare!!
https://forum.xda-developers.com/attachments/boot-img.5460945/
this link says like this
Oops! We broke the matrix. Someone call Neo!You do not have permission to view this page or perform this action.
Ok. So I think if f-ed up big time! only message I get now is a big red "!" and: "the current image have been destroyed please flash te correct image....
HELP!
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
lachatol said:
Hi, I have a question. I have an unlocked bootloader, if I have my mobile service serviced and I have the original rom reinstalled there will the botloader be locked?
Click to expand...
Click to collapse
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
exis_tenz said:
Definitely, no doubt about that. But the rooting-proces after that is easy and well described here. Don't forget to FIRST take you OTA's, that makes things easier!
Click to expand...
Click to collapse
I want to lock the botloader, I don't want root anymore. I just need to be sure that if I service the phone for reinstallation to the original firmware, then the bootloader will be locked. Will be? thank you for answer
No worries, it'll be locked after a factory flash!
farhansaeeddnp3021 said:
wifi is not working. everything working after relock bootloader but wifi is not working
Click to expand...
Click to collapse
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
extranoob said:
This happened to me. It turns out that I had version A10 and flashed the A12stock_boot.img and when rebooting I had no wifi. I had no twrp either, since I had just flashed the stock recovery too.
So, I figured "did this actually updated to A12?" I checked the build version on the settings and no, it did not. So maybe thats the reason the system gets confused and some functions (I only noticed wifi) don't work properly.
Anyway, this is how I solved it:
1) restored my A10 version (flashing the file I got from a link on this post)
2) rebooting to A10, I did have wifi. I tried to update to A19 through Software Updater, but even though it did download the update.zip, it failed to update ("didn't pass the verification"). So, I:
3) flashed TWRP again, rebooted into it and installed the update.zip file (in data/ota_package/) that had just been downloaded by Software Updater.
4) Rebooted.
5) Fastboot flashing lock
6) Rebooted again. Congrats, its a brand new phone!!
P.S. Don't forget to lock the OEM unlocking option in Settings.
Click to expand...
Click to collapse
If u gets wifi issue just flash boot image of OOS version u r using via fastboot