Database Users

[HELP] No signal no matter what I try

Hi. So here's the thing:
I was trying to unlock my Samsung Galaxy S4 GT-I9505 and I kinda messed up. I chose the DM/DUN/RmNet over HSUSB option from the *#9090# where it said that all NV data will be erased, and I chose YES. Then after reboot, I didn't get any signal from my carrier. I've tried other SIMs, but nothing changed.
Then I found out that I needed an EFS backup or something like that, which unfortunately I didn't make.
I tried flashing the original stock rom (MDE), but nothing happened. I updated the rom to MDM, but then the baseband version became unknown and the IMEI number became NULL. So I flashed the MDE rom again and I got the IMEI and baseband version back. Then I tried to root my phone. Root was successful, so I tried to use EFS Professional. I backed up everything, and restored but nothing changed,
I know the phone reads the SIM card because I can see the SIM Toolkit change to the carrier's. The problem is I don't get any signal.
Can anyone please help me?

Did you ever get any info or help with this?
poopsmcgee said:
Hi. So here's the thing:
I was trying to unlock my Samsung Galaxy S4 GT-I9505 and I kinda messed up. I chose the DM/DUN/RmNet over HSUSB option from the *#9090# where it said that all NV data will be erased, and I chose YES. Then after reboot, I didn't get any signal from my carrier. I've tried other SIMs, but nothing changed.
Then I found out that I needed an EFS backup or something like that, which unfortunately I didn't make.
I tried flashing the original stock rom (MDE), but nothing happened. I updated the rom to MDM, but then the baseband version became unknown and the IMEI number became NULL. So I flashed the MDE rom again and I got the IMEI and baseband version back. Then I tried to root my phone. Root was successful, so I tried to use EFS Professional. I backed up everything, and restored but nothing changed,
I know the phone reads the SIM card because I can see the SIM Toolkit change to the carrier's. The problem is I don't get any signal.
Can anyone please help me?
Click to expand...
Click to collapse
I did the same thing. I did make a NV Backup. Copied them back but that didn't change the no signal problem. I have tried odin back stock root and unrooted. Some how you have to get out of the DM/DUN/RmNet over HSUSB setting and back in DM/DUN over HSIC but I can't find a way. Can you get into the *#9090# without it being blanked out settings?

Did either of you ever manage to solve this? I have the same problem.

I bought a new phone for my girlfriend a s4 and copied the nv items from her new phone to my phone. I had service, changed esn spc and reflashed my phone. Everything is working great now
Sent from my SPH-L720 using XDA Premium 4 mobile app

Great news! Any chance of getting a copy of the NV items so I can try this aswell?

madmediapro said:
I bought a new phone for my girlfriend a s4 and copied the nv items from her new phone to my phone. I had service, changed esn spc and reflashed my phone. Everything is working great now
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi , can u plz tell me where is nv_data on s4 i9505 bcoz i can't see nv_data on i9505 efs folder.

If snow is coming in like its suppose to in va tomorrow. If not I will do it this weekend. I will tell everyone in detail what I did and what programs I used to restore my phone to get service back on my phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app

That would be amazing. I look forward to your post.

i'm looking forward to your post.
madmediapro said:
If snow is coming in like its suppose to in va tomorrow. If not I will do it this weekend. I will tell everyone in detail what I did and what programs I used to restore my phone to get service back on my phone.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

