I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!
I got blinking brick. I can not go into fastboot
@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power
95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.
aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?
Related
Hey I've seen lots of posts around XDA about Win8 and RSDLITE issues, I can do everything - fastboot, see SD Card on phone, EVERYTHING, but when I installed RSDLITE 6.1.4 onto my Win8 machine, it just won't recognise my Razr M (XT905).
Just trying to get the newly released firmware files for JB onto my razr...can you fastboot them or do you need to use RSDLITE on the XMLs?
HELP!!!
Just do it manually using command-line fastboot.
In your case full list will be:
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash devtree device_tree.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase tombstones
fastboot erase cache
If you want to delete user data, add:
fastboot erase userdata
After that continue booting by typing:
fastboot continue
and you've done.
You can make simply bat-file and just copy these lines there to simplify the procedure.
i'm running windows 8 and have never had any issues with rsdlite.
i'd try running usbdeview as admin and remove all moto drivers and then plug in phone to let the drivers load again.
another thing to be aware of is rsdlite asks for network access on first start, so make sure you allow access.
Q9Nap said:
i'm running windows 8 and have never had any issues with rsdlite.
i'd try running usbdeview as admin and remove all moto drivers and then plug in phone to let the drivers load again.
another thing to be aware of is rsdlite asks for network access on first start, so make sure you allow access.
Click to expand...
Click to collapse
Thanks Osmatic, just noticed there's a flash_fastboot.bat file in the folder...here goes!!!
Edit: JELLY BEANS JELLY BEANS JELLY BEANS!
Only For X829 owners... 16s stock rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
https://drive.google.com/file/d/0B9KXxWUKQWYBaml4aEhFeFV5N2M/view
Extract zip file in adb on your c:/ directory.
Fastboot rom execute Chinese bat file in fastboot mode.
---Instructions---
How to flash it! First flash or boot twrp via fastboot. Do a clean wipes. Reboot into fastboot. Execute the chinese word bat file.
There will be a few error. Missing file. The zip provided was not complete. Missing stock recovery etc. Anyway, it work. For stock recovery here https://forum.xda-developers.com/le-max-2/development/official-lemax2x820x822-t3508823
After finishing youget fully working stock 5.8.16s LEX829.
Also these will change ur device info in fastboot to le_x2_na_oversea
More info >> https://forum.xda-developers.com/showpost.php?p=72708251&postcount=29
If you have problems with bat.. Put all rom files Inside tools file type on cmd as administrator one by one
It may some files missing inside rom... Don't worry
fastboot flash ddr ddr.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devinfo devinfo.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash pmic pmic.elf
fastboot flash pmicbak pmic.elf
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash xbl xbl.elf
fastboot flash xblbak xbl.elf
fastboot reboot
Hey @CrisBalGreece
Could you give some more specification of the rom?
paxcolo said:
Hey @CrisBalGreece
Could you give some more specification of the rom?
Click to expand...
Click to collapse
Official 16s X829 fastboot rom from US officials forums.
Thank you for posting this man ?
im getting error zipfile is corrupt shuld i download again?
Ok I downloaded it again and it's saying zip file corrupted still
allrockedout said:
im getting error zipfile is corrupt shuld i download again?
Ok I downloaded it again and it's saying zip file corrupted still
Click to expand...
Click to collapse
Check your adb and drivers otherwise go manually one by one. Read OP info. Download it only through pc.
I just got my x829 with a shop rom that does not allow for OTA updates.
Is your stock rom the same one I have on my phone currently?
Please help I know it's not exactly related but I'm getting this in twrp now
I don't understand fastboot and CMD very well
This is to complicated i just want to flash its not working
Here's a log from twrp I'm still getting corrupt zip file error, when trying to flash official x829 zip ?
https://mega.nz/#!dFYVTBYY!NSzhFbQca87Em5XtnQ_-sCKf4FDFwWe0s3avpKkRjKo
Hi
I have x829 and now I'm on 19S indian. But this rom doesn't support polish language and I want back to original 16S from USA.
I do not have TWRP installed, can I rename the file to update.zip and move it to the root directory? Then install from recovery ?
ymmi21 said:
Hi
I have x829 and now I'm on 19S indian. But this rom doesn't support polish language and I want back to original 16S from USA.
I do not have TWRP installed, can I rename the file to update.zip and move it to the root directory? Then install from recovery ?
Click to expand...
Click to collapse
I haven't try that but you can still try it through fastboot commands.
CrisBalGreece said:
Only For X829 owners... 16s stock rom
If you don't know how to flash fastboot rom and make the above just flash this through TWRP
TWRP zip Flashable rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
Click to expand...
Click to collapse
I tried this file with renamed to update but after reboot and turn on it to normal recovery I received update field - file incorrect.
Something like that. But I pushed back button and then phone restart normally but on 19S.
Any idea ? How back to 16S without fastboot (now I'm at work) and TWRP ?
ymmi21 said:
I tried this file with renamed to update but after reboot and turn on it to normal recovery I received update field - file incorrect.
Something like that. But I pushed back button and then phone restart normally but on 19S.
Any idea ? How back to 16S without fastboot (now I'm at work) and TWRP ?
Click to expand...
Click to collapse
Yes I was afraid so. Try to contact with your seller or put TWRP and after installation put back the official recovery with the same Way.
Why on web I find only files for x822 and x820 ? Where is a department with the files of rom for USA version X829 ?
ymmi21 said:
Why on web I find only files for x822 and x820 ? Where is a department with the files of rom for USA version X829 ?
Click to expand...
Click to collapse
I don't know. You may ask to moderators to make new threads for x829.
allrockedout said:
Here's a log from twrp I'm still getting corrupt zip file error, when trying to flash official x829 zip
https://mega.nz/#!dFYVTBYY!NSzhFbQca87Em5XtnQ_-sCKf4FDFwWe0s3avpKkRjKo
Click to expand...
Click to collapse
This Logcat is from flashing and backing up Omni rom for max2. That you have or this is the one you try to wipe. Sorry I haven't understood....
Yes I know that I can write to moderators for new threads but for what ? I'm looking this rom on Leeco company site. Not here. (not exactly, this family of xda is big support )
Why do not they have it on their website ? I found only for Chinese and Indian versions, but not for USA (x829).
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
CrisBalGreece said:
I don't know. You may ask to moderators to make new threads for x829.
Click to expand...
Click to collapse
ymmi21 said:
Yes I know that I can write to moderators for new threads but for what ? I'm looking this rom on Leeco company site. Not here.
Why do not they have it on their website ? I found only for Chinese and Indian versions, but not for USA (x829).
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
Click to expand...
Click to collapse
I don't know why. All so given by my friends in Greece that they have it and flash to give it back to seller after fingerprint issues.
CrisBalGreece said:
Only For X829 owners... 16s stock rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
https://drive.google.com/file/d/0B9KXxWUKQWYBaml4aEhFeFV5N2M/view
Extract zip file in adb on your c:/ directory.
Fastboot rom execute bat file in fastboot mode.
If you have problems with bat.. Put all rom files Inside tools file type on cmd as administrator one by one
fastboot flash ddr ddr.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devinfo devinfo.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash pmic pmic.elf
fastboot flash pmicbak pmic.elf
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash xbl xbl.elf
fastboot flash xblbak xbl.elf
fastboot reboot
If you don't know how to flash fastboot rom and make the above just flash this through TWRP
TWRP zip Flashable rom
https://mega.nz/#!ZG4G1YiS!FHW2u7EAwzVkXr1djEJlAaoZxa2AvjkZlakCRuLLmZw
Click to expand...
Click to collapse
Where you found this rom or it is yours ?
Which exactly bat file I have to open ?In file of first link I find 2 bat files, scripts.bat and some chinese signs.bat ?
File of last link (kind of like for twrp) is the same like file of first link ?
Where are differences ?
Rom 16s
CrisBalGreece said:
Check your adb and drivers otherwise go manually one by one. Read OP info. Download it only through pc.
Click to expand...
Click to collapse
1. Error when unzipping on file system.img !
2. Link to download firmware for TWRP the same as for flashing in FASTBOOT !!!
Please fix it, thanks in advance
Download Firmware From here---> http://en.miui.com/a-234.html
Extract everything , Copy all file & images into Adb Folder
Minimal ADB and Fastboot ---> https://forum.xda-developers.com/showthread.php?t=2317790
Commands
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash devcfgbak devcfg.mbn
fastboot flash dsp adspso.bin
fastboot flash sec sec.dat
fastboot flash splash splash.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash cache cache.img
fastboot flash mdtp mdtp.img
fastboot flash lksecapp lksecapp.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlibbak cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash cmnlib64bak cmnlib64.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash keymasterbak keymaster.mbn
fastboot flash cust cust.img
fastboot reboot
Copy to a text File and save as .bat
Copy bat file to adb folder
Now open bat now it will getting flash
Sit Back & Relax
In My case mi tool was not working so i did this to flash
Thank You .
Is this method working fine bro?
Sent from my Redmi Note 4X using Tapatalk
abees said:
Is this method working fine bro?
Sent from my Redmi Note 4X using Tapatalk
Click to expand...
Click to collapse
Works Fine NO Issues Bro Tested On Three Different as well Devices
bparihar said:
Works Fine NO Issues Bro Tested On Three Different as well Devices
Click to expand...
Click to collapse
Thanks a lot man.. for me too the miflashtool is not working
Sent from my Redmi Note 4X using Tapatalk
Cool bro Thnkz
i have only flash system recovery cache n boot files ..my device is working fine..is there any problem
[email protected] said:
i have only flash system recovery cache n boot files ..my device is working fine..is there any problem
Click to expand...
Click to collapse
[no problem but a fresh clean flash is a must (have a backup)]
The extracted images package already includes .bat and .sh files for different purposes, why create another one?
Just execute flash_all.bat or flash_all.sh are you're done.
in my case in part "fastboot flash system system.img" notification "error " cannot load system.img"
before bootloop I used ROM epic miui 10 .
now my MIDO stuck in logo MI and restart again adn again ..
help me please fix this error..
I am trying to flash Lineage OS, and from TWRP it appears to flash but now this Storm Kipper will not boot into Lineage.
From TWRP if I select power off it goes straight into Fastboot.
From Fastboot:-
Start: reboots and goes straight into fastboot
Restart bootloader: reboots and goes straight into fastboot
Power off: reboots and goes straight into fastboot
Recovery mode: goes to Team Win Recovery Project 3.1.0-0
I have a number of lineage-14.1-2017xxyy-nightly-kipper-signed.zip on a microSD card, and I have checked the SHA256 hashes and they match the ones on the website
Another oddity is that if I try and flash open_gapps it says wrong architecture, I have tried arm and arm64 and it makes no difference.
I have tried using the repair feature on System, Data and Cache and it seems to complete without issues but lineage still won't boot.
Can anyone advise? thanks
also I just tried the ADB sideload feature in TWRP (just to rule out the microSD card)
it appeared to work with a progress bar and at the end said "script succeeded", but when you select reboot it says "No OS installed! Are you sure you wish to reboot?"
ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?
Did you have success? I have the same problem...
Possible solution found!
dieselnutjob said:
ok people.
If I extract the boot.img from the LineageOS zip file and flash that using fastboot is that likely to make things better or worse?
Click to expand...
Click to collapse
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS
android_paul said:
I got my wf storm up and running again!
Look here -> reddit-forum for LineageOS
Click to expand...
Click to collapse
Thank you for this. I now also have Lineage 14.1 working.
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Anyway, as per the reddit post.
Download cm-13.1.5-ZNH2KAS7EC-kipper (fastboot).zip
unpack the zip file into a new folder
follow these instructions (I am using Linux)
Code:
cd ~/cm-13.1.5-ZNH2KAS7EC-kipper-fastboot/
fastboot flash aboot emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
This got it back to a working CM13.1
From here I went to bootloader mode and had a play with CM Recovery but didn't get on with it.
So I flashed on TWRP+3.1.0-0.img again.
This time it wouldn't pick up the microSD card, but adb sideload worked and that is how I installed lineage, su and gapps.
Thanks again.
Now that Lineage 14.1 is on TWRP can now see the microSD card.
dieselnutjob said:
...
The back button still doesn't illuminate though. I'm not sure if it's a bug or a hardware fault.
Click to expand...
Click to collapse
My led of the back button is off too. I'm afraid, it's a hardware issue. If my phone gets cold (using as a navigation tool on bike in winter....), the led begins to shine - until it's warm again. So this looks like an electrical (dis)connection problem.
There are bigger problems to imagine.
Can't flash twrp to Wileyfox Storm!
I can't install twrp of my Wileyfox Storm (I've tried several times)!
* I've unlocked the bootloader.
* I change to the directory where the twrp image is stored.
* I do <adb reboot bootloader>
* I do <fastboot flash recovery ./twrp-3.2.1-0-kipper-20180110.img>
I then get the message:
target reported max download size of 268435456 bytes
sending 'recovery' (26676 KB)...
OKAY [ 0.923s]
writing 'recovery'...
OKAY [ 0.339s]
finished. total time: 1.262s
* I then do <fastboot reboot>
The phone then reboots OK, but if I try to reboot to recovery I just get the 'vanilla' boot menu.
I'd be grateful for any help, please.
Jim
Hi all,
This is a long shot, I hope there is someone somewhere that can help with this issue. I know it's a fairly old phone now, but if anyone has any knowledge about android recovery, it would be greatly appreciated!
Version: OxygenOS 3.6.1.
Rooted via Magisk and Bootloader Unlocked years ago.
The problem was unexpected. It was suffering battery drains for the past month, and last night, whilst on charge, I noticed it restarted. And now it's stuck on the OnePlus LOGO Screen. D:
I can only access FASTBOOT and NOT RECOVERY mode.
What I've tried:
MSM RECOVERY TOOL (w/ QCOM drivers)
Installing ABD Interface Drivers to try an ADB Sideload (but can't get to recovery)
Fastboot flashing stock and TWRP recoveries (can't boot into it - error dtb not found).
Fastboot flash_Ox211.cmd *
Spoiler: * flash_Ox211.cmd does the following
Code:
rem adb reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
rem fastboot erase recovery
rem fastboot flash recovery unofficial_twrp_2.8.7.0-bacon.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sdi sdi.mbn
fastboot flash pmic pmic.mbn
fastboot flash hyp hyp.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oem_stanvbk static_nvbk.bin
rem fastboot flash userdata userdata_64g.img
pause
rem fastboot reboot
None of the above has worked or has fixed recovery mode.
I want to keep my userdata. Is it possible to access that partition, and/or somehow do an 'adb backup'. It might be impossible without the recovery
To keep documenting my findings on extra things that I have done or will do.
Reseating the battery
I have drained the battery and taken the battery connection out the phone for an hour.
UPDATE: After re-plugging, and putting it into charge, the phone bootloops now instead of staying stuck on the OnePlus/Android LOGO continuously. NO CHARGING INDICATOR.
Replacing the battery
If it's a battery issue, then a replacement might work. I have ordered one.
UDPATE: TBD
Fastboot Flashing other recovery img's
dtb not found (or device tree blob) - was an issue when I tried booting into a flashed recovery (stock or TWRP). According to some forum posts, it may be due to flashing the wrong recovery version on the device.
UPDATE:
stock []
twrp-2.8.7.0-oneplus2 [] - no dtb error
twrp-3.0.0-1-oneplus2 []
twrp-3.0.2-1-oneplus2 []
twrp-3.2.1-0-oneplus2 []
...
↑ Doing a fastboot boot <recovery>.img bootloops the phone.
Try asking in the op2family discord server, there are some pretty knowledgeable ppl there. Also you could try asking _undead, he's the one who made lineage 19.1 for op2, see in Original Android Development on this forum.
Huh, it sounds like you're having a similar issue as me. Except I can access recovery but not fastboot... and sideloading isn't working for me.