yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] Arju:
If you haven't tried it at all then first try to do a factory reset from recovery. If that doesn't work and if you're on stock and have stock recovery. Download ota: https://developers.google.com/android/ota and see if you can push it to phone using fastboot if you can't access storage of course. And then apply update in recovery. You should be able to boot then.
[Android Software Development] clcombs262:
Hello all you modders and power users and others!

We are very pleased to announce our new ROM, lunaOS!

Current status is internal testing only, with a beta or alpha release to the public scheduled for 4th quarter 2019.

Built off of the popular lineageOS source and with a bit of AOSP and AOSiP, you are guaranteed a stable and fast ROM. With code level battery and performance optimization you'll experience speed like never before, all without sacrifice of battery life

Features (this list may change and is not a promise of anything):

- Magisk built in, providing access to hundreds of modules

- High performing even on low end

- Substratum system service allows you to theme to the max

- Developed with care and handcrafted experiences

- Highly stable and fast

- Customizable to the absolute maximum

- the list goes on and on

Join our telegram group @Lunaos for announcement and feedback/support

XDA:DevDB Information

The lunaOS Project, ROM for all devices (see above for details)

Contributors

clcombs262, itexpert.120, M.A.P, alexiacortez, everyone on the lunaOS Project Team, Innonetlife

Source Code: https://github.com/lunaOS-ROM

ROM OS Version: 9.x Pie

ROM Kernel: Linux 4.x

ROM Firmware Required: Unlockable bootloader

Based On: Primarily lineageOS, some from AOSP

Version Information

Status: Testing

Current Beta Version: 0.0.1-privatebeta-13

Beta Release Date: 2019-06-05

Created 2019-06-09

Last Updated 2019-06-09
[Android Software Development] aydinbahadir88:
very nice it is getting more ;)

Will there be synonymous for Pixel 3 XL?
[8525, TyTN, MDA Vario II, JasJam ROM Development] superman13:
Hello,

i like faria32 rom with this options i dont know whats name of the progs

http://img142.imageshack.us/img142/9199/92635098fc6.jpg

http://img291.imageshack.us/img291/8316/46320619ex5.jpg

i use tnt professional and i missed this progs

where i cant find the cabs please.

Big thanks
[8525, TyTN, MDA Vario II, JasJam ROM Development] blackout128:
Here you go.
[8525, TyTN, MDA Vario II, JasJam ROM Development] egoist6:
the first one is htc task manager.

not sure about the second one, maybe htc large start menu

----

doh. i was too slow...
[Android Software Development] clcombs262:
Hello all you modders and power users and others!

We are very pleased to announce our new ROM, lunaOS!

Current status is internal testing only, with a beta or alpha release to the public scheduled for 4th quarter 2019.

Built off of the popular lineageOS source and with a bit of AOSP and AOSiP, you are guaranteed a stable and fast ROM. With code level battery and performance optimization you'll experience speed like never before, all without sacrifice of battery life

Features (this list may change and is not a promise of anything):

- Magisk built in, providing access to hundreds of modules

- High performing even on low end

- Substratum system service allows you to theme to the max

- Developed with care and handcrafted experiences

- Highly stable and fast

- Customizable to the absolute maximum

- the list goes on and on

Join our telegram group @Lunaos for announcement and feedback/support

XDA:DevDB Information

The lunaOS Project, ROM for all devices (see above for details)

Contributors

clcombs262, itexpert.120, M.A.P, alexiacortez, jmpf_bmx, everyone on the lunaOS Project Team, Innonetlife

Source Code: https://github.com/lunaOS-ROM

ROM OS Version: 9.x Pie

ROM Kernel: Linux 4.x

ROM Firmware Required: Unlockable bootloader

Based On: Primarily lineageOS, some from AOSP

Version Information

Status: Testing

Current Beta Version: 0.0.1-privatebeta-13

Beta Release Date: 2019-06-05

Created 2019-06-09

