yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] delt01:
Hello everyone,

Several days ago, i damaged the EFS partitions on my LG G3's new motherboard by overwriting it with a backup from the old motherboard, which is also D852 but originally from a different carrier. I managed to "partly" fix the problem - original thread here: https://xdaforums.com/showthread.php?t=3912717

Now the problem i'm having is that cell network keeps dropping after a few hours, or often right after a call. I can sometimes reconnect by killing and restarting the "RIL" service, but most often i need to reboot the phone. This happens both with Lineage OS and with stock firmware, and with any of the "fixed" EFS i generated, either by:

(1) restoring the backup from the other LG D852 board, then booting the stock firmware and using Qualcomm's "product support tool" to write the correct IMEI of the new motherboard, or

(2) zeroing out the modemst1 and modemst2 partitions, then rebooting with the stock firmware to have the Qualcomm chipset re-generate them, then using QPST to poke back the correct IMEI as described above.

Additional info: I noticed that since this happened, after wiping the data partition in stock firmware i have to manually set up the APN before i can use cellular data, however in LineageOS 15.1 it puts the (almost) correct one by default, but i can't edit it, remove it, or add another one from the settings app. The Proxy and Port fields say "Not set" however the "MMS Proxy" and "MMS Port" are correct.

Also the battery power used by "Mobile network standby" is extremely high (almost 50% overnight with a PowerBear 6500MAh battery) but i guess that is caused by continuously trying to reconnect to the network.

...anything else i could try? Thanks very much for any assistance!!!
[Android Q&A, Help & Troubleshooting] delt01:
I just wanted to add: from futzing around with restores and backups, i've noticed some weird behaviour that i can't explain.

For example, if i restore a TWRP backup of Lineage 15.1 after restoring stock firmware (4.4 i believe) then wifi is unusable until i re-flash Lineage from the install zip. Until then i can't turn it on in the settings, it turns itself off after 1 second. There is no problem if i restore the data from a Lineage backup aftewards however. I haven't looked deep into details about this yet, but i have no idea what causes it. All the backups contain both system and data partitions.

I also noticed that if i make consecutive backups of the phone's EFS partitions (without writing anything to them in between) they don't match. This happens both with TWRP backups, and with dd'ing the /dev/block/... device nodes to files manually, either from TWRP or from the main OS. So something is clearly writing to those partitions while the phone is in normal use. Again, i have no idea what that could be, especially since EFS/NVram is kind of a sealed "black box" with no specs available anywhere, and very little tools available to manage anything about it.
[Android Q&A, Help & Troubleshooting] delt01:
Ok, now stuck in a bootloop, this is the second time this sh!#$%t happens: i setup a tasker profile to try to reconnect to the cellular network when the phone gets booted from it. It shuts down the RIL daemon, rewrites the modemst1 and modemst2 partitions from a backup, waits 30 seconds, then restarts RIL. It worked when testing it, then "sometimes" worked during actual use in the past 20 hours or so, and then suddenly i take the phone out of my pocket and it's stuck bootlooping on the LCD's hard-coded startup logo.