I have to start out by saying that my phone is Sprint Samsung S4(SPH-L720). I’m not sure if this is going to help you. I came here for help. Hoping that I can help out because this site has helped me so much the last four year I have been here. And of course I’m not responsible in anyway for what you do to your device. Just posting what I did to fix my phone. Programs used Win7 64-bit (WIN XP should work), Odin3 v3.07, EFS_Professional_2.0.72, QPST 2.7 Build 422, HxD, DFS CDMA Tool Demo.
My old phone and new phone I bought did not have knox bootloader on them.
First thing I did to both was flash (Oldest Firmware) SPH-L720_MDC_Rooted_Restore.tar.md5 with Odin3 v3.07. Updated both SuperSU and BusyBox from PlayStore on both phones.
Then I used EFS_Professional_2.0.72 to Backup all NV Items from new phone that had cell service. Turned phone off and pulled battery. Then Formatted all NV Items on old phone and restored backup from new phone. Restarted and had cell bars in status bar. So I knew I was good to good with flashing my service back on the device.
Using QPST 2.7 Build 422, HxD, and DFS CDMA Tool Demo verison will work just fine to do what you need to do. Go to Device Manager and find what com port your device is on. Open QPST Configuration click “Add New Port…” the com port will not be visible but if you type “COMXX” in both port and port label it will be added to qpst configuration. Example is my port COM23 so I added COM23. Close window and open DFS connect com and send spc and pwd close DFS. Note: “You have to send SPC then Pwd with DFS before using any programs on QPST.” Open EFS Explorer send spc go to directory nvm\num copy items 0 85 1943 to desktop. Use HxD to zero out items. Then delete items from nvm\num directory on EFS Explorer. Then copy the zeroed out items back to phone. Reset phone and open DFS and restore original setting that came with the phone. You should be able to restore MEID, ESN, SPC, and IMEI with DFS.
I hope XDA Developers will understand that this is just restoring your phone back to original state. That is exactly what I did. Hope this helps you.

madmediapro said:
I have to start out by saying that my phone is Sprint Samsung S4(SPH-L720). I’m not sure if this is going to help you. I came here for help. Hoping that I can help out because this site has helped me so much the last four year I have been here. And of course I’m not responsible in anyway for what you do to your device. Just posting what I did to fix my phone. Programs used Win7 64-bit (WIN XP should work), Odin3 v3.07, EFS_Professional_2.0.72, QPST 2.7 Build 422, HxD, DFS CDMA Tool Demo.
My old phone and new phone I bought did not have knox bootloader on them.
First thing I did to both was flash (Oldest Firmware) SPH-L720_MDC_Rooted_Restore.tar.md5 with Odin3 v3.07. Updated both SuperSU and BusyBox from PlayStore on both phones.
Then I used EFS_Professional_2.0.72 to Backup all NV Items from new phone that had cell service. Turned phone off and pulled battery. Then Formatted all NV Items on old phone and restored backup from new phone. Restarted and had cell bars in status bar. So I knew I was good to good with flashing my service back on the device.
Using QPST 2.7 Build 422, HxD, and DFS CDMA Tool Demo verison will work just fine to do what you need to do. Go to Device Manager and find what com port your device is on. Open QPST Configuration click “Add New Port…” the com port will not be visible but if you type “COMXX” in both port and port label it will be added to qpst configuration. Example is my port COM23 so I added COM23. Close window and open DFS connect com and send spc and pwd close DFS. Note: “You have to send SPC then Pwd with DFS before using any programs on QPST.” Open EFS Explorer send spc go to directory nvm\num copy items 0 85 1943 to desktop. Use HxD to zero out items. Then delete items from nvm\num directory on EFS Explorer. Then copy the zeroed out items back to phone. Reset phone and open DFS and restore original setting that came with the phone. You should be able to restore MEID, ESN, SPC, and IMEI with DFS.
I hope XDA Developers will understand that this is just restoring your phone back to original state. That is exactly what I did. Hope this helps you.
Click to expand...
Click to collapse
Thanks for sharing and i don't think it will work on my device i9505 but i do appreciate the work u have shared thumbs up.

I still think this may work. I want to attempt but I need a known good EFS pro backup from an i9505. Unfortunately it's not that easy to convince any of my friends to let them tinker with their phones. If somebody could send me one to try I would be hugely grateful.

