yashsingh1/xdaforums huggingface dataset:
[Wileyfox Storm] ftabashir:
My device stops at boot animation, so i cant go to developer option.

I need stock recovery for kipper. but cyanogen links not available. do you have kipper stock recovery? i can't find it via google.

---------- Post added at 02:24 PM ---------- Previous post was at 02:20 PM ----------

currently the only available option for me is fastboot. i have installed custom recovery and suddenly locked oem. and also my device stops at boot animation, so i cant go to android settings to unlock oem. when i try with fastboot to unlock oem it says that "remote: oem unlock is not allowed"

i appreciate you if you send me kipper files. (zip, img, ...). can you upload them?

---------- Post added at 02:37 PM ---------- Previous post was at 02:24 PM ----------

Here is all of works i did:

fastboot boot kipper-custom-recovery.img

downloading 'boot.img'...

OKAY [ 0.863s]

booting...

OKAY [ 0.084s]

finished. total time: 0.954s

flashing SU zip file

restart phone and it stopped at boot animation

fastboot flash recovery kipper-custom-recovery.img

target reported max download size of 268435456 bytes

sending 'recovery' (21208 KB)...

OKAY [ 0.905s]

writing 'recovery'...

OKAY [ 0.330s]

finished. total time: 1.245s

try again to flashing SU zip file

restart phone and still stopped at boot animation. after that i tried to factory reset. but still stopped at boot animation.

fastboot oem unlock

...

(bootloader) Device already : unlocked!

OKAY [ 0.005s]

finished. total time: 0.005s

<<< This was the first time that i tried to unlock oem. i also forgot to check oem unlock at developer options >>>

fastboot oem lock

...

(bootloader) Warning: Only official images boot when locked

(bootloader) Please confirm

OKAY [ 4.093s]

finished. total time: 4.096s

fastboot oem unlock

...

FAILED (remote: oem unlock is not allowed)

finished. total time: 0.005s

fastboot boot kipper-custom-recovery.img

< waiting for any device >

downloading 'boot.img'...

OKAY [ 0.937s]

booting...

FAILED (remote: bootimage: incomplete or not signed)

finished. total time: 0.957s

---------- Post added at 02:46 PM ---------- Previous post was at 02:37 PM ----------

i think the solution is:

flash stock recovery of storm (because oem is locked and i can't unlock it, and also my device didn't let me to go to recovery because recovery is a custom one and when oem is locked it's not possible to boot custom recovery)

aftar flashing original kipper recovery i can install CyanogenOS and make my phone alive.

but i didn't find original recovery via google. can you upload for me.
[Wileyfox Storm] immermehr:
Hi [MENTION=5957610]bobslesbricoleurs[/MENTION]

hi all,

I got my mobile on wednesday and want to install lineageos 14.1 on it. I've tried the whole saturday and this sunday morning without success.

Firstly, I'm newbie. Pls foregive me, if I have some stupid questions.

Now here are what I've done:

- Dev options, OEM unlock: worked

- adb, fastboot on my computer: worked

- reboot Bootloader: worked.

- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img" : seems to work. It took me about 1,2 seconds. After that I got succeded information on my computer.

On my mobile I got a black screen named "Cyanogen Recovery" with 8 options: reboot now, apply update, wipe data/factory reset, wipe cache partition, wipe media, reboot to bootloader, power down, view recovery logs. (Sorry, I have made a picture of it, but I'm not allowed to put it here)

Does it mean, that I have successfully installed TWRP on my phone, and can install Super Su : SuperSu-v2.46_signed.zip now?

I have Cyanogen OS Version 13.0 ZNH0EAS45F (Android 6.0.1). Dose this version of custom rom and SuperSu work with this version?

Thank you very much for your help.
[Wileyfox Storm] FluffyTwit:
Hey :)

First of all, none of these are stupid questions - we all have to start learning somewhere and a year ago I was a total noob, just look at some of my past posts xD

Bear in mind if you want to install Lineage it will remove root and any custom recoveries, so do this step first. To do this:

Enter your phone's recovery by holding volume down (or up I can't remember) + power.

Wipe all data.

Select Apply Update then Install From ADB Sideload.

Put the Lineage.zip file into ADB's directory, enter the ADB shell from your computer and type

adb sideload filename.zip

Wipe cache then reboot device :)

Then, once you have Lineage, you need to install the custom recovery. By the way, this is not TWRP (which is a different custom recovery) - it is a modified CyanogenMod custom recovery. I personally use TWRP (found here for the WF Storm [kipper]) because I find it easier to use and it has more functions, also this custom recovery has caused me problems in the past whereas TWRP hasn't. It is installed the same way - again by flashing it via ADB fastboot.