FAAAAAAAAAAACK the engineers that design and sell this purposely sabotaged junk should be skinned alive and hanged by the balls until they die :( :mad:
[Samsung Galaxy S9  Accessories] iaptekar:
Any ideas for a set of of attachable lenses that can work without me having to take my Parallax Caseology cover off?

Thanks
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Cletis989:
I am having a heck of a time installing the stock firmware on this device. It came to me softbricked and I have used almost every firmware available from the XDA official Galaxy Tab 4 forum, Sammobile and even the SAMFIRM tool. I do not know if this is a PDA issue or what, But I have been able to flash the bootloader with TWRP and install some custom roms which makes me think I am using the wrong firmware but I am lost as of right now.

FIRMWARES I HAVE TRIED:

T530NUUEU1BQC1_T530NUXAR1BQC1_HOME.tar

T530NUUEU1AOA2_T530NUXAR1AOA2_HOME.tar

T530NUUEU1ANK1_T530NUXAR1ANK1_HOME.tar

T530NUUEU1AND4_T530NUXAR1AND4_HOME.tar

T530XXU1AOA1_DBT1AOA1_v4.4.2_Repair_Firmware ( 4 file repair) Only one I can find

Other Regions XAC and BNN Firmwares

_T530NUXAC1BQC1_HOME.tar

T530NUOVS1BPL1_T530NUBNN1BPL1_HOME.tar

I have tried multiple cables and odin3 versions

Odin3 v 3.04

Odin3 v3.07

Odin3 v3.12.3 & v3.12.5

Odin3 v3.13.3

Odin always fails on aboot.mbn not matter what...sometimes I can get it to say re-partition failed or secure boot fail PIT or secure boot fail aboot

When I flash the stock bootloader I can see at the top of the screen T530NUUEU1BQC1 and at the bottom Multi CSV, XAR selected.

Any help would be very much appreciated.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Cletis989:
Anyone have any suggestions at all?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Cletis989:
If someone could please let me know what I am doing wrong or any other suggestions I would greatly appreciate it.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Cletis989:
Something I forgot to mention is whenever I try to flash the stock firmware it always fails on aboot.mbn. I really hope someone can give me some insight on this.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] djhooker:
I can't answer your questions, but: Does it have to be the original Stock Rom? Why don't you stay with a custom rom? Dirty Unicorns MM may be old but it's very stable since years on my device.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Cletis989:
I mean I don't " have" too install the stock rom but I would like to know what my problem is it would greatly help me in the future on other devices.

I will give dirty unicorn a go.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
This is the final version 1.0 Release of WM6.1 for the HTC Juno/Phoebus.

This is for developers and anyone who wants a clean rom without any T-Mobile bloatware or 3rd party apps, inlcuding ArcSoft MMS 4.0.

Download:

http://rapidshare.de/files/39379214/PHOEIMG.rar.html

Installation:

Instructions: (see attachements)

Patches:

Install Freddy Reyes Landscape camera fix 5.03 (Portrait camera doesn't work at all)

Customizations:

Check freddyreyes.com and allshadow.com for skins and customizations

If you want the startup animation length to be shorter, change [HKLM\System\Startup\2] "Duration" anywhere from 1000 to 4000 (msecs)

Upcoming Releases:

WM6.1 ND4SPD edition: Inlcludes custom startup and some popular 3rd party software and customizations

WM6.1 T-Mobile Edition: Includes all the T-Mobile bloatware you could possibly imagine, hopefully with Neo

Credits:

Freddy Reyes, shadowmike, pixelwix, kron2, benjaminries for fixing up all the bugs I had no idea on how to fix and for constant support

jockyw2001 whose CID Unlock enabled us to do this

Dr.Martin Gonzo for his advice

bepe, maimach, tadzio, everyone else for their tools

Everyone who was brave enough to test my beta roms!

Note to developers:

As soon as I have the OEM and SYS packages ready, pixelwix will create the rom kitchen. I'll be making another rom kitchen too.
[Non-Touchscreen Windows Mobile Other] LGSilva:
Thanks :) (hehehe)

I was waiting for this release!
[Non-Touchscreen Windows Mobile Other] romeo0119:
Thanks, I have beta 4.1 right now. Will flash this and try it out.
[Non-Touchscreen Windows Mobile Other] romeo0119:
Just install this...seem it does not have mms message and a few other thing or am I missing something?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
This release has none of that stuff. It's just a base so that anyone else who wants to make a WM6.1 ROM can do so. Or if you want an ultraclean rom that's fast and has lots of space.
[Non-Touchscreen Windows Mobile Other] shadowmike:
SWEET !!!... Nice job bd4spd. Im going to make a strict htc 6.1 rom for the shadow...

