yashsingh1/xdaforums huggingface dataset:
[Android General] scottfan81:
@Viva La Android Thanks for doing what you can to help? I actually emailed KonnectOne asking if they would be able to provide this information to me as I was able to have them send me the firmware that I was excited to come and share here to find they literally made it available at the same time and it was already posted here only hours before I logged in to give good news. Lol. Anyways, the lady I dealt with and was very helpful for the firmware seems to not quite understand my situation. She said she has already provided me all the files that are available and my information should be in the firmware. But if I am understanding things correctly from my hours of searching. That is not actually the case. Again, if I am reading things correctly....

If you wouldn't mind @Viva La Android. Would you be willing to take a minute to read her response to my request for either the QXCN file or even just the information in the file so I can resolve this? I just want to make sure I'm not missing anything or mistaken. I don't want to push the issue if im wrong thinking the information needed is not in the firmware sent to me...

I would post it here but I don't want to violate any policies if that is not allowed. I could message it to you. But I will gladly post here if it is allowed and possibly helpful to others.
[Android General] Viva La Android R.I.P.:
Sure. I don't mind a bit. You are probably referring to Faith Flores at Moxee support. She's very helpful. She and I battled it out with a series of back and forth legal letters, policies, open source licensing guidelines, etc., for several weeks regarding the release of the kernel source code (which manufacturers are required by law to make openly available upon request). Because KonnectOne (like many device makers) was not privy to the mandates of the General Public License (GPL) v2.0, requiring the release of source code, we were finally able to compromise, with KonnectOne agreeing to make factory firmware for its devices available upon request. Ms. Flores was very open-minded, professional and willing to negotiate upon a resolution. Prior to our compromise, however, KonnectOne did not release firmware to the public and considered it to be proprietary in nature and not subject to GPL v2.0 mandates. Technically, they are correct on this point, but compromised due to their noncompliance on maintaining and releasing the kernel source code.

Go ahead and PM me the correspondence and I'll look it over. Also, I am going to attempt backing up and editing my QCN this evening. I finally have time. My device screen is damaged and not functional, but I shouldn't need the display for working with EDL mode anyway.
[Android General] scottfan81:
Yes. It is Faith. She has been very helpful and polite. I'll send that in a few min. Thanks again!
[Android General] scottfan81:
I am not experienced here on XDA so I am most likely looking in the wrong area, but I haven't been able to find the option to PM you. So I requested to follow you and that is why I haven't sent the correspondence to you yet. I just wanted to let you know so you didn't think I forgot. So if you could just help me to find the option to do so or accept my request I will send you the information as soon as I am able. And please know I am in no rush and I greatly appreciate you taking time to try and help me to resolve this.
[Android General] Viva La Android R.I.P.:
It's probably my messaging settings. You can post the correspondence here. Since the thread is mine, it won't be violating off topic posts or rules. I have been trying to get my Moxee into diag mode for the past hour or so. It requires some adb commands via root shell terminal. My issue is I can only see the left 20% or so of the screen, so I'm not able to see to grant the terminal root access when prompted. I'm going to keep trying for a little while but it isn't looking promising on my end. This is what I'm dealing with, plus the screen is just barely responsive to touch.
[Android General] scottfan81:
It definitely looks like I am out of luck see seeing what you have to work with. That sucks. Judging by the lack of response to my issue beside you of course, it seems that you and Faith were pretty much my best chances to get this fixed. But my appreciation remains the same. You did not have to help at all but you have been trying. So whether you are able to succeed or not, I'm grateful regardless.

I'm just including a screenshot of Faith's last email to me because there is not really anything missing leading up to this. I asked if they could provide me the XQCN file or even just the information I need to enter and her only response before this screenshot was she has no other files available to send me beyond what she already sent me. And that is the firmware which we have had for some time now. So unless I am mistaken, I don't think she is aware of what exactly I am asking for or Is not allowed to share it. Or, I'm just completely wrong. Lol
[Android General] Viva La Android R.I.P.:
Hey I found something in the firmware package that may be what we need. I'll post back shortly once I get a better look at it. I have to research some terminology first. (I'm not highly familiar with these Qualcomm factory firmwares, as I'm accustomed mostly to MediaTek & Allwinner.) I'm not giving up on this. We need a QCN file not only for you, but as a resource for any members who face this issue in future.
[Android General] scottfan81:
That's great to hear. I hope it turns out to be what we have been looking for. And even better, it may end up being useful to anyone else in the future. I've said it a hundred times but thank you again for your efforts.
[Android General] Viva La Android R.I.P.:
I thoroughly checked out the contents of the firmware file. For your reference, it's an archived file within the archived firmware folder, with file name orig_MODEM_PROC_IMG_8937.genns.prodQ.elf

