yashsingh1/xdaforums huggingface dataset:
[MDA, XDA, 1010 Software Upgrading] ronin:
Possible solution.

Ok, Sorry for the non techies here, but:

I hope someone at TMO or AT&T with RIL and RSU access can validate, test and correct this issue and save a lot of its customers the aggravation of lost data.

Since there are no SD card issues with non phone WM2003 editions. I figured the issue had to be related to the RIL and RSU. I used 6 devices with different ROMs and ran the same tests coming up with similar results with "erasures" happening when the RIL was updating itself.

Since I do not have access to the code and the API and do not want to reverse engineer the code and breach your IP. I am posting it here.

You can monitor RIL functions and calls by using a modified tstril found in this site.

The problem with SD erasure is caused when WM2003 RSU files are trying to share the same memory address, handles and I/O MRUs list calls the SD cards are using.

According to the patent on the RIL. The native RIL device will always superceed a PnP device(SD card, GPS and others), renaming it and causing the erasure of file allocation tables with certain cards. Albeit the files are still there the card seems erased and data is not accessible by current software.

This problem is compounded by of your native code that does the same thing within SMS and Bateery Monitor.

I tested this in PPC2002, WM2003 all versions to date. I have attached the the registry settings for PPC V3.0.12039 ( build 11178) with ROM v3.14.40 ENG, RSU 6.18, Protocol 324e4. In which no SD card erasures are occurring. Monitor how the RIL interfaces with the RSU on this and the issue should be resolved.

[HKEY_CURRENT_USER\Software\Microsoft\File Explorer]

"LastLocation"=dword:00000000

"LocalPath"="\\My Documents\\Templates"

"StorageCardPath"="\\Storage Card"

[HKEY_CURRENT_USER\Software\Microsoft\File Explorer\MenuMRU]

"MRUList"="bdac"

"b"="\\My Documents"

"c"="\\Windows\\Start Menu\\Programs"

"d"="\\Storage Card"

"a"="\\"

[HKEY_LOCAL_MACHINE\Drivers]

[HKEY_LOCAL_MACHINE\Drivers\Active]

[HKEY_LOCAL_MACHINE\Drivers\Active\29]

"Hnd"=dword:00097820

"Name"="DSK1:"

"ClientInfo"=dword:00000000

"Sckt"=dword:00000000

"PnpId"="UNKNOWN_MANUFACTURER-"

"Key"="Drivers\\PCMCIA\\SDCard"

[HKEY_LOCAL_MACHINE\Drivers\Active\08]

"Hnd"=dword:00078480

"Name"="RIL1:"

"ClientInfo"=dword:00000000

"Key"="Drivers\\BuiltIn\\RIL"
[Samsung Galaxy Nexus] bmata1980:
I don't know if this is an issue with the new OS but it seems that we cannot run tethering apps (rooted). specifically it is the WEXT (ad-hoc) function... Which as far as I can tell is the way it broadcasts to other computers. Please don't respond telling me to use "foxfi" or some other "non-rooted" app. The reason we use the rooted ability is to be able to bypass the network hoops and use a "backdoor" to get what's rightfully ours. The function of teather ring was working fine on the pervious jellybean OS so it goes to say that someone just needs to fix this bug. Please help
[Samsung Galaxy Nexus] langdonx:
I guy offered up a fix and signed it with his developer key here: code.google.com/p/android-wifi-tether/issues/detail?id=1661#c109 (can't link it since I'm new)

It'll tide you over until they officially fix it in the Play Store.

It's near perfect (laptop connects and gets out fine, but my Vita connects and cannot get out... to the internet).
[Samsung Galaxy Nexus] bmata1980:
OK I'm a dummy at this point. I downloaded the patch ( from user pfnguyen on post #109) its a ".man" file..? Not sure what to do with this... Am I going in the right direction?
[Samsung Galaxy Nexus] a2f:
There's an actual file there. Use your browser's search function to look for ".apk".

