Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
grneyez said:
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
followed that guide
Had this working for months and needed to wipe so I did a factory reset and all my phone does is boot to twrp
I tried this process again and all goes good or so it seems but just boots to twrp
I tried a restore from my backup from twrp and get all the way done and it fails on "unable to wipe Fsg."
Above there is a bunch of red failed:
Could not mount /data and unable to find crypto foooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount'/cache' (invalid argument)
failed to mount'/system'(invalid argument)
Failed to mount storage
failed to mount'/data'(invalid argument)
failed to mount'/cache'(invalid argument)
failed to mount'/data/media/twrp'(invalid argument)
unable to wipe fsg.
any ideas? right now just a brick here. i have tried flashing roms from twrp and still just boot to twrp
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
D13H4RD2L1V3 said:
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
Click to expand...
Click to collapse
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
royalflush5 said:
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
Click to expand...
Click to collapse
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
D13H4RD2L1V3 said:
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
Click to expand...
Click to collapse
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
royalflush5 said:
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
Click to expand...
Click to collapse
Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS.
There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
raymccoy said:
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
Click to expand...
Click to collapse
thanks for the Rescue same trick work for me though as i was been stuck on TWRP after flashing stock firmware via fastboot , so i manage to flash irfan v4 stock rom and booted to factory image to get it resolved , But now i want to move to complete stock without twrp as i think Oreo update is near by but i get the same issue again, Just wanna ask can u help me out with the process to go back to stock Rom
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
that worked for me also, but it's not a fix, its a workaround. is there an actual fix for this? I've tried the Verity_FE_patcher but that didn't work also.
Related
I accidentally flashed TWRP to the boot instead of recovery. Whenever I turn on the phone it goes straight to TWRP. As it stands the phone is unsuable! AS far I understand it the way to fix this is to flash the phone's original boot.img to the boot. Is this correct? If so my phone is MT2L03 with the 5.1 update. Does anynone know of any link or could anyone PLEASE share their stock boot.img with me. I really need help!
Thank You.
Boot image is part of OS. If you want to install CM12, while you are in twrp, just transfer the cm12 rom and gapp from pc to your sdcard, then flash both. You get complete cm12 with its boot image.
But if you want stock boot image back, you can just flash the stock firmware using the 3 button boot. It is available in the "official stock firmware" section in the INDEX page: http://forum.xda-developers.com/showthread.php?t=3149530
If you have difficulties doing that, let us know. I maybe can find it somewhere, but to be honest, I don't use stock anymore once CM is out.
Thanks. CM12 flash problem
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
fcbfan2k said:
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
Click to expand...
Click to collapse
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Moody66 said:
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Click to expand...
Click to collapse
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Also twrp, have you install the twrp listed in that same page? other twrp version doesn't work.
Edit, saw you mentioned already that install twrp error using app. So try install the correct twrp in bootloader.
fcbfan2k said:
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Click to expand...
Click to collapse
If you flashed b321 boot image you are not on b322 boot... And the correct twrp is found in the same OP....
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!
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!
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
ClockUpEx said:
So I accidentally flashed a wrong boot.img while on my current ROM (AOSiP 8.1) The wrong flash caused my system to be somewhat destroyed (Can't mount and others). The only hope I had was to do the FastBoot method which somehow worked but returned me to MIUI 9.
I did all the rooting and recovery process again and decided to flash the AOSiP ROM again with the proper procedures but as soon as I install after wiping I get the error something like "twfunc failed to flash repacked image". I thought it was just a corrupt download but after downloading twice and using another ROM it was still the same. Can somebody please help me? It's a hassle going through the FastBoot flash method again and it might get worse if not yet fixed ASAP.
Click to expand...
Click to collapse
Did you try using redwolf recovery? Also do this. Go to en.miui.com and dl the latest miui zip. Using redwolf try to flash it. If you are able to do it then possibly it's something with stock twrp. If not then you might need to fastboot flash miui again. The last option would be to use edl mode.
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
ClockUpEx said:
I tried FastBoot method flashing the latest MIUI 9 build. Worked out fine but after Rooting again and adding Recovery, flashing ROMs give me Error7 most of the time. What I did is I accidentally clicked the Clear All on the MiFlash and resulted to my problem being fixed while losing all files in my internal. Noooooo!
Click to expand...
Click to collapse
Soo? Is it fixed now? Is that what you mean?