The .elf file extension is indicative of the type of data stored in QCN...sensor calibration data, Bluetooth & WLAN configuration data, and identifiers specific to the device, such as IMEI, MAC addresses, ESN, etc. Obviously, the QCN file we need isn't going to include device specific identifiers because, of course, those are different on every single device, but will include sensor calibration data and other data which is consistent on every model. Identifiers like the IMEI must be edited in by the user, per the guide I listed in a previous post. I'm still researching this matter. The actual QCN file, from what I understand, is very small in file size, only Kb in sum. The .elf file I noted above is almost certain to encompass what we need. It's just a matter of finding out which of those many files it is.

And you are most welcome. I do appreciate your appreciation .😆
[Android General] scottfan81:
Well that makes me almost feel smart. Lol. I say that because before I posted my issue about this I did attempt to diagnose and resolve it myself. And I thought that exact file you are referring to was the answer. But since I'm still learning things and don't have the knowledge and experience, I am not sure what to do with that file. I tried to flash modem but it was to large. I already figured out how to fix my IMEI number before I came here for help and it absolutely has positive effects. But I'm still missing something because it will not read any sim cards. Ive been wondering if it's possible that something as simple as the SV of the IMEI could be the difference between functional and broken. But I don't have the slightest clue where I would even enter that and it appears to me it is done automatically. I can only enter the correct amount of digits for the IMEI and there is no place to enter the SV unless I would enter that in the IMEI2 section but that is for dual sim so it seems obvious that is not the answer. I can only say that before I fixed it my IMEI showed 0 and nothing else but after entering my IMEI which I will not post, it also says the SV is 08. Sorry for the long post.
[Android General] Viva La Android R.I.P.:
I assume your bootloader is unlocked. If your IMEI is intact, but your device still isn't reading a SIM card, perhaps try resetting NV data to its factory default. First remove your SIM, then reboot. Boot into fastboot mode, connect to your PC, open a command window in your ADB & Fastboot path, and execute these commands:

fastboot erase modemst1
fastboot erase modemst2
fastboot erase DDR
fastboot erase carrier
fastboot oem config fsg-id umts
fastboot oem config carrier umts

Upon reboot, open your stock dialer app, enter *#*#4636#*#" then select Phone Information from the menu. Under Preferred Network, select GSM/WCDMA/LTE (auto PRL) from the menu (if it isn't already set to that value). Power your phone off and insert your SIM. Reboot and see if it's reading your SIM card.
[Android General] scottfan81:
I will say I have tried all of those suggestions based off of attempting to get lucky but aware very unlikely that your custom rom may have given me a resolution. But that did not include the three fastboot commands following erase DDR. I will give it a shot and let you know what happens. And I've tried the preferred network step and tried entering about 300 dialer codes looking for another menu that may help. Lol
[Android General] scottfan81:
Last two commands return error. My bootloader is unlocked as well as unlock_critical. When I enter those commands in fastbootd I get FAILED <remote: Command not supported in default implementation">. And in bootloader I get unknown command. Almost forgot to add, after trying these my IMEI is back to showing 0. Not a big deal as I now know how to correct it but I thought I should share this if it for some reason it helped diagnose the situation at all. I have not done anything to the device since trying your suggestion and don't plan to without first hearing your input. I would hate to miss out on a possible solution by doing anything to prevent it.