d3v147 said:
I still think this may work. I want to attempt but I need a known good EFS pro backup from an i9505. Unfortunately it's not that easy to convince any of my friends to let them tinker with their phones. If somebody could send me one to try I would be hugely grateful.
Click to expand...
Click to collapse
Using an EFS backup on two phones simultaneously will result in blacklisting of both mobile devices.
So do not try to restore an EFS backup from an usable phone..

AlanDS said:
Using an EFS backup on two phones simultaneously will result in blacklisting of both mobile devices.
So do not try to restore an EFS backup from an usable phone..
Click to expand...
Click to collapse
I did seem MadMediaPro did not encounter this. Also it is unlikely to occur if a SIM is never inserted in the phone. The other possibility is hex editing out the IMEI in the backup.

[Q] Wifi Problems [Solved]

Phone: Samsung S4 mini SGH-I257m (Canada Rogers)
Android 4.2.2 I257MVLUAMK5
I used an app called "Wifi Pass Recovery & Backup" and it killed my wifi. It tries to turn on and fails. I could redo my phone completely but I would rather fix it.
I have tried many things:
I made a backup with the app before doing anything and restoring that did nothing. Using the in app "reset wifi settings" button also did nothing but remove my saved networks.
Using ES File Explorer I have looked at the /system/bin/wps_supplicant, /data/misc/wifi/wps_supplicant.conf, /system/etc/wifi/wps_supplicant.conf. Played around with permissions, owner and checked MD5 with backed up versions. One thing I noticed was that the permissions seemed to reset when I would reboot.....
I used logcat and couldn't gain any ground there.
Some post I saw said something about replacing /system/bin/wps_supplicant with the one from the stock firmware, but i couldn't figure out how to find the files in the firmware I downloaded. I did find a factory image from google and was able to extract the files I was looking for, but they didn't work either. No surprise there.
I would love some help this as you guys are the experts!
Thanks!

Are there any other files that have to do with wifi? They might be worth checking out.

Solved
Ok....So, I was able to fix the problem by going back to the stock ROM. Not what I was wanting but whatever.
In an effort to try to figure out what happened, I cross-checked the stock files with the the ones I had before.
- the MD5 checksum of /system/bin/wpa_supplicant was identical
- /system/etc/wifi/wps_supplicant.conf was identical
- /data/misc/wifi/wps_supplicant.conf had a difference with config_methods. Stock was 'physical_display', old was 'physical_display virtual_push_button keypad'
So as far as I can tell.....that one entry was the problem.

Unbricking and QPST - All Snapdragon / Qualcomm devices

Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.

What made your device hard brick
Sent from my SM-N910G using Tapatalk

Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.

can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot

AlexanderDAB said:
can you explain to me everything that is happening?
i got my note 4 hardbricked from......
i really dont know
i was modifying my phone but then it would not boot
Click to expand...
Click to collapse
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G

Update:
So far I have contacted Qualcomm, Intrinsyc (they sell Snapdragon development boards), and a Samsung retail outlet.
All have come back as a negative - the closest I could get was the Samsung retail outlet where a dude used to work in the repair centre and had access to the files then.
Unfortunately, Samsung revoked his permissions now that he only works in a retail outlet.
He knew what I was talking about, but due to Samsung and their encryption etc, he couldn't provide me with the files.

