Hi,
my OPX is currently running:
Android V5.1.1
Oxygen v2.2.3
and I'm looking to update to MM, either Oxygen or CM.
When I try the offered OTA Oxygen update, Oxygen 3.1.3, it fails to update.
When I try to do it via recovery, using OnePlusXOxygen_14_OTA_018_all_201609291837_741146bcf28e4587.zip, it installs but then hangs on reboot.
My bootloader is unlocked:
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
I'm running the stock recovery, but when I try to update it, I get this message:
Code:
fastboot boot OPX_MM_recovery.img
downloading 'boot.img'...
OKAY [ 5.575s]
booting...
FAILED (remote: dtb not found)
finished. total time: 6.908s
I've tried other recoveries, Sultan-TWRP-onyx-3.0.2-3_2016-10-23.zip, twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img, twrp-3.0.2-0-onyx-20161102-155427.img, all with the same result.
Any help welcome please!
maxnutter said:
Hi,
my OPX is currently running:
Android V5.1.1
Oxygen v2.2.3
and I'm looking to update to MM, either Oxygen or CM.
When I try the offered OTA Oxygen update, Oxygen 3.1.3, it fails to update.
When I try to do it via recovery, using OnePlusXOxygen_14_OTA_018_all_201609291837_741146bcf28e4587.zip, it installs but then hangs on reboot.
My bootloader is unlocked:
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
I'm running the stock recovery, but when I try to update it, I get this message:
Code:
fastboot boot OPX_MM_recovery.img
downloading 'boot.img'...
OKAY [ 5.575s]
booting...
FAILED (remote: dtb not found)
finished. total time: 6.908s
I've tried other recoveries, Sultan-TWRP-onyx-3.0.2-3_2016-10-23.zip, twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img, twrp-3.0.2-0-onyx-20161102-155427.img, all with the same result.
Any help welcome please!
Click to expand...
Click to collapse
U cannot update to mm recovery while u r in lollipop... So the opx mm recovery will not boot... Try reflashing opx stock lollipop recovery and then try to flash the ota 3.1.3
cva_kabil said:
U cannot update to mm recovery while u r in lollipop... So the opx mm recovery will not boot... Try reflashing opx stock lollipop recovery and then try to flash the ota 3.1.3
Click to expand...
Click to collapse
I've tried that numerous times and it doesn't work.
Is the mm recovery needed after the device is updated to MM?
Yes this is obvious, mm recovery is needed when you updated on mm os.
You can try to install fresh os lollipop with stock recovery, if all the things goes right,
Then try to install mm version of os 3.1.3 through stock recovery.
yuv93 said:
Yes this is obvious, mm recovery is needed when you updated on mm os.
You can try to install fresh os lollipop with stock recovery, if all the things goes right,
Then try to install mm version of os 3.1.3 through stock recovery.
Click to expand...
Click to collapse
It's not that obvious, I thought maybe you needed mm recovery to install mm, seeing as I can't get mm to install through lollipop recovery!
I've got lollipop OS, lollipop recovery, and MM update won't boot after installation.
maxnutter said:
I've tried that numerous times and it doesn't work.
Is the mm recovery needed after the device is updated to MM?
Click to expand...
Click to collapse
As u said before wen u flash 3.1.3 it hangs on reboot right? So wen u reboot manually again u r back to 2.2.3? Is it so?
There may be a problem with ur 3.1.3 zip file redownload it from here https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip and flash it
If that fails Try the following methods but i am not sure, hope it works
Lollipop stock recovery https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Reflash this recovery in fastboot mode
Now try updating to marshmellow via recovery
If its not working then try this method
1.take a backup of all your apps contacts etc.,
2.try to revert back to 2.2.2 by flashing this - http://oxygenos.oneplus.net.s3.amaz...OTA_012_all_201607282126_44490f44e82446dc.zip do clear data and cache before flashing
3.Now go to recovery and flash 3.1.3 @maxnutter
Yes, that's right.
Flash 3.1.3, fails to boot.
Re flash 2.2.3, boots OK.
Sent from my ONE E1003 using Tapatalk
cva_kabil said:
As u said before wen u flash 3.1.3 it hangs on reboot right? So wen u reboot manually again u r back to 2.2.3? Is it so?
There may be a problem with ur 3.1.3 zip file redownload it from here https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip and flash it
If that fails Try the following methods but i am not sure, hope it works
Lollipop stock recovery https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Reflash this recovery in fastboot mode
Now try updating to marshmellow via recovery
If its not working then try this method
1.take a backup of all your apps contacts etc.,
2.try to revert back to 2.2.2 by flashing this - http://oxygenos.oneplus.net.s3.amaz...OTA_012_all_201607282126_44490f44e82446dc.zip do clear data and cache before flashing
3.Now go to recovery and flash 3.1.3 @maxnutter
Click to expand...
Click to collapse
The first two don't work. Might try the last one over the weekend. Thanks.
maxnutter said:
The first two don't work. Might try the last one over the weekend. Thanks.
Click to expand...
Click to collapse
if you're on stock lollipop recovery just flash the full ROM 3.1. 3 zip within recovery mode. that's it.
*wipe data,dalvik,cache are recommended (factory reset).
seacowx said:
if you're on stock lollipop recovery just flash the full ROM 3.1. 3 zip within recovery mode. that's it.
*wipe data,dalvik,cache are recommended (factory reset).
Click to expand...
Click to collapse
He said he already tried it so many times
cva_kabil said:
He said he already tried it so many times
Click to expand...
Click to collapse
then he might missed something back there. 99 out of 100 was succeeded. and i've done twice from 2.2.1 and 2.2.3 to 3.1.3, nothing troubles if you doing it with proper ways.
I'll give it another go on Monday.
FYI, I soft bricked it, then recovered back to stock Rome and recovery (2.2.1?). It happily downloaded the 2.2.3 OTA update, but won't do 3.1.3.
Sent from my ONE E1003 using Tapatalk
Does the bootloader need to be locked for OTA? It's unlocked atm, so maybe that is causing the problem?
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Does the bootloader need to be locked for OTA? It's unlocked atm, so maybe that is causing the problem?
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
the full ROM zip you wrote earlier that was exactly the same ver./number like mine. just make sure you ain't got the corrupted one.
no, bootloader needs to be unlocked all the time. or else you'll end up softbrick or even worse.
PS: I never did OTA update, I always flashed full ROM zip. it less errors and troubles. *clean flash more better
edit: you should try directly flash 3.1.3 from 2.2.1 (I only did factory reset) while 2.2.3 I did fully wipe system,data,etc.
seacowx said:
the full ROM zip you wrote earlier that was exactly the same ver./number like mine. the size should be 760.25 mb. (I checked with es file explorer pro). just to make sure you ain't got the corrupted one.
no, bootloader needs to be unlocked all the time. or else you'll end up softbrick or even worse.
PS: I never did OTA update, I always flashed full ROM zip. it less errors and troubles. *clean flash more better
edit: you should try directly flash 3.1.3 from 2.2.1 (I only did factory reset) while 2.2.3 I did fully wipe system,data,etc.
Click to expand...
Click to collapse
Is the bootloader unlocked out of the box?
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Is the bootloader unlocked out of the box?
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
of course not. we do :
Code:
fastboot oem unlock
to get unlocked.
seacowx said:
of course not. we do :
Code:
fastboot oem unlock
to get unlocked.
Click to expand...
Click to collapse
So OTA shouldn't need the bootloader to be unlocked.
Sent from my ONE E1003 using Tapatalk
maxnutter said:
So OTA shouldn't need the bootloader to be unlocked.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I don't know about that, never did OTA update since I'm always rooted and modified system. but flashing new ROM/custom ROM needed unlocked bootloader. and as far as I know you need stock recovery in order to install OTA update.
seacowx said:
I don't know about that, never did OTA update since I'm always rooted and modified system. but flashing new ROM/custom ROM needed unlocked bootloader. and as far as I know you need stock recovery in order to install OTA update.
Click to expand...
Click to collapse
Pretty sure I have stock, the one with the Chinese text on the first menu, right?
Just wondering if unlocking the bootloader prevents the OTA update working.
Sent from my ONE E1003 using Tapatalk
maxnutter said:
Pretty sure I have stock, the one with the Chinese text on the first menu, right?
Just wondering if unlocking the bootloader prevents the OTA update working.
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
yes, as far as i remember. you could choose 'english' either in start menu.
no, the only thing that prevent you gt OTA update is rooted or modified system partition. or else you're on different ROM, indeed.
well, good luck with yours then.
Related
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
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 guys,
Before you say again a topic on a non bricked One Plus X, I would like to let you know that I've checked and try almost all of the tutorial I've seen on xda and one plus forum.
I was on CM14.1 with this ROM : https://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-14-onyx-t3452150
Unfortunately, I made the 25-12-2016 update and it totally broke up the phone..
I download the OnePlus X OxygenOS 3.1.4 on the One Plus website. So I flash it on the stock recovery, it tells me "Install success" then I reboot and it stays on the bootlogo.
For information, I can't access the oem unlock menu if needed, but when I ask the oem device info it says unlocked. The phone is detected by the computer sometimes with unknown device and sometimes correctly with the qualcomm drivers..
I have a back up made from TWRP, I can access the device by the fastboot mode, it seems that all the operations written here worked but it doesn't install or even boot on TWRP..
Thanks for your help guys.
Are you using latest TWRP from website think version 3.0.3?
Exodusche said:
Are you using latest TWRP from website think version 3.0.3?
Click to expand...
Click to collapse
I'm not even using TWRP, since I can't boot on it.. But I tried to flash the twrp-3.0.2-2 from blue spark v41, after the installation via Flashboot, it doesn't boot up on the recovery..
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Exodusche said:
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Click to expand...
Click to collapse
Exactly, the phone is stuck on the one plus logo..
defqon_1 said:
Exactly, the phone is stuck on the one plus logo..
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Divyesh49 said:
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Click to expand...
Click to collapse
Didn't work. I tried to lock and then unlock to be sure but not is stay in false for tempered AND unlocked.
So I don't have any idea on how make android back on my phone.
I just have access to Fastboot mode. No recovery, nothing else..
EDIT : phone is not starting anymore. I try to charge it hoping it just a low battery problem..
You should send it to RMA
Trimis de pe al meu Redmi 3S folosind Tapatalk
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Help Pls
defqon_1 said:
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Click to expand...
Click to collapse
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Fix It!
Exodusche said:
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Click to expand...
Click to collapse
Done! finally i can reinstall stock rom and recovery with drivers by usb.
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Done
defqon_1 said:
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Click to expand...
Click to collapse
Don't worry i have restored my OPX 5 days ago. I used the method of this video: https://youtu.be/R4SVSovw4Jo and files from this thread: https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 , if it can help someone.
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
shreyasminocha said:
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
Click to expand...
Click to collapse
What was your last rom? Did u upgrade ur bootloader?
You probably looking at mega unbrick guide
cva_kabil said:
What was your last rom? Did u upgrade ur bootloader?
Click to expand...
Click to collapse
I was running stock OxygenOS(>3.0.0) ROM.
shreyasminocha said:
I was running stock OxygenOS(>3.0.0) ROM.
Click to expand...
Click to collapse
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
That said, should I follow a bricked guide before doing the above?
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
Also, is there any way I can downgrade my bootloader?
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Flash any 2.X.X ROM. One way is to fastboot flash old stock recovery and flash safest way I think. The other is to flash with twrp make sure after flashing the ROM to flash old twrp IMG after. Make sure you boot right back into twrp.
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Assuming you're on OOS3 with TWRP for new bootloader,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Flash twrp for old bootloader via fastboot, use this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img
Done
-Now u hv sucessfully downgraded ur bootloader,flash PA or any supported roms
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
TravaPL said:
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
Click to expand...
Click to collapse
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
iamsandiprathva said:
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
Click to expand...
Click to collapse
Did you managed to sort it out? How?
Mega unbricked guide?
During installtion of stock rom os 3.1.4 , status error 7 occurs and installation failed . I used the recovery TWRP 3.0.3 version . Please help me out. I checked the 'assert' in META folder but 'assert' is not present there.
What did you do just before that?
What is you bootloader version? OS on the phone?
Kéno40 said:
What did you do just before that?
What is you bootloader version? OS on the phone?
Click to expand...
Click to collapse
i installed the ressurection remix MM with bootloader 2.2.x ,then i upgrade the bootloader and tehn recovery image and then wipe every thing execpt internal storage(there will be rom) After that i flashed the stock rom , patching is done(progress bar goes blue) but at verification step it shows the error(status 7) . How 2 fix this please tell me ??
Mandeep Singh 07 said:
then i upgrade the bootloader and tehn recovery image
Click to expand...
Click to collapse
How, with BLupdater process?
Kéno40 said:
How, with BLupdater process?
Click to expand...
Click to collapse
BL upgrade normally, process used mention in xda
The normal way is to have the OOS 2 stock recovery, & to flash 3.1.4 and it updates itself.
So did you used that :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
And what this fastboot command gives you ? fastboot oem device-info
Kéno40 said:
The normal way is to have the OOS 2 stock recovery, & to flash 3.1.4 and it updates itself.
So did you used that :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
And what this fastboot command gives you ? fastboot oem device-info
Click to expand...
Click to collapse
Fastboot shows device unlocked true
If the bootloader is updated, you should be able to install OOS 3 stock bootloader or a TWRP for this version to install all the roms with the new BL.
But, without knowing at which step something went wrong on your device, it's a kind of difficult to help now..
I think I would redo the BLupdater procedure, then flash good TWRP then OOS 3.1.4