It would probably help giving you a little information about the state of the device before trying your suggestion that also may be preventing a fix. It is rooted as it is my understanding from my searching that is my only option in order to complete the process of restoring the IMEI. So I also did not factory reset before or after running these commands. Let me know if you would suggest any other steps. And please don't feel pressured or rushed as I am not in a hurry and already appreciative for your time and efforts as it is.
[Android General] Viva La Android R.I.P.:
Ok thanks for the additional info. Have you tried making a backup of your QCN by way of the XDA guide I previously posted? If you could backup your QCN, it would suffice to edit and restore.
[Android General] scottfan81:
I'm in the process of going thru the steps today.
[Android General] scottfan81:
I'm still here and have not disappeared. Sorry for not replying until now. I have had a lot going on the last few days. It appears my only hope is for someone to see this thread and able and willing to share their QCN file minus the IMEI number. I tried the guide you posted and I think without me having an original backup that something is still missing or not quite right. I still cannot connect to a network no matter what sim I try using. I learned a valuable lesson out of this mess and I hope anyone else who sees this may avoid this by making sure to backup everything before doing anything. If we had twrp for this device I would have made sure to backup everything but since we don't I honestly was not sure how to create a full backup. But it's my fault for not searching for that before anything else.
[Android General] Viva La Android R.I.P.:
Unfortunately, TWRP does not backup the complete QCN file. It is capable of backing up some EFS and NV data, but only the QCN file itself can restore a lost or corrupt IMEI. Because the QCN is made up mostly of proprietary code and vendor-specific sensor calibration data, it takes a proprietary tool such as QPST/QFIL to perform a true QCN backup. (Due to security protocols put in place by Qualcomm, TWRP cannot properly access the sensitive partition in which the QCN is stored.)

In reality, yes, it's always ideal to make a QCN backup as a precautionary step to flashing a Qualcomm based device with QFIL. However, the loss/corruption of the IMEI on your phone was actually quite a rare occurrence. I've been flashing Qualcomm based phones and tablets for years and it's never personally happened to me. Like your unfortunate instance, I have only read about it when it's happened to others. In a full decade of flashing Qualcomm devices, your mishap makes perhaps the 3rd or 4th time I've ever heard of this occurring. It happens much more often on MediaTek based devices via the SP Flash Tool, when a user inadvertently selects the Format All option without having first backed up the /nvdata partition (MeduaTek's equivalent to Qualcomm's QCN file.) So don't kick yourself too hard. Most device users never backup QCN prior to flashing firmware with QFIL. I have not given up on finding a solution yet either. I have reached out to a couple of developers well-versed in the science of Snapdragon board platforms, and now await replies.​
[Android General] Viva La Android R.I.P.:
@scottfan81, never despair my friend. The Android Gods have smiled down upon us. I've just been provided with the factory QCN file for this device, with the IMEI value blank. I'll link it here shortly. I'll be posting a step-by-step guide for restoring a lost or corrupted IMEI in my firmware flashing guide for this phone.
[Android General] Viva La Android R.I.P.:
• Moxee m2160 QCN file (No IMEI)

• QCN Editing Tool v1.0.0 (by tungtata.net)
[Android General] scottfan81:
Your the man!!! Thank you!! I will try to do this tonight and let you know how it went.
[Android General] Viva La Android R.I.P.:
If you run into any difficulties, I have already tested the entire procedure on my own busted device, and everything went smoothly. I purposely corrupted my IMEI in order to test the steps for restoring the IMEI by virtue of the QCN file. My device is virtually inoperable, so I didn't have anything to lose had it not worked. I will be outlining the exact steps in the firmware restoration thread later tonight.
[Android General] scottfan81:
I was bummed out and thought I was SOL after trying the QCN file and the editor you posted because it did not fix anything. That is until I saw you had started your post with instructions and see there are additional steps I was not aware of yet. So I am optimistic still and will see how it goes once you are finished posting the rest of the guide. Thanks again and I will cross my fingers.
[Android General] Argonon:
I have 2 of these devices. Let me look for the other 1 and I can mail one device to you @Viva La Android Please keep in mind I'm on disability and might take me a couple weeks to get the funds together to do so
[Android General] Viva La Android R.I.P.:
Thanks for your support. I'm hoping to have the guide finished in the next day or two.
[Moto G7 Play Questions & Answers] sudQ:
i am looking for an android 12 rom (preferably android 12.1/12L) for my phone because i really like android 12
[Moto G7 Play Questions & Answers] copone92:
You can search online for Android 12 ROMs, visiting top 3 sites you will find it, preferably Android 12.1 or 12L, for your phone to experience the features of Android 12 that you like. Make sure to follow proper installation procedures and use ROMs compatible with your specific device model.
[Moto G7 Play Questions & Answers] sudQ:
i'm mainly looking for lineage os, but i cant download it from their website and its the only android 12 rom i can find for my phone
[Moto G7 Play Questions & Answers] sudQ:
also, i have tried the unofficial rom but it fails to flash and my terminal says `xfer: 0.87%`
[Moto G7 Play Questions & Answers] chuy19312:
I have LineageOS 19.1 (Android 12L) on my Google Drive, is for Moto G7 Play, sadly, since it's Arm64, you will have some problems with app restarts