If you're a Sprint user, it won't work. Look for WiFi Tether Router in the Play Store. I'm using that now and it works fine.
[Samsung Galaxy Nexus] pupule:
I have similar issue with vzw gnex

I tired Mwalt2s method of disabling native tether check here: http://xdaforums.com/showthread.php?t=2176954

But I still get errors on startup of wifi tether. Does the above instructions apply to vzw as well?

Thanks,

Pupule
[Samsung Galaxy Nexus] bmata1980:
OK so this download form "pfnguyen" in the "TrevE Mod" which I already had. So how does one get this thing to work? The phone is verizon so I don't know if that makes a diff. There are a lot of settings on this app and I really have no idea what they really mean. Really... I'm dumb when it comes to this so you're gonna have to draw it out in crayon for me
[Samsung Galaxy Nexus] tgeery:
wow! thanks for sharing this link! hopefully, it's gonna work well... will test that right now!
[Samsung Galaxy Nexus] bmata1980:
HELP!!! THIS SUX!!! This tether is my only source of internet at my house... Don't ask. I really need help to figure this thing out. Any help will be much appreciated!
[Samsung Galaxy Nexus] bmata1980:
Anyone that can help at this point would be great... Still cannot get WiFi tether to work. Currently running treve mod WiFi and still no dice...
[Android Themes] mowmo:
ICON PACK

Romow HD

300x300px - 420dpi

PLAYSTORE

ROMOWCUBE

Download PlayStore

Sense5

Download PlayStore

Holo Dark Minimal

Download PlayStore

Holo Light Minimal

Download PlayStore

Sense 5 Weather UCCW Skin

Download Playstore
[Android Themes] mowmo:
added sense5
[Android Themes] ftarules:
Coudl you provide an icon mask? THis way all the icons will be themed similar to your app.
[Android Themes] mowmo:
R: [Icons Pack] RomowCube & Sense5 For APEX-NOVA-GoLAUNCHER-ADW

Yes. The theme has the mask for all icons
[Android Themes] mowmo:
added new icon pack
[Android Themes] mowmo:
added new icons pack HD 300x300 - 420dpi
[Android Themes] mowmo:
added .Sense 5 Weather UCCW Skin
[Android Q&A, Help & Troubleshooting] kalilxd11:
help me with this phone. is a cell phone from china, I was flashing the rom and it did not do the backup, result lost his cell phone and do not know which is the original rom it, many do not know it because I have no information as to see because he does not care anymore. Please some sympathetic soul could help me and give me the original rom it?

I just know it was bird73_gb is brand Yusu. I bought as light wei (y801) and heeeeeeeeeeeeeeeeelp meeeeeee
[Android Q&A, Help & Troubleshooting] kalilxd11:
pleaaaaaaaaaaaaase
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baddaybeav:
Ok, I'm drawing a blank on this...

I have Encryption Enabled in CM10.1 on my GSIII

The problem is that when I reboot to apply an update it fails due to not being able to decrypt the mmc.

TWRP acknowledges that it's encrypted and asks for the password (a PIN that I set up)

but every time I try it tells me it's a bad password.

Am I missing something, some setting somewhere?

The work around is rather annoying, it just involves me copying the zip to the external SD card and installing from there.

Does CMUpdater support storing the zip on the sd natively that'd be a great work around for this as well? I can't find that setting anywhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glennexpert:
Have you been able to resolve this? I'm running in a similar issue.

Company policy demands encryption and today, suddenly out of the blue, it reboots and asks for decryption password.

When I enter it, devices says it's invalid... no way to boot into recovery or into flash mode.

Device is a samsung galaxy s3 mini

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] walleyeuk:
Me too!

This is really strange, I'm getting this too. I also have to have my device encrypted for my work's MS Exchange access :rolleyes:

I'm using latest TWRP 2.6.3.3 and have had no issues with my encryption password not being recognised with this version of TWRP before.

