yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 Edge Questions and Answers] cyaclone:
Is there any progress in finding the solution to open the bootloader for these units?

Or is this just a lost cause and the bootloader for these units will always be locked.

No TWRP or ROMS to load to get rid of TW. Sad.
[Samsung Galaxy S7 Edge Questions and Answers] Misterjunky:
re: rooting and rom'ing

It's a lost cause, the bootloaders for snapdragon will remain locked forever.

It's not like most other bootloaders which are all rootable with proper software.

The snapdragon bootloaders are infused in the phone's hardware.

Next time when you purchase a Samsung phone be sure it has the Xynos cpu

chip and rooting will be a breeze. (took me a full minute to root)

All Samsung Galaxy phones which have the Xynos chip are not

only easily rootable but they all come factory sim unlocked.

Good luck, have a great day!
[Samsung Galaxy S7 Edge Questions and Answers] cyaclone:
Thanks for the response. Very Sorry, like most of us, that this is a done deal!
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
Dropped my naked & beloved Note3 onto the concrete.

Screen is cracked, wacom encoder still seems good (, but I'll test it more thoroughly tonight.)

Have any of you replaced (or used a repair service to replace) only the cover glass?

Comments on your experiences are welcomed - costs, places selling parts, bad experiences, things to watch out for, etc.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] donc113:
Ouchie! Bad! I'd say tongue in cheek, since it's gorilla glass, use gorilla glue... But that'd be bad.... I'd suggest a whole display assembly but have zero experience so can't say for sure.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
First quote I got from a repair service is $190 "out the door". About $130 for the LCD+Wacom Digitizer+Glass assembly and $50+tax for labor.

I understand the issue is that the gorilla glass is glued to the digitizer, so repair shops regard the process of cover glass replacement to be too risky/involved to deal with.

Found a video on youtube of a guy doing it... he said something like "you've got to get the glass too hot to touch in order to melt the glue" and "it takes about 45 minutes to carefully remove the glass". Ugh.

Maybe I'll price out LCD assemblies and do the work myself... anybody know a reputable parts supplier that is NOT in Hong Kong / China / Taiwan ?
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] Sczar:
I dealt with (Etrade Supply) before and they are pretty good.

I once tried to replace my gorilla glass and it was a bad experience. The Digitizer part was so fragile I destroyed it lol.

so I had to buy a full LCD+Wacom Digitizer+Glass assembly. That was way back.

I think if you are willing to spend a $150 + your time to install it. mine as well buy a used Note 3 from Ebay they run now around $150 to $180.

Good luck to you Sir and sorry to hear what happened to your phone.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bftb0:
Thanks. I looked at a bunch of those LOCA gluing vids on youtube and started pricing things (both parts and used phones) last night, and came to pretty much the same conclusion.

I suppose I could buy a used phone and attempt the less expensive (glass replacement) repair method - if it succeded, I could resell either of the two. And there would be no reason to hurry the repair that way.

I'll get it squared away eventually. I'm hoping to find an OEM part number list someplace - I get the impression that there are a ton of grey/aftermarket replacement parts (eg non-laminated, untempered glass lens or even non-Wacom digitizers), and there are sellers that don't pay attention to those details (or just flat-out misrepresent junk as something else).
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] willclein:
So I just encrypted my phone when I was prompted to do so by Outlook as part of my company's security policy. I begrudgingly complied and now am unable to boot into my phone as it sits at the boot screen. When I try to boot into TWRP, it asks for my password. I used a PIN to set up the encryption, and TWRP asks for a password. When I use my PIN, it appears to decrypt the partition and mount, but then while loading, TWRP shows a continuous stream of

E:Error parsing XML file

errors until it just restarts. My problem is that my backup is on my system partition (I know this was dumb, but I forgot to move it back to my SD card last night after formatting it.) so I have no way to restore the backup.

Anyone have any suggestions? I'd hate to have to completely reset my phone again.

Specs -

Device: Galaxy S4 SPH-L720

ROM: Team OctOS Oct-N (Nougat 7.1.1)

Recovery: TWRP 3.10
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Mattcam:
Hi everybody,

I am now using a Galaxy tab 2 P5110, running under Android 4.1.2, not rooted.

My problem is that my Tab is really slow when I use basic apps (chrome, office apps).