The only issue of this specific ROM is the Ambient Display, it doesn't work, outside that, there are no problems

lineage-19.1-20221225-nightly-channel-signed.zip

drive.google.com

Edit: There is /e/ OS android 12 ROM too, here is an link with android 11 and 12 versions of the ROM, sadly, on android 11 version, wifi doesn't work, so don't install it

/e/ OS - Moto G7 Play
[Android Q&A, Help & Troubleshooting] Bruhbub23:
I could not find a specific section for this model, so just posting it here, hopefully someone can lend me some help.

I have a model C100(cheap $39 one), trying to root the device, but cant find a way to get past the bootloader(I think its locked by default), i turn power off, connect phone to computer, press power button + volume key, phone goes into bootloader screen, but theres no options just says "bootloader >>". I thought it was just stuck there loading, but now it just seems like the bootloader is locked, I've tried looking for boot imgs to use in mgisk, but also can't find any of those...

Have tried adb, it shows up when I have it turned on(Dev mode, USB debugging, cant toggle OEM on this one, anyone know how?) , but when I reboot to go into fastboot, it no longer shows up on listed devices. Also installed all drivers, with adb/fastboot tool on here

basically asking if anyone has the slightest idea of how to root this phone/is it even rootable at all?

if anyone could link me a good boot img to use or how to find it on this particualr phone, that would b nice aswell

Thanks, hopefully the post wasn't too confusing
[Android Q&A, Help & Troubleshooting] mr falcon:
Hi. I own one of these and it is possible with the MTK flash tool. Beyond that, you may be able use a custom os to remove bloatware. Unfortunately, you won't get any help from Nokia (hmd global).
[Android Q&A, Help & Troubleshooting] luridphantom:
whats the software version on your phone? mine is all patched out
[Android Q&A, Help & Troubleshooting] mr falcon:
it is android 12, kernel 4.19.191

non rooted as nokia has removed the oem unlocking option. it's mainly used for storage as it has 32 GB decent for the price.
[Android Q&A, Help & Troubleshooting] luridphantom:
you cant use a custom os if oem unlocking is removed
[Android Software/Hacking General [Developers Only]] Bruhbub23:
So I tried this version of the adb installer:

https://xdaforums.com/t/official-to...vers-15-seconds-adb-installer-v1-4-3.2588979/

you guys have on here earlier, worked fine with my computer(still no luck unlocking my c100 tho, if anyone wants to help lol).

For whatever reason, it does not want to install on my laptop whatsoever, I've tried installing SDK, Android studio, and doing it thru the plugins on there, nothing works

View attachment 5933541

also not installing any drivers either

What am I doing wrong here? I seriously don't know why it wont work on my laptop, since both my pc and this one have Windows 11

Thanks for any help, hope I can get this on my other machine, as it would be rlly nice to have a mobile version of adb
[Touch Pro, Fuze Accessories] allthatinny:
would a sprint active case work on ATT Fuze? i know physically they are different but internally the same but will it work even with the slight difference
[Touch Pro, Fuze Accessories] jknuckey:
I actually got a sprint store worker to crack open the package and let me try it on my fuze. It doesn't fit due to the sprint touch pro having the smooth back, and it is longer and wider due to the chrome bezel. See the other thread on the rubberized case just made available on ebay.
[Touch Pro, Fuze Accessories] allthatinny:
k mate, thanks for the reply :) was really looking for a clear active case that fits snug, they look sexy :)
[Sony Xperia 1 IV] hellcycle:
Which expert can share the settings for SONY XPERIA 1 IV ANDROID13 incoming call ringtone dual speakers?