C_dog_1 said:
Mistake 1: I bought the phone with the known problem of a USB port not working.
Mistake 2: I bought a replacement USB board and replaced it myself, after which the fun and games began. The one time the screen did light up I got an error message about mmc read fail and could not boot.
Mistake 3: Like a fool, I pulled the battery. Now I have a hard bricked / useless Note 4.
Unless the mmc is physically damaged (which I refuse to believe) the phone should be salvageable from its hard brick state. Provided I can find the right files to go with QPST.
Edit:
I have tried contacting Qualcomm to get the files, who have pointed out that they are proprietary to the licensee, ie Samsung. Here's the e-mail below.
Any information other than what is listed on our website (URL listed below for your reference) is Proprietary to Licensees.
However, the following link should help you with the information you're looking for:
http://www.mydragonboard.org
Alternatively, we recommend you follow-up with a vendor that carries this product and seek their feedback on your technical questions.
Please note, Qualcomm is the technology provider, not a manufacturer of consumer products and therefore we are unable to answer your product specific question. We hope this direction helps.
Thank you for your inquiry,
Qualcomm Technologies Inc.
Click to expand...
Click to collapse
I have the same problem and also looking for a solution. I will contribute to this post as I find something.
There is a similar post here:
http://forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
---------- Post added at 07:10 PM ---------- Previous post was at 06:30 PM ----------
Try this manual.
http://dl-1.va.us.xda-developers.co....rar?key=yrJPiZgu63c6RxNIbU_xVA&ts=1474829412
I've found it earlier today but haven't had a chance to try it yet.

Says the file is gone
Sent from my SM-N930W8 using XDA Labs

It's just the pdf and .pit that i used here: http://forum.xda-developers.com/note-4/help/hard-brick-phone-off-long-help-fellow-t3468792

yashthemw said:
Is it going in download mode or recovery ?
What were you exactly flashing ?
Is it detected in pc as qhsb loader ?
Is the splash screen GALAXY NOTE 4 showing up ?
Sent from my SM-N910G
Click to expand...
Click to collapse
it won't boot at all
i was messing around with the system on the factory binary firmware
yes, it is
nope, it will not boot

i have same problem does any one sucess with this process ?

Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.

yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Reporting Via N910G.
Click to expand...
Click to collapse
can you get me a dude with an AT&T note 4?

