Yes if the 'Qualcomm USB Settings' button disappears then use the terminal command to access it instead.
Sent from my GT-I9305 using Tapatalk 2
[WARNING! + GUIDE] Backup and Restore IMEI / NV Data Procedure for GT-I9305
- Thread starter lyriquidperfection
- Start date
Yes if the 'Qualcomm USB Settings' button disappears then use the terminal command to access it instead.
Sent from my GT-I9305 using Tapatalk 2
In the modem.bin file i have came across these lines at line :149480>149481>149482
S000=%03d S002=%03d S003=%03d S004=%03d S005=%03d
S006=%03d S007=%03d S008=%03d S010=%03d S030=%03d
S103=%03d S104=%03d
now if we take a look at this we can see it looks to relate to imei descriptions somehow.
Highlighted in bold are 5 x 3 char encoding which equates to 15 being a IMEI number is 15 we can see a relation.
Now having access to the ability to open modem.bin without corruption/encryption would enable us to have a better understanding on how to restore out IMEI numbers. (high expectations here)
now im not sure of the significance of this or how to manipulate it. but i will enter some codes into it and see how we go.
I have also come across a plugin named buildagent when gogling of this it gives me a Plugin for microsoft software. maybe someone can make use of this to decompile?
S000=%03d S002=%03d S003=%03d S004=%03d S005=%03d
S006=%03d S007=%03d S008=%03d S010=%03d S030=%03d
S103=%03d S104=%03d
now if we take a look at this we can see it looks to relate to imei descriptions somehow.
Highlighted in bold are 5 x 3 char encoding which equates to 15 being a IMEI number is 15 we can see a relation.
Now having access to the ability to open modem.bin without corruption/encryption would enable us to have a better understanding on how to restore out IMEI numbers. (high expectations here)
now im not sure of the significance of this or how to manipulate it. but i will enter some codes into it and see how we go.
I have also come across a plugin named buildagent when gogling of this it gives me a Plugin for microsoft software. maybe someone can make use of this to decompile?
Last edited:
Ok so why are people still having this problem if they can access the qualcom usb settings? Is it because they did not have a backup of the qn before it was lost? So please be clear about this.. people that have previuosly made backups of efs and nv data should be safe even if they loose the qualcom usb button because they can access it through terminal and restore it that way. Please confirm 
Sent from my GT-I9305 using xda app-developers app
Sent from my GT-I9305 using xda app-developers app
Last edited:
Ok so why are people still having this problem if they can access the qualcom usb settings? Is it because they did not have a backup of the qn before it was lost? So please be clear about this.. people that have previuosly made backups of efs and nv data should be safe even if they loose the qualcom usb button because they can access it through terminal and restore it that way. Please confirm
Sent from my GT-I9305 using xda app-developers app
Yes thats correct there are also 3 other partitions relating to efs that im currently looking into aswell.
Sent from my GT-I9305 using Tapatalk 2
we'll im on Official Telstra 4.1.1 RUU with stock kernel and recovery and i dont have any *#id# commands that work.
i type one in and it just sits there and nothing happens.
I have a little grey box that pops up and tels me im in Factory Mode-ON
i cant access the phone with ADB devices or EFS explorer
i got no power button menu its just restarts when hit.
so for me i cant do Squat unless it can be done from the android terminal emulator.
Im also wondering if we can direct inject imei via qemud with something like
i type one in and it just sits there and nothing happens.
I have a little grey box that pops up and tels me im in Factory Mode-ON
i cant access the phone with ADB devices or EFS explorer
i got no power button menu its just restarts when hit.
so for me i cant do Squat unless it can be done from the android terminal emulator.
Im also wondering if we can direct inject imei via qemud with something like
Code:
qemud=`getprop ro.kernel.android.qemud`
case "$qemud" in
"")
radio_ril=`getprop ro.kernel.android.ril`
case "$radio_ril" in
"")
[COLOR="SeaGreen"] #not sure of ro.ril.imei or just ril.imei
#or do we need yes? or 0 / 1 on off etc?[/COLOR]
setprop ro.ril.imei=123456789012345 yes
stop ril-daemon
;;
esac
;;
esacOk so why are people still having this problem if they can access the qualcom usb settings? Is it because they did not have a backup of the qn before it was lost? So please be clear about this.. people that have previuosly made backups of efs and nv data should be safe even if they loose the qualcom usb button because they can access it through terminal and restore it that way. Please confirm
Sent from my GT-I9305 using xda app-developers app
Last edited:
regarding the backup. I did a efs backup by the aroma installer from SSH v1.0 many days ago but as I found out it was pointless anyway. and I candidate seem to workout how to copy the efs.img back to the phone I did dd for=/efs.img of=/dev/block/mmcblk10/ but I was not able to get that command to work from the terminal as I got no adb from pc as phone is somehow stuck in factory on mode
as for the nv backup don't have one. don't have the nv files on both my s3's.
although I do have a 700$ development phone now and one working. lucky I got two.
well now to workout how to get my pit file from this phone and inject It over to my other one. as my phone won't boot past the logo cause I accidentally had partition ticked on the bloody Odin. I got to pay more attention but damn me Grimm was on. fml
so yes still nothing. all my java files can get a good run but don't suceed in getting my imei back any of the random ways I tried. or even read the unknown name for that matter and to think I could Of been fishing today instead of coding to no avail.
sent from my working mobile. not the dead one
as for the nv backup don't have one. don't have the nv files on both my s3's.
although I do have a 700$ development phone now and one working. lucky I got two.
well now to workout how to get my pit file from this phone and inject It over to my other one. as my phone won't boot past the logo cause I accidentally had partition ticked on the bloody Odin. I got to pay more attention but damn me Grimm was on. fml
so yes still nothing. all my java files can get a good run but don't suceed in getting my imei back any of the random ways I tried. or even read the unknown name for that matter and to think I could Of been fishing today instead of coding to no avail.
sent from my working mobile. not the dead one
Last edited:
hi,bro...i got my pcn file ,it is only 250kb,is it ok??? based on 9305,hk version,thank u for your method:good:
Yes scroll up I asked the exact same thing. He said it was all good
I did mention to the op he might like to add that in the OP so people are aware its only 250kb and dont have to worry, hmmm maybe i didnt .. thought i did.Thanks for the update!
Possibly a dumb question but does a nandroid backup hold this info? I assume not but wanted to ask just in case.
No a nandroid backup contains no efs data whatsoever.
Sent from my GT-I9305 using Tapatalk 2
hey bud, any luck finding out the command to get to the nvdata menu from terminal emu?
i tried a few things by guessing but but keep getting activity does not exist. shows my bad android skills. lol.
Not yet mate ill take a look on weds when im off work.
Sent from my GT-I9305 using Tapatalk 2
followed exact command line for those 3 backups. And it says Cannot open for read: permission denied.
I am rooted definatley you sure thats the command line?
Sorry you need to su first. Ill update the guide.
Sent from my GT-I9305 using Tapatalk 2
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
200
Click HERE for information on the long awaited and all new EFS Professional v2.0 including download! Now supporting Qualcomm devices!
Setting up QPST with your PC:
- Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom. Now select 'RNDIS + DM + MODEM' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now in DIAG Mode.
- Download and Install: SAMSUNG_USB_Driver_for_Mobile_Phones_1590.exe - 23.06 MB if you don't already have Kies or a USB Driver installed.
- Download and Install: QPST v2.7.378.zip - 14.68 MB
- Now connect your phone to the PC with a USB cable and wait for Drivers to install.
- Start the 'QPST Configuration' application and select the 'Ports' tab then press the 'Add New Port...' button.
- Select the COM Port that has 'USB/QC Diagnostic' next to it, change the Port Label if you like to 'Samsung GT-I9305' then press 'OK'.
- You should now see your phone listed in the 'Ports' tab and the 'State' should indicate 'Enabled'.
- You can now Close this application.
Backing Up IMEI / NV Data:
- Start the 'Software Download' application and select the 'Backup' tab.
- Press the 'Browse' button and choose a Save Location for your QCN File.
- Press the 'Start' button and wait for it to finish. This will back up all your phones NV Items and save them to the QCN Backup File.
- The resulting QCN Backup File should be 250KB.
Restoring IMEI / NV Data:
- Start the 'Software Download' application and select the 'Restore' tab.
- Press the 'Browse' button and select your QCN Backup File.
- Press the 'Start' button and wait for it to finish. This will restore all your phones NV Items from the QCN Backup File.
- Your IMEI / NV Data should now be fully restored. Dial *#06# on your phones keypad to check your IMEI is restored.
Restore USB Settings after Backup / Restore:
- Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom. Now select 'MTP + ADB' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now back to default USB operation.
Recovering IMEI And Data Connection After Flashing WRONG Root Package Intended For I9300:
- Make sure you have Samsung Kies or the Samsung USB Driver installed on your PC.
- Download and Extract: Odin3 3.04.zip - 457.11 KB to your PC if you don't already have it.
- Download and Extract: Param_Bin_I9305.zip - 612.14 KB to your PC.
- With your Phone Switched Off, press and hold: 'VOL DN' + 'HOME' + 'POWER' to enter Download Mode.
- Connect your phone to your PC via USB Cable and start Odin.
- Check your phone is connected by seeing if a COM Port in a Blue box is present under ID:COM.
- Press the 'PDA' Button and select the 'Param_Bin_I9305.tar.md5' file you extracted from the Zip Archive earlier.
- Press the 'Start' Button and wait for it to finish flashing. If successful, you will see a Green Box with 'PASS!'.
- Wait for your phone to reboot then go to your Dialer and press: *#06#. You should now see your IMEI and your Data Connection will be back.
If I have saved your bacon then please buy me a coffee!4Okay I can now confirm I have a working fix for those who have lost their IMEI and Data Connection by flashing the Wrong CF-Root intended for the I9300.
Check out the first post in this thread at the bottom for the solution.
Confirmed working by: nixxss - Thanks for testing!3
Hello, fellow QPST users.
QPST 2.7 Build 4.2.2 is a fake version with keylogger.
Some a$$hole downloaded latest public QPST build (4.0.2) and decompiled MSI installer package, then edited all "4.0.2" to "4.2.2", added "fake changelog", added keylogger (qualcomm.exe), then repackaged and spread around web!
Everyone who downloaded QPST build "4.2.2" should change all his passwords.
More info about malware from fake 4.2.2 build (QPST.2.7.422.msi)
MSI package (QPST.2.7.422.msi) was embedded/tampered with qualcomm.exe which is a .NET based malware that logs your keystrokes and sends it to attacker's server.
How to delete the actual malware from your system?
Look at the startup from msconfig or CCleaner, there should be a file called qualcomm.exe thats set to start everytime system starts. Delete both registry and file.
If you wanted to see what data thief was stolen from you. Just open the .dc file (in "dclogs" folder) with Notepad and see for yourself.
In XP, dc file is located here!
C:\Documents and Settings\Administrator\Application Data\dclogs
there should be a file called "201X-XX-XX-X.dc
if you open that DC files with Notepad, you'll see all your keystrokes.
Here is mine. I've intentionally entered paypal site with fake info.
Keylogger sends the logs from keylogger to "qpst.hopto.me"
So please report about this incident where and when you encounter QPST 4.2.2 somewhere (forums, posts, sharing-sites, etc)
Copy my whole post and paste it where you see 4.2.2 mentioned.
Bonus: Fake Changelog
If you've installed this 422 build, then open the Readme.txt in C:\Program Files\Qualcomm\QPST\Documents
Scroll down and see the "6/12/13 QPST 2.7.422 changelog"
Changelog above is actually cloned from QPST 2.7.394 Just scroll down and see Build 2.7.394 changelog. Its same!
So forget about Build 422. It doesn't exist.
Use QPST 2.7 Build 402. It's the latest public build
Sorry about my english
Best Regards
AnycallMongolia3Dev-Host seems to have an issue in downloading (error 500).
however, i searched for the param file and found it, i attached the Param file and Odin 3.04 in the post here 2phew, was about to dive into flashing and then saw this thread. THANK YOU!
I am an iOS refugee. Totally new to android. I guess I'll wait for more developments to come out for my Quad core LTE S3.
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
ah tauran you saw this thread first, good good. Was about to actually pm to let you know that this thread is for you!
Hope you get your device working.
Sent from my GT-I9305 using xda app-developers app - Dial *#7284# on your phone to access PhoneUtil and select 'Qualcomm USB Settings' at the bottom. Now select 'RNDIS + DM + MODEM' and press 'OK' to return to the previous screen. Now press your 'Back' key to exit PhoneUtil. Your phone is now in DIAG Mode.
New posts
-
-
[Question][ADB] How to "adb push" with timestamps like "adb pull -a"
- Latest: anmac1789@gmail.com