wait. this has no mms at all ?
[Non-Touchscreen Windows Mobile Other] LGSilva:
I'm waiting for the kitchen. There are some "brown" images I want to replace, remove welcome center (useless) and other stuff.

The bug with the "display clock on unlock screen" still no resolved right?
[Non-Touchscreen Windows Mobile Other] romeo0119:
Well then I will go back to the beta 4.1 until some one can cook a custom wm 6.1. I'm wondering if the "flash 7" hack can be implement into the rom?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
As I said before, I can make the cab files of software you need. Just give me a list.
[Non-Touchscreen Windows Mobile Other] buckbullstallion:
Thanx guys

i just want to say thanx I will be testing this bad baby out. will report ne fixes that i can find as i love testing this. I am so looking forward to the custimizations. this is awesome..

I unlocked my phone through t-mobile so i skipped the step sda unlock. but ran the CID program and no hickups im at 68% and climbing will check out the MMS issue. also if you view SNN3.1 for the wizard MDA he installed a CAB that does automatic Network set up. I am wondering if this cab would work on the smartphone? that way the mms and t-zones will be set up .. if not i will go to t-mobiles site to see if i can manually configure it. im sure with the dotac configurator should be easy. device is up and running. now time to start installing cab fixes and my faves.. woot. im playing with arcsoft mms cab right now .. seems buggy .. but will look into other options..

Arcsoft_MMS_4281.cab should fix the mms problem its a bit buggy i have like mms and mms1 listed but i can send and recieve mms when i set up the tmobile mms servlets in the options settings .. the page i found the program is

http://xdaforums.com/showthread.php?t=365601&page=9&highlight=itsblack

and i used the links from that page .. so now i have a cool working striped wm6.1 tabbed sms and all its awesome. thank you guys for the hard work and pm me if you want to voice me through how to work the kitchen.
[Non-Touchscreen Windows Mobile Other] benjaminries:
CABs needed?

Hey ND4SPD,

Once again, great work. For those interested, I'd like to confirm that this ROM contains WL Messenger, Voice Command and Office Mobile.
[Non-Touchscreen Windows Mobile Other] shadowmike:
yeah that cab would work for most users but not some.

as the only wep server i connect to is for mms

the only internetserver i connect to is internet3.voicestream.com

so that program would set everything up wrong for me.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Yes, the rom does have WLM, Voice Command, and Office Mobile. I think I'll just have to use T-Mobile's provxml files to setup the data and mms.

I got an idea yesterday and this weekend I'll be testing to see if I can get Neo to work. I'm going to have two sets of plugins. The wm6.1 currently reference the bronze resources and that's why Neo doesn't show up. I'll just add the Neo plugins with different names and replace the CHome and confetti core with the old ones.
[Non-Touchscreen Windows Mobile Other] buckbullstallion:
well the program from this thread is awesome mms

http://xdaforums.com/showthread.php?t=365601&page=9&highlight=itsblack

that is in that thread works but has a few screeen bugs as far as rendering the bottom correctly or having top keys menu and select missing but other than that i installed it than i set up t-mobiles dotac settings and voila i now have mms.

okay .. i think this acrsoft cab is for a touch. so now i am searching for a smartphone MMS cab i will be in and out of this post. but that cab works just made for a touch screen but still manageable you can recieve and send mms. i think i need to fix the camera issue first but i will search around for the smartphone MMS cab.
[Non-Touchscreen Windows Mobile Other] kron2:
worked out for me but i had to go to windows to use it .nd4spd could you make this last rom with the flashlite.dll file cooked in it I think it needs to be part of the rom to work with my faves
[Non-Touchscreen Windows Mobile Other] benjaminries:
Cosmetic issues

I'd like to gently suggest that the incoming/in-progress call screens are still messed up.