Device details - I'm using an international (GSM) HTC One. Recently I have upgraded to Android 4.3/Sense 5.5 via Telstra OTA update. The ROM is entirely stock from Telstra, just unlocked/rooted. Super user is via SuperSU v1.80
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] glennexpert:
Hi, I haven't had an HTC since the first "desire" and before that I had an HD2 for over 5 years... :)

So, if you are able to access TWRP you can get around this by fully formatting all your encrypted partitions and installing your custom rom again.

If that doesn't work you can try to restore the device with proper HTC tools, like Kies for Samsung devices. It fully resets the device back to stock recovery and stock rom.

I've found no way to restore any of my data. Luckily I had a cloud back-up with Titanium Back-up pro.
[Sony Xperia S, Acro S, Ion] daddyspud:
OK I've rooted recovery etc but wana flash a custom kernel and all kernels require unlocked boot loader the issue I have is that unlocking the boot loader official way Im not able to do due to system configuration telling me boot loader can't be unlocked

So I wondered is there any way I can change this I'm on .50 firm ware n on xzxxperience v2 all is well just like me custom kernel as well

Thanks spud

PS I'm have a Xperia s 3uk
[Sony Xperia S, Acro S, Ion] Ben36:
Nothing you can do if it's not unlockable I'm afraid
[Sony Xperia S, Acro S, Ion] daddyspud:
ahhh i c thats abit of shame ow well ill just have to stick to stock kernel
[Sony Xperia S, Acro S, Ion] Ben36:
I know I think its stupid why some have been made unlockable and some haven't. Why not just make them all the same
[Sony Xperia S, Acro S, Ion] Vaith:
Odp: Unlocking boot loader assistance

I have answer : Money.
[Sony Xperia S, Acro S, Ion] UchihaDareNial:
View attachment 1843301

Contract
[Android Stick & Console Computers General] marvi0:
Dear all quick question, I bought a mk809ii but unfortunately the keyboard won't be delivered until next week. Problem is I want to take this with me away for the weekend, what can I buy and use in the time being until my proper keyboard comes. Am in UK and will now obviously have to buy this in store somewhere so your valued input please.?
[Android Stick & Console Computers General] bananapeal:
I believe you need a powered usb hub for usb keyboard to work well. Simplest might be to get a bluetooth keyboard that is known to work well with android. oh also, maybe a bigger electronics store will have a "fly air mouse" or "entertainment keyboard". I know amazon has these, so with 2 day shipping...

maybe you can try pairing a ps3 controller if you have one of these around. but you prob need keyboard first...
[Android Stick & Console Computers General] ColinB63:
As said above, if you have a usb keyboard and mouse, you can use them with a powered usb hub.
[Android Stick & Console Computers General] mattyinob:
My two cents...

I've been using this on my SGS3. Force closes upon orientation change as well as some other glitches, but works for the most part. Solution if you don't have your keyboard/mouse with you. If this helped, please thank me to the left. Good Luck

Description w/video: http://tabletrepublic.com/forum/android-mini-pc/rkremotecontrol-remote-control-app-rk3066-3285.html

Confirmed Working download: http://fs1.d-h.st/download/00022/CBg/RKRemoteControlV1.1.0-1116.apk
[Nexus 4 Original Android Development] lyriquidperfection:
Okay here is how you enable DIAG Mode on the Nexus 4:

su -c 'setprop usb.sys.config diag,adb'

And to restore MTP Mode:

su -c 'setprop usb.sys.config mtp,adb'

Note: You must be rooted in order to issue the above commands.

Now for the hard part. Although enabling DIAG Mode is easy, finding the Qualcomm diagnostic drivers for this device on the other hand is not and without these we cannot do much more.

If anyone can get these drivers or has the knowledge to patch Samsung's drivers to enable the Diagnostic Serial Port then please get in touch.
[Nexus 4 Original Android Development] Kaffeekranz:
My first guess for obtaining the drivers would be LG.

