yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M8)] dottat:
Have you tried a different sim card?
[Verizon HTC One (M8)] thekwijibo:
The day before I went to the Verizon store and swapped out SIM cards. Interestingly enough, when I walked into the store the SIM was detected, and the phone worked fine. I swapped the SIM anyways. The phone worked great for about 12 hours until the SIM pooped out again, and now it hasn't worked since. I might see if I can stop by the store again, since I already did another RUU and running stock.
[Verizon HTC One (M8)] thekwijibo:
*Update*

Just got back from the VZW store. New SIM card, and presto. Works like a charm....but for how long?

The tech said that it is likely a hardware issue, and suggests a replacement phone under warranty.

I suppose I now have to research how to do the true S-On factory reset process.
[Verizon HTC One (M8)] dottat:
It's not hard but I hope you don't need that.
[Verizon HTC One (M8)] thekwijibo:
Do you hope I don't need the guide? Or hope I don't need to go through a warranty replacement?

If I get a factory replaced M8, the threat of toasting another SIM card goes away and I get a new phone.

However, I'll loose S-Off, and might have to try my luck with Sunshine, unless there's another method out there that has surfaced in the past year or so.

So far in this week my M8 has "fried" two separate SIM cards. I'm using a third right now after my second trip to the VZW store, and I'm eying my phone frequently, expecting to see the dreaded "No SIM Card" error once again. (going on 20 hours strong now under very very light use) However, it has the tenancy to die at the worst possible time, like calling for a ride from the airport. I haven't seen anything in any forums about this happening that is related to any setting, ROM, etc. I am leaning on the side that it is indeed hardware related.