1. For incoming calls (HKLM\Security\Phone\Skin\INCOMING\portrait\text) this ROM makes all text white (HEX:FFFFFF or DEC:16777215) which is bad for the off-white background. Black (HEX:0 or DEC:0) and perhaps dark-grey (HEX:222222 or DEC:2236962) should be used here.

2. For in-progress display (HKLM\Security\Phone\Skin\PROGRESS) this ROM uses Backgroud_port.bmp and Background_land.bmp images that are based on the "Windows Default" (Green) theme. Switch to a different color-scheme (ie. red Guava bubbles), and the green looks awful. Just as with the comm manager, a neutral background should be used here.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Thank you for the suggestions. I'll make sure that these are changed.
[Non-Touchscreen Windows Mobile Other] buckbullstallion:
MMS working

Okay managed to get mms working using arcsoft.cab the file i found searching endlessly is ArcsoftMMS_5_0_31_7_US.cab. than I applied t-mobiles server information in the options. the SMS / MMS are now one and you have 2 or so locations where you can set your MMSC info. But so far so good. still testing out other apps some which just wont work. Tried to install the myfaves cab but just hangs than says MY5APP.EXE is corupted or not found. so im still looking in on how i can fix this. but having the ability to send and recieve MMS is awesome. sometimes it takes a bit to send a file or recieve one but working.
[Non-Touchscreen Windows Mobile Other] sman234:
how do i sync with my computer after i have installed the new rom?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Go to Settings > Connections > USB To PC and uncheck the enhanced USB funtionality option
[Non-Touchscreen Windows Mobile Other] kron2:
nd4spd can you cook the flashlight.dll file in to the clean rom I think it needs to be cooked in to work for my faves I would do it but still don't get how to
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Sorry I never made an explanation. I'll make sure to do that as soon as I'm done making this new rom image.

I have added the file to my MyFaves package that I made. In the meanwhile, go to the HTC Wizard forum and look at the stickies. Especially the one by faria. These will help you before you actually cook anything.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Neo's working on wm6.1!! Unfortunately, sliding panel doesn't work now. The only solution I can think of now is the switcher application I thought of a while ago. There are still some problems on Neo though. The battery settings won't show up and when the messaging section is enabled, Neo dies and you are left with black screen until you take that plugin out again.

T-Mobile Edition coming soon...
[Non-Touchscreen Windows Mobile Other] falcon72:
does anyone have problem with the camera on this roms my camera stop working either from launch the apps on press on the button.
[Non-Touchscreen Windows Mobile Other] kron2:
did you read the first post Patches:

Install Freddy Reyes Landscape camera fix 5.03 (Portrait camera doesn't work at all)
[Non-Touchscreen Windows Mobile Other] Aqua_Daemon:
Dear ND! You in yours ROM could not place files russian mui?
[Non-Touchscreen Windows Mobile Other] shadowmike:
nd4spd can i get a cab with voice cammand and mms ?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
@shadowmike: sure, as soon as I figure out how to make the package into a cab file...:). Is it okay if I get it to you this weekend?

@Aqua_Daemon: I have the russian MUI files that are on Microsoft's site. However, other than the system files, I don't know how to make it show everything in cryllic. If you can help me find out, I'll be glad to make a russian wm6.1.
[Non-Touchscreen Windows Mobile Other] kron2:
nd4spd how is it going with a new t mobile rom or one with FlashLiteDll.dll cooked in it loveing the clean rom but would like the my faves working
[Non-Touchscreen Windows Mobile Other] romeo0119:
I want the WM6.1 ND4SPD edition Rom!!!
[Non-Touchscreen Windows Mobile Other] freyes01:
Great job ND4SPD! Can you create a "Neo" version of WM6.1 maybe we can help you to debug the problem?

Maybe that could be the T-Mobile Edition
[Non-Touchscreen Windows Mobile Other] shadowmike:
ND4SPD, if you want just send me the files you have for the rom.

i can make the cab i just need the packages. as long as they contain all the files the file that says were all the files go and the reg edits. if not i can wait untill the weekend.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Sure thing. Should i send you the version I have right now?

