Database Users

[ROOT][Recovery]Wileyfox Storm

## 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.

Post Your Current or Last Boot Issues here (READ BEFORE POSTING PLEASE)

Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.​
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)

reserve 1

reserve 2

reserve 3

reserve solution 4

reserve solution 5

Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.

https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.

Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated

Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.

Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!

aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++

I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think

Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.

I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.

Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!

Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.

Rooted, Custom Rom a huge fail

Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?

Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke

mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.

Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?

Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.

Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.

AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp

AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.

AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes

[Bootloop] N9005 not booting after frame (display) replacement

Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon

Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .

I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.

Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.

I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??

Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...

What happens when you flash correct stock rom via Odin ??

I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.

AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .

I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.

AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.

Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.

after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)

Error E3004 when trying to install any ROM on Samsung J5 (2015) SM-500FN

What I have:
I have a Samsung J5 (2015) SM-500FN which ran out of storage and basically hung itself up. There is no data I want to recover, but I want to install either a stock ROM or (preferably) something else like Lineage - I just want to get a usable phone again.
My problem:
I have tried to download *many* stock ROM
s from reputable sources like SamMobile (for this specific phone, but trying different release dates and country codes) but every single one of those ZIPs is corrupt, even when downloading from a different computer.
Flashing with ODIN anyway gives a FAIL result and a device that cannot boot, not even into recovery: It gives a green screen with the text: `An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.`
Ironically, the Smart Switch software just says this device is not supported. The older Kies3 software lets me enter the exact model# followed by the serial# - but then it says this device is not supported. So neither Samsung software is usable, but I can still use ODIN.
Even with the phone in this broken state, I can install TWRP again. So it is not completely bricked. I boot into TWRP and copy a LineageOS ZIP file to /sdcard, but when I try to install that, the TRWP console says: `E3004: This package is for device j5nlte,j5nltexx; this device is .` Note how it doesn't appear to recognize that this device is indeed the model j5nlte!
Android.SE says that "E3004" means my TWRP is too old, but I use `twrp-3.1.1-1-j5nlte` which is currently the newest version for this phone.
I would also like to try a factory reset, but that requires the stock recovery which won't boot (see step 2 above).
My question: How do I get out of this catch-22?
It seems that if I could just get around that E3004 then I would be fine. But I have found no ways to trick the installer into ignoring that error.

Flash an updated twrp .IMG file which you can extract from the file here j5nlte (TWRP)
Just flash the img in twrp and reboot to recovery
Then with the updated twrp try flashing the rom again

garylawwd said:
Flash an updated twrp .IMG file which you can extract from the file here
Click to expand...
Click to collapse
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?

torbengb said:
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
Click to expand...
Click to collapse
No problem at all, glad all is working for you now. Happens all the time with people having the wrong recovery its no big deal but a lesson learned is always make a backup in twrp before going tinckering around with things or keep a copy of a rom, that you know works, on your SD card.
From the bootleggers pie rom thread.
The Dev of that also builds his own twrp for all j5 2015 models.
he's a really great guy to have supporting our j5 community