In order to get a bit more power from it (removing the Samsung layout, but I know it's a 2012 tablet...) I am looking for the most stable ROM I could use, and if possible running under a quite recent android version.

I am quite new to this kind of manipulations, so I am also looking for a tutorial to instal the ROM you could advice me.

I know I have to root my tab before doing anything. Does the tutorial available here (https://xdaforums.com/showthread.php?t=1657056 - by Weltwon) work with 4.1.2 android version?

Thank you all for your answers!

Matthieu

------------------

Edit: I have an other question. Is the root enough to remove the Samsung touchwizz layer? If yes, how to do it?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] GuestD2200:
Lineage OS 13.0

You could get a Lineage OS 13.0 nightly, and from my experience those are fairly stable.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tasnim_tamim:
For starters if you want to get rid of TouchWiz you can remove all of the bloatware and Samsung apps (like TouchWiz home, AccuWeather widget, Samsung Apps, Group play).

But I recommend just install custom ROM. Maybe cm11 or cm12.. I am using Dhollmen 4.4.4 on my tab for 1 years and it is working very well for me.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] Mattcam:
Thank you for your advices,

[MENTION=7334657]tasnim_tamim[/MENTION]: I dont know Dohllmen. Is it à cyanogenmod Android version? Which tab do you run under this ROM?

[MENTION=7059214]orionboughton[/MENTION]: are nightly versions if lineageOS stable? I have heard that these are update vert often, and some Android functionality can be disabled
[Galaxy Tab 2 Q&A, Help & Troubleshooting] tasnim_tamim:
Its a ROM based of SlimROM.. I am running it on my galaxy tab 2 7.0 p3100
[Galaxy Tab 2 Q&A, Help & Troubleshooting] GuestD2200:
Lineage OS 13.0

Lineage OS is basically an updated version of Cyanogenmod, so i guess that's what it's based off of.

I've been running a nightly of Lineage OS from their website at https://download.lineageos.org/espressowifi , and it's really smooth compared to touchwiz and the ram is managed much better. The camera works, the gyroscope works, and I've only had one or two problems (like root not being enabled out of the box, and needing to flash a supersu zip to get that running), and besides that it's all good. If you have a problem, rebooting usually fixes it and I've rarely had to do that in the past few weeks I've been running it.

Another plus is it runs android 6.0, which seems to be better in every way. Great standby time, 4h or more screen on time, etc.

However if you do decide to get it, make sure to flash with the latest version of twrp, and if not you might softbrick your device.
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] rivierakid:
I'm also dissapointed that the OS is far from the pure AOSP.

But it is possible to tweak it without losing the future OTAs:

1. Install google launcher, google messenger

2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/

3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
That is also a possibility but:

1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way

2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine

And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there :)
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] rivierakid:
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.

I'm not sure...

You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.

But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...

The final solution for this is LineageOS, if they provide the source :)
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] jdtanner:
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!

*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*

JT
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).

Reverting all of that, your system will go back as it came with the Nougat OTA.
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] MCPoppa:
Hello,

thanks for your effort to the community.

I have a question.

How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.

To repair this I flashed the newest "system.img".

But I can't replace my stock recovery.
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] jdtanner:
Any chance of updating debloater to change the UI colour scheme from orange back to blue? :)

JT
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command

fastboot flash recovery <name-of-the-file>.IMG

Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.

I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions ;)
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] MCPoppa:
Everytime i installed twrp i got stuck in a bootloop :/
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] MCPoppa:
Still doesnt let me boot up after I installed your debloat zip.

Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.

I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.

When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.

I think it has something todo with the update to Nougat.

How did you bring it run on your device?
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
I explained it last night here, but I also stated it in the OP:
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] MCPoppa:
Thanks, i've installed magisk mask again and the message didn't appeared.

I've also flashed your debloater and everything works fine.

Can I now flash TWRP or do I have to boot it up via fastboot everytime?
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine ;)

Cheers!
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.

I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.

In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).

I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change :)
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] Ianharding:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".

Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] linuxct:
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.

For magisk: are you

sure

you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.

My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly :)
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] digidude512:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
[Wileyfox Swift 2 ROMs, Kernels, Recoveries, & Othe] bjlabuk:
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article

I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.

Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?
[Samsung Galaxy S7 Questions and Answers] martyxng:
On the international Galaxy S7 (G930F) - How do I get the Nougat OTA update on Straight Talk (AT&T SIM) in the USA? I've tried manually checking for updates, but it says it's up to date. Everyone I've talked to on AT&T (without an MVNO) seems to have received the update already. Do I need to do something different because it's the international version, or because it's on an MVNO? I'm on the stock firmware.
[Samsung Galaxy S7 Questions and Answers] *Detection*:
Flash stock Nougat firmware for the G930F?

Pick a CSC such as XEU or BTU?
[Samsung Galaxy S7 Questions and Answers] martyxng:
Is that the only way to get it on an MVNO? I was hoping for a low-risk OTA upgrade instead of worrying about flashing the right firmware but can certainly do a manual flash if that's the only way.
[Samsung Galaxy S7 Questions and Answers] *Detection*:
If your carrier has not / will not send out the OTA, then manual flashing is the only way, luckily for you the G930F is the most popular / compatible of the S7s
[Android Q&A, Help & Troubleshooting] fanatik15:
Hi I have problem with download firmware for XperiFirm because program say error N/A near all firmware