Last Updated 2019-06-09
[Android Software Development] itexpert.120:
Yay!
[OnePlus 7 Questions & Answers] Linuxkek:
You got any issue with VoLTE or Wifi-Calling?
[OnePlus 7 Questions & Answers] romanlink:
I had this problem. Oddly what solved it was removing the sim and factory reseting then putting the sim back in. Volte finally worked after that. Seems like a bug in OxygenOS
[OnePlus 7 Questions & Answers] Linuxkek:
No Wifi-Calling?
[OnePlus 7 Questions & Answers] LandLockedPH:
WiFi calling works without issue
[OnePlus 7 Questions & Answers] humayunarshad:
Any particular app to use for WiFi calling??
[OnePlus 7 Questions & Answers] -fluffy-:
no u just switch it on an wwn u are near a wifi it will make call from that an recived sms an mms
[OnePlus 7 Questions & Answers] ambuj22263:
How to switch?

Can you let me know please?
[OnePlus 7 Questions & Answers] -fluffy-:
what do u mean switch

u just actived it under settings/network/simcard provider

then u can set it to use volte or vowifi

as standart
[OnePlus 7 Questions & Answers] Linuxkek:
You guys have stable Wifi-Calling connection?
[OnePlus 7 Questions & Answers] LandLockedPH:
Yes. I've had no issues with T-Mobile WiFi calling. Works fine.
[OnePlus 7 Questions & Answers] TX-Brad:
[MENTION=2590202]LandLockedPH[/MENTION] T-Mobile US??
[OnePlus 7 Questions & Answers] TX-Brad:
Quick update...

I went ahead and pulled the trigger on the OP7 (non-Pro).

I'm using a T-Mobile SIM (Sim 1) and AT&T SIM (Sim 2).

I can confirm that I"m getting VOLTE on both SIM's and VOWiFi on the T-Mobile SIM.

Really happy with the device!
[OnePlus 7 Questions & Answers] LandLockedPH:
I know not band 71 but how about 66?
[OnePlus 7 Questions & Answers] larsdennert:
Vowifi doesn't work on vzw
[OnePlus 7 Questions & Answers] Limeybastard:
Does firmware for gm1905 exist? I'm thinking this also opens bands 66 and 71.
[OnePlus 7 Questions & Answers] Limeybastard:
I don't think however carrier aggregation works with the op7 and TMobile USA.

I ran a few ookla speed tests compared to my s10+ using mobile data only. Long story short the S10 would average download at approx 90mbps and the OP7 around 35mpbs.

The only way I could get the S10+ to attain similar figures to the OP7 was for me to disable LTE bands 2, 12 and 66 . In essence making it just use just band 4. Then the download speeds were similar.

On side a side note, having wifi calling enabled slowed the tests results further as you can see by the lower earlier results. Attached screen shot.

View attachment 4811548
[OnePlus 7 Questions & Answers] Limeybastard:
It would have been nice if there was a clear indicator that one was making a wifi calling is ready. Due to the notch I have disabled a few status bar icons including viofa and Volte. When placing a wifi call I have swipe down to check it it's wifi calling or not lolz
[Nokia 2.1 Guides, News, & Discussion] hikari_calyx:
WARNING: Overall procedure requires disassembly, YOU MAY LOSE WARRANTY.

I'm not responsible for bricking or damaging your device! PLEASE DO IT AT YOUR OWN RISK!

For Nokia 2.1, please read: https://xdaforums.com/nokia-2-1/how-to/guide-how-to-unlock-bootloader-nokia-2-1-t3938089

If you want to know details about NB1-Collision for other models as reference, please read:

Nokia 8.1 X7: https://xdaforums.com/nokia-8-1/how-to/nb1-collision-how-to-unlock-bootloader-t3935688/

Nokia 5 & 6: https://xdaforums.com/nokia-6/how-to/nb1-collision-how-to-unlock-bootloader-t3935820/

Step 1: Download firmware which consists the firehose file, and prepare the unlock key / IMEI1 and SN of a Nokia 8

You can download it from https://fih-firmware.hikaricalyx.com/hmd_en.html#e2m