As for the superSU, I use the most up-to-date binaries which can be found here.

But yeah in answer to your questions: 1. Yes, you have installed the custom recovery. 2. Yes, you can install SuperSU now. 3. Yes, SuperSU and the custom recovery works with CM13 and Lineage 14 :)

If you have any more questions you can always ask me :)

~ Adam
[Wileyfox Storm] immermehr:
Hi Adam [MENTION=7564114]FluffyTwit[/MENTION] ,

Thank you very much for your help. I still have some questions, before trying to test with my mobile.

So what I have to do are:

1. install/flash Lineage

2. install/flash TWRP

3. install Supersu

As I downloaded Lineage, I found on wiki site of LineageOS (wiki.lineageos.org/devices/kipper/install) that I have to:

1. install custom recovery (e.g. twrp)

2. install Lineage

3. install su

Which sequence is corrrect?

I still have another question for your post:

Is it a must? I think, I only need it, if I want to have Root on my device.

In order to install TWRP, will I have to use command: fastboot flash recovery TWRP-2.8.7.0-kipper-recovery.img?

Then can I download and install supersu (over Play store)?

Thanks again for your help and wish you a very nice weekend!

anp
[Wileyfox Storm] FluffyTwit:
Hello :)

So there are two ways to flash a new ROM (in your case, Lineage). You can either install via ADB or via your custom recovery. I personally find installing via ADB easier, and you do it by the method I explained in the last post. To install from your custom recovery, you must first install one (either TWRP or the one on this forum), then move the .zip to your phone and use the recovery's install option to flash it (see here for more info on how to do this). So via ADB you don't need a custom recovery essentially.

So once Lineage is flashed, via whatever of the two methods, you need to root it. To do this you need to flash TWRP using ADB (unless LinageOS has its own custom recovery but I don't think it does...) via 'fastboot flash recovery TWRP-blahblahblah.img'. Just remember that the TWRP image has to be the one I linked in my last post because that is made for the WF Storm (kipper). Once TWRP is installed, you transfer the superSU .zip file to your phone and install it using TWRP.

The SuperSU app simply manages root permissions and what-not. You cannot gain root access by installing it, this is done by flashing the .zip as stated above. The app is automatically installed when you flash the .zip though.

And yeah, custom recoveries aren't a must, however, they are very useful because they can quickly do stuff like backups, .zip installs etc. etc. To install superSU and ROMs (from the phone's storage) you need one though because most stock recoveries do not allow installation of unsigned zips.

Oh, and LineageOS doesn't come with Google's apps (such as play store, chrome, play services etc.) by default, so you need to flash Gapps to get them (see here for more info).

Have a nice weekend yourself :)

~ Adam
[Wileyfox Storm] Zugschlus:
Installing recovery does not work

Hi,

I am trying to install the custom recovery image to be able to make a Nandroid Backup before I flash LineageOS. Unfortunately, my Device crashes immediately after the system has booted up, so I cannot use any methods from the running OS to make a backup. The system that is on it is the new Wileyfox branded Android 7 that was rolled out OTA a month ago.

I have downloaded the twrp 3.1.0-1 from https www androidfilehost com ?fid=24591000424963153 as suggested earlier in this thread. I have then renamed the twrp-3.0.2-1-kipper.img recovery.img to recovery.img. When I boot my saystem into the bootloader, I get a bootloader saying the following:

fastboot boot recovery.img says:

(and the device stays in the booloader)

fastboot flash recovery recovery.img says:

When I now select "Recovery mode" or "Restart bootloader", I end up in the bootloader again.

When I select "Start", I get the dysfunctional flashed Wileyfox OS.

How do I go on from here?

Greetings

Marc

P.S.: The -i 0x2970 trick doesn't work with my device (hangs at "waiting for any device")
[Wileyfox Storm] image45:
This your issue, you need to flash the CM13.1 bootloader onto your device. I replace my Los 14.1 ROM with current Wileyfox that was rolled out and had to do this too. Read this topic to see how it was resolved.

https://xdaforums.com/wileyfox-storm/development/rom-test-build-lineageos-14-1-t3528016/post72394825.

That TWRP is better suited for 6.0.1 ROMs you need TWRP-3.0.3.0-kipper.img

Nugget based device tree for improved backups on 7.1.1 based ROMs

https://www.androidfilehost.com/?fid=529152257862697990