My phone: sony xperia1 iv

Operating system: Android 13 Hong Kong (already ROOT)

Who can share how to modify system parameters to achieve dual speaker ringing for incoming calls?
[Sony Xperia 1 IV] hellcycle:
Directory: Is system/etc modifying a certain parameter here? Request expert guidance! Thank you.
[Redmi Note 10S] orangpelupa:
in miui 13, there was a setting that would requies the phone to be unlocked to be turned off, but i cant find this option in miui 14.
[Samsung Galaxy M51 Questions & Answers] kn8_:
Hello there fellow M51 users. I’ve been using the M51 ever since it launched. all was good, until last month, the display just stopped working. Took it to Samsung service centre, and they said it was the display. Kinda frustrating how it just stopped working despite having no physical damages. Anyways, I set out to find an aftermarket display as replacement, as the original one from samsung costs wayy more than the phone’s current resale value. After installing the 3rd party display, the phone turned on (in safe mode?) and then turned off a few seconds after I got into the home screen. This kept on happening as i tried restarting. I also noticed the phone get unusually hot. Now a dialogue box saying “Serious software issue detected” pops up while booting with a “Check for updates” prompt. I believe it is updated to the latest version. Is there any way over this? The technician suggests we do a factory reset, but I have 5 years worth of valuable data in there. Can I at least be able to retrieve the data? Should i try using an original display, would that solve this? Technicians locally are unbothered and lazy to help, so I hope someone can help me from here. Thanks a lot in advance.
[Samsung Galaxy M51 Questions & Answers] blackhawk:
Welcome to XDA.

If it will boot into safe mode you can get the data.

If you get into safe mode don't power it down, grab the data. Go into safe mode, if it crashes in safe mode you got big problems...

In the future redundantly backup all critical data otherwise sooner or latter you will likely lose it.

If you have expandable storage always use it as a data drive; all critical goes here, don't encrypt it, and then backup the SD card data on a regular basis. Many time if the OS or phone crashes/burns the SD card and its data are still intact.
[Samsung Galaxy M51 Questions & Answers] Squeeky-Sandwich-1991:
I have a 3rd party display in my M51, it is LCD, you can take it the guy who fixed it and he'll have a solution. My phone works fine except sometime when i use a "amoled specific feature" the display goes blank and i need to hard reboot.
[Touch HD General] mascot4m:
Hello

I have a problem with installation .NET framework. I can t install it because the blackstone wrote the installation was unsuccessful.

Please help
[Touch HD General] Mew789:
I had the same error. Problem solved after a hard reset.

So if you don't have too much programs installed...
[Touch HD General] umexed:
once you installed it on your pc go to

C:\Program Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE

there you will find some cabs for wm!

install: NETCFv35.wm.armv4i.cab
[Touch HD General] umexed:
are you trying to install it on your storage card ?
[Touch HD General] mascot4m:
thanks umexed. its working.
[Touch HD General] umexed:
came across the same problem a few days ago :) glad i helped!
[Touch HD General] ScarySquirrel:
To get it installed on mine I just had to run the setup on my PC, then I plugged in my HD and it updated the device on its own :)
[Touch HD General] denied1977:
Sorry, i'm a big noob - it's my first wm phone, so i think it's better to ask then to sc**w something up.... :p

I can't start .msi file on the phone because it says the file is not associated with any prog on the phone. If I install this on my pc and copy just NETCFv35.wm.armv4i.cab (if i understood correct) on HD - after i click on it twice it will install? :o
[Touch HD General] umexed:
Installations of .exe and .msi are for pc.. if you run them on the pc it'll automatically send it for installation to the ppc via activesync.

if the installation isnt successful for some reason, copy the .cab file mentionted on the previous post and run it from the ppc :)
[Touch HD General] denied1977:
Thanks, it worked!!! :p
[Touch HD General] Bennyboy1985:
I get "Installation error" aswell, but is there any other to to get around this other than doing a hard reset? :(