same boat with my N910F
C_dog_1 said:
Hello All,
First let me say thanks to all XDA Developers, and without this forum I would still be a pleb when it comes to unbricking. :highfive:
The link to QPST: androidbrick.com/download/latest-qpst-2-7-build-422-425-430-437-qfil-qualcomm-flasher/
(Sorry, I haven't passed 10 posts yet, so you have to manually enter into the address bar)
I came to this forum seeking answers to unbrick my hardbricked Note 4, and after many hours of heartbreak and headache, I have come across a tool called QPST.
This tool is used by Qualcomm, and if you read carefully through the accompanying documentation, you will find some interesting stamps - such as "Confidential" etc.
While I am no expert in the use of QPST, from my own incomplete research I am convinced this tool can be used on any device which sports a Qualcomm chipset (Snapdragon etc.) to unbrick it from certain death.
I have not yet succeeded with my attempts at unbricking, but it is now only a matter of time and kind people pointing me in the right directions. :fingers-crossed:
I am looking for the right files to go in the "phone image" and "boot image" lines in the QPST Software Download program.
I hope we can all see the opportunity this tool represents and spread the word among the greater community, not just developers.
Edit:
Using Software Download:
Phone image files will have a .hex extension and I do not believe they can be found on sammobile. I still haven't found the right one.
Boot image files: I still don't know what they will look like. Likely a .hex file.
Using QFIL:
I suspect all these files can be acquired from a service ROM (whatever a service ROM is - I don't think it is a ROM for android as I know them). I am not completely sure of this however.
Using the flat build option will let you select the programmer. It will have a file name like:
prog_emmc_firehoseXXXX.mbn
(Replace XXXX with the correct numbers for your snapdragon. I don't know what the right ones for the Snapdragon 805 are, but I strongly suspect 8084, with a remote possibility of 8064. Edit: I don't know, don't take my word.
There are posts for other phones on XDA, I don't know if they use the 805 chipset or if the files are compatible.) <--- If anyone wants to research, feel free. Team efforts make a big job seem easy! Please post your results!
Accompanying your firehose file will be a bunch of other files in the same folder.
You will need two .xml files to go with the above (usually in the same folder), which will look like as follows:
rawprogram0XXXX.xml (here XXXX denotes some numbering system which will be determined by the internal memory of the device eg 16GB, 32GB, 64GB. I saw an example for a OnePlus One which had rawprogram0_64G.xml.
I'm NOT 100% SURE on this numbering system, as elsewhere on XDA I have come across different file names!
Here's the truncated link: androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/)
patch0.xml
When I find the above, I will post or hassle an admin to post, as these will likely unbrick any Snapdragon 805. Happy hunting!
Here's a truncated link to XproZayd's thread, where a different avenue is explored (and where I got my idea about the 8084 number for firehose -- Remember, I could be wrong!)
forum.xda-developers.com/note-4/help/unbrick-samsung-galaxy-note-4-sm-n910w8-t3249970
This thread is for discussing QPST and how to use it - if you have a hard bricked phone I am not able to help at this stage. However, should anybody find / 'acquire' the right files to use with QPST, we will all benefit.
Click to expand...
Click to collapse
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers

Lofhario said:
Im in the same boat with my NOTE 4 N910F. Totally blacked out but still picking it up on the PC with QFIL files have found some files but there not the right phone I think.
so fails to load with SAHARA.
cannot find firehose for 910F. Wish someone could solve this one and then publish it all. someone will eventually but QFIL will unbrick all Qualcomm provided you can make the files.
Let me know if you or anyone does. cheers
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3488114
Tried this?
Reporting Via N910G.

Hi, got a Phicomm Energy M+ (E551). It turned off as the battery was empty, so I charged it overnight.
But:
-Switching it on only shows the phicomm logo
-Trying to enter recovery, shows phicomm logo for a second and then the screen stays lit. Nothing else happens.
-On Windows 7 device manager shows it as "RELINK HS-USB QDLoader 9008 (Com3)" (VOL Up+VOL Down + Power)
-fastboot/adb wont find it
-I tried this http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
I dont have a emmc backup but an unzipped Stock ROM of the E551L which support told me to use. (put on SD card and reboot into recovery, but I cant get into recovery)
Hence I use the unzipped ROM with the Qualcomm FLasher :S (http://na.phicomm.info/release/E551L...TA package.zip)
-It starts the process but then says "Failed to enter EDL" (Emergency) mode
Another thing I stumbled across is :
E551L has Qualcomm MSM8916 and Android 4.4.2
E551M has Qualcomm MSM8915 and Android 4.4.4
Will I have to quire a deepflash cable or am I missing something here ?

yashthemw said:
Hey guys, i successfully created a Debrick.img for note 4 , used my own functional note 4 to create one .
http://forum.xda-developers.com/showthread.php?t=3488114
Don't forget to Press thanks .
Click to expand...
Click to collapse
tried but not working
waiting for other solution

[Q] Touchscreen doesn't respond after using bogus photo recovery software

Hello, ladies and lads!
Here's a short version of where I'm at: after installing Wondershare' s dr.phone Recovery on my mom's PC and using it on her phone:
its screen won't respond to touch (can't enter SIM card's PIN nor open screen lock)
the On/Off button won't turn off the phone on long press (maybe due to screen lock)
on restart there's a yellow text that reads "Set Warranty Bit : kernel"
the physical buttons still work
I can see the phone's files and folders only through PC's command prompt, using ADB ('This PC\Galaxy Grand Prime' folder in Win Explorer says it's empty).
Ideally I want to keep her data (FB Messenger, Skype, Chrome, WiFi passwords, etc), and her phone to function again. What do you think I should do?
I think I need an advice and suggestions from someone more experienced than me - I don't even know trusted sites where to download the firmware roms from.
The phone's details are (I'm afraid you'll have to walk me through to get more details to this list, as I'm new to the forum):
Phone: Samsung Grand Prime
Model name: SM-G530FZ
Firmware version: G530FZXXS1BQC2 (Android 5.0.2 with Baltic bloatware, I guess)
Now in detail:
My knowledge and experience regarding the smartphone software & restoration is very basic (I've only restored the firmware to a LG-L70 once some years ago, and that's it).
Before the problem I lost some over 600 media files from that phone by Cutting and Pasting a folder from phone's internal SD to PC's disc. Now I learned never to Cut-Paste important or irreplaceable files. The files ended up on the phone, because a folder with over 800 files couldn't be uploaded to the Google Drive (the camera's folder had over 1k files in it, so I moved some of them to another folder, which the phone created on the internal partition rather than the SD Card, where the original folder was from).
Instead of using a trusted software, I foolishly Googled a photo recovery program for phones, using my mom's PC. A list of bogus recovery program sites appeared (had to look them up on her PC, as I found only legit, widely trusted programs now, using my laptop. Those darn Google's personalized search result algorithms!).
Before using the dr.fone Recovery software I synced most of the data to her account.
Used the "free" dr.fone Recovery software as per its site's instructions, the phone did a restart and the touchscreen went unresponsive to touch. Later the software showed the lost files it found, and offered to restore them for a sum. Naturally I declined.
The software said that to return the phone to normal I need to disconnect the USB cable. I did so, but the phone's screen remained unresponsive to touch, even after restart (long-press [Pow] + [Vol-]).
I tried connecting an USB mouse via the dongle, but the mouse cursor didn't appear (maybe this phone doesn't have this functionality).
Now, after using that FAIL-covery program, I was overly cautious not to make things even worse.
I wanted to make a copy of the phone's internal SD state (or is it called a phone's hard drive?), to get the media files from the clone and to have a backup of mom's files.
But I failed: I downloaded APK, ncat, KingoRoot and BusyBox. Tried to follow the steps in this video: youtu[dot]be/KKkvkCgMeMA. Got stuck at "busybox not found" at about 10:27 mark in that video ("dd if=/dev/block/mmcblk0" "busybox nc -l -p 8888"). Turns out you need to run some of the apps from that phone prior to that step, and I don't know any workarounds.
Then I remembered that the files were on the external SD in the first place. Well duh! I then connected the Micro SD card to PC's reader via a Micro SD adapter. To make a copy of the SD card's 1s & 0s, and to restore the media files from said copy I used ZAR (Zero Assumption Recovery) z-a-recovery[dot]com/. The backup creation (an .ISO file or some such) and media recovery are free of charge.
Now I only need to remove duplicates and blurry pics (I think I had a Moleskinsoft's Clone Remover from an old PC magazine's CD lying around somewhere for the latter). Oh, and I better not forget to run a malware scanner on her PC and remove the mr.fone installed services and folders from it. Went a bit off-topic here, sorry!
Last I pulled a wifi passwords file with "adb pull /data/misc/wifi/wpa_supplicant.conf" command as per instructions on this page: mashtips[dot]com/see-wifi-password-android/. I don't know whether putting the file back on that phone will do the trick or not.
That's pretty much all.
I hope the situation can be resolved and I appreciate your input! :fingers-crossed: Maybe someone has come across a similar post, has constructive commentary or knows something obvious that I haven't come up with? Thank you in advance!
Edit 30 Jan '19: Got the phone working. Accessed the phone with a Chrome browser extension (name here). All accounts except some mail account were gone. WiFi didn't work.
Found a stock ROM here: (address here).
Found the Odin3 tool here: (address here). It came with a different locale ROM.
Flashed the 1st ROM with Odin. The screen started to work.
Flashed the 1st ROM with Odin again. The WiFi started working.
I'll update this with links soon.

I've got the exact same problem after using Dr Fone app!
Hi there.
I've got the same problem with my Samsung Galaxy Grand Prime after using Dr Fone, like you. I contacted Wondershare website from which I downloaded the app but they haven't bothered replying. Not happy at all!!
I contacted Samsung's support team and after trying different things (the usual stuff: reboot; remove the battery and SIM card; restart in Safe Mode; etc) which didn't solve the problem, they ended up telling me to reset the phone to the factory settings but that didn't work either.
Now my phone is stuck on the Samsung Galaxy Welcome screen which asks me to choose the language I want on my phone. The touchscreen is still unresponsive.
How did you manage to fix the problem if the touchscreen was unresponsive?
Thanks in advance for your help!
Your-Mum said:
Hello, ladies and lads!
Here's a short version of where I'm at: after installing Wondershare' s dr.phone Recovery on my mom's PC and using it on her phone:
its screen won't respond to touch (can't enter SIM card's PIN nor open screen lock)
the On/Off button won't turn off the phone on long press (maybe due to screen lock)
on restart there's a yellow text that reads "Set Warranty Bit : kernel"
the physical buttons still work
I can see the phone's files and folders only through PC's command prompt, using ADB ('This PC\Galaxy Grand Prime' folder in Win Explorer says it's empty).
Ideally I want to keep her data (FB Messenger, Skype, Chrome, WiFi passwords, etc), and her phone to function again. What do you think I should do?
I think I need an advice and suggestions from someone more experienced than me - I don't even know trusted sites where to download the firmware roms from.
The phone's details are (I'm afraid you'll have to walk me through to get more details to this list, as I'm new to the forum):
Phone: Samsung Grand Prime
Model name: SM-G530FZ
Firmware version: G530FZXXS1BQC2 (Android 5.0.2 with Baltic bloatware, I guess)
Now in detail:
My knowledge and experience regarding the smartphone software & restoration is very basic (I've only restored the firmware to a LG-L70 once some years ago, and that's it).
Before the problem I lost some over 600 media files from that phone by Cutting and Pasting a folder from phone's internal SD to PC's disc. Now I learned never to Cut-Paste important or irreplaceable files. The files ended up on the phone, because a folder with over 800 files couldn't be uploaded to the Google Drive (the camera's folder had over 1k files in it, so I moved some of them to another folder, which the phone created on the internal partition rather than the SD Card, where the original folder was from).
Instead of using a trusted software, I foolishly Googled a photo recovery program for phones, using my mom's PC. A list of bogus recovery program sites appeared (had to look them up on her PC, as I found only legit, widely trusted programs now, using my laptop. Those darn Google's personalized search result algorithms!).
Before using the dr.fone Recovery software I synced most of the data to her account.
Used the "free" dr.fone Recovery software as per its site's instructions, the phone did a restart and the touchscreen went unresponsive to touch. Later the software showed the lost files it found, and offered to restore them for a sum. Naturally I declined.
The software said that to return the phone to normal I need to disconnect the USB cable. I did so, but the phone's screen remained unresponsive to touch, even after restart (long-press [Pow] + [Vol-]).
I tried connecting an USB mouse via the dongle, but the mouse cursor didn't appear (maybe this phone doesn't have this functionality).
Now, after using that FAIL-covery program, I was overly cautious not to make things even worse.
I wanted to make a copy of the phone's internal SD state (or is it called a phone's hard drive?), to get the media files from the clone and to have a backup of mom's files.
But I failed: I downloaded APK, ncat, KingoRoot and BusyBox. Tried to follow the steps in this video: youtu[dot]be/KKkvkCgMeMA. Got stuck at "busybox not found" at about 10:27 mark in that video ("dd if=/dev/block/mmcblk0" "busybox nc -l -p 8888"). Turns out you need to run some of the apps from that phone prior to that step, and I don't know any workarounds.
Then I remembered that the files were on the external SD in the first place. Well duh! I then connected the Micro SD card to PC's reader via a Micro SD adapter. To make a copy of the SD card's 1s & 0s, and to restore the media files from said copy I used ZAR (Zero Assumption Recovery) z-a-recovery[dot]com/. The backup creation (an .ISO file or some such) and media recovery are free of charge.
Now I only need to remove duplicates and blurry pics (I think I had a Moleskinsoft's Clone Remover from an old PC magazine's CD lying around somewhere for the latter). Oh, and I better not forget to run a malware scanner on her PC and remove the mr.fone installed services and folders from it. Went a bit off-topic here, sorry!
Last I pulled a wifi passwords file with "adb pull /data/misc/wifi/wpa_supplicant.conf" command as per instructions on this page: mashtips[dot]com/see-wifi-password-android/. I don't know whether putting the file back on that phone will do the trick or not.
That's pretty much all.
I hope the situation can be resolved and I appreciate your input! :fingers-crossed: Maybe someone has come across a similar post, has constructive commentary or knows something obvious that I haven't come up with? Thank you in advance!
Edit 30 Jan '19: Got the phone working. Accessed the phone with a Chrome browser extension (name here). All accounts except some mail account were gone. WiFi didn't work.
Found a stock ROM here: (address here).
Found the Odin3 tool here: (address here). It came with a different locale ROM.
Flashed the 1st ROM with Odin. The screen started to work.
Flashed the 1st ROM with Odin again. The WiFi started working.
I'll update this with links soon.
Click to expand...
Click to collapse