Regards Robert.
[Wileyfox Storm] Zugschlus:
Thanks for the pointer. But, the androidfilehost link fid=817550096634749259 just points to a 404 :(

Greetings

Marc
[Wileyfox Storm] image45:
Sorry your quit correct, however the below link does works and will give you access to the radio.zip file.

file description

Last official radio firmware for the Storm (kipper) from CyngnOS 13.1.2-ZNH2KAS3NA

https://www.androidfilehost.com/?w=files&flid=139759

The emmc_appsboot.mbn file is the important one as it will give you the cm13.1 bootloader.

You can then use the below to flash new bootloader. Then you should be able to flash the TWRP-3.0.3.0-kipper.img to run stable with the cm13.1 bootloader.

fastboot -i 0x2970 flash aboot emmc_appsboot.mbn

Then

fastboot -i 0x2970 flash recovery TWRP-3.0.3.0-kipper.img

The kipper-7.1-TOS125B ROM did not use the ext4 file system so I had to reformat the system partition and run a wipe on all except internal and SD card memory so I was able to install the los 14.1 ROM.

Hope this a better reply for you. Robert.
[Wileyfox Storm] Zugschlus:
Success, but only without the -i 0x2970. When I add the -i 0x2970, fastboot waits indefinetely on "waiting for any device".

After flashing the booloader, i was able to run an unflashed twrp 3.0.2 ("fastboot boot recovery.img") for a Nandroid backup. Unfortunately, the twrp does not recognize my 128 GB Micro SD card (selecting "Storage" in the backup menu says "Micro SD Card (0 MB)".

Do I really need to flash the recovery to be able to access the Micro SD Card? Or is there a maximum size of SD card that twrp will recognize? Unfortunately, I don't have any Micro SD cards bigger than 2 GB handy other than the one 128 Gig card.

Greetings

Marc
[Wileyfox Storm] image45:
TWRP can't access the micro SD card if its been formatted with the encrypted storage that started with android 6 marshmallow however the internal storage is still accessible. I place my nandroid backups on the internal storage and also download lineage os updates to the internal storage so I can access the files via the twrp install function.

I had to use ADB sideload once due to not having a big enough internal memory on another device and no free micro SD cards.
[Wileyfox Storm] Zugschlus:
The SD card in question is an unencrypted exfat file system. a 32 GByte Card with vfat is also not recognized by twrp 3.0.2-0 ("Micro SDCard (0MB)").

What do I do now?

A backup on internal storage doesn't help me at all since it'll probably be zapped when I flash a new OS. I need the backup to be on a removable device.

Can exfat be the culprit?

Greetings

Marc
[Wileyfox Storm] image45:
Normally the internal storage is unaffected, only the system partitions are flashed when installing a new ROM. I even wiped all the partitions except internal storage and micro SD then install the new zip with out any data loss.

Yes very possible, if the SD card is not encrypted can you copy its contents on to PC, then format in fat32/NTFS, then copy files back to SD then check if TWRP can read them.

Also in the mounts section see if the SD card is mounted, if it won't let you select it then this normally means the file format is not support. If you save files in the PC, you can opt to format SD card in TWRP then copy files from PC and then access them from recovery.
[Wileyfox Storm] image45:
The default is not to have SD card mounted. I could not mount my system partition a while back when I installed the official wileyfox os for the storm as it was not on ext4 like linage os is, so I had to wipe/ reformat it before I could run the restore feature and get my nandroid backup to successful run.

This was when I had to flash the CM13.1 bootloader as the official 7.1.1 stalled on the linage OS ROM.
[Wileyfox Storm] image45:
Partition options should let you reformat the mirco SD card so TWRP can read it, assuming you could copy contents to PC first for retrieval!
[Wileyfox Storm] Zugschlus:
The (linux) PC sees the card as /dev/mmcblk0 with a single partition, /dev/mmcblk0p1. I formatted that partition with mkfs.vfat /dev/mmcblk0p1, no change. Can twrp format the SD card in a format it is actually willing to use?

Btw, twrp behaves the same if no SD card is inserted in the first place, how can I verify that the card reader is working?

Greetings

Marc
[Wileyfox Storm] image45:
Normally you can access the micro SD and internal storage via the PC when TWRP is running, even if the file management is active.

---------- Post added at 01:27 PM ---------- Previous post was at 01:25 PM ----------

Yes I have done this before, check my partition options post above on advanced wipe section.
[Wileyfox Storm] Zugschlus:
So I start twrp, click on "Wipe", "Advanced Wipe", click on "micro SD card" and swipe.

This brings me to:

Updating partition details:
Failed to mount '/system' (No such device)
...done
Formatting Micro SDCard using mkfs.fat...
mkfs.fat process ended with ERROR: 1
Unable to wipe Micro SDCard.
Unable to wipe /external_sd.
Updating partition details:
Failed to mount '/system' (No such device)
...done

More ideas?

---------- Post added at 02:40 PM ---------- Previous post was at 02:34 PM ----------

How would I do _that_? When twrp is running, I see an USB device 18d1:d002, but that one does not offer USB storage capabilities, and adb shell ends in "device unauthorized". It wuld be ok to make a nandroid backup to internal memory and then being able to pull it from the device later before flashing the OS.

Greetings

Marc
[Wileyfox Storm] image45:
At this end I get both internal storage and micro SD visible on PC when TWRP is running.

I can move files from the SD card to PC and from internal storage to PC.

---------- Post added at 03:17 PM ---------- Previous post was at 03:00 PM ----------

If TWRP will run a nandroid backup then do so, then copy to PC then flash a new ROM or you might be going round in circles chasing the miro SD card file formats for an eternity.
[Wileyfox Storm] Zugschlus:
To cut things short, I was unable to make twrp 3.0.2 recognize _any_ Micro SD Card in the Storm's cardreader. I finally ended up making the Nandroid backup to Internal Memory and then using twrp's file manager MTP interface to pull the backup from the device to the Linux PC (using jmtpfs instead of plain mtp on the Linux side).

After that, flashing twrp and lineageOS just went on like a charm. Two days later, I broke the Storm's display :(

I am now waiting for the replacement device to arrive and will then have the chance to retry the process. I will report back if I'm encountering problems.

Greetings

Marc
[Wileyfox Storm] image45:
That's a real shame to do all that work, then suffer a hardware breakdown/ breaking.

Last I was advised the storm was no longer supported by Wileyfox, are you obtaining a new device from a secondary source?
[Wileyfox Storm] Zugschlus:
Indeed. Thanks for your compassion ;)

I feel that I would have been really mad if the device had failed by itself, but being entirely at my own fault made things significantly easier to handle.

I got one for ~ 160 Euros from Amazon Warehouse Deals. It was already unboxed but looks like totally new. Will flash it later tonight.

Greetings

Marc
[Android General] jameswilliam723:
Smartphones are essential thing that can live forever in peoples hand in these days. We all knew that Android is the more usable OS than iOS. Because it is cheap and user friendly. Even uneducated peoples can able to use android smartphones than iPhones.

This is why Android is more popular. This is very common factor that we knew.

Other than this point, I need some more technical details.

Answers would be thankful.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] mmuntean2:
Hello,