@ shadowmike: Will send it later this evening.
[Non-Touchscreen Windows Mobile Other] LGSilva:
Hey ND4SPD,

do you know if the smartphone version of wm6.1 have the SQM "problem"?

I was browsing the Development & Hacking forum and found that this SQM keep sending data to MS (and probably using resources).

Because it's so integrated with the system you can't simple delete it, you have to use a dummy dll.
[Non-Touchscreen Windows Mobile Other] shadowmike:
Nd4Spd You may want to look into this. http://xdaforums.com/showpost.php?p=2209597&postcount=1 :) may be good to add into the rom.

also what happend to that package you were going to send ? I need MMS Man :D

/side note\

http://www.allshadow.com/forum/viewtopic.php?f=5&t=1741&p=11148#p11148
[Non-Touchscreen Windows Mobile Other] -MyHTC-:
I’m hopping I can get some help from the Shadow ROM developers.

I’ve taken the XT9 from the Shadows ROM and im using it on my StarTrk.

These are the files im using:

T9ImeCustom2.Bmp

eT9MyWords.exe

XT9Settings.exe

eT9Dictionary.dll

eT9DisInput.dll

eT9Ime.dll

XT9Menu.dll

XT9Settings.dll

eT9.hpd.9Keys.English.kdb

eT9.HQD.kdb

ENlbUN_xt9s.ldb

eT9.StrTrk.0409.kmap.txt

HTCMDB.txt

And these are my registry settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Inbox\Compose_View\{265B8269-7639-4e61-9200-7B0AECA3BDB3}]

@="try"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Extensions\ContextMenus\Contacts\Edit_Menu\{265B8269-7639-4e61-9200-7B0AECA3BDB3}]

@="try"

[HKEY_CLASSES_ROOT\CLSID\{265B8269-7639-4e61-9200-7B0AECA3BDB3}\InprocServer32]

@="XT9Menu.dll"

[HKEY_CLASSES_ROOT\CLSID\{59B4CAE2-3EAE-4003-92D5-CF3CDDB9113E}]

@="T9 Settings"

[HKEY_CLASSES_ROOT\CLSID\{59B4CAE2-3EAE-4003-92D5-CF3CDDB9113E}\InProcServer32]

@="XT9Settings.dll"

[HKEY_CURRENT_USER\keyboard layout\Preload]

@="e0010409"

[HKEY_CURRENT_USER\keyboard layout\Preload\1]

@="e0010409"

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD]

"3PartyIME"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9]

"AddWordToUdb"=dword:1

"SpellCorrectionMode"=dword:1

"Prediction"=dword:0

"AutoAppend"=dword:1

"AutoSubstitution"=dword:1

"WordCompletion"=dword:0

"MultitapWordCompletion"=dword:0

"AvailableLanguages"="0109"

"ResetDB"=dword:0

"InstallFolder"="\\Windows"

"DefaultLanguage"=dword:109

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\IME]

"MdbFile"="HTCMDB.txt"

"DefaultInputModule"=dword:1

"KeyboadLayout"=dword:1

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\IME\InputIcons]

@="\\Windows\\Programs\\tegic\\eT9\\T9ImeCustom2.bmp"

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\IME\KDbFiles]

"0609"="enhpd.kdb"

"07FF"="eT9.HQD.kdb"

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\IME\KeyboardLayouFiles]

"000007FF"="eT9.StrTrk.0409.kmap.txt"

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\InputModuleDlls]

"1"="eT9DisInput.dll"

[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\LdbFiles]

"0109"="ENlbUN_xt9s.ldb"

[HKEY_LOCAL_MACHINE\Software\OEM\MASD]

"xT9"="1_02_B120707_2"

[HKEY_LOCAL_MACHINE\Software\XT9 Input Method]

"IMEMode"=dword:0

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]

"Ime File"="\\windows\\et9ime.dll"

