Database Users

NASCAR Sprint Cup Mobile for Mogul Working

Hello All,
I found this on another board for my friend who is a BIG NASCAR fan and got it to work on her Mogul by following the included instructions. I have tested and it is working. The final test will be during this weekends race. Keep in mind that it's a Java App and you will need Java installed. The stylis isn't used, you have to use the arrow keys to control.
Enjoy, I will try to support it any way I can, but no promises.
http://rapidshare.com/files/116171004/NASCAR_Sprint_Cup_Mobile.zip

i dont have a windows folder on my mogul?
never mind, I found it...it was hidden
confirmed, this is working on my mogul also!!!! awesome I have been waiting for this!

Can someone make a cab file for this application

I installed this on mt VZW xv6800 and it works great. I probably cant get the subscription stuff being on VZW but i will test the rest of it on race day.

sliverr7x said:
Can someone make a cab file for this application
Click to expand...
Click to collapse
I don't think this is possible because of the procedure to get it working. A cab file cannot determine what the file name of the file created is, (At least as far as I know).

i must have done something wrong. I followed the instructions correctly I thought.
Using the second set of files that Brett posted I was able to get it to work and I'm not even a sprint customer. Here is what I did:
1. Copied the following files from Brett's zip file into the \Windows\Appdb\ directory. s40__d0.db,s40__d1.db,s40__d2.db,s40_suite.jar,s40 _suite.utf.
Click to expand...
Click to collapse
I had no appdb directory, so I created one, then copied all 5 files into it. I didnt however copy the bin directory over, since it didnt mention that....
I also tried copying with the folder and running things from inside the folder....
Excluding the above files make a note of the highest set of numbered files that starts with an s.
Click to expand...
Click to collapse
I had no files in there.....
2. Using my phones file explorer I browsed to \windows\appdb and opened s40_suite.jar.
3. I went through the normal install steps and received the same error that everyone did.
4. Closed java.
Click to expand...
Click to collapse
that worked fine, java ran, but it never got to an error. Just a white screen with exit and pause on the soft keys.
5. On your phone browse to the \windows\appdb\ folder.
6. There should be 2 new .jar and .utf files that that start with 's' and are one number higher then the number you made a note of earlier.
Click to expand...
Click to collapse
there were a bunch of s0 fies
7. On you PC rename all 5 files by replacing the 40 in each file's name with the number of the new file that was created.
Click to expand...
Click to collapse
went back to the original files from the zip file and renamed them all to s0
8. Copy all 5 files to \windows\appdb
Click to expand...
Click to collapse
copied everything back over and overwrote whatever files it asked to
9. Open java and launch app.
Click to expand...
Click to collapse
Went back to Resco and ran the s0 jar file that I had just copied back over.
No good. I get a 955 error

corey113888 said:
I installed this on mt VZW xv6800 and it works great. I probably cant get the subscription stuff being on VZW but i will test the rest of it on race day.
Click to expand...
Click to collapse
Capture some videos please. I wanna see 'em.

RESTORE IMEI and Product Code w/o ADB, PC (ALL DONE ON PHONE) nv_data.bin