Please download EVW-0440-0-00WW-B01 one in this case.

As for unlock key and IMEI/SN, I will not provide mine, please do it yourself.

Step 2: Trigger your phone to EDL mode

Nokia 2.1 is pretty simple to disassemble. To disassemble the phone, you'll need a T5 Torx screwdriver and a standard Philips screwdriver to remove 15 screws on the back.

Then use your fingernail to peel off the back along with copper frame.

Then you'll need to use anything conductive (such as tweezers) to connect two points under the camera, which is indicated in attachment below, and connect your phone to PC at the same time. If everything goes fine, your phone will boot to EDL mode directly, and you can now release the conductive.

Step 3: Dump deviceinfo partition, hack it and write back

Now use QFIL, load the firehose file in stock firmware. To dump the mfd partition, use the partition manager in QFIL, and right click on the mfd partition, properties, then click "read". Dumped mfd partition is located at %AppData%\Qualcomm\QFIL\COMPORT_XX .

The identification to verify if the unlock key valid is located at deviceinfo partition, and here are the offsets:

SN: 0x00000010

IMEI1: 0x00002010

After you changed them, save it as deviceinfo_mod.img and write your deviceinfo partition back.

Step 4: Boot your phone to Download mode (Fastboot mode)

If you quit Partition Manager, your phone will reboot directly.

To trigger it to Download mode right after your quit Partition Manager, you can execute this command before you quit Partition Manager:

fastboot oem alive

Then your phone will boot to Download mode.

Step 5: Unlock the bootloader and restore the original deviceinfo

fastboot flash unlock /path/to/unlock.key
fastboot flashing unlock_critical

Your phone will reboot immediately and erase userdata. Don't stop right here, execute following command straight forward:

fastboot oem alive

When fastboot responsed OKAY, please proceed:

fastboot flash unlock /path/to/unlock.key
fastboot oem unlock-go

All done. Your phone has unlocked bootloader.

Then reboot your phone to Download mode again and restore deviceinfo:

fastboot flash deviceinfo /path/to/deviceinfo.img

That wraps up the overall unlock procedure.

In case HMD will block this by changing public key to verify unlock key, just downgrade the aboot partition by using QFIL.
[Nokia 2.1 Guides, News, & Discussion] das.das.saheb@gmail.com:
please help me to unlock the bootloader of nokia 7 plus global version
[Nokia 2.1 Guides, News, & Discussion] Shmegma:
so im getting confused with all these links. is this for 2.1 or 8 or 6 or 5 or 7 cuz the first bit u say to read 2.1 link then half way through the guide u talk of 2.1

then when i use the 2.1 link you provide u mention using E2M-0390-0-00WW-B02 but here u say to use EVW-0440-0-00WW-B01 :confused::confused::confused::confused:

---------- Post added at 06:41 AM ---------- Previous post was at 05:49 AM ----------

tried using this method, short the pins, pc reads HS-USB Diagnostics 9008 (COM9)

then i follow to get partition manager "start To EDL" then "Download fail:switch to EDL FailFAiled to switch to emergency download mode"

---------- Post added at 07:10 AM ---------- Previous post was at 06:41 AM ----------

got a bit further now i have this issue:

2019-07-16 15:05:51.808 ***** Working Folder:C:\Users\xxxx\AppData\Roaming\Qualcomm\QFIL\COMPORT_9

2019-07-16 15:05:51.809 Download Fail:FireHose Fail:FHLoader Fail:FHLoader Fail:The system cannot find the file specified

2019-07-16 15:05:51.824 Finish Get GPT
[Nokia 2.1 Guides, News, & Discussion] huaweiman:
nokia 2 v verizon

Just bought this phone from e***y brand new £10, now they do say it is locked to verizon network "yes it is" but what they did NOT say is that the firmware is also locked , when you start the phone up it says this phone need to be activated on verizone network before it will work, so you cannot do nothing with the phone no setting no desktop just a screen telling you it needs activating.