"Layout Text"="eT9 IME"

"Keyboard Layout"="00000409"

I only have one problem the writing options wont open the T9 settings I have to press and hold the * key to open the settings, I would like to fix this.

I also have XT9 Settings available under my all settings menu.

So what do you think have I missed a file a registry setting anything?

Would greatly appreciate any help.

Thanks
[Non-Touchscreen Windows Mobile Other] Aqua_Daemon:
@ ND4SPD

I not the programmer. The algorithm is represented to me so: to try to add all files 419.mui in ROM, to stitch the device and compulsorily to specify in the registry replacement 409 on 419. Or I something not so think?

Or to try to compile .cab which will add in ROM all files 0419.mui there where files 409.mui are stored and to make corresponding editing of the registry?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
@shadowmike: sorry, Hotmail was being stupid and so was gmail. I could upload so I had given up and completely forgotten about it. download: http://www.sendspace.com/file/65pk6a

@Aqua_Daemon: will do so. Look for a russian beta rom next week.

@freyes01: Will recreate a T-Mo rom soon. I've

@-MyHTC-: look at those layout keys and dlls. (et9ime.dll, etc.) those might give you an idea. I haven't looked at anything yet.

I won't be working on this stuff at all as I've got finals this week. After that, I have summer break an am willing to do some work on it.
[Non-Touchscreen Windows Mobile Other] Aqua_Daemon:
Wow! I with pleasure shall test new ROM
[Non-Touchscreen Windows Mobile Other] shadowmike:
nd4spd check your pms i sent you a code to upgrade your sendspace account for 1 month :)
[Non-Touchscreen Windows Mobile Other] -MyHTC-:
Thank you for the suggestion I will have a look.
[Non-Touchscreen Windows Mobile Other] motivecc:
new user first post, so sorry if i skipped over some stuff

i followed the .zip of installations to the T, and when i try to run RUU with the .nbh provided on rapidshare, it stops at 2 percent and says the file is corrupt, and well right after that, my computer got virused up so one of the mirrors, don't know which one may be f'ed... i'll be going through safe mode when i get the time to repair the damage done, so downloaders beware... i've never had a virus on my main PC ever (at least one that lasted more than a day without me fixing it) so dl'ers beware...

i'm guessing i may have messed the SSPL up somehow, maybe fixed a step, if anyone can enlighten me it would be apreciated

EDIT: and just for added reference, i thought my shadow was bricked until i fiddled around and converted the ROM back to the original tmo ROM after a little searching, so a sigh of relief on that note

UPDATE: got the rom to get to 100 percent, try starting up the device and it gets stuck at the htc logo, waited over 20 minutes and it wouldn't go past that, i try turning the device off then it goes into a cold boot config, gets to 2 percent again, and then shuts off... think i'm out of luck unless somebody has the same batch of devices as me maybe, mine is a specially packaged shadow direct from htc that came with an extended battery and factory backplate
[Non-Touchscreen Windows Mobile Other] shadowmike:
so you had a unlocked phone. let me see a pic of your phone.
[Non-Touchscreen Windows Mobile Other] motivecc:
naw, i recieved a free shadow via a sales competition directly from htc... am a t-mobile employee

i got it working btw after the original tmo rom was loaded back on... now if someone can help me with opera installation would be nice, i downloaded the cab file thats posted somewhere on these forums, but i guess i have to get a java program to run this i'm assuming
[Non-Touchscreen Windows Mobile Other] shadowmike:
opera 9.5 from the new diamond does not work on the t-mobile shadow.

go to opera.com get operamini for windows mobile or opera 8.x for windows mobile and install from there.

also the shadow has java built in. go to start > accesories > java.

btw for being a t-mobile employee you dont play with the phones much do you. :p

also I have been in management/sales at my current job (automotive) for the past 3 years. I dont want sales but would t-mobile possibly offer me a management job if i tried to work for them ?