**VIDEO GUIDE ADDED BELOW**
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
(This should be done from stock 2.1 (JF6) but may not be required (got this to work while in phoenix 1.5 without reverting)- results may very in custom rom environments....
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.
fyi this fix is intended specifically for persons with borked product codes and imei's due to custom rom flashes and will not address nv_data issues of carrier blocks/etc. for those who had unlocked their devices and may in fact undo your unlock.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Android Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext. *Since i have good backups now on PC and external sd...i generally just edit the nv_data.bin file in place and save over the original in the efs folder.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete all nv_data files from efs folder EXCEPT FOR YOUR NEWLY CREATED NV_DATA.BIN. (Delete the following: .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files. This differs from video but i also delete any .nv_state or nv.log file present and they are recreated). FYI IF YOU ARE USING A GINGERBREAD ROM AND YOUR EFS CONTAINS .nv_core.bak and .nv_core.bak.md5 DO NOT DELETE THEM with the other .nv files.
15. (This step may not be necessary unless you lose your voice/data connection upon reboot)
Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
**NEW: VIDEO GUIDE**
SPECIAL THANKS TO CONNEXION2005 for providing the video guide below:
http://www.youtube.com/watch?v=JqLK_2I-SBM&feature=player_embedded#!
-----------------------------------------------------------------------------
*DISCLAIMER*
have already had one person post a response that this thread was misleading and stating that:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Click to expand...
Click to collapse
I have seen other users make this claim as well, however, they are either mistaken or what i experienced was a complete anomoly.
I had never backed up my efs folder or nv_data files prior to them being messed up (i didn't know they were there and had never used root explorer to view them until i had to research a fix). The first thing i did was use a hex editor to look at my nv_data.bin and its bak(s) and in fact none of them were good. They all contained wrong product code.
So the process i described was conducted without any previously backed up original nv_data.bin or nv_data.bak files.
I started with:
wrong IMEI
wrong product code
totally botched nv_data files with no backup of original unmolested efs folder or nv_data files
I ended up with
Restored original IMEI
Correct Product Code
Healthy/Correct nv_data files that i immediately backed up in multiple locations.
So if you didn't back up your original untainted efs or nv_data files and this fix doesn't work to restore your original imei and product code then allow me to apologize in advance for "misleading" you and trying to assist with your problem by posting what did in fact work for me.
--------------------------------------------------------------------------------------------------------------
DONATIONS NOT REQUIRED OR EXPECTED. IF YOU FEEL THIS THREAD HAVE HELPED YOU WITH A SICKLY DEVICE OR SAVE YOU ANY HEADACHE OR TROUBLE FEEL FREE TO CONTRIBUTE:

bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efa/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.

I think i deleted the file i wasnt supposed to... can someone post that file?

krips2003 said:
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
Click to expand...
Click to collapse
you should revert to stock to run this.
your welcome to try it with any rom you are using but i have only used it in stock jf6 as that was when i discovered the problem. I tried odin one click jf6 when i noticed both my product code and imei were wrong thinking go full stock reinstall would fix. No luck....with alot of reading i discovered one method of fixing the problem then also worked out the 2nd method that doesn't require adb or pc in case it needed to be done on the fly away from computer.

Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?

CapnPez said:
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
Click to expand...
Click to collapse
yes..thanks...duly noted and corrected

So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.

rwj5279955 said:
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
Click to expand...
Click to collapse
what are you looking @ your efs folder with? It shouldn't be empty...even if you had completely deleted your nv_data files when trying the other method there should have been other folders in /efs. You didn't cut and paste or move all the folders/files from efs (rather than copy) somewhere did you?
PS - aside from the files starting nv_ you should have two folders /efs/imei and /efs/.android

bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.

KALI2000 said:
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
Click to expand...
Click to collapse
suspected would only work with stock. the generic id is less of an issue because i think as long as your product code isn't screwed in the nv_data files your original imei will restore upon reflash of stock.
One interesting thing and may be just luck. I had flashed all kinds of roms before and it usually changed the imei to the generic one but it was no big deal because it would restore when going back to stock (and the product code was never altered).
Since having them get messed up and doing this fix i have flashed multiple roms Axura, Assonance, Perception, Epsyl, and currently chronos and it has yet to alter my original imei in the process. Right now i am running chronos and it still has my original imei.

Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App

krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post):
http://forum.xda-developers.com/showthread.php?t=786532

krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post and it contains links to both versions):
http://forum.xda-developers.com/showthread.php?t=786532

Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.

rwj5279955 said:
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
Click to expand...
Click to collapse
hope it helps. let me know your results when you get a chance.

I did a similar method, but only changed the AATT part in a hex editor and moved the file back with super manager, gave owner full chmod access, rebooted, made sure kies mini detected my device and then reflashed stock/master clear.
Now everything is back to normal.

I don't have an EFS folder and a search in Root explorer finds no nv_data.bin.
Apparently I flashed too many ROMS...lol

So ... As I can get my imei?

This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
EDIT - apparently my statement is incorrect in regards to the captivate. I had been researching fixing my unlock that got relocked and many on the Vibrant forums have the generic IMEI with no way back. As of Jan-3-2011 - bames testing shows that changing the product code, does indeed fix the IMEI - I have to assume that the encrypted IMEI in the nv_data.bin is tied to the product code (maybe a pad or salt) and the phone can't read the IMEI if the product code changes.
Still, the best solution, before any modding, is to back up nv_data.bin.