I hopped on their site, looked for the OG resources and downloaded them; they do include generic diag drivers.

I thought I'd just try and see if they worked for a N4 in diag mode, but your command did nothing as far as I could see on a non-stock ROM.

The Nexus still shows up with MTP access, and enumerates with the same VID and PID, with and without USB debugging enabled that is.

Next step would probably be having a look at the Optimus G's driver entries and changing them to the N4's, if we could see what the N4 enumerates with.

If that makes sense to any of you.

Good old Motorola days, weeks spent sifting through their OMAP bootrom drivers.
[Nexus 4 Original Android Development] lyriquidperfection:
Well here is a link to the USB initialisation rc script source code:

https://android.googlesource.com/de...974430a67da4878c61de0970b56f/init.mako.usb.rc

Here we can see exactly what gets changed when setting property sys.usb.config to diag,adb.

As you can also see we also have the ID and vendor info to modify another devices driver with.

Let the games begin!
[Nexus 4 Original Android Development] Kaffeekranz:
Without changing anything in LG's drivers it already recognized LGE AndroidNet For Diagnostics Port (COM3) and AndroidNet USB Serial Port (COM4), but it got stuck on a CDC serial driver.

And right when I'm typing this and downloading QPST the phone reboots.

But you should have a go at LG's drivers, they already seem to work partly.. I'm going to put it in diag mode again and see how QPST responds.

Yup, both ports are basically recognized, though I'm lacking knowledge of QPST.

I'm guessing the first one is the modem?

The read out on it works flawlessly (after figuring out that an unlocked phone probably has no MSL/SCP) with a QPST version you uploaded last year (what a coincidence!), but I can't connect to the QC apq8064 and I don't know whether I'm even supposed to. But a newer QPST version would be worth a shot.

But like I said, I'm seriously in over my head.
[Nexus 4 Original Android Development] lyriquidperfection:
Thanks a lot for doing this. This certainly gives me something to work on! :)
[Nexus 4 Original Android Development] frescoraja:
Would this allow us to unbrick a nexus 4? Or perhaps unlock radio bandwidths for use on LTE networks ? I am not familiar with qpst I think I used it once to flash a droid to cricket.
[Nexus 4 Original Android Development] lyriquidperfection:
OK I installed the LG Drivers but still a no go for me. Can you have a look in your device manager and tell me what driver name goes with each PID & VID.

Thanks in advance.
[Nexus 4 Original Android Development] scottx .:
Isn't qpst for cdma phones? I've never used it on a GSM phone, only sprint and cricket phones.
[Nexus 4 Original Android Development] lyriquidperfection:
Not necessarily. Advanced functions maybe but I used QPST on my Samsung SGS3 LTE I9305 which was GSM but as it used a Qualcomm Modem I was able to backup and restore nv items in diag mode.

This is what I am trying to achieve with the Nexus 4.

I also think having access to the nv area will allow us to tinker with other things.
[Nexus 4 Original Android Development] Kaffeekranz:
Does it even pick up on the additional devices?

It was pretty straight forward for me, besides getting into diag.

I first enabled USB debugging, then terminal

su

setprop sys.usb.config diag,adb

Afterwards I connected the phone and my Win7 x64 PC already started installing the LG diag drivers.

But I'll have a looksie what drivers and VID/PID it uses specifically when I'm back home tonight.

(And I deleted the standard N4 ADB drivers first, but I doubt that made a difference)
[Nexus 4 Original Android Development] lyriquidperfection:
Didn't install anything for me. I just have 4 devices. 3 say Nexus 4 and one says CDC Serial.
[Nexus 4 Original Android Development] RussianBear:
What's the goal with the diag mode here? lg uses lgnpst for their phones, and we have a thread on here somewhere that has stock roms in that format, if anyone wants to try it out. You can get your nexus in download mode(vol buttons combo) and potentially revive a bricked device.