What i have done so far is followed all the threads on this site about flashing/unlocking the boot/shorting the pins/adb and the list goes on.

some are saying you need the phone to be in debuging development mode etc: but you cannot get to the setting on the phone ?.

I can get to the bootloader by " turning the phone OFF > plug the phone into your laptop with the usb cable> wait for the charging symbol to show on screen > now hold down the v/up and power and wait until nokia logo shows then leg go of the power button but keep the v/up held when you see the android man and it will say "no command" press the power and tap the v/up until you get the bootloader.

On my screen it says>

Android Recovery

Nokia/Dynamo2_vzw/evw

8.1.0/opm1.171019.026/00ww_0_27d

user/release-keys

use vol/up/down and power

reboot system now

reboot to bootloader

apply update from adb

apply update from sd card

wipe data/factory reset

wipe cache partition

mount /system

view recovery logs

run graphics test

power off

i have run adb/sd card with firmware factory reset ETC: as stated above and still cannot get my laptop to talk to this phone.

I am just asking if this can have new firmware (stock) or bootloader unlock or what ever just so i can use the phone or do i BIN IT, it was only a tenner and do i need the headache, thank to any body that can help and may be help others that are looking for this phone to be sorted.

ps: i am on my 3rd week now and my laptop is win 10 NEW one.

thank you Gary

PS: when i use ADB and then put adb devices " no devices found" i have loaded all the adb drivers that i can think of or downloaded from here.
[Nokia 2.1 Guides, News, & Discussion] boblutznet:
Hi - Did you make any more progress with Nokia 2V version?
[Nokia 2.1 Guides, News, & Discussion] datzno2004:
my nokia 2.1 phone is on androif pie 9.0, can i downgrade to android version 8.0 using this method
[Nokia 2.1 Guides, News, & Discussion] J-Mizzle:
Does your NB1 unlocking guide still apply to a Nokia 2V running Android 9 with August 1St security patch? Don't want to bother trying if it will not work. If it still will work I figure I'll do it to run Android without Gapps for a phone to use outdoors, etc.
[Nokia 2.1 Guides, News, & Discussion] Lolerhy:
Any idea how to fix that error?

Download Fail:Sahara Fail:QSaharaServer Fail:process fail

different versia different problem error

Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode

Switch To EDL Fail Failed to Switch to Emergency Download mode

Download Fail:Fail to find QDLoader port after switch

I feel still no have full access.

On the picture you can see something is not right with connection.

where exactly need activate ELP mode, inside of Android, Inside of Download mode, in turn off mode ???

edit: in Windows 10 safe mode I found more information about that error connection

ERROR: function: port_connect:99 Failed to open com port handle
[Nokia 2.1 Guides, News, & Discussion] Alpha S Loga:
Can I do it now?
[ZTE Axon 7 Questions & Answers] savoirtous:
Hello

I followed Oki's guide to LOS 15.1 Official and it completed successfully. However, on testing the ROM for few days I felt I am missing Dolby Atmos more than I should so decided to go back to stock(I know we can install Magisk and Dolby Oreo package but am a lil skeptical of the stability as I have read of all sorts of issues about it here + GPAY is finnicky even with the Hide Props module)

So, I followed this guide to return to Stock AFTER I deleted the /vendor partition using the Treble Party tool :

https://xdaforums.com/showpost.php?p=68873482&postcount=2

Now, I cannot get into the system at all. I am stuck with the "unlocked bootloader" screen on every boot and of the available options, I can Reboot, Get to recovery(TWRP), power off and restart only.

If I choose recovery I am going back to a different version of TWRP(3.1.x i guess) from when I had while using Oki's Guide(3.3 I think).

Luckily, EDL is still working so I can go back to LOS 15.1 using Oki's guide but my questions are:

1. Why do I see 2 different TWRPs even though I installed only one(Oki TWRP Labs Mod)?

2. How do I fix this and get back to stock?
[ZTE Axon 7 Questions & Answers] Choose an username...:
well, you're wrong. You installed TWRP 3.1.x unknowingly, because it comes on the stock files that Draken added there.