I'm open ears as to anything I've overlooked, or any suggestions on how to avoid another SIM failure. For the time being, I might just use it until it kills my 3rd SIM card and go for a warranty replacement.
[Verizon HTC One (M8)] thekwijibo:
3rd SIM card died the other day. Flashed stock, going to S-On for warranty replacement. :(
[Verizon HTC One (M8)] dottat:
Sounds more like the modem itself is toast.
[Verizon HTC One (M8)] tobalaz:
I know I'm late on this one, but had the same issue.

All I did was pull the sim, clean it with a qtip and alcohol and blew out the sim slot with a can of compressed air.

6 months later, no problem.
[T-Mobile LG G5 Guides, News, & Discussion] Dozenboy0012:
Here is something I found maybe others haven't but I guess minus the app drawer seemed to ruffle a few feathers here's how to get it bacc.
[T-Mobile LG G5 Guides, News, & Discussion] wolfu11:
Already been covered a while back but today I got an update for home 5.0 see pic.

Much smoother than home 4.0

View attachment 3732862

View attachment 3732866

View attachment 3732869

View attachment 3732870
[T-Mobile LG G5 Guides, News, & Discussion] srimay:
Where's the 3rd screen shot come from. App updates.? Is that from LG smartworld app?
[T-Mobile LG G5 Guides, News, & Discussion] hungmung:
Settings>about phone>update center>app updates
[T-Mobile LG G5 Guides, News, & Discussion] srimay:
Thanks they still didn't add a option for screen grid size
[T-Mobile LG G5 Guides, News, & Discussion] rebar71:
Good to see they brought the app drawer back. Did they also bring back the ability to re-arrange your home screens? That was a bigger annoyance to me and the main reason I installed another launcher.
[T-Mobile LG G5 Guides, News, & Discussion] wolfu11:
yes its there too
[T-Mobile LG G5 Guides, News, & Discussion] scottricketts:
Is there anything compelling here that would make it worth using over Nova?
[General Questions and Answers] Ritchiejoe:
After the upgrade to 6.0.1 I began to experience high levels of battery drain which has been attributed to the process "mediaserver" by the battery application I use.

I have tried the following.

- Clearing cache

- Going back to complete stock and fresh install of all the app's I use via the Play store.

I'd appreciate any suggestions on how to rectify this problem :fingers-crossed::cowboy:
[General Questions and Answers] DevUt:
Media server is songs and other stuff do you listen to them a lot?
[General Questions and Answers] Ritchiejoe:
No I have no Music or photo's on my phone. Photo's I access through cloud storage accounts but they are not in my actual storage. as for music I use my ipod or rarely youtube.
[General Questions and Answers] DevUt:
Can you give the detailed info by Gsam on mediaserver
[General Questions and Answers] Ritchiejoe:
Hi Dev,

Sorry for the delayed reply I missed this notification.

I have attached the requested screen shots.
[General Questions and Answers] DevUt:
Try this : Delete all small files in your SD card (which wait few KB)

And try this app https://play.google.com/store/apps/details?id=com.rrr.android.mediaserverkiller&hl=en
[General Questions and Answers] Ritchiejoe:
Already tried both but appreciate the suggestion :good:
[E 2015 Q&A, Help & Troubleshooting] billard412:
Was running total stock with stock recovery (Unlocked BL tho). Latest update (attached) flashed without a hitch and upon boot, hangs on the Motorola logo. Anybobdy else experience this?

UPDATE:

Restored previous system and boot image and it booted without issue. Said the update was complete upon boot despite being the old system. Then, almost immediately tried to re-update (which i assume would brick it due to it already having the new bootloader). Look forward to feedback cuz this got me bummed.
[E 2015 Q&A, Help & Troubleshooting] 903tex:
You can't take ota updates if you updated the Bootloader past 5.1 Bootloader. So if you want to run the latest firmware but keep stock flash a custom stock ROM. Or better just flash cm12.1
[Wileyfox Storm] jcadduono:
Team Win Recovery Project 3.0.2

Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!

I am currently looking for users to test all the features and report back with what works.

Quote the 2nd post and put a pass or fail in each of the [ ] boxes!

Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log

adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log

WHAT IS TWRP?

Oh come on, you know what it is - don't try to fool me!

In case you're serious, though...

Team Win Recovery Project is a custom recovery for Android devices.

It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

DOWNLOAD

You can find the device page here:

https://idlekernel.com/twrp/kipper/ (temporary! THESE ARE TEST BUILDS!)

Find instructions on how to unlock and root your device with fastboot here:

https://twrp.idlekernel.com/devices/wileyfoxstorm.html (temporary device page - do not download from here!)

CHANGES

v3.0.2-0 - See here for the changes.

FEATURES

MTP support

USB Mass Storage support

Micro SDcard support

f2fs file system support (read, write, format, backup & restore)

exFAT file system support (read, write, format)

NTFS file system support (read, write)

ADB root

Full SELinux support

Built in android 6.0 tree

KNOWN ISSUES

Brightness node not set (unknown location, join #twrp to help!)

Battery status possibly unknown

CONTACT & SUPPORT

You can find us on IRC at #twrp on chat.freenode.net.

You can also post in this thread and I will attempt to answer any questions you may have.

SOURCE CODE

Device tree: https://github.com/jcadduono/android_device_wileyfox_kipper

Kernel sources: https://github.com/jcadduono/android_kernel_cyanogen_msm8916/tree/twrp-6.0

TWRP: https://github.com/omnirom/android_bootable_recovery

CONTRIBUTIONS

Gerrit for TWRP: http://gerrit.omnirom.org/

Gerrit for officially supported devices: http://gerrit.twrp.me/

XDA:DevDB Information

Team Win Recovery Project - Wileyfox Storm, Tool/Utility for the Wileyfox Storm

Contributors

jcadduono, The Team Win Recovery Project team

Source Code: https://github.com/jcadduono/android_device_wileyfox_kipper

Version Information

Status: Testing

Current Beta Version: 3.0.2-0

Beta Release Date: 2016-04-27

Created 2016-04-28

Last Updated 2016-04-29
[Wileyfox Storm] jcadduono:
TWRP functional checklist

Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page

Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level

Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
[Wileyfox Storm] Johndawolf:
I really want to see this get done but I don't have time to test everything right now. Done some basic tests, will edit with the rest whenever I have the time to do so.
[Wileyfox Storm] aciupapa:
Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?
[Wileyfox Storm] image45:
Flashed twrp-3.0.2-0-test3-kipper.img and found unable to use mirco SD card as available storage.

Previously had TWRP-2.8.7.0-kipper-recovery on device, however after updating to CM13 this was unable to find/use micro SD card as available storage too.

Marshmallow issue or recovery one.
[Wileyfox Storm] aciupapa:
To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
[Wileyfox Storm] image45:
So create a TWRP backup, install cos12 then simple restore the back and should work?
[Wileyfox Storm] aciupapa:
Yes. I use it like this now

---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------

But after flashing cos12 reboot into recovery ans check if partitons mount
[Wileyfox Storm] image45:
I Google for a TWRP cos 12.1.1.zip however no joy.

Fail to install via a custom recovery users advised.

The issue only occurred after I installed CM13, that's when TWRP couldn't find microsd storage.
[Wileyfox Storm] aciupapa:
Go to cyngn.com/support and look for zip withouth fastboot in name
[Wileyfox Storm] image45:
Installed the none fastboot cos 12.1.1 zip via recovery, then let it run the install build, however when I rebooted into recovery I was unable to get the external sdcard to be accessible still.

Thanks for suggested fix. :good:
[Wileyfox Storm] aciupapa:
Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?
[Wileyfox Storm] image45:
I made TWRP backup of my current CM13 ROM, then wiped all partitions except internal and external SD card storage. Installed cos12.1.1 zip within TWRP, then rebooted to let stock lollipop ROM initialised. Then rebooted to TWRP to find external SD still not found.
[Wileyfox Storm] aciupapa:
Maybe try reflashing twrp
[Wileyfox Storm] image45:
I tried reflashing TWRP-2.8.7.0 recovery, then twrp-3.0.2-0-test3-kipper, cm-13.0-20160305-recovery and final cm-12.1-none-sign-recovery.

None of them could find the external SD card only internal storage. Would love to say it worked however sadly not. When on stock lollipop 5.0.1 all the recovery storage paths worked, so you would think installing cos 12.1.1 zip would restore things.

Have noticed that the original boot loader has returned, but not the battery charging while powered down image that you see getting fuller if you hit the power button. The original one was much larger under stock.

What's the function of the image file compared to the zip one please?

cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img
[Wileyfox Storm] image45:
Did a final version get abandoned after the test 3 release?
[Wileyfox Storm] Blinkin89:
Probably to less tests?

I loved TWRP on my good old S2 (which seems to have NAND rw corruption since last week). Now I have the Storm I would love TWRP on my device too, but it needs proper testing.

I'm wondering: what are the risks of testing this? I might be able to help. :)
[Wileyfox Storm] image45:
Well I have the test 3 one running on my storm, no issue's found.
[Wileyfox Storm] Blinkin89:
Ok thanks. I'll try flashing it. :)
[Wileyfox Storm] image45:
Link updated in next post

None test version here
[Wileyfox Storm] image45:
None test version here

TWRP-3.0.2-1-kipper.img

Marshmallow based device tree

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

Extra storage points and increased number of back up partitions, test 3 removed from build number.

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

TWRP 3.1.0-0.img

Only for the bootloader from 13.x with the fix for SD, not just a picture, but the MENU in fast-boot mode. Recommended only with Android 7.1.2

https://www.androidfilehost.com/?fid=745425885120718899
[Wileyfox Storm] RBredereck:
Hi, I am using the lastest stock rom and could successfully (but temporarily) flash and boot "TWRP 3.1.0-0.img" and "TWRP-3.0.2-1-kipper.img". However, both versions are unable to mount /system (it says that this partition does not exist).

I guess I will need to mount system to root my device. Can someone help?
[Wileyfox Storm] image45:
I made the mistake of installing the stock ROM ( That's the TOS 7.1.2 ) and found that the TWRP recovery could not mount system as I believe it was in the /dev/block/mtdblock0 /system yaffs2 file format rather than Ext4. I was not able to flash update-supersu or Magisk.zip to achieve systemless root. The update flashed a new emmc_appsboot.mbn file that caused my TWRP backup to stall on boot due to it needing the COS 13.1 bootloader.

I returned to the linage 14.1 OS for Wileyfox storm ROM, after flashing COS 13.1 bootloader and splash screens. I also had to restore/ format system partion to Ext4 before so TWRP could mount successful.

Yes the commonest rooting methods use boot.img patching via TWRP recovery to achieve systemless root for nougat.

This is the case with TWRP-3.0.3.0-kipper.img too then.

Robert
[Wileyfox Storm] ghertas:
TWRP-3.2.1-0.img for Wileyfox Storm

download

https://androidfilehost.com/?w=profile&uid=457095661767144032
[Wileyfox Storm] 1f5:
Could you please make official TWRP builds?
[Wileyfox Storm] Zugschlus:
Hi,

I would like to know whether there is a possibility to get a TWRP version that can actually access the SD card and/or (preferably for me) an USB OTG memory device. The advice given in this thread to flash an original Cyanogen OS cannot be used today since cyngn.com is gone.

Any ideas?

Or does one have a spare image of COS 12 around that I can snarf from somewhere?

Greetings

Marc
[Wileyfox Storm] ghertas:
https://androidfilehost.com/?w=files&flid=59917
[Wileyfox Storm] Zugschlus:
Hi,

on that link I found cm-12.1-YOG7DAS2FI-kipper-signed-9b353dd59a.zip which didn't run when just installed with adb sideload (booted, showed the logo, booted, showed the logo , ad libitum). After I wiped the entire device and a new adb sideload, the OS now runs, and my USB stick on the USB OTG adapter is correctly detected.

This does, however, not solve the issue: When I boot into TWRP 3.2.3, the device still doesn't see the USB OTG adapter. I only see the internal memory and a (not inserted) SD card of 0 bytes capacity.

Any more ideas?

Greetings

Marc
[Sprint HTC One (M8)] Hitira38:
So I tried to root my M8 with this site and now it doesn't work. I don't know what to do... Can someone guide me through this?

htconeroot.com/htc-one-root/how-to-root-htc-one-m8/

I just want to play my zombie game again I am never going to try and root my phone.. Please,, someone help me..

:crying:

:crying:

:crying:

:crying:
[Samsung Galaxy S7 Edge Questions and Answers] luieavila:
I'm having an issue where after taking a picture, I go to review the picture by tapping the small preview on the bottom right corner. I get to see the picture and when I hit the back button to go back to the camera the phone will freeze for a few seconds. The most has been about 10-15 seconds. Its happening a lot more. I've force closed, cleared data, forced stopped and still same issue. I have done one factory reset and same issue. I actually have two S7 Edge that are doing the same thing. Any thoughts? Help would be greatly appreciated! :confused::good:
[Wileyfox Swift] jcadduono:
Team Win Recovery Project 3.0.2

Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!

I am currently looking for users to test all the features and report back with what works.

Quote the 2nd post and put a pass or fail in each of the [ ] boxes!

Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log

adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log

WHAT IS TWRP?

Oh come on, you know what it is - don't try to fool me!

In case you're serious, though...

Team Win Recovery Project is a custom recovery for Android devices.

It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

DOWNLOAD

You can find the device page here:

https://idlekernel.com/twrp/crackling/ (temporary! THESE ARE TEST BUILDS!)

Find instructions on how to unlock and root your device with fastboot here:

https://twrp.idlekernel.com/devices/wileyfoxswift.html (temporary device page - do not download from here!)

CHANGES

v3.0.2-0 - See here for the changes.

FEATURES

MTP support

USB Mass Storage support

Micro SDcard support

f2fs file system support (read, write, format, backup & restore)

exFAT file system support (read, write, format)

NTFS file system support (read, write)

ADB root

Full SELinux support

Built in android 6.0 tree

KNOWN ISSUES

Brightness node not set (unknown location, join #twrp to help!)

Battery status possibly unknown

CONTACT & SUPPORT

You can find us on IRC at #twrp on chat.freenode.net.

You can also post in this thread and I will attempt to answer any questions you may have.

SOURCE CODE

Device tree: https://github.com/jcadduono/android_device_wileyfox_crackling

Kernel sources: https://github.com/jcadduono/android_kernel_cyanogen_msm8916/tree/twrp-6.0

TWRP: https://github.com/omnirom/android_bootable_recovery

CONTRIBUTIONS

Gerrit for TWRP: http://gerrit.omnirom.org/

Gerrit for officially supported devices: http://gerrit.twrp.me/

XDA:DevDB Information

Team Win Recovery Project - Wileyfox Swift, Tool/Utility for the Wileyfox Swift

Contributors

jcadduono, The Team Win Recovery Project team

Source Code: https://github.com/jcadduono/android_device_wileyfox_crackling

Version Information

Status: Testing

Current Beta Version: 3.0.2-0

Beta Release Date: 2016-04-27

Created 2016-04-28

Last Updated 2016-04-29
[Wileyfox Swift] jcadduono:
TWRP functional checklist

Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page

Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level

Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
[Wileyfox Swift] Epmak:
Blocking checks

[pass] - Correct screen/recovery size

[pass] - Working touchscreen

[pass] - Backup to internal/microSD

[pass] - Restore from internal/microSD

[pass] - Reboot to system

[fail] - ADB & ADB shell

[pass] - Flash zips in Install page

[pass] - Flash boot.img/recovery.img using Flash Image in Install page

Medium checks

[ ] - Flash zip with ADB sideload

[pass] - UI colors (red/blue inversions)

[pass] - Screen goes off (and back on :))

[pass] - EXT4 support (wipe/format/restore to)

[ ] - F2FS support (wipe/format/restore to)

[ ] - exFAT support (wipe/format)

[ ] - NTFS support (wipe/format)

[pass] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices

[fail] - Decrypt encrypted /data

[pass] - MTP read/write

[pass] - USB Mass Storage read/write

[pass] - Set brightness level

Minor checks

[pass] - Reboot to bootloader

[pass] - Reboot to recovery

[pass] - Power Off

[pass] - Battery level

[pass] - Temperature

[fail] - Encrypted backups

[pass] - Vibration

[pass] - Screenshot
[Wileyfox Swift] jcadduono:
Thanks! You're sure adb isn't working? I can't find any reason it wouldn't. :S

I will try CM 13.0 decryption libs instead of CyanogenOS, maybe that will help with encryption.

For the third item, encrypted backups - you were unable to backup say...system, and use the encryption option in the options page?

(if that is so, can you get me a log trying to make an encrypted backup?)
[Wileyfox Swift] Epmak:
Yes, i plug phone usb cable.

adb shell

see

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device not found

adb working in another UNOFFICIAL TWRP beroid

I use the encryption option, backup can't encrypt.

See log files.
[Wileyfox Swift] jcadduono:
i don't see any error in the log for encrypted backup? it saved fine?

uploaded test3 if youre up for trying again!
[Wileyfox Swift] ryzened:
I'm planning on giving this a run through later (possibly later in the week), but I needed to clarify something in the mean time:

Do the above requirements apply to the SDcard, or just the phone internal storage?

(My phone is currently encrypted, so I'm currently stuck with an older CM13 build, so have to flash anew. I haven't tested restoring from backup, and I'm hesitant to potentially lose access to a certain app right now.)

The list of mountable partitions includes a partition named "persist", unsure if this is of any relevance?

Additionally, comparing the Swift's fstab in TWRP to others, it would appear that it might be lacking in the encryption related flags on some mounts?

Also, thanks! :)
[Wileyfox Swift] jcadduono:
I suppose you can ignore NTFS as the Swift doesn't support OTG storage anyways.

exFAT/vfat/f2fs would apply microSD cards.

ext4/f2fs would also apply to data, however you would need a rom with a kernel/fstab capable of taking advantage of that.

I can remove persist from the fstab, it probably shouldn't be there anyways.

Explain what you think is missing related to encryption? I believe I have everything.

When backing up data, it will be unencrypted unless you select the encrypt backup option (even if the partition is already encrypted), and when restoring a data backup, it will be whatever the partition currently is (if the filesystem is encrypted, then restoring unencrypted data backup will still keep your data partition encrypted), unless you use the [Format Data] button on the Wipe page to remove encryption from the data partition.