Mod Edit: xxxx A New Way OF ROOTING LATEST SAMSUNG PHONES BY [EASY-FIRMWARE-TEAM]

Hello every one .
Easy Firmware team proudly presents
The new site for root files WHICH SUPPORT ANY ANDORID VER FOR NOW
mod edit: xxxx
mod edit: xxxx Manager application
The site will be the source of root files in the GSM world
and it is free for everyone
It contains root files for all models and protections and if any new protection is released or new software is built, its root file will be uploaded directly!
mod edit: xxxx root provides full root access without problems
File sizes are between 7MB and 50MB
The download is free regardless of the number and size of files
Also the site allows you to report any file inside the site through the report button and also you can request a new file if it is not available through the site
The flashing process is done exclusively through the on-site tool
mod edit: xxxx Root Supports :
All models of Samsung devices, including exclusive models such as
A51 and M315F etc ...
The site contains mod edit: xxxx manager app to manage the root access and also to install any external addsons for the phone (such as pupg hacks etc.)
You can download files from the official website
mod edit: xxxxx
And through Google Play
You can download root manager app
mod edit: xxxx
https://play.google.com/store/apps/details…
Video For Website
mod edit: xxxx

Has anyone tried this? I hope i don't regret it. By the way, your .exe file is rejected as a virus when attempting to download it.
*UPDATE*
Tried it on SM-A207M, A20s
Does not work at all. Immediate boot.img fail
Was this tested?
I used Jamaica firmware as it matched one of the three file options. A207MUBU2ATC4. It also was ther most recent for Android 9. The wallpaper is horrific. Anyway, please fix this or at least test it before people assume it's working as you suggest. It's not.

SM-N910P worked perfectly
Already had my Note 4 (SM-N910P) rooted, but wanted to give this a try....,it worked perfectly. Only have one suggestion with the verbage the .exe will use in regards to what mode to reboot the phone into. The .exe has Reboot into Recovery which isn't correct for Samsung phones, so I clicked vol - to highlight reboot to bootloader, then clicked power button, as soon as the phone went to download mode the xxxx software did its thing and rooted the phone,
I do have a question in regards to the .apk file. After loading it does a root check and shows Not Rooted within the xxxx app itself (even though my phone was still rooted. So I uninstalled root, opened the xxxx again and yes still shows not rooted which now would be correct. Then rooted using xxxx recovery file download and went through the process, this is where I noticed the use of Recovery vs Download modes. First using adb reboot recovery... nothing happened...so I used vol - & then power to reboot to bootloader.... booooyaaaaa! Very smooth, superb work to anyone that helped put this tool together.
PimpinAintEasy ItJustAint

My Internet Security already blocked the download due to some HTTP content on the xxxx website. Later when I checked the download tool - 2 different anti virus complained about a Trojan in the file. Sorry, too risky for me.