I have a S6 Edge: SM-G925F model of this phone, running Android 5.1.1 on XEF unbranded Firmware, non-rooted.

I want to flash a branded Orange Romania firmware on it and it does not seem to work. Every time I try, ODIN ends in FAIL within seconds and on the phone in the Download Mode screen I see: SW Rev. Check Fail Device:3 Binary:2

There isn't any obvious explanation anywhere, like no one is able to tell why this fails?

Is it because of the PIT? As I do not receive any PIT related error message, just the one above.

What could be the reason?

The orange firmware is also 5.1.1 so no downgrade here. The only difference is that the XEF firmware is 5.1.1 released in Oct, the one updated with the round icons and the Orange one is from September 5.1.1 with the square icons.

I knew that downgrade to 5.0.2 was not possible, but even on the same version 5.1.1 but with an older build?? I cannot explain..

Does anyone here know any reason or solution? I would not want to mess with the PIT if it is not needed although I do have a PIT file for 240MB hidden partition that fits the ORange's hidden partition size.

Thanks.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] superior8888:
Yes i found it impossible to downgrade older build as well.

Skickat från min SM-N920C via Tapatalk
[Galaxy S6 Edge Q&A, Help & Troubleshooting] mmuntean2:
So, it seems that the fact that the Orange firmware has an older baseband could be the cause although the Android version is the same. Bummer...:(

I'll have to wait for Orange to update their ROM before trying again...and, as usual as most carriers, they are late...
[OnePlus X Original Android Development] eng.stk:
It's up!

All right crew!

Some of you may know me from Nexus and other devices development in Code_Blue and blu_spark projects.

I decided to release the first kernel for my newest device, the OnePlus X.

I manage to do a nice and stable base, keep in mind that more stuff will come in the future, patience is a virtue ;)
[OnePlus X Original Android Development] droids@m:
Good to see the development going...
[OnePlus X Original Android Development] Rossyyy:
Awesome to see development has started, nice work

is USB fast charge like fast charging? for example samsung fast charging?
[OnePlus X Original Android Development] batam:
Excellent news.

