Related
I hope starting a new thread is the way to go on this...
I just updated to the new Sprint Official WM 6.1 ROM, and immediately could not connect to the internet.
I tried running the IOTA automatic data provisioning update (Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start) and it failed repeatedly with a 1012 error. As was posted by others, I noticed that there was a "CurrentUserName" setting in Start->Settings->System->Device Information that had [email protected] where I would have expected to see [email protected] instead. (that would have been my Sprint provided email address) The first thing I tried was to go to the phone dialpad and dial ##3282# to start the EPST program and check my data provisioning settings (this requires that you know your MSL - Master Service Lock Code - if you are going to edit). UserName was blank there, so I tapped the blank setting and held down until an "EDIT" menu popped up. I tapped "EDIT" and changed it to the previously correct [email protected] value. After saving changes and another reboot, I still could not connect to the internet, run IOTA, and the "CurrentUserName" was still wrong. After searching through various settings looking for a way to change the currentusername, I installed PHM Registry Editor and searched again.
In HKEY_LOCAL_MACHINE/Software/OEM/DIM there is a key "EnableCurrentUserName" and it was set to 1. I edited that and set it to 0, exited the Registry Editor, and restarted the device by holding the power button until it warned me about shutting down. I tapped "Yes" and it shut down and restarted. The "CurrentUserName" setting no longer appeared in the Device Information page. At this point I was able to run IOTA successfully and imediately after that I could use the internet and other data services.
I hope this helps someone. Sorry to be so long winded, but I was trying to answer as many "How? Where?" questions as I could as I went.
Briefly:
1. Using WM Registry Editor software, change HKLM/Software/OEM/DIM/"EnableCurrentUserName" from 1 to 0 then save changes and exit editor.
2. Dial ##3282# and edit UserName to correct [email protected] address. Device will reboot when you exit and save changes.
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Thanks to all the others here who have helped me along the way,
Scruffy
anyone else know if this works?
i just flashed the new sprint rom and now the data connection does not work.. no internet.. ? I was just wondering if anyone else had this problem and does this fix it?
After some more time with this ROM installed I have found that it is not neccessary to change the ##DATA# (##3282#) user name settings. Just change the HKEY_LOCAL_MACHINE/Software/OEM/DIM/EnableCurrentUserName value to zero, save changes and then you can run the IOTA update successfully (or at least I can).
I have found that I need to do this every time I do a hard reset of my device. I hope this helps someone else.
Scruffy
this did not work for me.. I Get error code 67
i started a new thread here........ http://forum.xda-developers.com/showthread.php?t=415666
so maybe someone will chime in... the ##3282# does not work for me at all.. you hit that on the dial pad and nothing happens... so i can not access that menu...
For now i went back to a OEM rom and called sprint and they got me working by doing a MASTER RESET... also ##3282# works on OEM roms but i think the file EPST.EXE is missing from the CUSTOM roms... any input would be great..
Not working for me.
i'm sure a master reset from within #778 or whatever would work but i don't feel like
putting in the data again.
Scruffy said:
I hope starting a new thread is the way to go on this...
I just updated to the new Sprint Official WM 6.1 ROM, and immediately could not connect to the internet.
I tried running the IOTA automatic data provisioning update (Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start) and it failed repeatedly with a 1012 error. As was posted by others, I noticed that there was a "CurrentUserName" setting in Start->Settings->System->Device Information that had [email protected] where I would have expected to see [email protected] instead. (that would have been my Sprint provided email address) The first thing I tried was to go to the phone dialpad and dial ##3282# to start the EPST program and check my data provisioning settings (this requires that you know your MSL - Master Service Lock Code - if you are going to edit). UserName was blank there, so I tapped the blank setting and held down until an "EDIT" menu popped up. I tapped "EDIT" and changed it to the previously correct [email protected] value. After saving changes and another reboot, I still could not connect to the internet, run IOTA, and the "CurrentUserName" was still wrong. After searching through various settings looking for a way to change the currentusername, I installed PHM Registry Editor and searched again.
In HKEY_LOCAL_MACHINE/Software/OEM/DIM there is a key "EnableCurrentUserName" and it was set to 1. I edited that and set it to 0, exited the Registry Editor, and restarted the device by holding the power button until it warned me about shutting down. I tapped "Yes" and it shut down and restarted. The "CurrentUserName" setting no longer appeared in the Device Information page. At this point I was able to run IOTA successfully and imediately after that I could use the internet and other data services.
I hope this helps someone. Sorry to be so long winded, but I was trying to answer as many "How? Where?" questions as I could as I went.
Briefly:
1. Using WM Registry Editor software, change HKLM/Software/OEM/DIM/"EnableCurrentUserName" from 1 to 0 then save changes and exit editor.
2. Dial ##3282# and edit UserName to correct [email protected] address. Device will reboot when you exit and save changes.
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Thanks to all the others here who have helped me along the way,
Scruffy
Click to expand...
Click to collapse
how do i find [email protected] where would that be?
Scruffy said:
3. Run IOTA by going to Start->Settings->Personal Tab->Phone->Services Tab->Internet->Get Settings->Start
Click to expand...
Click to collapse
I just upgraded to NFSFAN's latest ROM, everything went well but I can not get my internet to work. The one thing I did notice is under the services tab, internet is not an option. I loaded the dcd sprint carrier 20090714 cab am I missing something else?
Thank you for any help you can provide.
Update:
Well I went back and flashed to the HTC 6.1 rom, then back to the 6.5 rom. That fixed my internet issues, but that option is still missing for me. Then after all of that my MSID was really screwed up. Everything seems to be good now.
please please help me clear the instructions
i have a horribly vague idea of what i need to do, to get the internet working again.
i already got the IOTA_1120 zip file in my cell but when i even try to open it up it says that there is no application that is related to to it, so i must start this application and open up the file from within. How do i do this? am I even doing what im supposed to??
Where exactly is HKEY_LOCAL_MACHINE/Software/OEM/DIM and how do i get there???
if you could please instruct me with simple stieps i would greatly appreciate it, simple being like start>program files> etc.
please help i am one step away from smashing this damm cell into the wall
electricfeel_2012 said:
i have a horribly vague idea of what i need to do, to get the internet working again.
i already got the IOTA_1120 zip file in my cell but when i even try to open it up it says that there is no application that is related to to it, so i must start this application and open up the file from within. How do i do this? am I even doing what im supposed to??
Where exactly is HKEY_LOCAL_MACHINE/Software/OEM/DIM and how do i get there???
if you could please instruct me with simple stieps i would greatly appreciate it, simple being like start>program files> etc.
please help i am one step away from smashing this damm cell into the wall
Click to expand...
Click to collapse
The path of HKEY.... is actually on the registry. You need to use a registry editor (like PHM Regedit) to make the necessary changes to the registry. I would recommend you to re-read those instructions as they will not get any easier than that. Alternatively, if you are on Sprint's official rom and have absolutely no clue what you are doing, you can always call them and ask them for help.
As far as the IOTA zip file, if you cannot open it, that means that you do not have any program to extract from compressed files in your device. Your best bet is to transfer the file to the desktop and extract it there. Once you are done, place the extracted contents back in the device and run it in there.
I have G-alarm 1.5. installed on my rhodium and i have noticed having daily G-alarm Debug files being created in the "My device" directory.
For instance i have the following files in "My device" directory:
20091112_GAlarmDebug.txt
20091113_GAlarmDebug.txt
Why does this happen and whats its purpose? Each of these files size arnd 4 - 10 KB, which without a purpose is a useless drain of memory space.
Does anybody have an idea why this is happening.
Try to disable debug logging
If you have "Enable Debug logging" selected in Advanced Options, it is normal to have them on your device, G-Alarm behaves as requested.
If you have the setting disabled, there is a problem with G-Alarm.
Radu
Thanks for reply,
But i can't seen any options of enabling/ disabling the debug logging in the advanced set-up.
I am using the 1.5 version of G-alarm. Is there anything else i should disable- enable to get rid of these .txt logs?
I have the same problem with the same G-Alarm version. It loks like, that the latest free version was a test version, and therfore ther is no way to disable debugging. I personally delete these files with TotalCommander, but if they really drive you to the nuts, you can write a small program in MortScript and run it sometimes (i think it would be maximum 5 lines of code) to automate this process.
Mod:
I wrote the MortScript program (see attachment).
You should have MortScript installed, and .mscr format associated to MortScript.exe.
The program contains only one line, which deletes every file in the root (\MyDevice) with the ending GAlarmDebug.txt.
Feel free to modify it (for example if you want to schedule it to run every day or want to add a GUI)
!!Don't forget to rename it to galarm.mscr (xda dev doesn't allow mscr files)!!
DOMy
Decided this should have a thread of its own instead of hiding in another thread.
I originally stumbled onto this thanks to cyryl's post where I found that disabling 3G helped prevent a lot of the Sleep of Deaths (SoDs) I was seeing. (Phone was sleeping with solid green LED, then suddenly switches to orange LED and is totally hung.) That led to the discovery that the Vogue sources (which XDAndroid is derived from) had a bunch of newer fixes to their RIL library that were never pulled into XDAndroid.
I set up a clone of the XDAndroid and Vogue repos and merged them all in here:
http://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/androidhtc1
I also fixed several bugs that weren't fixed in either of the previous source trees as well (mostly memory leaks). The result was working well on my phone, but since then I've gone on to fix additional bugs, making this RIL behave almost identically to the native HTC RIL running on my G1 phone.
I used to get SoDs within about 10 minutes of booting up if I had 3G enabled. Now my phone has lasted 24 hours at a stretch without any crashes. The binary is attached here if anyone else wants to try it out. Instructions courtesy of Entropy512.
Entropy512 said:
To test this fix (should work with any Froyo 2.2.2 based builds):
Unzip the attached zip file
Place libhtcgeneric-ril.so somewhere on your SD card. For organization, I use bindfiles/lib/libhtcgeneric-ril.so
Open conf/froyo.user.conf in your favorite text editor
Within the custom_shells{} section of froyo.user.conf, add:
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
On Gingerbread it would be
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /system/lib/libhtcgeneric-ril.so
Click to expand...
Click to collapse
If you run into problems, get a log taken when the problem occurred and attach it with your post describing the problem!
Problem reports without accompanying logs are useless and a waste of time.
You will always need the output from "logcat -v time -b radio". Sometimes you will also need the output from "logcat -v time" (simultaneous with the first). If you don't know how to obtain these, then please STOP NOW and don't proceed any further with this.
There is an alternate set of files in post #6 for use with a patched rootfs. See that post for the details.
The ril in this post is no longer being updated. Use the alternate ril in post #6 to get the latest bug fixes.
Using CDMA Mode
Documenting this here for my future reference, don't do this unless you're actively involved in helping me debug:
To switch into CDMA mode with your current install
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
update secure set value='4' where name='preferred_network_mode';
.quit
Reboot for it to take effect.
Alternatively you can blow away your data.img and edit /system/build.prop and set ro.telephony.default_network = 4 before booting. (Earlier versions of this post said to use 6 for the mode. That was a mistake, 4 is the correct value.)
The original value was 0, so you can switch back to that if you need to.
You will also need to edit a property file to add your network info anyway. You must add e.g.
Code:
ro.cdma.home.operator.alpha = Sprint
ro.cdma.home.operator.numeric = 310120
Replace "Sprint" and "310120" with the correct name and ID number (MCC/MNC) for your mobile network. If you don't get the operator ID right some features will not work properly (roaming display, international dialing...). The easiest way to do this is just to create a file /data/local.prop and put these settings there. I believe the operator ID for Verizon is 310012 but haven't verified this. A complete list of operator IDs can be found on Wikipedia.
If you run into problems we need "logcat -v time -b radio" starting from as soon as possible in the boot to catch all the gory details. Also a regular "logcat -v time" running at the same time.
In fake GSM mode the phone always used a hardcoded operator ID of 310995, and the APN for that ID was used for mobile data settings. In CDMA mode the phone sees the actual operator ID, so you'll need to add an appropriate APN to match that ID. See http://cleanimport.xda/index.php?threads/1023116/.
Thanks for creating a separate testing thread for this - it needed it, and I was going to suggest it if you hadn't already made this thread .
I have tested this on my CDMA RHOD400.
Seems to work well - unfortunately I'm not a good test case, as I very rarely, if ever, get SoD's.
I do know that 30s sleep issue seems resolved - I made several calls, ran it overnight, and it still sleeps quickly with WisTilt2's test kernel. Now we need him to commit his code, get your code tested a little more and commit yours... Holy cow batman, our port is lookin great!
I use Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Here is my log http://forum.xda-developers.com/showpost.php?p=12403347&postcount=22
Borrow to use once:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
New init version
This is an alternate version of the ril which uses /system/bin/pppd instead of /bin/pppd. In order for it to work, you also must change some files in the rootfs. The new files are attached here in rootnew.zip. Here are the instructions for installing from a root command shell, assuming the zip file is in /sdcard/rootnew.zip:
Code:
# cd /
# mount -o remount,rw /
# rm -rf .git
# mv init.android init.android.BAK
# unzip /sdcard/rootnew.zip
# chmod 755 init.android init.etc/ppp/ip-*-*
# mount -o remount,ro /
Reboot after installing. You only need to do this once on a given rootfs. If you switch to a different rootfs you will need to do it again.
The advantage of using this approach is that the /system/bin/pppd doesn't ever try to write to /etc/ppp (so there is less opportunity for filesystem corruption when things go wrong) and the ril will not interfere with Android VPN use. Also this approach is required for NAND installs. I expect that this approach will be the default in the next FRX/GBX releases, but so far the changes haven't been merged yet.
This ril is no longer functionally the same as the ril in the first post. The code is in the initpppd branch of my git repo.
https://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/initpppd
Update: Everything in my initpppd branch has been merged into the main xdandroid repo. All of my fixes will be in the next official xdandroid builds, there's no longer any need to use my personal repo.
You can safely install the rootnew files regardless of which ril you use. But the ril in this post requires these files; it will not work without them.
Note: the init script in this rootnew archive is a patched version based on the xdandroid git repo. If you're running on F22's rootfs, you don't need this archive. Instead, you can grab F22's rootfs image with my patches already applied.
Also note: the ril attached here is no longer equivalent in functionality to the one in the original post. This ril no longer has fake GSM support; if you're using a CDMA phone see below. This ril also no longer uses any options in the startup.txt file. If you had force_cdma or north_am_dialing in your startup.txt file they are now ignored. If you set your operator name and ID correctly in build.prop then the dialing is automatically handled by Android.
Also this ril supports dynamic mode switching for world phones. If you have a rhod400/rhod500 and use both GSM and CDMA you can switch back and forth on demand. Currently the menu for this is buried inside the *#*#INFO#*#* menu.
[size="+2"]New CDMA support[/size]
This version now switches into CDMA mode automatically; you no longer need to set the default_network property or muck with sqlite3. If you have a rhod400/rhod500 and no SIM card installed, your phone will use CDMA by default. If you have a SIM card installed, it will default to GSM and you'll have to switch to CDMA yourself. If you're using my updated Phone.apk (a new version of that as well, not yet uploaded) then the World Phone menu will be enabled automatically and you can use that to select the mode. Otherwise just use the *#*#INFO#*#* phone menu.
You will still need to set your APN for MMS to work, and you'll probably still need to install an eri.xml file. And you still need to set your operator ID properties.
Note: if you try to switch modes on the current GBX image, the Phone app will crash. It's a bug in Google's code, not the RIL. I've written a fix for this and the fix is in the XDAndroid repos, so it will work fine in the next GBX release. Froyo is fine either way.
muziling said:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
Click to expand...
Click to collapse
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
highlandsun said:
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
Click to expand...
Click to collapse
Okay, so just to clarify, this shouldn't work for CDMA at this point? Arrrghhh is on CDMA, it seemed to work for him?
highlandsun said:
OK. Definitely it will fail with Gingerbread. I'm only testing with Froyo so far.
Click to expand...
Click to collapse
Also, just to clarify, this shouldn't work on Gingerbread at all at this point (and not just setting the network to 6 will fail)? I have it mounted in Gingerbread under the lib/froyo directory, since there is no /lib/gingerbread directory, and everything seems to be normal so far but I'm not sure how to tell if it's actually being used and I haven't called the network 6 command yet.
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6 4).
OK, here's the current status before I leave for the weekend:
Currently the ril code sets a radio status of "SIM not ready" when the radio power is first turned on. The CDMA phone sees this and says "wtf, it's trying to use a GSM SIM card" so it kills itself to start the GSM phone code again.
So we need to be able to obtain the current operating mode in the ril so we can see, if we're trying to startup with network mode 6, it should use some other radio status code instead of the SIM-related codes.
Anyone who wants to dig into it and think about how to do that, please do...
highlandsun said:
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6).
Click to expand...
Click to collapse
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
pdawg17 said:
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
Click to expand...
Click to collapse
It's only working well for GSM. Sounds like you should pass it by for now.
Request - for those of us following your source tree, when you upload a binary can you post which git revision that binary was built from?
Thanks
Started running this last night when you posted it in the other thread. I'm GSM only (Rhod210) so I can't help with CDMA, but I've been the victim of what are probably RIL related bugs. In areas with bad signal and when switching between EDGE/GPRS/UMTS networks I've experienced a bug where the "phone" part of the phone starts going haywire. The first symptom is that the phone no longer responds to incoming calls. From that point on, I can receive one text message after which point I can no longer send or receive text messages nor can I make or receive calls. Switchiung to airplane mode doesn't fix the issue and a reboot is required.
I'm hoping you've accidentally fixed this bug too.
highlandsun said:
It's only working well for GSM. Sounds like you should pass it by for now.
Click to expand...
Click to collapse
Confirmed. Works well on my Tilt2. It seems that data speeds are better as well. Can't say for sure but will keep testing. Great work!!
For the less educated amongst everyone, what chance is there of making a quick kernel zImage for us to try out?
I can't use anything after Feb 28th or I get a home screen lock.
The RIL is not a kernel module (.ko), but a loadable library (.so). This is why you need to use the mount command in froyo.conf.
-- Starfox
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Okay, found the conf file. Making the changes now! Must've been a late night. lol
problem still, logs below
6d5b27e_6.zip is network mode 6 's log, com.android.phone keep FC.
6d5b27e_0.zip is network mode 0 's log, when 3G enable, phone in, who call me will listen hang up audio ,and I can not accept and reject this call in my phone.
Raa_1 said:
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Click to expand...
Click to collapse
That's odd - what build are you running, and how was it installed?
I know the conf file was included with the FRX05 full ZIP bundle (or was it the FRX04 bundle?)
k guys, this thread is coming about after respectfully moving the discussion from kalaker's s-off thread.
i've been looking for a while about how to back up my nv keys for data, just in case anything happens to my one v. this is thanks to New Optimus (for steps 8-10) and jmztaylor, who informed me the open sesame door trick works. I AM NOT RESPONSIBLE FOR HOW SOME MAY USE THIS. open sesame door trick has the potential to screw your phone up if you dont do it right, or delete an nv item.
CDMA ONLY (i dont think gsm works the same way anyway)
YOU ARE NOT MODIFYING ANYTHING. All you are doing is backing up your AAA and HA keys. they are used to identify and register your device's data on the VM network. IF YOU MODIFY ANYTHING, ITS YOUR FAULT IF YOU SCREW IT UP.
step 1:
download and install qpst. im not linking to the file, you should be able to find it easily enough by googling it.
step 2:
open up qpst configuration, and let it sit in the background for a minute. install the htc diag drivers for one v from here: http://www.htc.com/www/support/
look for the one v, and download and install the HTC Sync program which will install all the drivers you need.
step 3:
close out of htc sync once its installed, its an annoying program anyway. connect your phone, make sure adb debugging is enabled in developer options in settings. open the dialer, type in ##3424# (##diag#) and a screen will come up that says on and off, with select at the bottom. click on, then select, and it will ask you for your msl code.
note: your msl code can be obtained by a app in market called MSL Reader, you need root for this. follow the prompts in the app, its easy enough to do.
step 4:
after entering your msl code and entering diag mode, go back into qpst configuration. click on "add new port" toward the bottom right, and make sure when the window opens "COMx- USB/QC Diagnostic" is selected and click ok. qpst configuration should now recognize your phone as SURF-MSM7830. if it doesnt, update your version of qpst.
step 5:
in qpst configuration, click on "Start Clients- EFS Explorer". make sure you put your msl in the box that says spc, and click ok. a please wait window will pop up, it will only take a few seconds.
from New Optimus's post: http://forum.xda-developers.com/showpost.php?p=29951978&postcount=796
8. Once the phone reads completely make a new directory named (open sesame door) without the parentheses and all lower case
9. After making the new folder locate abd.exe from the android sdk install folder and press: start, run and type cmd then press enter you will get a command prompt window that opens up navigate to the android sdk directory and type; adb reboot, the phone should then reboot if you’ve done as you were supposed to.
10. After the phone reboots read it again with QPST EFS Explorer which still should be opened, you will notice that the red no access circle has been removed from the nvm directory so expand it and go to the num directory,
Click to expand...
Click to collapse
(note: edited New Optimus's post to remove links to esn/meid changing which is frowned upon in the forums, also i already had the open sesame door folder created upon making the pictures.)
left click and drag 465, 466, 1192 and 1194 to your desktop.
keep 465,466, 1192 and 1194 in a safe spot, they are how you have data on your phone. if something happens to your HOV and those are gone, good luck getting data back.
Quick noob question, do these files get generated by the carrier when you activate the phone?
whoshotjr2006
Do AKEY, SSDA and SSDB files need to be saved? if so, where are the files?
reachforthesky said:
whoshotjr2006
I know the content of file 0 and 1943. Could you briefly describe the contents of these 4 files (465, 466, 1192 and 1194)? Which one is HA, AAA, SSDA and SSDB? Are there any more important NVM files need to be saved?
Click to expand...
Click to collapse
465^"Data Services Mobile IP General User Profile"^"Data*"
466^"Data Services Mobile IP Shared Secret User Profile"^"Data*"
1192 is the AAA secret
1194^"HDR Access Network Stream CHAP Authentication User ID"^"Data*"
The reference is here: http://forum.xda-developers.com/showthread.php?t=1954029
Got sooo excited when I saw this. Used to switch firmware's on my optimus v with the firmware of the optimus s, and use optimus s roms. Had all of my nv data and everything else backed up. Forgot you have to have be on an aosp rom for this to work because you need a port. -_- I don't have a stock backup and right now I'm tethering, so it'd take awhile to download a stock backup. Guess I'll have to wait a week or so.
nvm, I found a backup. I tried it out, and i got to the qpst efs explorer. I did the open sesame door, and it unlocked the nvs, but I only had a couple of the files from the list. I did not have 465 or 466. Also, I had an issue when I tried to recognize the phone. It did recognize the phone in diag mode with the port, but not as surfmsm7830. I have the most updated version of qpst.
I'll have to check what version I'm running of qpst, I know its close to the newest if not the newest. It wouldn't recognize my phone correctly until I had a new enough copy.
Also the first time I tried the open sesame door trick, I too had the limited nv items. I used the ruu to go back to stock, and once I did that the open sesame folder dir survived the ruu and unlocked the rest of the nv items.
Hope that helps.
Sent from my One V using xda app-developers app
What version of QPST are you using for this? I get an error "Online connection failure: Unspecified error" when trying to connect.
I think my phone isn't getting read properly by QPST because under phone it says "(unknown)" even though the other fields fill in correctly.
CDMA Workshop reads my phone no problem, but this thing no luck.
EDIT: Found an updated build and it displays the specified info under phone. Not sure what the lowest working version is, but v2.7 build 323 will not read it, build 366 will though.
HI all
maybe its wise to start a new thread how to make an offline package for our phones
especially because of these info :
Microsoft begins to block Windows 10 Mobile updates for the majority of Windows phones
https://mspoweruser.com/microsoft-begins-block-windows-10-mobile-updates-majority-windows-phones/
https://mspoweruser.com/only-13-windows-phones-will-get-the-windows-10-creators-update/
My question is :
-how to make an offline install able upgrade/update package for our phones ( fiddler i think )
-how to update the phone with all the cabs downloaded ( uitool.exe ?? )
What i know .. first install old firmware on your phone , install fiddler on your pc and download from your phone thats connected to the fiddler proxy your files.
Can one of you guys make a SIMPLE instruction how to download these CAB files from microsoft ? and how to configure fiddler in this case
The last question ...
What i know ... use uitool.exe to "upload" / install these downloaded cab files ( through fiddler ) on you phone.
Can one of you guys make a SIMPLE instruction how to install these cab files ???
I think i can speak for a lot of people with the same question.
Now i have to google/use xda search to find what i need but all the threads are old an out-dated or have old information.
Many thanks in advance !!!
Micheal
megasounds said:
-how to make an offline install able upgrade/update package for our phones ( fiddler i think )
Click to expand...
Click to collapse
That's one way:
- you set up a sniffing proxy on your PC (like Fiddler or Paros)
- configure it to record, maybe even save a copy, of the data it passes through
- flash a rom with WDRT to uninstall updates and start from a known and replicable point, configure a network with your proxy ASAP, and just let it download updates to have a list of cabs to redownload (or even the files themselves, again I'm not terribly familiar) on your PC!
OR you can go to the Microsoft Update Catalog with a non-IE browser, search for a W10M update pack (suggested search string: "000-ru") and from there you can get a list of every single cab for the version you selected!
In fact you will find even cabs not applicable to your phone (indeed you've probably heard of this method from the "download continuum/reset protection to unsupported models" topics), plus there may be a sequence to respect (for instance you can't flash RS3 directly from WP8, as some versions - TH2 in this example - add support for new update formats ["servicing stacks", you may have seen in PC updates])
megasounds said:
What i know ... use uitool.exe to "upload" / install these downloaded cab files ( through fiddler ) on you phone.
Can one of you guys make a SIMPLE instruction how to install these cab files ???
Click to expand...
Click to collapse
This part is easy: you indeed download iutool (from some "windows sdk" download from Microsoft, or a portable version from some interop unlock topic here on xda), then the command is:
iutool -v -p {path to folder with the update files}
And you wait for the files to be copied (nothing will be obvious on the phone) then it'll just reboot to the usual "update/format progress bar" screen - assuming everything went right! All failures, you'll see on the computer screen, in a not terribly useful way...
Fiddler settings:
Tools > Telerik Fiddler Options > Connections (tab):
- Act as system proxy on startup = off
- Monitor all connections = off
- Allow remote computers to connect = on
Restart Fiddler and allow on firewall; Enable "Stream" button on the toolbar
Flash your phone, turn off all WWAN and privacy-related options during initial setup, don't use a MS account, run to the store and turn off auto updates (all of these to minimize non-update network requests)
Configure wifi to have a proxy at your computer's IP and port 8888 (you could have changed it in the settings above),
Just download the updates from system settings as usual, you'll see the list of requests fill up in Fiddler
[Do not enable File>Capture Traffic, that's for dumping the activity of the same computer that runs Fiddler, despite the name]
Once your phone gets to "preparing to install updates", all have been downloaded: so sort the columns by "Host" and select all requests related to "download.windowsupdate.com"
File > Export Sessions > Selected > Raw Files > select a dump folder and leave all 3 options enabled
The dump folder will open, now you have to flatten it (go inside the subfolders and copy all the files in one single folder; if you have Unix "find" this is easy to automate, but with only 10 folders or so it's not too tedious even by hand)
This single combined folder is now what you can pass to iutool for updating via USB!