DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
AWFRONT said:
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
Click to expand...
Click to collapse
I was going to do the same but I got tired of the ads and bloatware, so I needed root to install AdAway and Titanium Backup to clean the preinstalled programs
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
doctahjeph said:
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
Click to expand...
Click to collapse
That is what they recommend on the other site. I do not know why.
once you've done this, does it block OTA updates from Asus?
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
I think so.
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
Once you unlock the bootloader the OTAs are blocked, even if you aren't rooted. It is okay you can still manually install the firmware easily.
mushufasas said:
[
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Click to expand...
Click to collapse
I updated it & still have root
I have rooted again on latest firmware and used Supersu 2.79. Works as advertised so far.
Gone Looking
mushufasas said:
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Click to expand...
Click to collapse
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
av8or091 said:
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
Click to expand...
Click to collapse
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
av8or091 said:
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
Click to expand...
Click to collapse
I do not know why, but I had to reinstall the rom on my phone, used the same files for root and it worked with no problem.
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Suggested Edit
mushufasas said:
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Click to expand...
Click to collapse
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
signature verification failed
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
krcma.cz said:
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
Click to expand...
Click to collapse
i flash downgrade fw WW-14.1010.1703.42
and flashing of supersu still not working
any idea ?
av8or091 said:
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
Click to expand...
Click to collapse
seems like all went well for me . . . unlocked / twrp / superuser / even the upgraded kernel & software upgrade ........ but the system hangs on the start screen ... but upon restart - the zenphon still goes into bootloader & twrp if i want to.
I don't suppose anyone made a twrp backup of a fresh / no added programs? Even one w/ bloat removed?
anybody able to show a bit of love?
thx in advance
Bummer . . . . no one's made a twrp backup yet? That's one of the 1st things i do - just in case.
.
Is it possible to update to new version of SuperSU then 2.80 ?
I try to update SuperSU with TWRP to version 2.82-201705271822.zip but installation failed....
Related
Hi people!
I very much like my new Oppo R5s (from the european store) and to make it even better, I want to root it.
I have read a few posts in this forum and people seem to be able to root it with TWRP (twrp-2.8.7.0-r7f.img), SuperSU (Beta v2.49) and ColorOS root method (Root_ColorOS_by_tantrums_v2.zip).
Here is what I have done:
Boot into fastboot mode with Volume Up + Power On [works!]
Connect via USB and do "fastboot flash recovery twrp-2.8.7.0-r7f.img" [works!]
Reboot into TWRP with Volume Down + Power On and enable write mode [works!]
IMPORTANT: In TWRP Mount menu mount "System" and unmount "Data" and "Cache" [works!]
Install "Root_ColorOS_by_tantrums_v2.zip" which I copied to sdcard earlier [works!]
Install "BETA-SuperSU-v2.49.zip" which I copied to sdcard earlier [works!]
Wipe cache and dalvik cache and reboot [works!]
Launch SuperSU after reboot and check that it works [works!]
Thanks to Lum_UK who helped getting me on the right track!
Flash this instead of the official SuperSU installer
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Thanks Lum, but installing your zip with TWRP and rebooting made no difference whatsoever...
What else can I try?
Try this one: http://lum.uk/n3/files/ForceRoot.apk
I haven't tried it with TWRP though, only stock recovery.
Install it like any other sideloaded app, run it, click the root button, it should reboot into recovery and root.
Lum_UK said:
Try this one: [..]/ForceRoot.apk
Click to expand...
Click to collapse
Thanks Lum for trying to help me . But I'm not sure if I can trust ForceRoot. Once I start it, it wants to install another App which requires every permission on the planet... That makes me nervous... Are there any other alternatives?
Did you mean you flashed Root_ColorOS_by_tantrums_v2.zip with the stock recovery instead of TWRP? I think its not possible?
The tantrums one is supposed to work for every version of coloros, though I have not personally tested it on the R5, only on the N3.
ForceRoot is what I used on my partner's unmodified R5S. I'm not aware of any other alternatives.
Yes! I managed to root my R5s now. I just did not know that I have to mount System in TWRP and unmount Data and Cache.
Then the Root_ColorOS_by_tantrums_v2.zip install works!
Hi guys,
I just got my Oppo R5s, and I was wondering if I can fit a custom ROM, something based on a stock, or very smooth version of Android 5.x
If this exist, what should I do? (I need to root first) I am a noob regarding Android.
No custom roms yet unfortunately. Best bet is to try to de-crapify the phone OS a bit, root it, uninstall bloatware, install a stock-like launcher e.g. Nova Launcher. If you're feeling brave maybe mess around with Xposed and GravityBox
The Oppo camera app is way better than stock Android anyway.
Thank you for sharing!
I have read here http://www.cyanogenmod.org/blog/expanding-the-cm-device-family that team is planning to support r5plus... may they mean r5s instead?
I can't even get into Fastboot.
When I hold power and volume up, I just get a quick vibration and no screen activity (doesn't turn on - nothing).
rhd-android said:
I can't even get into Fastboot.
When I hold power and volume up, I just get a quick vibration and no screen activity (doesn't turn on - nothing).
Click to expand...
Click to collapse
Yes that is how it works . Fastboot mode shows a black screen and is only reacting to input from a USB data cable.
You are supposed to connect a USB cable and use the fastboot.exe from Android SDK to flash twrp.
I tried this but it failed "remote size too large".
Try Catch said:
Boot into fastboot mode with Volume Up + Power On [works!]
Connect via USB and do "fastboot flash recovery twrp-2.8.7.0-r7f.img" [works!]
Reboot into TWRP with Volume Down + Power On and enable write mode [works!]
IMPORTANT: In TWRP Mount menu mount "System" and unmount "Data" and "Cache" [works!]
Install "Root_ColorOS_by_tantrums_v2.zip" which I copied to sdcard earlier [works!]
Install "BETA-SuperSU-v2.49.zip" which I copied to sdcard earlier [works!]
Wipe cache and dalvik cache and reboot [works!]
Launch SuperSU after reboot and check that it works [works!]
Click to expand...
Click to collapse
After having my R5s a couple of month, I was ready to root the device following the post.
No 1, works
No 2, seemes to be working too: fastboot flash recovery twrp-2.8.7.0-r7f.img
target reported max download size of 268435456 bytes
sending 'recovery' (13200 KB)...
OKAY [ 0.444s]
writing 'recovery'...
OKAY [ 0.277s]
finished. total time: 0.727s
No 3, definitely does not work. Device hangs up showing just Oppo on the screen. No TWPR Screen :crying:
Any suggestions, what went wrong?
Pferdi said:
After having my R5s a couple of month, I was ready to root the device following the post.
No 1, works
No 2, seemes to be working too: fastboot flash recovery twrp-2.8.7.0-r7f.img
target reported max download size of 268435456 bytes
sending 'recovery' (13200 KB)...
OKAY [ 0.444s]
writing 'recovery'...
OKAY [ 0.277s]
finished. total time: 0.727s
No 3, definitely does not work. Device hangs up showing just Oppo on the screen. No TWPR Screen :crying:
Any suggestions, what went wrong?
Click to expand...
Click to collapse
I had that same problem, i also had a problem where the screen went black when trying to boot into TWRP (crash). I can't remember exactly how i solved it but i know i was messing about and sudenly TWRP was booting. Unfortunatly, i'm running an alpha build now so i can't help you trace back the issue...
Some of the following things may help you:
- Have a look in "developer setting" and see if there is a lock on recovery.
- Download the R5-TWRP and try to flash that.
- After flashing R5, try the R7 again.
- Boot the system and use ADB to reboot in recovery.
- Use Kingroot to root the device and then use flashify to write TWRP.
Don't give up, your problem is solvable
I successfully updated recovery to TWRP some months ago. What about updating to Project Spectrum? Is it possible with TWRP? Or do I need to replace the recovery to the one suggested by OPPO for updating to Project Spectrum?
Thanks in advance for any information.
faldo said:
I had that same problem, i also had a problem where the screen went black when trying to boot into TWRP (crash). I can't remember exactly how i solved it but i know i was messing about and sudenly TWRP was booting. Unfortunatly, i'm running an alpha build now so i can't help you trace back the issue...
Some of the following things may help you:
- Have a look in "developer setting" and see if there is a lock on recovery.
- Download the R5-TWRP and try to flash that.
- After flashing R5, try the R7 again.
- Boot the system and use ADB to reboot in recovery.
- Use Kingroot to root the device and then use flashify to write TWRP.
Don't give up, your problem is solvable
Click to expand...
Click to collapse
What alpha build do you use now ? on a R5s ?
I would like to install TWRP on a R5s and I have the same problem so if you have an idea....
I know it's not much help for people wanting TWRP. But CyanogenMod 13 recovery is working on the R5S. Don't use the CM14 recovery though!
Lum_UK said:
I know it's not much help for people wanting TWRP. But CyanogenMod 13 recovery is working on the R5S. Don't use the CM14 recovery though!
Click to expand...
Click to collapse
yes but you can't install lineageos with it so now it is not very usefull as cyanogenmod is over
I was able to install CM13 with it, and apparently it also works for CM14.
Are there actual builds for LineageOS for R5 yet? I've not found any.
I followed the directions from this post, but every time I try to install the upgrade, it fails because the partition size is not large enough. I had to flash recovery_MT2L03_mmcblk0p19.img because when I tried to use B321 it also gives me an error that says "failed: remote size too large".
How can I fix this? Thank you!
Also, food for thought, when I look at available internal storage within the stock ROM, it says only ~6gb are free out of 8, and I know this phone is a 16gb device. I don't know if that's related, but it's rather odd.
Are you following the B322 Huawei upgrade instructions PDF? What does it say the firmware version needs to be initially? Are you paying attention to that ?
divineBliss said:
Are you following the B322 Huawei upgrade instructions PDF? What does it say the firmware version needs to be initially? Are you paying attention to that ?
Click to expand...
Click to collapse
Yes I've also read those instructions. I successfully got to this screen once, and at about 25% completion, it said the process failed.
Right now I have no installed OS because it fails for all of them, just FYI.
Update: This is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Is your HAM2 a Consumer Cellular by chance? Have you tried starting over by putting B148 recovery and firmware on the phone? That's what I would do.
divineBliss said:
Is your HAM2 a Consumer Cellular by chance? Have you tried starting over by putting B148 recovery and firmware on the phone? That's what I would do.
Click to expand...
Click to collapse
Completely unlocked L03, brand new. I've tried installing the old OS from the JB downgrade pack, still fails.
You did not answer my questions ....... and what version ROM/recovery is on the phone now?
divineBliss said:
You did not answer my questions ....... and what version ROM/recovery is on the phone now?
Click to expand...
Click to collapse
I figured that was a proper response to both questions... Apologies. It is not CC, and yes I have done both of those things. There is no installed ROM or OS. Recovery is variable, I've tried stock and TWRP 2.8.7.
1. What model # is this phone?
2. What versions of ROMs, recoveries have you had on it?
3. Is the bootloader unlocked? You're going to need in unlocked to put custom ROMs on it.
4. I would try getting it back to stock B148 ROM and recovery if its a non-CC MT2L03. You might have to hunt around the HAM2 forum for threads on how to recover from bricked phones if you're having problems getting to stock B148 or some other stock version that B322 instructions say can be a starting point to upgrade to B322.
divineBliss said:
1. What model # is this phone?
2. What versions of ROMs, recoveries have you had on it?
3. Is the bootloader unlocked? You're going to need in unlocked to put custom ROMs on it.
4. I would try getting it back to stock B148 ROM and recovery if its a non-CC MT2L03. You might have to hunt around the HAM2 forum for threads on how to recover from bricked phones if you're having problems getting to stock B148 or some other stock version that B322 instructions say can be a starting point to upgrade to B322.
Click to expand...
Click to collapse
1. Model is MT2-L03...
2. I have not had any ROMs, just the stock JB out of the box. Stock recovery and TWRP 2.8.7
3. Bootloader is fully and properly unlocked.
4. I said already, I cannot flash ANY ROM, stock or otherwise, because every time it tells me the partition is not large enough...
Again, this is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Correction: I was able to flash the stock recovery and then the stock B148 ROM. So the only problem I have now is the system partition is only ~1gb in size, not large enough to accommodate for the ~1.6gb for the B322 or B321 update. I'm trying again now tho.
Tried to flash B321, same error. This is what I see.
Just tagging some people more knowledgeable than I who can probably help. @xordos @SHM
ScoobSTi said:
Just tagging some people more knowledgeable than I who can probably help. @xordos @SHM
Click to expand...
Click to collapse
Any and all help is appreciated, thank you! Btw, the storage size issue has self-remedied since I reflashed the B148. It now says 12.5gb free of 16gb. Apparently the ROM they shipped me with had some issues...
Also: I have tried the repair and resize functions from TWRP 2.8.7 on my system partition to no avail. It remains ~1gb.
Why are you trying to install B321 vs B322?
Go back to B148 (ROM + recovery), then try using the Huawei provided instructions to install, B322 and post what happens.
I went from B148 out of box to B322 to custom recovery / custom ROMs.
divineBliss said:
Why are you trying to install B321 vs B322?
Go back to B148 (ROM + recovery), then try using the Huawei provided instructions to install, B322 and post what happens.
I went from B148 out of box to B322 to custom recovery / custom ROMs.
Click to expand...
Click to collapse
Because that's what Nigel's directions say. Both the B321/B322 recovery and ROM fail independently. So regardless which one I try, I still have the partition problem.
chill8888 said:
1. Model is MT2-L03...
2. I have not had any ROMs, just the stock JB out of the box. Stock recovery and TWRP 2.8.7
3. Bootloader is fully and properly unlocked.
4. I said already, I cannot flash ANY ROM, stock or otherwise, because every time it tells me the partition is not large enough...
Again, this is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Click to expand...
Click to collapse
format internal Sd and try again.
Moody66 said:
format internal Sd and try again.
Click to expand...
Click to collapse
Reformatted to ext4, partition size is still the same. See attached photo.
Tried to do an update from within the B148 ROM update app, same error as the first image I uploaded.
chill8888 said:
Reformatted to ext4, partition size is still the same. See attached photo.
Tried to do an update from within the B148 ROM update app, same error as the first image I uploaded.
Click to expand...
Click to collapse
Try to do the 309 update first. That should clear up the partitions for L to update.
Moody66 said:
Try to do the 309 update first. That should clear up the partitions for L to update.
Click to expand...
Click to collapse
I may need some help tracking that down. I got the MT2L03_B309_withRoot_Orig.zip from Nigel's Gdrive, but it contains the system and boot.img files, not the update.app file...
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, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Thank you for the quick reply.
NightCrayon said:
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Click to expand...
Click to collapse
Hi, I have followed all the above instructions, but i am still getting the same error. Since there is no OS installed, I have performed the following steps:
1 . Downloaded the twrp-3.0.M6-0-mt2.img and renamed it to TWRP.
2 . Rebooted the phone into bootloader mode and flashed the phone with the twrp-3.0.M6-0-mt2.img (twrp).
3. Rebooted the phone into recovery mode.
4. Wiped the phone to factory settings and also wiped the /system, data, cache, except internal storage.
5. Used the adb push command to transfer the rom, extra (su arm), and gapps to the external memory.
6. Upon flashing the rom I get the error below:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
Please let me know if I am missing anything. Thanks again
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
techswy said:
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
Click to expand...
Click to collapse
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
NightCrayon said:
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
Click to expand...
Click to collapse
Thank you so much for the link. I will definitely let you know if I run into more issues with the upgrade. Thanks again.
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
ScoobSTi said:
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
Click to expand...
Click to collapse
Thanks for the reply. I really appreciate the response. :good:
Thank you xda forum, NightCrayon and ScoobSTi for helping me fix my phone. Thanks again.
You must be from Wind Mobile from Canada
techswy said:
Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
Click to expand...
Click to collapse
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
vivek76 said:
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Click to expand...
Click to collapse
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
sevenday4 said:
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
Click to expand...
Click to collapse
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
I was finally able to install Lineage lineage-14.1 awhile back. I figured out where to get the Rom and modify it in order to flash it on my mtl02. But, it's been acting kinda kinky so for grins I'm going to try Candy that divhandyman suggested. ?
divhandyman said:
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
Click to expand...
Click to collapse
I have just flashed Candy ? about two weeks ago. Had some issues with substratum and magisk. I guess it was because you need a certain version of TWRP. Then a few days ago I with the LOD (loop of death). Lineage had the same issue
Code:
PS E:\root\GREE> .\fastboot flash recovery twrp-recovery-v1.2.img
target reported max download size of 536870912 bytes
sending 'recovery' (48973 KB)...
OKAY [ 1.089s]
writing 'recovery'...
FAILED (remote: please install correct signature)
finished. total time: 1.114s
I get this error when trying to flash TWRP on my phone, IDK what the signature means here .. ?
The phone defends you from uploading the wrong file. Are you sure you are flashing the right file for your phone model? Did you compare the checksum after downloading the file with the checksum posted on the download page?
More info:
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
ze7zez said:
The phone defends you from uploading the wrong file. Are you sure you are flashing the right file for your phone model? Did you compare the checksum after downloading the file with the checksum posted on the download page?
More info:
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
Click to expand...
Click to collapse
Yes, I followed a Chinese forum that says they have flashed the same twrp img for this specific phone (GREE G0215D) but it's preventing me from flashing it on the phone is there any way around it?
Phone specs
Look first for a way to unlock the booloader based on the thread:
Install Google Play Services on Chinese Phone (Gree G0215D)
Hi there, I received a Gree G2015D Phone as a gift from a Chinese friend. (Here is a Russian Site showing the phone) It comes with a 6.0.1 based Rom but without google play services installed. There are a lot of guides how this can be done for...
forum.xda-developers.com
I can't advise anything else. Good luck.
ze7zez said:
Look first for a way to unlock the booloader based on the thread:
Install Google Play Services on Chinese Phone (Gree G0215D)
Hi there, I received a Gree G2015D Phone as a gift from a Chinese friend. (Here is a Russian Site showing the phone) It comes with a 6.0.1 based Rom but without google play services installed. There are a lot of guides how this can be done for...
forum.xda-developers.com
I can't advise anything else. Good luck.
Click to expand...
Click to collapse
Thank you for answering but I already unlocked the bootloader, do you think the error is from the twrp.img ?
Mark Wasfy said:
Thank you for answering but I already unlocked the bootloader, do you think the error is from the twrp.img ?
Click to expand...
Click to collapse
The way I understand it, the message comes from fastboot and is a response from the phone's bootloader to an attempt to upload data to the protected recovery partition.