Related
## Disclaimer and acknowledgements
All your actions with your phone are at your own risk;
## Intro
Hey,
I propose a tutorial to root Wileyfox Storm with lastest SuperSu Binary, but you can flash zips too ^^
Wileyfox storm's stock recovery has a signature verification, so you can't flash SuperSu 2.46, but with long work i got custom cyanogen recovery with no signature verification ;D
## Tutorial
Step 1 : Unlock bootloader !!!! It will erase All Data So backup first !!!!
- Go to settings>about phone and tap a few times on build number to unlock dev options
- Go to Dev options and check OEM Unlock and reboot bootloader (volume +)
- Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y
Step 2 : Flash Custom Recovery
- Reboot Bootloader
- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img"
- Wait the flash process and reboot recovery (volume -)
- Now Flash SuperSu-2.46.zip
Step 3 : Enjoy !!
## Download
Super Su : SuperSu-v2.46_signed.zip
Custom Recovery : kipper-custom-recovery.img
Corrected link to recovery?
Hi,
The custom recovery link is to the supersu file as well. Can you post the corrected link?
Thanks
Sorry xD
Thanks, I haven't had time to try compiling the Cyanogen Recovery for the Storm myself yet.
The above recovery image worked for me using fastboot boot xxx thus leaving the stock recovery intact.
F:\downloads\kipper>fastboot boot kipper-custom-recovery.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
OKAY [ 3.082s]
finished. total time: 3.758s
Wileyfox Storm (Kipper) - 12.1-YOG4PAS3MG
SuperSu and Busybox successfully installed.
Thanks.
No prob i'm happy, i've done it myself ^^
Phone wont boot pasted the Cyanogen logo
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
bobslesbricoleurs said:
## Tutorial
Step 1 : Unlock bootloader !!!! It will erase All Data So backup first !!!!
- Go to settings>about phone and tap a few times on build number to unlock dev options
- Go to Dev options and check OEM Unlock and reboot bootloader (volume +)
- Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y
Step 2 : Flash Custom Recovery
- Reboot Bootloader
- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img"
- Wait the flash process and reboot recovery (volume -)
- Now Flash SuperSu-2.46.zip
Step 3 : Enjoy !!
Click to expand...
Click to collapse
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
codeclinic said:
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
Click to expand...
Click to collapse
The first boot after wiping takes a few minutes so do be sure that you are waiting long enough, otherwise sounds like something borked.
Are you able to boot back to recovery by holding volume down while powering up?
If so you should try clearing cache and wiping.
You can also try restoring to stock CyanogenOS images : https://cyngn.com/support
If just installing the stock recovery the image can be extracted from the fastboot zip.
There is now also a CyanogenMod nightly build, you can try flashing the recovery from there instead (there is also the nightly Cyanogen build if you are feeling brave): https://download.cyanogenmod.org/?device=kipper
There is a separate download for the recovery image.
Flashing su is not required to boot after flashing the custom recovery.
However to flash it, first copy the SuperSu zip onto the phone (for simplicity use the main memory not the SD card), either download directly onto phone, copy from computer when connected as a usb device or transfer using adb. From the custom recovery you can then select Apply Update and browse to the SuperSu zip file.
codeclinic said:
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
Click to expand...
Click to collapse
Did you unlocked bootloader before?
Envoyé de mon Wileyfox Storm avec XDA Forums
bobslesbricoleurs said:
Did you unlocked bootloader before?
Envoyé de mon Wileyfox Storm avec XDA Forums
Click to expand...
Click to collapse
Yes, i followed all the instructions. I even tried doing it with the 'fastboot boot' method. But still no luck.
In the end I did a factory reset from the recovery and rebooted. I'm now able to get into android normally.
However, if i go back to recovery and try to flash the su binaries, it fails with the output sayings something about the signature of the package.
Any ideas?
codeclinic said:
Yes, i followed all the instructions. I even tried doing it with the 'fastboot boot' method. But still no luck.
In the end I did a factory reset from the recovery and rebooted. I'm now able to get into android normally.
However, if i go back to recovery and try to flash the su binaries, it fails with the output sayings something about the signature of the package.
Any ideas?
Click to expand...
Click to collapse
If you are getting messages about the signature then you are probably running the stock recovery again,
Go back to the bootloader and use fastboot to boot or flash the customer recovery above or cyanogen recovery again.
You can also grab an unsigned version of SuperSu from the developer : https://download.chainfire.eu/696/supersu/
miSAKe said:
If you are getting messages about the signature then you are probably running the stock recovery again,
Go back to the bootloader and use fastboot to boot or flash the customer recovery above or cyanogen recovery again.
Click to expand...
Click to collapse
I figured / hoped that was the case. I'll give it another shot tonight.
miSAKe said:
You can also grab an unsigned version of SuperSu from the developer
Click to expand...
Click to collapse
Are there any pros/cons of using the unsigned version over the signed one? If not, is it not better to use the unsigned version and not bother with the flashing of the recovery?
Thanks
Maybe i'll try later to port philz to this phone ^^
Is it possible to relock the bootloader again?
I've successfully managed to install the custom Cyanogen recovery, and CyanogenMod on my WF Storm this afternoon. I largely did this by following the instructions posted previously - unlocking bootloader, installing CM recovery image with fastboot, then installing CM12.1-kipper from recovery.
I did encounter some problems - namely that the nightly version of the CM recovery (cm-12.1-20151120-NIGHTLY-kipper-recovery.img ) just did not seem to work, despite reportedly being installed OK - Whenever I tried to install anything in recovery mode, it came up with "failed to verify whole-file signature" or similar errors. Strangely I was able to overcome this by using fastboot to boot from the image of it downloaded to my PC, and installing the CM ROM that way; initially it came up with an error about filesystems being incompatible, but after erasing all data, it seemed to go on OK.
I installed the openGAPPS aroma version (allows you to choose which GApps to install interactively) and used the ARM-64 version. Initially, I had the problem with the recovery and couldn't install it, so finally decided to install the cyanogen recovery linked to above in one of the first posts (kipper-custom-recovery.img) rather than from the nightlys. This seemed to solve the problem, about signature errors and I tried to install GApps. The first time I tried this (after going through and selecting what to install from the huge list), it seemed to start OK then said there was not enough space on the device - which seemed very odd indeed. I rebooted and tried again, this time with a few less GApps selected, and it seemed to work fine. I think it was just some kind of a glitch the first time, because there is plenty of space left.
During the first boot after installing the GApps, the systemUI crashed, the screen went black and it was not looking good. Following another reboot though, it seemed to be OK, and I am very happily now using the Storm with CyanogenMOD and root access. I've now installed the dozens of extra apps I use, from the play store, and so far, everything is working well.
Of course, I haven't checked evreything yet, but the camera, phone, 4G LTE, tethering, google account etc. all seem to be working very well.
I hope this info might be of help to anyone looking to get CM12.1 going on their WFStorm. If you get signature errors, just make sure you try installing a different CM recovery!
A huge thanks to earlier posters, and everyone who's worked on getting a version of CM for the Storm. Peace-out,
Neon
nsam1 said:
I've successfully managed to install the custom Cyanogen recovery, and CyanogenMod on my WF Storm this afternoon. I largely did this by following the instructions posted previously - unlocking bootloader, installing CM recovery image with fastboot, then installing CM12.1-kipper from recovery.
I did encounter some problems - namely that the nightly version of the CM recovery (cm-12.1-20151120-NIGHTLY-kipper-recovery.img ) just did not seem to work, despite reportedly being installed OK - Whenever I tried to install anything in recovery mode, it came up with "failed to verify whole-file signature" or similar errors. Strangely I was able to overcome this by using fastboot to boot from the image of it downloaded to my PC, and installing the CM ROM that way; initially it came up with an error about filesystems being incompatible, but after erasing all data, it seemed to go on OK.
I installed the openGAPPS aroma version (allows you to choose which GApps to install interactively) and used the ARM-64 version. Initially, I had the problem with the recovery and couldn't install it, so finally decided to install the cyanogen recovery linked to above in one of the first posts (kipper-custom-recovery.img) rather than from the nightlys. This seemed to solve the problem, about signature errors and I tried to install GApps. The first time I tried this (after going through and selecting what to install from the huge list), it seemed to start OK then said there was not enough space on the device - which seemed very odd indeed. I rebooted and tried again, this time with a few less GApps selected, and it seemed to work fine. I think it was just some kind of a glitch the first time, because there is plenty of space left.
During the first boot after installing the GApps, the systemUI crashed, the screen went black and it was not looking good. Following another reboot though, it seemed to be OK, and I am very happily now using the Storm with CyanogenMOD and root access. I've now installed the dozens of extra apps I use, from the play store, and so far, everything is working well.
Of course, I haven't checked evreything yet, but the camera, phone, 4G LTE, tethering, google account etc. all seem to be working very well.
I hope this info might be of help to anyone looking to get CM12.1 going on their WFStorm. If you get signature errors, just make sure you try installing a different CM recovery!
A huge thanks to earlier posters, and everyone who's worked on getting a version of CM for the Storm. Peace-out,
Neon
Click to expand...
Click to collapse
Wich open gapps you need ? mini, micro, full ?
Hi,
I used the aroma version of GApps, which has the interactive graphical installer so you can choose whichever apps you want. I am sure Nano and Pico etc. are all fine, I just wanted to install a lot of GApps.
I downloaded from here: http://opengapps.org/?api=5.1&variant=nano
It is set to nano by default but I chose aroma. Make sure you select the correct architecture (ARM64) and android 5.1 (if you are using kipper).
Best of luck,
Nsam
https://youtu.be/b6XUFmHoY4U
I upload it just wait 1 Hr
bobslesbricoleurs said:
https://youtu.be/b6XUFmHoY4U
I upload it just wait 1 Hr
Click to expand...
Click to collapse
All looks good I seem to have a slight problem with one bluetooth device, but I need to look in to it more before I say it is a problem with kipper. Other bluetooth devices work fine
keep up the good work
Nsam
Hei it has been the second day running nightly built of CM12.1, and so far its been great never had serious issues. I just noticed that the proximity sensor distance when call is engage is set to very near like 1cm. If the phone goes further the screen lights on and gets activated.
Nightly most of time runs well, apart from "Not Responding" whatsapp every once in a while. Battery life is average almost the same stock CM. Call gets cut/muted at the middle of the conversation, not sure if the network or the phone has it. Hopefully there will be a TWRP soon for the device as NANDroid backup is very important when using nightly. Thanks for all the devs.
Hi all,
I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.
After updating I followed this guide: http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992
And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper
Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.
I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).
When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:
<bootloader> Device already : unlocked !
OKAY [ 0.000s]
finished. total time : 0.000s
Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...
I continued to start rooting it, but not before testing if I could still boot but everything was fine.
I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.
I checked if everything still was ok and it was. I could boot and everything.
So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.
I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.
I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.
This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.
I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.
I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).
So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.
I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.
And now the rom is in a boot loop.
I already tried a full factory reset but it's still boot looping.
I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.
The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".
But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?
I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..
Thank you in advance.
Edit: I've found my solution and had to change something.
You can read it here starting from Edit 2.
http://forum.xda-developers.com/showpost.php?p=68632922&postcount=84
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning signifies a mismatched vendor and system partition. The vendor partition was integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS base. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone. The phone will fail to boot if you mismatch the vendor.img with a different OS base. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat.
Click to expand...
Click to collapse
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
SlimSnoopOS said:
Hey there,
Regarding your TWRP 3.0.2-0/MultiRom 3.0.2-0 and TWRP 3.0.3 issues, check out post #1152 in the official TWRP 6P thread. If there is an update to MR to support Nougat encryption, you'll just have to follow the MR thread or Github for updates.
Here's a brief explainer from my guide in the Nexus 5X forums about Vendor.img:
Hope this clears things up for you!
Edit: Also, certain rom teams keep an up to date listing of vendor.img available on their websites. Usually this is detailed in the rom thread OP. Find a reliable thread and bookmark their vendor.img downloads, if not download the factory image each month and extract the img.
Click to expand...
Click to collapse
Thanks so much for the swift reply! I'll check these links out right away. I'm sure they will fill in the gaps for me.
Best,
KT
KilgoreTrout71 said:
Hi, All . . .
I believe it would be appropriate to label me as an intermediate-to-advanced newbie. That is, I'm not clueless, but there are lots of blind spots in my knowledge.
I just bought a 6P and while I've been waiting for my SIM card to arrive, I've gone ahead and rooted, installed TWRP 3.0.3-0, and made a few customizations here and there. One thing I don't understand is the significance of the vendor image now. I'm coming from a 6 where that wasn't an issue. Also, in the rooting instructions it indicates that one should "find the correct vendor image," without really indicating how one can go about learning which one is "right." In the end, I took the latest one I could find, because my phone did an OTA update and I simply reasoned that I should match latest with latest.
In any case, I want to install MultiROM and I keep running into this problem:
The MultiROM version of TWRP doesn't load. It hangs on the splash screen. The version it uses is 3.0.2-0, so I suspected it was an issue with that. I flashed the TWRP-only recovery version 3.0.2-0 after having no luck, and it wouldn't load beyond the splash screen, either. Finally, I re-flashed the stock system recovery and tried flashing both the 3.0.2-0 TWRP-only recovery and the MultiROM-integrated version, both without success.
Is there something about the move from 3.0.2-0 to 3.0.3-0 that makes a rollback impossible. Is it even necessary?
Re-flashing 3.0.3-0 solved the problem of basic functionality. TWRP comes right up after I do that. But I can't get the MultiROM recovery or the 3.0.2-0 TWRP recovery to work no matter what I try.
My phone says that the vendor version is N4F26J and my "build number" is N6F26Q, and I'm running PureNexus 7.1.1. Those two numbers appear like a mismatch to me, but everything I could find indicated that the vendor version I have, being the latest, is the right one.
What am I missing? Can someone with more experience solve this puzzle, or at least lead me in a direction where I know which questions to ask on my own and can get things to start making sense again?
I appreciate your help! Thanks!
Click to expand...
Click to collapse
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
jhs39 said:
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0..
Click to expand...
Click to collapse
MultiRom support for this device was released when Marshmallow was out. So MR33 is based on the Marshmallow branch and ships with 3.0.2. The developer just isn't ready to release support for Nougat 7.0 and couple that with the issues of TWRP 3.0.2-x. He's actively pushing commits to support Nougat.
Sent from my Nexus 5X using Tapatalk
jhs39 said:
Your vendor image and build number do sound like they are mismatched. If you can't find the vendor image you need on XDA you can find the matching build on the Google site, download the whole factory image and unzip it and get the vendor image that way.
I believe TWRP 3.0.2-0 was buggy. I'm not familiar with Multi rom and I don't know why they would use that build. You should be using 3.0.2-3 or 3.0.3-0.
I personally wouldn't install a custom ROM before activating the phone. I know a couple people have reported in the past that they were unable to activate their phone on a custom ROM. Hopefully you won't have that issue.
Click to expand...
Click to collapse
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
KilgoreTrout71 said:
Thanks for the input! I actually just got my card and some of the activation seems complete. (I got my voice mails and so on, but no data connection yet.) I didn't have a problem with the Nexus 6 on PureNexus, but we'll have to see how this one plays out. I'm not able to call over WiFi yet.
Click to expand...
Click to collapse
It might just take a while for the service to go through. Good luck.
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.