Edit: here's the thread. http://xdaforums.com/showthread.php?t=1976057
[Nexus 4 Original Android Development] lyriquidperfection:
Thanks for the info. I have already been looking into this however as QPST is specifically for Qualcomm chipsets you can potentially do alot more with it. LG's Tool is quite restricted in many respects.
[Nexus 4 Original Android Development] RussianBear:
What are you trying to accomplish? I could point you towards a few very good threads on here. Different chipsets, but goes deep into some Qualcomm stuff.
[Nexus 4 Original Android Development] lyriquidperfection:
Mainly backing up and restoring of all nv items etc. I have a program I made that can communicate with Qualcomm chipsets which allows IMEI repair etc so im really looking to make Nexus 4 work correctly with it then I will release to the masses for testing etc.
[Nexus 4 Original Android Development] airswoosh1:
I can't seem to get my computer to recognize DIAG mode after entering the command in terminal emulator. I tried uninstalling the ADB drivers and tried it without touching them. Any tips?
[Nexus 4 Original Android Development] RussianBear:
Check this post for drivers: http://xdaforums.com/showthread.php?p=40195799

Asus padfone2 has the same apq8064 chipset.

Can't test, as I'm at work.
[Nexus 4 Original Android Development] sucsss:
did you ever get this working?
[Nexus 4 Original Android Development] lyriquidperfection:
Yes I have it working and can backup nv in QPST but restore always fails at 9 percent.

To get device recognised in diag mode you must install the latest LG United USB drivers then place phone in diag mode as per the first post.
[Nexus 4 Original Android Development] freddysam:
I have found that restoring certain nv values causes errors on some phones. I think it is a protection system. If you an figure out where exactly it is failing, you might have success skipping over the trouble nv values.
[Nexus 4 Original Android Development] sucsss:
yep. i'm running into the same problem.
[Nexus 4 Original Android Development] phr3ak128:
Could you please send a link for cdc driver for windows? Thanks
[Nexus 4 Original Android Development] Masaker514:
So I'm trying to get this to work. I'm able to get qpst to see an open port when the phone is in download mode, but it says no phone. If I use an older version of qpst it reads the port and shows the phone in download mode but won't read it because it needs to be in diag mode. I tried to use the command in the OP but still nothing. Anyone get qpst to read the nexus 4?
[Nexus 4 Original Android Development] Lei M:
the nexus 4 seemed to be a great device. But without an easy possibility to repair broken IMEI we are lost^^
[Nexus 4 Original Android Development] RussianBear:
You just need to find the partition that holds imei, then dd it out and hex edit it, then load back.
[Nexus 4 Original Android Development] pincher65:
can be found here http://xdaforums.com/nexus-4/general/efs-nexus-4-imei-efs-backup-restore-t2740788
[Nexus 4 Original Android Development] Lei M:
If it just would be that easy...