pls help...

[IMG="xpefirm error"]http://www.imgup.cz/images/2017/04/10/xpefirm.jpg[/IMG]
[Android Q&A, Help & Troubleshooting] fanatik15:
Problem FIX ... XperiFirm not work on Windows XP
[Galaxy S3 Neo Q&A, Help & Troubleshooting] planethackz:
I want to know if this error means hardware fail...and time to say farewell to my device? No matter on stock or CM or LP motion rom...the error remains same. No clue what the problem seems to be..?:confused:
[Galaxy S3 Neo Q&A, Help & Troubleshooting] mitu725:
bro , ur sim socket is normal or broken ?? check it :)
[Galaxy S3 Neo Q&A, Help & Troubleshooting] planethackz:
I just unscrewed the back..sim tray looks intact...I know nothing about circutry:cyclops: as im a pharmacist.I will take a trip to the technician today...see what happens...
[Galaxy S3 Neo Q&A, Help & Troubleshooting] mitu725:
Hmm Bro That would be right :good: :o
[Nexus 4 Original Android Development] Ziyan:
The Unlegacy Android Project​

Introduction

Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.

On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for mako include:

- Linux kernel 3.4.y merged in (currently 3.4.113 - mostly security patches and minor bug fixes)

- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority

- F2FS support from kernel 4.9 (for /data only! no point of f2fs on /cache)

- SELinux in Enforcing mode

Installation

If you're planning to install GApps, be sure to read the second post!

Aside from that, installation and upgrading is no different than on other ROMs.

Problems

- No known issues for mako yet.

If you notice anything, be sure to report it in this thread. Stability is our main concern. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.

Downloads

See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds :)

We will have a built-in OTA updater (just like stock) soon (it's a work in progress) :)

Features?

There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.

As usual, feedback is appreciated :)

XDA:DevDB Information

Unlegacy Android Project, ROM for the Google Nexus 4

Contributors

Ziyan, amaces

Source Code: https://github.com/Unlegacy-Android

ROM OS Version: 8.x Oreo

ROM Kernel: Linux 3.4.x

Version Information

Status: Stable

Current Stable Version: 7.1.2

Current Beta Version: 8.1

Created 2017-04-10

Last Updated 2018-09-04
[Nexus 4 Original Android Development] Ziyan:
Reserved

GApps

If you want to install GApps, we recommend Open GApps Micro.

An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.

In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.

Stock-like setup

Disable the following built-in (AOSP) apps:

- Android keyboard (once you installed Gboard)

- Browser

- Calculator

- Camera

- Clock

- Email

- Gallery

Install the following apps from the Play store:

- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)

- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)

- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)

- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)

- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)

- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)

- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)

- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)

SafetyNet

The ROM should pass SafetyNet after installing GApps, without anything else. Keep in mind that installing extra stuff (SU, ...) might make it fail!

Rooting

You can flash the latest Magisk to get rooted.
[Nexus 4 Original Android Development] zaclimon:
Just a little note on this, I've been testing his build and it's been really smooth so far. (Even more than my own AOSP build) Also for other ROM's devs out there, he's the original dev who fixed the sensors and he also fixed the camera without relying on AOSP hacks. (Well except SELinux but that's another thing...) You can check out the source for more info about it.

Because I didn't have much time to work on it, I want to thank [MENTION=2633638]Ziyan[/MENTION] for his work on this. I could even say that eventual people who are currently on the AOSP build should go on this one moving forward. :)
[Nexus 4 Original Android Development] ze7zez:
From 1 February I check ROM periodically. For now ROM is not for me. It is too raw.

There are no navigation buttons

for me

and I can not disable them if I want to use Button Savior, for example. ROM does not see WiFi 5GHz.

However, I am pleased that there's a thread on XDA.
[Nexus 4 Original Android Development] jer_ying_fd:
Forgive me if it has already been posted in the gapps thread, but is open gapps working for 7.1.2 builds? Last I checked, it was reported that setupwizard crashes on 7.1.2 due to being outdated. Thx!
[Nexus 4 Original Android Development] Has_anDroid:
Thanks not work gapps setup wizard screen
[Nexus 4 Original Android Development] Ziyan:
Never heard about the navigation button issue... Might investigate it if I can get more feedback or reproduce the issue :)

About 5 GHz, it seems to work fine for me: View attachment 4108596

Yeah, Open GApps has a problem with setup wizard on 7.1.2 at the moment. I hope they'll fix it soon... :rolleyes:
[Nexus 4 Original Android Development] jer_ying_fd:
Thx for confirming! For now I'll anxiously wait with the build already on my laptop ready to flash when the gapps are :P