alphadog00 said:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
from my own experience you are either mistaken or my result was an anomoly.
I had NEVER backed up my efs (had never used root explorer and didn't know the folder was even there prior to researching a fix) folder prior to having my imei, product code, and nv_data files messed up. (Once it was discovered and started researching a fix i used hex editors to view my nv_data files and both the original and BAK copies were messed up).
I ran the fixes and in fact my original IMEI and product codes were restored and in fact have remained in tact for each of the 4 or 5 times i have flashed new 2.2 roms after completing the fix. Right now i am running Chronos and still have my original IMEI (not a generic).
Once i saw the fix worked and i had healthy proper nv_data files the first thing i did was back up the entire efs folder in multiple places.

|Help| how edit Read-Only files?

Hey guys
im using CM10.1 on my nexus 4.
im trying to export some times to my PC but they are read only so i cannot, i also wanted to edit some files in the phone itself
but again, no can do....
is there a way to make these files not Read-only? at least till i make the changes and than make em read-only again?
111
ty

Caniv said:
Hey guys
im using CM10.1 on my nexus 4.
im trying to export some times to my PC but they are read only so i cannot, i also wanted to edit some files in the phone itself
but again, no can do....
is there a way to make these files not Read-only? at least till i make the changes and than make em read-only again?
111
ty
Click to expand...
Click to collapse
Root explorer, change permissions

so it worked, i changed premissions but stil when i open it it either says NULL (in hexedit) or "opened in Read only mode) in the text reader
ive no idea what to do
i cant even explort the file to my pc.. i moved it to DOWNLOAD folder and when i open the folder in the PC the file is like invisivle (and yes invis files and folders are set to show)

which files are you trying to bring over? i would sugget you start with a decent explorer first. solid explorer for instance.

molesarecoming said:
which files are you trying to bring over? i would sugget you start with a decent explorer first. solid explorer for instance.
Click to expand...
Click to collapse
been using Root Explorer and File Manager (both really good imo)
The file i wanted to edit, its mainly for good fun, after beating a game called 9th Dawn i wanted to see how editing save game file works..
i like to play around with save files and thought itd be nice to do it on 9th dawn but i couldnt make it happen.

[XAP] vcREG:Lumia Reg Editor+Jailbreak WP8 version NO LONGER SUPPORTED

WP8 version no longer supported by me, but if others offer fixes, I will post them here. W10M version is discussed in this thread here http://forum.xda-developers.com/win...creg-lumia-reg-editor-interop-unlock-t3451723
WP8/8.1 MixRadio easy method working with instructions from @xboxmod
https://forum.xda-developers.com/showpost.php?p=64350590&postcount=318
WP8/8.1 HERE Maps method working with instructions from @slavanap
WP8.1 instructions (SD card needed)
1.Do device registration to allow sideloading of apps
2. Install HERE Maps (microsoft.com/en-us/store/p/here-maps/9wzdncrfhw6b) from the store, and move it to sd card. Download installation file manually ( wpsnitch.appspot.com ), if you want to install it from SD card.
3.Install Windows Explorer, keep it on phone
https://www.microsoft.com/en-us/stor...r/9wzdncrdrl4w
4.Sideload WPSystem_Folder_Unlocker_Release_ARM.xap(thanks @djamol and @contable),keep it on phone
5.Extract Install.zip from below , and put the extracted "Install" folder on the root of your sd card. The Install folder should have 4 files in it.
6.Open WPSystem Folder Unlocker app. Hit Unlock WPSystem Folder(sd card) button. It should say Success. Now close it
7.Open Windows Explorer.
8.Hit the app bar, go to "access folders",hit the +, choose sd card, then click the check mark
9.Navigate to D:\WPSystem folder. Rename the Apps folder to Apps1. Now open Apps1 folder
10. Navigate to {EFA4B4A7... or {6C28635B-... (I got the second GUID after reinstall)
11. Delete all directories here except Install . Then navigate to Install folder. Delete following 3 files from there: AppManifest.xaml NokiaRegistryUtils.dll NokiaRegistryUtils.winmd
12.Navigate to D:\WPSystem folder and rename Apps1 back to Apps
13. Navigate to the root of your sd card. Get into "Install" folder we put here earlier. Choose all 4 files from there to Copy.
14.Navigate to D:\WPSystem\Apps\{EFA4B4A7-74...}\Install folder. Hit the app bar then paste.
15. Go to your apps list and run HERE Maps. vcREG should open. Apply unlock.
16. After you apply the unlock, you can sideload vcREG_1_2_SIDELOAD.xap to have the app available in your applist for future use.
Q&A
HOW TO USE THE APP TO CAP UNLOCK
now that the app is open, you want to unlock all capabilities. hit the app bar, and tap "templates". here we see two options, interop/caps unlock, and full fs access through MTP. check your options, and click apply. Reboot for MTP.
HOW TO USE THE REGISTRY EDITOR
the main registry editor is pretty straightforward. put the correct path, the key name and value if its a write.
string: it will read as one string. writing is the same,write a string, no spaces, hit write
multistring: multiple strings are read as strings separated by spaces. to write multiple strings, separate each string by a space, hit write.
dword: it will read as 8 characters of ascii. so a value of 1 will read as 00000001. writing is the same. you MUST write 8 characters or it wont write it,so a 1 is 00000001 and B0000 is 000B0000. all bytes are hex, not decimal.
binary: when you read, the app will return 20 bytes, regardless of how long the binary is. if the whole binary sequence is 11 22 33, it will read as 112233 and then 17 00s. the reason for this is that there isnt a method to know how long the binary sequence is,so i hardcoded it to read 20. even if its longer than 20 bytes, you will only get 20 bytes back. i can up the limit at a later time if its something people need.
writing binary is also limited to a max of 20 bytes. if you are writing less than 20 bytes though, dont put the extra zeroes. if you are writing 4 bytes such as 11 22 33 44, then simply write it like this 11223344(no spaces) then hit write.
DO THESE REGISTRY CHANGES PERSIST AFTER A HARD/FACTORY RESET?
no. if you hard reset, you will revert back to the stock rom and any changes you made to the registry will be lost. you will have to make the changes again after a hard reset. file system changes, especially in the windows folder can persist though.
[/HIDE]

Work with me very fine.
THANKS

Is there a way to sideload marketplace apps such as tetra lock screen 1.2.0.0 ? I loved that app.
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
And thanks for bringing us another option. It brings our community closer together

followed your steps. thank you. not sure how to do this though:
"Once completed, you can remove the app and put extras+info back". How to remove it....
never mind. renamed apps folder on SDCard to appx, deleted the app, renamed the folder back to apps, rebooted, changed time to 2115 and was able to uninstall and reinstall.
cheers

derausgewanderte said:
followed your steps. thank you. not sure how to do this though:
"Once completed, you can remove the app and put extras+info back". How to remove it....
never mind. renamed apps folder on SDCard to appx, deleted the app folder, renamed the folder back to apps, rebooted, changed time to 2115 and was able to uninstall and reinstall.
cheers
Click to expand...
Click to collapse
updated the first post with a dead easy method I use

Ok did everything from the package you PM'ed me and ya phn is now interop unlocked.. Changed the MaxUnsignedApp to 170(thats enough for me) I didn't have time to check the homebrew apps I'll try them later. Thnx for this

Pretty Awesome Bro !!!
So what i was looking for... Good job mate.
NTDK Server is a great more than Samsung RPCComponent.
I hope that you can expand it to the more API's.
Like File System API and much more.
Other people's. Please do not spam such thread with your questions. Leave it completely for development related.
Your Q/A goes Here.

@vcfan
So this is similart to what root access on android phone? What is the main advantage if we do this, what do we gain? For me on android the bes thing was customization of the look, and the possibility to block ads in free applications . The ads in windows phone aplications are really annoying when the pop up through whole screen, it would be great if there was a way to block them with host file or something, like in android.

I wonder if we can add an extra quick action. I tried editing the "AllowedQuickSettingsElements" registry but it reverts back to 4 as soon as I pull down the action bar.

MultiPDev said:
I wonder if we can add an extra quick action. I tried editing the "AllowedQuickSettingsElements" registry but it reverts back to 4 as soon as I pull down the action bar.
Click to expand...
Click to collapse
Same happens with my 630 .

Will this work on W10 TP?
As im trying to ,the system wont grant WPCustomSystem access to change the name of the "Apps" folder so that the data can be patched

surya467 said:
Will this work on W10 TP?
As im trying to ,the system wont grant WPCustomSystem access to change the name of the "Apps" folder so that the data can be patched
Click to expand...
Click to collapse
No it doesn't work with wp10 tp . You should get unlocked before going for 10 tp.

irshad2809 said:
No it doesn't work with wp10 tp . You should get unlocked before going for 10 tp.
Click to expand...
Click to collapse
I did it, but i cant deploy some apps, maybe something went wrong, thanks

surya467 said:
I did it, but i cant deploy some apps, maybe something went wrong, thanks
Click to expand...
Click to collapse
As I know I wasn't able to change names or access wpsystem folder with file managers other than official one . How did you do that?

Has anyone tried to replace black background under All apps (the list of all apps) with some custom wallpaper?

Can anyone with a Lumia 830 confirm this is working?

irshad2809 said:
As I know I wasn't able to change names or access wpsystem folder with file managers other than official one . How did you do that?
Click to expand...
Click to collapse
What I did was,
I had Windows Phone 8.1 Update 2 installed with developer unlock
I unlocked the phone with Interop Unlock but did not hard reset
Then i updated WP 8.1 to Win 10 TP and then i hard reset
it seems the unlock worked.
I can deploy ,
App data manager which WORKS
CustomWPsystem which works but cannot patch because Win10 TP doesnt allow permissions to WPSystem folder
I deployed vcREG: Lumia Reg Editor too
but since i hard reset developer unlock should be removed, so im guessing its interop unlock
The only issue is i cannt deploy io explorer, wphtweaks and accept colors app
Is this only bcuz of power tools ? IDK because i have VS 2013 on home PC and it still gives manifest file error.
---------- Post added at 11:13 AM ---------- Previous post was at 11:11 AM ----------
irshad2809 said:
As I know I wasn't able to change names or access wpsystem folder with file managers other than official one . How did you do that?
Click to expand...
Click to collapse
XDRdaniel said:
Can anyone with a Lumia 830 confirm this is working?
Click to expand...
Click to collapse
Yes ofcourse it is
https://onedrive.live.com/redir?res...08447&authkey=!AAkZG-uRpRAzdbM&ithint=folder,
take the data.bin file from here, depends on your RM though

surya467 said:
What I did was,
I had Windows Phone 8.1 Update 2 installed with developer unlock
I unlocked the phone with Interop Unlock but did not hard reset
Then i updated WP 8.1 to Win 10 TP and then i hard reset
it seems the unlock worked.
I can deploy ,
App data manager which WORKS
CustomWPsystem which works but cannot patch because Win10 TP doesnt allow permissions to WPSystem folder
I deployed vcREG: Lumia Reg Editor too
but since i hard reset developer unlock should be removed, so im guessing its interop unlock
The only issue is i cannt deploy io explorer, wphtweaks and accept colors app
Is this only bcuz of power tools ? IDK because i have VS 2013 on home PC and it still gives manifest file error.
---------- Post added at 11:13 AM ---------- Previous post was at 11:11 AM ----------
Yes ofcourse it is
https://onedrive.live.com/redir?res...08447&authkey=!AAkZG-uRpRAzdbM&ithint=folder,
take the data.bin file from here, depends on your RM though
Click to expand...
Click to collapse
Nope, the same. Crash right after i press "Aply XAP" :'(

XDRdaniel said:
Nope, the same. Crash right after i press "Aply XAP" :'(
Click to expand...
Click to collapse
its not an unlock issue, your not able to patch the app, that is an sd card issue
I think u can do it manually or format SD card and try again

thanks for the app but I can't write any reg key? i wonder if it did not send me the confirmation notification or it just can't?

(6/12/15)Again Interop/cap Unlock in lumia and temporary solution for WPINTERNALS.

Edited - Added A new procedure and no more reset anymore.
:good::good::good::good::good::good::good::good:
people who have audio problem after "root unlock" can use this trick temporary.in this trick there is no issue in audio..and i think the audio fix option will come soon.
ok here is The latest trick for interop unloking listed lumia devices.i will write the post shortly.the 60% work will do the wpinternal app.so u have to read the post.
Device supported:
Lumia 520,521,525,620,625,810,820,822,920,925,1020,720 (Other devices is not suported in WPINternals that's why those devices owner have to wait).
**1st a big thanks to "Heathcliff74" for his awesome tool.and 2nd Big thanks to "AndroidXsK" for the SBL3 partitions.
ok here is the procedure.
1st follow this link to unlock ur bootloader.The wpinternals app has all Answers of ur questions.
http://forum.xda-developers.com/windows-phone-8/development/windows-phone-internals-unlock-t3257483
1st download the tool and read the getting started section carefully. (don't do anything just read).
2nd download the SBL3 Partion files from this link. --- http://forum.xda-developers.com/showpost.php?p=64100811&postcount=267
now with the Wpinternals app unlock ur bootloader with the supported SBL3 partitions.
here u have to choose exact partition which match with ur phone..
well if u have a same cpu which matches with sbl3 partion supported phone u can use that for ur phone also..suppose u r using lumia 521/525 but there is no sbl3 partition for those phone then u can use 520 sbl3 partition .bcz 520 has the same processor.i think u understood.
after unlocking bootloader ur phone will reboot to normal mode..keep connected ur phone with pc by USB ..now from the wpinternal app go to manual mode and select "mass storage mode" in the app.the phone will boot again and will go black(unresponsive) ..don't worry.then u will find a new mounted drive partition in ur pc.it's ur phone mainos partition.
go to that drive and u will se some folders .if u don't know pls don't play with those folders.just go to (windows>packages>registry files) folders..u will find many reg files just copy the "Software.reg" file in ur desktop.we will work with that file.
now open 7zip file manager (don't have just download or install)
select the software reg file from desktop.
after clciking on software reg u will see a file named software without any extension.
right click on the file and click "edit".
now a notepad tab will open with many lines..
now add these quoted(add without quotes) lines from the attachment at the end of the software file lines.
View attachment 3566593
now save the file by pressing "Ctrl+S"
now a msg box will appear on 7z file manager just click yes...
after that put/replace the modified software.reg files in the (new mounted drive>windows>packages>registry files) folder.
now soft reset ur phone by clicking "volume down+power button" for 10 second.
then the phone will boot up normally..now u have to must give a hard reset ur phone to get the new capabilities unlocked...
2nd Procedure(No reset anymore) :
Thanks to @_wook_
There's easier way, no need fot 7zip at all
Just switch device to the mass storage mode, go to [MainOS mount point]:\windows\system32\config\ and copy SOFTWARE to some location on PC, then make duplicate just in case you mess up with some registry entry.
Open RegEdit.exe and click on HKLM > File> Load Hive and select file you copied from your MainOS partition drive, then type in the name - anything like lumiaSofware...
Edit what you want (probably capabilities... or something) and unload hive by selecting the lumiaSoftware > File > Unload Hive.
Close RegEdit (no need for it anymore); copy your SOFTWARE file to the place where you got it from (There will be more files, with LOG or similar extension, disregard them). Eject device and hold down power button for 10 seconds (or at least until it vibrates) and voila, you edited your registry with success.
Important notes:
You can mess up your System, but probably you will be able to repair it by re-flashing ffu again - not tested.
Maybe I skipped some step in tutorial and you will be confused what to do next, so, just in case you don't have clue what I am talking about, then this is no good tutorial for you, no good at all!
In case Explorer.exe tells you that you don't have permission to access to [MainOS MP]:\windows\system32\config just press enter (it will be ok I think). Maybe this will cause an issue for some path, or for some devices, not causing any issue to me.
I have crazy phone and a lot of things works on it...
I am using Win10 and Win 10 Mobile.
In case you don't know who is the guy named Explorer.exe forget everything you read in this post and go to some place else.
Best regards and be safe
//edit:
Uploaded attachment for detailed instructions.
attachment Link - forum.xda-developers.com/attachment.php?attachmentid=3563171&d=1449110333
Remember, this works on my device, there might be some issues with it I don't know and I haven't found any so far. Maybe it will brick your phone, mine is working good so far...
Zip file contains screenshots with steps from 0001 to 0031.
And, please, If i had nerve to write entire post, have nerve to read it too...
N.B.-
somethings u must be remembered that the unlock will be parmanent.and i will not responsible for any kind of harm in ur phone.and devices which (like 720) doesn't have sbl3 partitions,u can also unlock ur device by dumping ur phone partition.for this u have to read WPinternals getting started section.
******Sorry for my bad english**************

audio working?

reksden said:
audio working?
Click to expand...
Click to collapse
Yes..thats why i said temporary solution..

Riyad_ said:
Yes..thats why i said temporary solution..
Click to expand...
Click to collapse
okay, but i have lumia 720(((

The version of 7z that you use ?

reksden said:
okay, but i have lumia 720(((
Click to expand...
Click to collapse
No rpoblem..u can try this by dumping ur phone mainos partition.check wpinternals.net

titi66200 said:
The version of 7z that you use ?
Click to expand...
Click to collapse
version 9.34..also works with version 9.20

Thanks

Riyad_ said:
No rpoblem..u can try this by dumping ur phone mainos partition.check wpinternals.net
Click to expand...
Click to collapse
okay, this instruction is older, i get interop unlock with oem setting and system and other reg(huawei w1 with 8.0 05420). but i flashed dump with interop unlock.

Why not writing reg values directly here ?
"C:\Windows\System32\Config"

Thank you so much Riyad_,
this a great notice and I will use now the toturial in my lumia 520

Riyad_ said:
:good::good::good::good::good::good::good::good:
people who have audio problem after "root unlock" can use this trick temporary.in this trick there is no issue in audio..and i think the audio fix option will come soon.
ok here is The latest trick for interop unloking listed lumia devices.i will write the post shortly.the 60% work will do the wpinternal app.so u have to read the post.
Device supported:
Lumia 520,521,525,620,625,810,820,822,920,925,1020,720 (Other devices is not suported in WPINternals that's why those devices owner have to wait).
**1st a big thanks to "Heathcliff74" for his awesome tool.and 2nd Big thanks to "AndroidXsK" for the SBL3 partitions.
ok here is the procedure.
1st follow this link to unlock ur bootloader.The wpinternals app has all Answers of ur questions.
http://forum.xda-developers.com/windows-phone-8/development/windows-phone-internals-unlock-t3257483
1st download the tool and read the getting started section carefully. (don't do anything just read).
2nd download the SBL3 Partion files from this link. --- http://forum.xda-developers.com/showpost.php?p=64100811&postcount=267
now with the Wpinternals app unlock ur bootloader with the supported SBL3 partitions.
here u have to choose exact partition which match with ur phone..
well if u have a same cpu which matches with sbl3 partion supported phone u can use that for ur phone also..suppose u r using lumia 521/525 but there is no sbl3 partition for those phone then u can use 520 sbl3 partition .bcz 520 has the same processor.i think u understood.
after unlocking bootloader ur phone will reboot to normal mode..keep connected ur phone with pc by USB ..now from the wpinternal app go to manual mode and select "mass storage mode" in the app.the phone will boot again and will go black(unresponsive) ..don't worry.then u will find a new mounted drive partition in ur pc.it's ur phone mainos partition.
go to that drive and u will se some folders .if u don't know pls don't play with those folders.just go to (windows>packages>registry files) folders..u will find many reg files just copy the "Software.reg" file in ur desktop.we will work with that file.
now open 7zip file manager (don't have just download or install)
select the software reg file from desktop.
after clciking on software reg u will see a file named software without any extension.
right click on the file and click "edit".
now a notepad tab will open with many lines..
now add these quoted(add without quotes) lines from the attachment at the end of the software file lines.
View attachment 3562770
now save the file by pressing "Ctrl+S"
now a msg box will appear on 7z file manager just click yes...
after that put/replace the modified software.reg files in the (new mounted drive>windows>packages>registry files) folder.
now soft reset ur phone by clicking "volume down+power button" for 10 second.
then the phone will boot up normally..now u have to must give a hard reset ur phone to get the new capabilities unlocked...
N.B.-
somethings u must be remembered that the unlock will be parmanent.and i will not responsible for any kind of harm in ur phone.and devices which (like 720) doesn't have sbl3 partitions,u can also unlock ur device by dumping ur phone partition.for this u have to read WPinternals getting started section.
******Sorry for my bad english**************
Click to expand...
Click to collapse
I get the black screen with sad face reboot loop.

into the ffu ? How ?

There's easier way, no need fot 7zip at all
Just switch device to the mass storage mode, go to [MainOS mount point]:\windows\system32\config\ and copy SOFTWARE to some location on PC, then make duplicate just in case you mess up with some registry entry.
Open RegEdit.exe and click on HKLM > File> Load Hive and select file you copied from your MainOS partition drive, then type in the name - anything like lumiaSofware...
Edit what you want (probably capabilities... or something) and unload hive by selecting the lumiaSoftware > File > Unload Hive.
Close RegEdit (no need for it anymore); copy your SOFTWARE file to the place where you got it from (There will be more files, with LOG or similar extension, disregard them). Eject device and hold down power button for 10 seconds (or at least until it vibrates) and voila, you edited your registry with success.
Important notes:
You can mess up your System, but probably you will be able to repair it by re-flashing ffu again - not tested.
Maybe I skipped some step in tutorial and you will be confused what to do next, so, just in case you don't have clue what I am talking about, then this is no good tutorial for you, no good at all!
In case Explorer.exe tells you that you don't have permission to access to [MainOS MP]:\windows\system32\config just press enter (it will be ok I think). Maybe this will cause an issue for some path, or for some devices, not causing any issue to me.
I have crazy phone and a lot of things works on it...
I am using Win10 and Win 10 Mobile.
In case you don't know who is the guy named Explorer.exe forget everything you read in this post and go to some place else.
Best regards and be safe
//edit:
Uploaded attachment for detailed instructions.
Remember, this works on my device, there might be some issues with it I don't know and I haven't found any so far. Maybe it will brick your phone, mine is working good so far...
Zip file contains screenshots with steps from 0001 to 0031.
And, please, If i had nerve to write entire post, have nerve to read it too...

_wook_ said:
There's easier way, no need fot 7zip at all
Just switch device to the mass storage mode, go to [MainOS mount point]:\windows\system32\config\ and copy SOFTWARE to some location on PC, then make duplicate just in case you mess up with some registry entry.
Open RegEdit.exe and click on HKLM > File> Load Hive and select file you copied from your MainOS partition drive, then type in the name - anything like lumiaSofware...
Edit what you want (probably capabilities... or something) and unload hive by selecting the lumiaSoftware > File > Unload Hive.
Close RegEdit (no need for it anymore); copy your SOFTWARE file to the place where you got it from (There will be more files, with LOG or similar extension, disregard them). Eject device and hold down power button for 10 seconds (or at least until it vibrates) and voila, you edited your registry with success.
Important notes:
You can mess up your System, but probably you will be able to repair it by re-flashing ffu again - not tested.
Maybe I skipped some step in tutorial and you will be confused what to do next, so, just in case you don't have clue what I am talking about, then this is no good tutorial for you, no good at all!
In case Explorer.exe tells you that you don't have permission to access to [MainOS MP]:\windows\system32\config just press enter (it will be ok I think). Maybe this will cause an issue for some path, or for some devices, not causing any issue to me.
I have crazy phone and a lot of things works on it...
I am using Win10 and Win 10 Mobile.
In case you don't know who is the guy named Explorer.exe forget everything you read in this post and go to some place else.
Best regards and be safe
Click to expand...
Click to collapse
Have you tested this?.

Rivo17 said:
Have you tested this?.
Click to expand...
Click to collapse
Of course, but, i recommend you to try first post. As I wrote, I have a crazy phone...

In that case, you must better edit your post for avoid confusion. Just saying.

_wook_ said:
There's easier way, no need fot 7zip at all
Just switch device to the mass storage mode, go to [MainOS mount point]:\windows\system32\config\ and copy SOFTWARE to some location on PC, then make duplicate just in case you mess up with some registry entry.
Open RegEdit.exe and click on HKLM > File> Load Hive and select file you copied from your MainOS partition drive, then type in the name - anything like lumiaSofware...
Edit what you want (probably capabilities... or something) and unload hive by selecting the lumiaSoftware > File > Unload Hive.
Close RegEdit (no need for it anymore); copy your SOFTWARE file to the place where you got it from (There will be more files, with LOG or similar extension, disregard them). Eject device and hold down power button for 10 seconds (or at least until it vibrates) and voila, you edited your registry with success.
Important notes:
You can mess up your System, but probably you will be able to repair it by re-flashing ffu again - not tested.
Maybe I skipped some step in tutorial and you will be confused what to do next, so, just in case you don't have clue what I am talking about, then this is no good tutorial for you, no good at all!
In case Explorer.exe tells you that you don't have permission to access to [MainOS MP]:\windows\system32\config just press enter (it will be ok I think). Maybe this will cause an issue for some path, or for some devices, not causing any issue to me.
I have crazy phone and a lot of things works on it...
I am using Win10 and Win 10 Mobile.
In case you don't know who is the guy named Explorer.exe forget everything you read in this post and go to some place else.
Best regards and be safe
//edit:
Uploaded attachment for detailed instructions.
Remember, this works on my device, there might be some issues with it I don't know and I haven't found any so far. Maybe it will brick your phone, mine is working good so far...
Zip file contains screenshots with steps from 0001 to 0031.
And, please, If i had nerve to write entire post, have nerve to read it too...
Click to expand...
Click to collapse
Loading hive and searching for capabilities i think it's more complicated...just adding some line is much more easier .but ur tut is good too.

djamol said:
Why not writing reg values directly here ?
"C:\Windows\System32\Config"
Click to expand...
Click to collapse
i was confused about it that's why i used software.reg. ..

Rivo17 said:
I get the black screen with sad face reboot loop.
Click to expand...
Click to collapse
i also got this 1st time. try again resetting or flash the ffu again.