Related
I just used casual to root and unlock my note 2.i have root and it booted up on twrp but I want to check if I am unlocked bootloader. Is there a way I can check? In my about phone my status says normal
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Unlocked Bootloader?
Jiggabitties said:
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Click to expand...
Click to collapse
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
If you just want to stop the update notification fteeze SDM 1.0
James Mac said:
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
Click to expand...
Click to collapse
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Jiggabitties said:
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Click to expand...
Click to collapse
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
The firmware update is done in ODIN and the ROM is done in TWRP.
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
Yes start by transferring the files to your SD card.
The firmware package from that thread is meant to be flashed via ODIN. If you are not comfortable in flashing firmware via ODIN then use this in it's place... https://www.dropbox.com/s/lz29kvrvzfttfpu/MJ9ModemParams.zip This is a TWRP flashable version of the firmware.
Place the MJ9 Deodex and the modemparam.zip I linked to above on your SD card. Flash the ROM file first, then the modemparam.zip. Then clear cache/ dalvik and reboot. That should be all you need to do. If when you boot you don't get service, then you will need to go ahead and flash the firmware vid ODIN. Some users have no issues with the flashable version that I linked above, some users do.
CLICK HERE FOR UPDATING TO B27 WITH
OR
WITHOUT ROOT
OR
COMING FROM ANY B20 FORM OR SHAPE
PLUS STOCK FLASHABLE ZIP FILES VIA TWRP
FOR ALL VARIANTS
I Apologize for creating a separate thread for all this but , was needed for all the info / files and guide for all of this.
ok, i see there's a few users with B20_boot or Rooted who want to get B27 OTA, well here is the little guide
- Download stock Recovery from here B20 stock recovery thanks @rczrider and this one ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Go to TWRP, WIPE DATA- CACHE-DALVIK .
- Now make sure SYSTEM was unchecked in mount and check mount system read-only ( THIS IS IMPORTANT DON'T SKIP THIS STEP)
- Flash this file ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Flash stock recovery you downloaded and reboot and you can now safely just Update to B27 via System Update app.
-------------------------------------------------------------------------------------------------------------------------
charlie.s said:
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
Click to expand...
Click to collapse
you are different story,
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to you SDCard.
- Enable OEM UNLOCKING in Developers Options
- reboot to stock recovery
- Apply via SDCard > Select your file and apply.
-------------------------------------------------------------------------------------------------------
If The first doesn't work out do this then :
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to your root of your INTERNAL STORAGE.
- Go to Software update
- you may or may not see the B27 Update CHOOSE that one there and apply .
--------------------------------------------------------------------------
with this method you do lose the unlocked bootloader, don't you?
I tried it on my friend's axon 7 the other day and he was able to get the update but the bootloader was locked again. For him it doesn't matter as he uses stock and no apps that require root.
clementinox said:
with this method you do lose the unlocked bootloader, don't you?
I tried it on my friend's axon 7 the other day and he was able to get the update but the bootloader was locked again. For him it doesn't matter as he uses stock and no apps that require root.
Click to expand...
Click to collapse
as far my understanding if you are already BOOTLOADER UNLOCK you still be in the same state (Unlock).
I must have used the "fastbook oem lock" by mistake through the whole process then.
So i only need recovery.img from B20 untouched provided by rczrider? or i need boot.img as well
DrakenFX said:
ok, i see there's a few users with B20_boot or Rooted who want to get B27 OTA, well here is the little guide
- Download stock Recovery from here B20 stock recovery thanks @rczrider and this one ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Go to TWRP, WIPE DATA- CACHE-DALVIK .
- Now make sure SYSTEM was unchecked in mount and check mount system read-only ( THIS IS IMPORTANT DON'T SKIP THIS STEP)
- Flash this file ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Flash stock recovery you downloaded and reboot and you can now safely just Update to B27 via System Update app.
-------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
genbu said:
So i only need recovery.img from B20 untouched provided by rczrider? or i need boot.img as well
Click to expand...
Click to collapse
i DON'T mention boot in my guide, just the recovery from him and my flashable zip file and you'll be set.
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
charlie.s said:
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
Click to expand...
Click to collapse
I'm guessing you went through the official ZTE bootloader unlock process, ie filled out the form on their site. When you do that, your device IMEI is placed on a list that will no longer receive regular OTA updates, and will only get B20_Boot.
Try putting the B27 OTA update ZIP on an microSD card, rename to update.zip, make sure that OEM Unlocking is enabled in your developer options, boot into stock recovery, and apply update from microSD card.
charlie.s said:
This procedure does not work for my officially unlocked Axon 7 (U). I am successful in reverting to stock v.20, but as soon as I ask for an update, i get the upgrade to v.20_boot.
Click to expand...
Click to collapse
you are different story,
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to you SDCard.
- Enable OEM UNLOCKING in Developers Options
- reboot to stock recovery
- Apply via SDCard > Select your file and apply.
-------------------------------------------------------------------------------------------------------
If The first doesn't work out do this then :
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to your root of your INTERNAL STORAGE.
- Go to Software update
- you may or may not see the B27 Update CHOOSE that one there and apply .
@DrakenFX - Have you updated to B27?
Just curious if I should update to B27 (from B20_Boot), or just wait a bit longer for something "bigger" before I update? Or even a flashable .zip file so I don't have to re-do everything (I'm getting lazy in my old age).
clementinox said:
I must have used the "fastbook oem lock" by mistake through the whole process then.
Click to expand...
Click to collapse
Must have. I am on B27 with bootloader still unlocked.
tele_jas said:
@DrakenFX - Have you updated to B27?
Just curious if I should update to B27 (from B20_Boot), or just wait a bit longer for something "bigger" before I update? Or even a flashable .zip file so I don't have to re-do everything (I'm getting lazy in my old age).
Click to expand...
Click to collapse
no i haven't , cuz i don't have the device right now...by trying to create a flashable update zip + keeping my data intact, i ended up with a brick, i'll be getting replacement in a few days.
DrakenFX said:
no i haven't , cuz i don't have the device right now...by trying to create a flashable update zip + keeping my data intact, i ended up with a brick, i'll be getting replacement in a few days.
Click to expand...
Click to collapse
Ouch!
DrakenFX said:
no i haven't , cuz i don't have the device right now...by trying to create a flashable update zip + keeping my data intact, i ended up with a brick, i'll be getting replacement in a few days.
Click to expand...
Click to collapse
That happened to me doing root on B20 - It took them a week of playing around before they sent me a replacement. Is it gone already? I am on full stock B27 now and if there is a way to pull the software off it for you just give me a step by step so you get what you want
I used method in the OP to go from bootloader unlocked B20 to bootloader unlocked B27. Thank you!!
DrakenFX said:
you are different story,
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to you SDCard.
- Enable OEM UNLOCKING in Developers Options
- reboot to stock recovery
- Apply via SDCard > Select your file and apply.
-------------------------------------------------------------------------------------------------------
If The first doesn't work out do this then :
- Download the update file from here update_P996A01_B20_to_B27.up (Thanks @TeutonJon78) ,
- Change the extension from .up to .zip ,
- Move it to your root of your INTERNAL STORAGE.
- Go to Software update
- you may or may not see the B27 Update CHOOSE that one there and apply .
Click to expand...
Click to collapse
I followed your first scenario and was indeed able to install B27. Thanks!
DrakenFX said:
ok, i see there's a few users with B20_boot or Rooted who want to get B27 OTA, well here is the little guide
- Download stock Recovery from here B20 stock recovery thanks @rczrider and this one ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Go to TWRP, WIPE DATA- CACHE-DALVIK .
- Now make sure SYSTEM was unchecked in mount and check mount system read-only ( THIS IS IMPORTANT DON'T SKIP THIS STEP)
- Flash this file ZTE_A2017U_StockB20U_by_DrakenFX.zip
- Flash stock recovery you downloaded and reboot and you can now safely just Update to B27 via System Update app.
-------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Did this, after AXON screen i am being asked for a password. I tried my backup password but it doesn't work. Was I suppose to turn off lock before attempting a revert to B20 or did I goof somewhere?
lifestar53 said:
Did this, after AXON screen i am being asked for a password. I tried my backup password but it doesn't work. Was I suppose to turn off lock before attempting a revert to B20 or did I goof somewhere?
Click to expand...
Click to collapse
You wipe data? I know is a pain reinstall things but that maybe you issue there.
What about steps to root B27 stock?
I am on B20 stock and haven't update to B27 yet due to waiting to see if Bootloader unlock and root are still possible after b20. Or is it like the old SGS5 days of having to go back to older version, root and then go forward with updates?
DrakenFX said:
You wipe data? I know is a pain reinstall things but that maybe you issue there.
Click to expand...
Click to collapse
I wiped data, dalvick and cache. I ended up letting the phone wipe itself. I'm in now. How do I return to root after updating to B27?
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!
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
t-shock said:
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
Click to expand...
Click to collapse
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Pretoriano80 said:
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Click to expand...
Click to collapse
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
t-shock said:
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
Click to expand...
Click to collapse
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
ante0 said:
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
Click to expand...
Click to collapse
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
t-shock said:
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
Click to expand...
Click to collapse
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
ante0 said:
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
Click to expand...
Click to collapse
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
t-shock said:
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
Click to expand...
Click to collapse
It shouldn't. And it works again with root. Apparently something broke in SEPolicy, but mankindtw fixed it in his pre-rooted ramdisk. Though, we can install Magisk "normally" now (as a package through recovery) so it shouldn't be a problem anyway SuperSU should install in a similar way too, if one would take the time to make it. I prefer Magisk though
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com