Related
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
kokorolove said:
Hi, everyone, I just got my z3 tablet and I am in love with it except i don't like the interface. So i decide to root my tablet without unlocking the bolted and I did made it and i did install TWRP. I have a question, since I have TWRP is it possible for me to install cm 12 rom or I need to have a unlock boot loader in order to install it?
Sorry for my bad english and thank you for answering my questions.
Click to expand...
Click to collapse
You need to unlock to flash a custom kernel which would be needed by the cm12 to run. So first.
1.Backup drm keys
2.Unlock BL
3. Flash CM kernel via fastboot
4. Flash CM Rom via recovery.
Sent from my SGP621 using XDA Free mobile app
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Cyberratchet said:
I just bought a Z3 tablet compact, which should be here at the end of next week. I haven’t found a tutorial which includes all steps to get from the standard rom to CM12. Did I miss any steps or does the following steps include everything?
Root tablet on the original Sony rom
Backup TA partition (I guess that's where the DRM keys are?)
Unlock bootloader
Flash a recovery (any recommendations?) I found this tutorial, but I only need one recovery and I don’t want to flash that zip every time I install a new rom.
Flash CM12. Are there any kernels beside that one included in the CM12 zips?
Click to expand...
Click to collapse
I guess you should just flash the kernel via fastboot after unlocking the bootloader, that would eliminate the need to flash a recovery. It's hitting 2 birds and one stone and besides CM uses a different kernel than stock so later you would really need to flash kernel.
Sent from my SGP621 using XDA Free mobile app
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
I'm also curious about this.
Right now, I'm trying to download the Flashtool program from Sony, but apparently, you need to "register" for it. Where did you guys download your Flashtool from?
Cyberratchet said:
Thanks for your reply. The whole flashing procedure is a lot more complicated than on my S3, so I have a follow-up question.
Should I just backup the TA partition, unlock the tablet, flash this kernel which should give me root and TWRP and then flash another recovery and CM12?
I found this recovery which is only semi-permanent, because you have to flash it before you upgrade/install a new CM12 version. It’s not big deal tbh, but is there a permanent recovery, which I only have to install once.
Click to expand...
Click to collapse
Correct, make sure the kernel is compatible with CM
Sent from my SGP621 using XDA Free mobile app
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Cyberratchet said:
The whole procedure is really frustrating, maybe someone can help me here.
I did a backup of the TA partition and unlocked the bootloader. I tried flashing the boot.img from the cm.zip, but I have no idea how to flash the rom via the cm-recovery.
Flashing the advanced kernel to get TWRP wasn’t successful as well. I tried the fastboot mode of the Flashtool and flashed the kernel, but nothing changed.
Can someone post a brief guide with the next steps to get CM12 running (with cmd commands pls)?
EDIT: I just tried to use “adb sideload” in the CM recover, but “adb devices” doesn’t show the tablet .
EDIT2: EDIT: Seems like I got it to work after all. The DualRecover Installer worked, even without SuperSU installed.
Click to expand...
Click to collapse
I ran into the same problem usin the cm12 nightlies from 27th march 2015:
Sideloading would not work because the tablet is not recognized by the computer. I tried with Windows 7 and gentoo Linux.
Installing from the sd-card in recovery mode was also not possible due to a error of missing "/misc".
I solved the problem by manually choosing the driver in Windows 7. I booted the tablet into recovery. Choose update using adb as detailed in this post:
http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534
Then I found the device in the windows device manager. Here I manually choose the adb driver that I installed earlier from the flashtool package. After that the device was correctly recognized by Windows and I could Sideloade the cm12 image.
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
@KaiserSnorezay
XZDR is still not compatible with MM, that's why you got a bootloop...
Also you can't install the "regular" TWRP with twrp manager on a LB as there is no recovery partition... it won't work and probably will mess your phone in the process.
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770
Just did it exactly this way yesterday on my friends d6503 (minus the d6502 patch obviously) had 0 troubles MM, root and recovery working perfectly.
Thanks, will try this today. Is wiping data required or can i get by by just flashing the older one?
ptmaniac said:
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
Click to expand...
Click to collapse
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
KaiserSnorezay said:
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
Click to expand...
Click to collapse
Weird, after you have your phone rooted it should be simple to install xzdr... just enable usb debugging in the phone and make sure you have the adb drivers correctly installed in your pc.
Download the latest xzdr from nut's thread ( http://forum.xda-developers.com/showthread.php?t=2261606 ) unzip it and run install.bat . After a successful install the phone should reboot to twrp automatically and it's done.
Okay, I fixed it..using Flashfire! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
KaiserSnorezay said:
Okay, I fixed it..using ! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
Click to expand...
Click to collapse
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
dodge911 said:
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
Click to expand...
Click to collapse
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
KaiserSnorezay said:
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
Click to expand...
Click to collapse
okay. you mean flashing any old firmware ( which i did and still in bootloop ) & root it. Then installing recovery for the same firmware ?
with "recovery" will i be able to get back my whole data ?
KaiserSnorezay said:
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
Click to expand...
Click to collapse
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
DedSec_35 said:
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
Click to expand...
Click to collapse
Sorry, I ditched my Z2 for a Oneplus 3 in August 2016. Learnt my lesson, only going to use phones with easily unlockable bootloaders.
Hey I have a
SGP321 with:
Android version : 5.1.1 / kernel version : 3.4.0-perf-gbccb33a / Build number : 10.7.A.0.228
I cannot comprehend how to root it.
I managed to unlock bootloader, using FlashTool, and a code from Sony's developer page.
I want to install this rom:
Resurrection Remix M for Xperia Tablet Z (Wi-Fi/LTE)
It seems like rooting is failing due to the Android 5.1.1 .. Then where can I get the 4.4.2 firmware ?
I'm from Norway, and the device isn't locked to any carrier.
Deimos87 said:
Hey I have a
SGP321 with:
Android version : 5.1.1 / kernel version : 3.4.0-perf-gbccb33a / Build number : 10.7.A.0.228
I cannot comprehend how to root it.
I managed to unlock bootloader, using FlashTool, and a code from Sony's developer page.
I want to install this rom:
Resurrection Remix M for Xperia Tablet Z (Wi-Fi/LTE)
It seems like rooting is failing due to the Android 5.1.1 .. Then where can I get the 4.4.2 firmware ?
I'm from Norway, and the device isn't locked to any carrier.
Click to expand...
Click to collapse
To flash RR 5.7.4 you need to have a Recovery.
To root:
Download kingroot apk from below link and install it. Follow the steps in that app and your device will be rooted.
https://king-root.net/wp-content/KingrootV4.9.6.apk
To flash recovery:
Select: TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip from the link below. And follow the Read Me.txt to install recovery.
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26
TAKE A BACKUP OF YOUR DATA BEFORE YOU START TO DO ALL THESE.
I JUST HELP AND TAKE NO RESPONSIBILITY TO WHATEVER HAPPENS TO YOUR DEVICE.
All the best
@Deimos87
@Alok Bajaj
It's actually much much easier/faster to flash RR boot.img straghtforward (Flashtool -> Fastboot -> Select Kernel to Flash) and install .zip afterwards via built in recovery.
Cause NUT's recovery is kinda dated now, and is not meant to install custom ROMs, though it can do it on pollux, but very often is unable on pollux_windy.
I'm going to download and try.
I managed to brick the tablet into a continuous boot and reboot. But I am lucky enough to get it into flashmode...
I tried flashing some other original ROM, but it was for Vodafone in UK. I tried to recover it with the official Sony program (Essentials?), but it said that my device was rooted. But I guess its because I have unlocked the bootloader. I have also requested to be able to use Sony Emma/Embla or something for flashing.
I was trying to get to Android 4.4.2 or 4.4.4 to be able to root. Its so much software out there. It's like getting into a new territory of learning.
I managed to do something....
What I have done before was to open the bootlocker. If it did matter... Using newest flashtool.
I got an Spanish FTF Rom file from the Flashtool Site, SGP321_10.1.1.A.1.307_Customized_ES.ftf. Flashed it somehow using a elderly flashtool (0.9.18.6), could probably work on a newer one but God's will and such.
I then downloaded DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit. And installed SuperSU or something. Settings: USB Debug and allow unsigned/foreign APK's.
There is a gap in my memory here (maybe I started TabZ-lockeddualrecovery2.8.26-RELEASE.combined).
My tablet booted into a recovery mode after doing something on my PC with the tablet powered in normal system (USB debug), and I now have managed to select my desired, ROM, and Gapps (No clue what it is yet) and a kernel that they recommended.
Now its currently Optimizing my apps (Preinstalled I guess). 106 apps.
Update1:
Popup "Unfortunately, Setup Wizard has stopped". I did see some google stuff also do the same
I am trying to factory reset with wipe.
There was now a different recovery menu.. Hmm. I had to disconnect the battery to get out of the menu. ( I have opened the tablet beforehand).
Maybe its that GAPS stuff that didn't install...
If this fails again I will try and install gaps again inside recovery.
Deimos87 said:
Popup "Unfortunately, Setup Wizard has stopped". I did see some google stuff also do the same
I am trying to factory reset with wipe.
Click to expand...
Click to collapse
you need to install gaps right after ROM install, or you'll will have setup wizard error.
I managed to install Ressurection M.
It was very painfull, I had many tries over the course of 3 days.
I flashed a older spanish 4.4.2 (i think) firmware.
Then I rootet it using kingroot I think.
Then I installed TWRP.
Since the Sony tablet doesn't boot into recovery with keypresses I had to boot into recovery in software.
I then wiped about everything, I formated System partition also. Because If I do not the old applications will follow into the new ROM.
I then flashed Resurection M, and GAPPS on the same time. I do not remember If I also flashed the Kernel also now or after.
I think I concluded with that the Kernel had to be flashed at the same time.
If I did something wrong I just flashed the old spanish firmware over again and redo. I actually liked the old firmware due to it was much nicer user interface. The new one on Android 6 is kind of hard to manage. But I get more screenspace now.
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've on my Mi A3 installed last month 11.0.7.0. And I have Root and TWRP as well.
Now, I would like to update to the V11.0.11.0 just released without losing any data (as a normal update more or less), but I can't find the download for the Full OTA zip or the Fastboot rom.
I'll then try to follow this guide to update: https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Unfortunately, I couldn't find any guide to do the update keeping TWRP but, hopefully, it won't erase all the data
If you have the OTA zip or the Fastboot Rom, could you point me to them?
Plus, if someone has some suggestion to do this kind of update, it's very welcome
In years of updating custom rooms, I never felt like today that, with an official rom, I would brick the phone with ahahah
Mauro
https://android.googleapis.com/pack.../935d7c7259037b861c8c4192631b33bd987a259f.zip
Source: http://4pda.ru/forum/index.php?showtopic=962154&st=3680#entry95409053
_mysiak_ said:
https://android.googleapis.com/pack.../935d7c7259037b861c8c4192631b33bd987a259f.zip
Source: http://4pda.ru/forum/index.php?showtopic=962154&st=3680#entry95409053
Click to expand...
Click to collapse
Cool, thank you _mysiak_!!!
After that I downloaded it I will start the most scary part so ahahah
This ROM is OTA
We cannot flash it with fastboot way
It has to install with stock recovery , And I have a question :
Can I install it directly from android 9?