Have you ever tried Viper4Android? IMO it's way superior to Dolby at least for headphones. I'd say you should try a Pie GSI like aex or havoc or kmni (you'll only lose VoLTE with gsi's) with Speedy 6.2 and baddar rc1.1

If EDL is working, why not just flash a full stock EDL file? That is probably what you should have done from the start.

But I think you may be able to boot the rom you already have installed if you format your data partition (format, not wipe). Try that before doi g anything else, sometimes the system fails to boot and hangs but formatting data fixes it
[ZTE Axon 7 Questions & Answers] savoirtous:
Thanks so much for your response :)

I was not aware that Draken had included TWRP in the Stock Files already. I will try using Viper and GSIs before I go back to stock.

PS: I have seen a lot of your responses throughout the Q&A thread and they have been very informative in understanding all possible implications of any action on our device. Thanks for it as well!
[General Questions and Answers] Shamim0242:
I Can't install GSI on My Mtk base Device because low system memory, How can I Expand System Partition???
[LG G6 Questions and Answers] matthew33:
Anybody tried it yet?

Matt
[LG G6 Questions and Answers] patruns:
Is this just a security update?
[LG G6 Questions and Answers] jonathanbarreto:
H870 open?

Carrier free?

What region?
[LG G6 Questions and Answers] tomy1802:
Most likely.
[Xiaomi Mi 9 SE Questions & Answers] Death_Keeper:
Hello,

Just got the phone last week and it spent all this time in the drawer for the unlock period to pass. Yesterday I have set it up using the great guidance of this forum posts. And all went great... But this weird hiccup - sometimes - usually when I'm using the side of my thumb to press back - I get the heptic feedback but it won't do anything - pressing again usually works - to replicate it I'm using YouTube or whatsapp - and watch a video or enter a conversation - than I'll try to use the side of my thumb and gently and quickly press and release the back button - it usually works (or should I say - won't work)

I guess what I am trying to figure out is what can cause this - if the back button wouldn't vibrate - I would think it's a hardware issue - but it does - the system just ignores it.

Anyone encountered this issue? Do you have any suggestions?

Thank you for reading this far.

Yossi
[Xiaomi Mi 9 SE Questions & Answers] shisaya24:
Spoiler: I don't have a solution. But I have a question - how long did you have to wait for unlock? Did it affect wait time to have the phone on? Mine is switched off while I wait...
[Xiaomi Mi 9 SE Questions & Answers] Death_Keeper:
Hi,

Had to wait for 7 days. All this time the phone stayed in a drawer as had far away from me as possible so I won't get tempted to start using it.
[Xiaomi Mi 9 SE Questions & Answers] Oscar B:
Factory Reset or Rom changing

Hey Yossi!

Its a software problem, try changing roms or factory reset, I'm sure it will fix it
[Xiaomi Mi 9 SE Questions & Answers] Death_Keeper:
I have tried several roms - pretty much the same.

Anyhow - do we have any mod that can space or enlarge the navigation buttons?
[Android General] smnahid:
[BETA] MAGISK V19.3 & MAGISK MANAGER V7.2.0 FOR PHOENIX OS V3.5.0 OFFICIAL​

Magisk Manager is best SuperSU app you can got lot's of future with magisk manager. Magisk v19.3 & Magisk Manager v7.2.0 Working Good On Phoenix OS v3.5.0 Official.

Changelog:

Magisk v19.3-

- [MagiskHide] Hugely improve process monitor implementation, hopefully should no longer cause 100% CPU and daemon crashes

- [MagiskInit] Wait for partitions to be ready for early mount, should fix bootloops on a handful of devices

- [MagiskInit] Support EROFS used in EMUI 9.1

- [MagiskSU] Properly implement mount namespace isolation

- [MagiskBoot] Proper checksum calculation for header v2

Magisk v19.2-

- [General] Fix uninstaller

- [General] Fix bootloops on some devices with tmpfs mounting to /data

- [MagiskInit] Add Kirin hi6250 support

- [MagiskSU] Stop claiming device focus for su logging/notify if feasible: This fix issues with users locking Magisk Manager with app lock, and prevent video apps get messed up when an app is requesting root in the background.

Magisk v19.1-

- [General] Support recovery based Magisk

- [General] Support Android Q Beta 2

- [MagiskInit] New sbin overlay setup process for better compatibility

- [MagiskInit] Allow long pressing volume up to boot to recovery in recovery mode

- [MagicMount] Use proper system_root mirror

- [MagicMount] Use self created device nodes for mirrors

- [MagicMount] Do not allow adding new files/folders in partition root folder (e.g. /system or /vendor)

Magisk Manager v7.2.0-

- Huge UI overhaul

- More sweet changes coming in the future!

Magisk Manager v7.1.2-

- Support patching Samsung AP firmware

- Much better module downloading mechanism

Apk Info:

• Name: Magisk Manager

• Version: v19.3 & v7.2.0

• Packed: com.topjohnwu.magisk

• File Size: 8.22 MB+2.5 MB

• Updated: 05-Jun-2019

• Developer: Topjohnwu

• Requires: Android 5.0 and up

• Supported Language: English

How to update:

1. Copy the initrd.img & ramdisk.img into the PhoenixOS system folder.

2. Clean the system(root)/data/adb folder.

3. Install/Update magisk Manager application. (After update: Clean magisk Manager data. *settings>apps>magiskmanager)

4. Connect the internet and run magisk Manager. Install the additional files. This much :)
[Android General] flex1911:
What's the point of that thread? We already have a topic for Magisk in the corresponding forum: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Closed.
[Samsung Galaxy S9  Questions & Answers] Ocelot584:
Hi everyone. When I view the info under Service Provider SW ver., I see a line that has three CSC codes separated by slashes. It says ATT/XAA/ATT. What does each code represent?