I used code_blue then blu_spark since I purchased my Nexus 5.

Glad to be able to use it on my Oneplus X now.
[OnePlus X Original Android Development] Maelstr0m:
just flashed and testing, thank you for your work :)
[OnePlus X Original Android Development] Fatsodonkey:
Now im just waiting for official TWRP. :)
[OnePlus X Original Android Development] Deleted member 2357893:
The return of Code Blue. Yeeees
[OnePlus X Original Android Development] primemonitor:
A custom kernel already! Awesome! Thanks dev, gonna test this tonight :D
[OnePlus X Original Android Development] jim_bocho:
No, this means that USB charging on a computer USB port is faster as is maxes out the port - still (a lot) slower than with your wall plug, though.
[OnePlus X Original Android Development] Calvin2394:
Awesome, gonna root my phone right now :D
[OnePlus X Original Android Development] eng.stk:
Exactly.

And I just found out that max AC charge is caped at 1800mA by OnePlus.

The proprietary charger can put out at least 2000mA and the PMIC can deal with 2500mA.

I don't know why Oneplus caped it at 1800mA, maybe because of heat, maybe to not stress the Chinese quality stock charger.

But this opens for a 2nd hack, high current in fast charge mode with AC charger.
[OnePlus X Original Android Development] sydeu:
great to see the development starting! I'll try to wait a bit, but will probably install this soon! :)
[OnePlus X Original Android Development] Dizzyrul3z:
Awsome, thank you for first kernel 4 OPX! GR8 work!
[OnePlus X Original Android Development] Funk Wizard:
Many thanks.. will be flashing tonight :D
[OnePlus X Original Android Development] criz.89:
Hello all, work as a projectleader by battery manufacturer.

Fast charge is not good for the lifetime of the cell. With high current you stress the cell and the chemistry in the cell. Normally it is better to integrate a slow charge function which you can use over night. Like 500mA.
[OnePlus X Original Android Development] Loureiro:
Portuguese people on the edge! What a nation!

Huawei Ideos X5 still remembers your ROM. Good times.

I'm fighting the urge to start flashing the bejesus out of this device.
[OnePlus X Original Android Development] RinoFxx:
Thanks for your fast work!! Can I flash it over stock rom?

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] Maelstr0m:
Yes, it works flawlessy

My setup is

CPU: 1497 MHz

GPU: 330 MHz

Saturation: reduced to 20

Nice work [MENTION=3873953]eng.stk[/MENTION] :)
[OnePlus X Original Android Development] mohammedtabish:
Thnks mate now hoping for custom rom...and i just flashed the kernel gonna test it :)
[OnePlus X Original Android Development] loveboy_lion:
Updated to rt37 from r25 no bootloops everything working fine for now thanks
[OnePlus X Original Android Development] sydeu:
I'm on r25 right now and it's working flawlessly, worth it to flash r37? :)
[OnePlus X Original Android Development] Roykooiman:
I moved to r36 just 5 min ago from r25, why should it not be better to upgrade.

Verstuurd vanaf mijn ONE E1003 met Tapatalk
[OnePlus X Original Android Development] mohammedtabish:
Good work just flashed r37 n its quite smooth and faster than r25
[OnePlus X Original Android Development] RinoFxx:
Did you guys flash r37 above r25 without flashing anything else?

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] mohammedtabish:
Yes just flash it and wipe cache+dalvik cache
[OnePlus X Original Android Development] Roykooiman:
Just dirty flashed only wiped cache twice

Verstuurd vanaf mijn ONE E1003 met Tapatalk
[OnePlus X Original Android Development] Bitman64:
wiped cache/dalvik

flashed kernel (r37)

wiped cache/dalvik

..... worx like a charme ....

Gr. B.

PS... came from Stock
[OnePlus X Original Android Development] anremi:
no wipe for me.

Dirty flash. It's smooth !

Undervolt : offset global -60mV
[OnePlus X Original Android Development] bubbl3:
Works for me too now, thank! (Upgraded from r25)
[OnePlus X Original Android Development] parasthakur37:
Guys all of you who've changed their partitions from ext4 to f2fs I want to ask you all if there's a performance boost? Because the whole point of changing is to gain performance (both multitasking and gaming) and smoothness, so if there is please tell and I'll change mine accordingly.
[OnePlus X Original Android Development] eng.stk:
Yes you will notice improvements in opening apps, multitasking, scrolling and overall general smoothness.
[OnePlus X Original Android Development] sydeu:
If we want to convert to f2fs we need to do a full wipe right? I've read that data can be restored after converting is that correct?