They normally are encrypted. :(

Regards :D
[Nexus 4 Original Android Development] RussianBear:
That's why I mentioned the hex editor. I've done this before on Sensation. You could also try efs, like the guy above suggested.
[Nexus 4 Original Android Development] Lei M:
I appreciate your help, but i fear it is not as easy...
[Nexus 4 Original Android Development] RussianBear:
Well, try it out and let us know.
[Nexus 4 Original Android Development] Lei M:
Well, I already searched anything that could be an IMEI in the hex-editor.

If I would have found anything, my phone could already be working.

But as far as I know may users have this problem (and (nearly) nobody got it to work).

We don't know either what the problem is. I know that one of the efs partitions is corrupted, but not what data in is... :(
[Nexus 4 Original Android Development] RussianBear:
Did you see the partition layout for n4? How did you use the hex editor and what on?
[Nexus 4 Original Android Development] Lei M:
i dd-ed the 3 efs partitions to a file

I opened the second file (partition m9kefs2 - IMEI should be there) with a hex editor.

(If you want i can PM you this file)
[Nexus 4 Original Android Development] RussianBear:
Sure. It has to be somewhere.
[Nexus 4 Original Android Development] wulsic:
This was the list from theEFS i thought

m9kefs1 something with radio

m9kefs2 this partition should contain phone number, imei and some other stuff.

m9kefs3 blank 0000000000000000000000000000000000 only zeros
[Nexus 4 Original Android Development] Lei M:
Giving up now :D

Went through a bunch of threads...

Have installed

* CDMAtoolbox

* EFS Professional

* LGNPST

* QPST

searched the efs2-Partition with hex-editor for hex-IMEI and reversed one.

Even got the drivers working:

At the end... I also didn't get any further as other forum members did the last year

thanks and best regards
[Nexus 4 Original Android Development] lmolas:
I know this is an old post, but this also helped me to connect to a Nexus 5, in DIAG mode, with QPST/QXDM, downloading this driver:

http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425

from this site:

http://www.mylgphones.com/lg-android-usb-device-drivers
[Sprint Samsung Galaxy Note II] nique0201:
Why does every other version of the phone have a choice of kernels and we only have Perseus.... I like Perseus but I want the option of further over clocking like the other phones. Is it possible to port the other kernels for the note 2 to our sprint variant?
[Sprint Samsung Galaxy Note II] cbucz24:
Ummm there's 3.

Perseus, the community one garwynn started, and another newer guy started one. Its all in the original thread.

If that's not enough for you, your more than welcome to build or port one yourself. Its all open source :thumbup:

-Team Nocturnal Like A Boss

-Galaxy Note II Lab Rats Edition
[Sprint Samsung Galaxy Note II] Skripka:
Why is rather simple. Perseus came out... And people have been happy with it it enough not to bother with developing another kernel from scratch.
[Sprint Samsung Galaxy Note II] MiguelHogue:
sleshepic kernel too

-TeaM VeNuM Like A Boss :flipoff2:

-SoA: Son's of Android™
[Sprint Samsung Galaxy Note II] nthornton1990:
Technically yes there are three but the one garwynn made has not been updated to ma7 and the other one is based for aosp Roms only. Perseus is the only kernel that is constantly updated and kept up with. People also have been having problems with performance with it.
[MDA II, XDA II, 2060 General] ID64:
:shock: Just dropped my imate on to concrete floor. Amazingly, it survived, screen is OK, just badly scratched left edge of the unit. Now, I am wondering where I can buy replacement cabinet for it. Any ideas?
[MDA II, XDA II, 2060 General] tbd@immigrantsong.de:
Welcome to the crowd!

I dropped mine on the street a week ago. Just a few scrathes, but it still works as new.

I don't think you'll have much luck finding a new case - expect at O2 (or T-Mobile).
[MDA II, XDA II, 2060 General] jenson:
If You find a way to get a new let us know. I also need one. :(
[MDA II, XDA II, 2060 General] stryker:
is it insured?

if so back it up.... then hold it over your head and drop it.... then repeat as neccessary. If the stubbourn blighter refuses to die, back you car over it.

Then go claim a new one.
[MDA II, XDA II, 2060 General] jenson:
Nice idea, :lol:

but I'm not sure about the insurance.

I'm not a murder

and right now it is hard to get a new one.

So I have to love my individual device with scratches made of my own.

Jens
[MDA II, XDA II, 2060 General] dadarkmcse:
Add me to the list... I dropped my imate this morning and a crescent shaped piece of black plastic broke off the top (right in front of the power button). If anyone finds these replacement cabinents or tops, please post it here!

Jon.
[MDA II, XDA II, 2060 General] ID64:
OUch! Even worse that mone!

I think, I am going to start a new thread - pictures of dropped IMATE :)
[MDA II, XDA II, 2060 General] BarnOwl:
They made the bloody thing way too slippery for a phone........maybe we can fix iPAQ 2200 style rubbers on the side.......... :?