If it matters, I have an unlocked AT&T S9 and my current carrier is outside the USA.

Thanks!
[Samsung Galaxy S9  Questions & Answers] *Detection*:
Read this thread

https://xdaforums.com/galaxy-s9/help/changing-csc-s9-t3884699
[Samsung Galaxy S9  Questions & Answers] Ocelot584:
Thanks for the link. I checked it out but I couldn't find what each segment represents. I'm new to flashing and CSCs and stuff like that.
[Samsung Galaxy S9  Questions & Answers] *Detection*:
Info is in that thread because I wrote it

Active CSC / Firmware Region CSC / Original Hardware CSC
[ZTE Axon 7 Questions & Answers] GeoffUK:
I have two Axon 7s, a silver 64Gb A2017G and a gold 128Gb A2017 which is successfully running A2017GV1.3.0B03.

I say successfully, but battery life on the gold one has dropped off. I'm pretty sure this is to do with the modem as I had the problem before on one of the phones and an upgrade cured it.

Anyway this is just a theoretical question at the moment, not least as I'm not really confident it would resolve the issue.

Could I backup the ROM (well, I mean the entire contents, not sure the terminology) of the 64 Gb phone and apply it to the 128 Gb phone, and what would be the tool to use?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] captain_lowbrain:
Has anyone a MDA2 working under WM6 with working phonesupport and t-Mobile (Germany)? I tried many combinations of phone-roms and WM6-roms, but no comination worked. On some cominations contacts and calendar was not working. Has anyone a working combination? Please tell me. (Perhaps with howto?)

I would be glad, if anyone could help me!
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] kinderenh:
Your MDA II will work with helmi_c's TOFCLOCK WM6.0 ROM and c_shekhar's WM6.1.2 ROM. For both ROMS you should restrict to Radio ROM version 1.17, as newer versions have not been released for the MDA II. My own T-Mobile NL MDA II is now running c_shekhar's WM6.1.2 ROM and Radio ROM version 1.17 without noticable problems.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] captain_lowbrain:
Thanks kinderenh!

Unfortunnately I tried both combinations you mentioned, but none was working for me.