Hey XDA,
So I need your help with something. This morning I woke up to my LG G3 D855 v10i stuck in a bootloop, for no apparent reason. I'd set an alarm to go off, and it did but only for a second and not the full 10 seconds it should have, and then it shutdown and went into a boot loop with the LG Boot Animation and the notification light was flashing yellow. I pulled the battery out, put it back in, and then restarted it. I got the same boot-loop except the notification light was alternating between blue and green as it should have been, but it was still stuck. So I pulled it out, tried again twice more, until the phone finally decided to boot. Then the phone boots, and I see my customized lockscreen with my lockscreen image and lock code, and then it goes to the screen to setup the phone completely again; Like it's a brand new phone with nothing on it, except that some of my apps were opening/running and I could see them doing things while on the setup screen. At this point I knew something was up, and I suspect a corrupted file or something on the phone, and then I started getting a whole bunch of errors on the phone itself, such as "Gmail has stopped working", "com.google.gapps has stopped working" "YouTube has stopped working" and basically all the Google apps had stopped working, but mine were still running fine.
So, after a whole day of trying to flash a new KDZ in Normal Flash mode to the phone using the LG Flash Tool 2014 here on the forums, and failing over and over (Yes, the phone was in download mode, COM port on the PC was set to 40 and I tried port 41 as well, I even put the .kdz file itself in the LG Flash Tool 2014 folder as it says to do, but nothing worked and I kept getting all this http://gyazo.com/158044ffe14287157a4388a2a42680c0 ) So I just decided to do a hard factory reset on the phone itself. I've now updated it and everything's fine, it's just a vanilla LG G3 with none of my apps on it.
Now I'm onto my current predicament. I've installed LG PC Suite when I first got the phone and since then I've done 2 full backups of the phone using it, as seen here ( http://gyazo.com/cebada2d6b06cd116afce22d8caad8bc ) but LG PC Suite recognizes NONE of them as seen here ( http://gyazo.com/3359f520739ab229334d9fa9d4e1edd2 ). In the area down the bottom where it should list the backups I've done, it doesn't list anything, even though the backups are in the correct folders themselves. Since factory resetting the phone wiped the internal memory, I lost all 32GB of my Apps, Photo's, Videos, and all my App Data. I NEED a way to get LG PC Suite or something else (Even ADB?) to push the backup/backup files to the phone and restore it. As you can see here, when LG PC Suite backs up the phone, it creates all of this data ( http://gyazo.com/a62ad1efa0e127c1b5830562965ed50a ) but in LG PC Suite's Backup/Restore device area when my device is plugged in, it shows no backups. I've even tried changing the directory the backups are in, re-installing PC Suite, everything.
I just really need a way for the PC, ADB or LG PC Suite to push all the files onto the phone and restore them, copying the files to the phone and using the G3's built-in restore app doesn't work either; All backups done by the phone were on the internal storage which was wiped with the factory reset
If someone could come up with a solution to this, I would be eternally grateful; You would save me an immense amount of time having to re-download my 32GB on my internet (Which is slow here in AUS) and I'd be eternally grateful. I'm not sure if it's the LG Software just being crap like their Android App Code, or if it's just an error or if the backups need to be in a specific place, I'm not sure. I just need a way to push them onto my phone and restore it. Thank you SO much to anyone that comes up with ideas or a solution!
TL;DR: I need a way to get LG PC Suite to recognize my backups I've done so I can push them to the phone.
iDefalt said:
the op
Click to expand...
Click to collapse
try This, I am sorry to say but you will have to redownload the 1gb file if this doesn't work esspecially since imei is motherboard depended'(imei error that you get) I guess you have a faulty motherboard you will have to bring your phone in for repairs
So I hope this thread isn't too useless. I've been researching how to restore my imei after losing 4g signal when my phone randomly (just sitting there on the desk, not touching it), decided to get stuck in a reboot loop.
Here's my specs:
Network: AT&T
ROM: CyanogenMod 11-20141112-SNAPSHOT-M12-d2lte
Modem: UCUEMJB
Recovery: ClockworkMod 6.0.4.3
Device Model: SAMSUNG-SGH-I747
Product Code: Not Active
PDA Version:
Baseband Version: I747UCUEMJB
CSC Version:
Kernel Release: 3.4.104-cyanogenmod-g9f57632
Kernel Version: #1 SMP PREEMPT Tue Nov 11 22:15:56 PST 2014
ROM Build: d2uc-user 4.3 JSS15J I747UCUEMJB release-keys
Android Version: 4.4.4
BusyBox Version: 1.22.1
SU Binary Version: 2.40:SUPERSU
So here's what I've learned. My IMEI was lost due to a weird Samsung backup procedure that backed up my /efs folder with essentially a blank copy of important information. I have my IMEI, but writing it to the phone is very difficult. From this tutorial I learned to download QPST, and somewhere else I heard about EFS Professional.
So I tried to use EFS Professional first, and have been able to connect my phone (Had to install adb first via the official android sdk). I was able to make a backup of my efs folder. I was also able to change the usb settings to DIAG + MODEM + ADB. Then I launched the Qualcomm NV Tools. From there, by unchecking "Send SPC" and "Read Phone" I was able to connect to the phone, but any other button I pressed didn't accomplish anything except disconnecting the phone again.
This is when I turned to QPST. I knew from EFS Professional which COM port my phone was using each time, and I added the COM ports to the QPST Configuration program for listening. But my phone was never listed as available in the ports tab, nor was it listed in my device manager under COM ports. I tried using the RF NV Item Manager anyway, entering in my IMEI "backwards" with an 8 in the first line and an "a" after the first real number in my IMEI, but my phone was never really connected, so of course nothing happened.
I learned this was probably because I have no IOTHiddenMenu / Qualcomm USB Settings Menu / whatever you want to call it with USSD codes, because I'm using an AOSP ROM (Cyanogenmod). This thread and this thread were useless in enabling DIAG mode, because of broken links and scripts that no longer work on newer versions of CM.
My next plan is to change ROMs to a TouchWiz ROM, but I haven't found a good one yet, especially considering I've upgraded my bootloader and I know that if I flash a ROM with a downgraded bootloader, I'll definitely brick my phone. So is there a ROM I can use with an upgraded bootloader that won't brick my phone and will allow me to enter DIAG mode so that I can connect to QPST via a COM Port, use the RF NV Item Manager, and put in my old IMEI? Or am I just going about this all wrong?
You do have to be on a TW ROM with a stock dialer for ussd codes to work. Based on everything you posted you should be on the mjb boot loader, but confirm that first. Enter this into a terminal or adb shell:
Code:
getprop ro.bootloader
If you are on an mjb bootloader, then this ROM should work for you http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18. It's a rooted deknoxed at&t stock mjb.
Good luck.
---------- Post added at 12:04 PM ---------- Previous post was at 11:57 AM ----------
You probably already discovered this in your research, but just in case. When you get your imei problem solved, before flashing something other than a TW ROM, enter this in a terminal or adb shell:
Code:
su
reboot nvbackup
That will fix Samsung's whoops and give you a working efs backup partition instead of a blank one.
Thanks! I'll try this and get back.
alexalexalex09 said:
Thanks! I'll try this and get back.
Click to expand...
Click to collapse
You were right about the bootloader - when I looked up the ro.bootloader property, it spit back what I thought was my modem identifier, I747UCUEMJB - so yes, MJB. I'll get a chance to flash the new ROM tomorrow or the next day and see how it goes.
So, two steps forward and three steps back. I did install the new ROM. Initially, it appeared to work, because I was able to dial *#7284# to access the service mode menu and change UART to MODEM, and then dial *#0808# to access the USB Settings menu and change that to RMNET+DM+MODEM. After that, the phone showed up under COM5 in the Device Manager. I opened up QPST Configuration and added COM5 (labelled it "COM5") under ports. However, the phone never showed up (Phone column read "No Phone").
I then tried EFS Professional, but it was unable to detect the phone. I opened up the command line and tried an adb shell, but it didn't connect. Of course, the phone was in RMNET+DM+MODEM mode, not and ADB mode. I then went back into USB settings, changed it to DM+MODEM+ADB, and reconnected the phone. The phone wasn't detected by the computer, and hasn't been since.
I've restarted the phone and the computer multiple times (Windows 7 32 bit), uninstalled the phone drivers, reinstalled them in two different versions, uninstalled and reinstalled QPST (removing the relevant registry entries in between installs), and went through a number of combinations of settings on the phone. I tried with UART set to MODEM and PDA, with USB settings set to DM+MODEM+ADB, RMNET+DM+MODEM, MTP, and MTP+ADB. I made sure superuser was installed correctly and that developer mode was enabled. I still have not gotten the phone to charge in that USB port or show up in Device Manager in any way, even though the USB port on the computer still functions (can access flash drives from it). I plan to do some more googling and troubleshooting about this, but I haven't had the time to yet. On Wednesday I'll hopefully have a minute to try using my work laptop to access the phone. I think once I get the phone to be recognized via USB again I'll be able to have QPST Configuration recognize it, then I'll be able to use that RF NV Item Manager to enter in the new IMEI.
Also, in potentially unrelated news, my install of Titanium Backup is unable to recognize any apps I backed up, even ones that have been previously restored. It sees them in the backup folder (backup folder location says this folder contains 52 backups), but no apps wee listed in the backup/restore tab. Maybe this has something to do with the mount namespace separation setting in SuperSU? I'll test that later.
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
audit13 said:
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
Click to expand...
Click to collapse
Thanks for chiming in, but I don't understand how this applies. I was on CM11 when my IMEI was removed. When you lose your IMEI, the main symptom is that you can't connect to 4g anymore, and you're stuck on EDGE, which is what happened in my case. I can in fact make calls and send texts, and even load web pages without wifi. It's just slow and prone to call dropping.
As for your advice to install an older ROM, I just flashed a stock ROM, the one linked above. It didn't cause my current lack of USB connection, because I had a USB connection for a while until I changed the UART and USB settings.
I definitely will not touch the bootloader - I've been warned about the dangers of downgrading from an MJB bootloader. I'm not sure what you mean by not touching the modem, but I'm going to assume it's as scary/difficult as the bootloader, so I'll be sure to stay away from changing that too.
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
alexalexalex09 said:
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
Click to expand...
Click to collapse
I should note that I took a look at my EFS folder while writing this last post, and it's completely empty now. So that's fun.
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
audit13 said:
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
Click to expand...
Click to collapse
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
alexalexalex09 said:
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
Click to expand...
Click to collapse
I got it! Problem solved!!
So what I realized after going back over those research threads quickly was that I was using Peoplearmy's QCN generator incorrectly. Here's how I fixed it.
1. Opened QPST, followed directions here to connect my phone and start up QPST Software Download.
2. Having already injected my IMEI, I used the backup tab to make a backup.
3. I opened Peoplearmy's SG3QCNGenerator and imported the QCN file that QPST just created. I left "inject IMEI" unchecked, since I already had my original IMEI. I clicked Save As to set the directory and name of the new file, and clicked the Verify IMEI button that appeared to verify that it was correct.
This was the step I had missed - because I never had a valid QCN file to import, I never was able to create a new QCN file. My error in thinking was that, since my current QCN file was obviously messed up, I couldn't use it to make a new QCN file, but that's the whole point of this software.
4. Once I had the new QCN file, I went back to QPST's Software Download program and used the Restore tab. The QCN file generated by Peoplearmy's tool didn't match my model number, but I approved it anyway. It restored the QCN file correctly, but it had an error when it tried to reset the phone.
5. I rebooted the phone manually, and I now have 4G signal!
So, to summarize the difficulties I had:
1. I didn't make an nvbackup before I flashed CM a year ago, and it didn't hurt me until now.
2. I lost my IMEI and couldn't restore it because 1) I was on CM, which stopped me from putting my phone in DM + MODEM + ADB mode and 2) The computer/cable I was using to work on my phone, for whatever reason, were being stupid.
3. I didn't understand that in order to fix my phone I needed to restore my IMEI and repair my nv items (.qcn file)
4. I didn't realize that I could use Peoplearmy's tool to take a messed up nv items qcn file, fix it, and restore it to my phone.
All the tools I ended up needing: Samsung Drivers, ADB, ES Professional, QPST, and Peoplearmy's SG3 Data Restorer. Hope this helps someone else out there.
:good: thanks for posting fix.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Great job. Thanks for posting your solution back here so others can find it.
I have been pulling my hair out over my Galaxy S4 recently. I think it is an issue where a virus has embedded itself deep into the OS or flash partitions that are not affected by ROM factory firmware flashing. Everytime I re-flash I have to reformat and wipe cache partition to stop it from being stuck on T-Mobile boot logo. The Samsung boot logo is choppy and not fluid like it once was, indicating extra boot time application loading. I have reflashed different firmwares multiple times and to no avail. I used a VPN proxy called Betternet and now my phone keeps getting internet in different locations of the world following an odd traceroute following the subnet of 10.170.205.XXX before reaching its final destination. And on top of that every new computer I use for mobile hotspot usb tethering it crashes explorer and various other applications on my computer, I'm guessing it is an infected hotspot apk embedded in flash recovery injecting malicious code onto the computer via usb as soon as the usb tether fature is activated. Whenever I put the phone into Kies Recovery mode yellow triangle(where phone will not boot, and no recovery menu with Vol up and power buttons) Kies says it does not recognize the phone and will not let me flash factory recovery firmware. I am pretty sure my phone is irreparable due to so many software issues. Is there any way to get a factory file system Image restored onto the phone. I have tried everything even installing TWRP and removing everything that way, but I have the strangest feeling it doesn't clear some of the flash partitions used for recovery and flashing where this Virus may be hiding it's malicious code and executing it every time I flash factory firmware. I'm on 4.4.4 FNK 16gb Galaxy S4 black model SGH-M919
Any advice I have not mentioned would be greatly appreciated because I do not feel like shelling out another 400 bucks for a new phone.
Thanks for taking the time to read that!
AndroidInitiate said:
I have been pulling my hair out over my Galaxy S4 recently. I think it is an issue where a virus has embedded itself deep into the OS or flash partitions that are not affected by ROM factory firmware flashing. Everytime I re-flash I have to reformat and wipe cache partition to stop it from being stuck on T-Mobile boot logo. The Samsung boot logo is choppy and not fluid like it once was, indicating extra boot time application loading. I have reflashed different firmwares multiple times and to no avail. I used a VPN proxy called Betternet and now my phone keeps getting internet in different locations of the world following an odd traceroute following the subnet of 10.170.205.XXX before reaching its final destination. And on top of that every new computer I use for mobile hotspot usb tethering it crashes explorer and various other applications on my computer, I'm guessing it is an infected hotspot apk embedded in flash recovery injecting malicious code onto the computer via usb as soon as the usb tether fature is activated. Whenever I put the phone into Kies Recovery mode yellow triangle(where phone will not boot, and no recovery menu with Vol up and power buttons) Kies says it does not recognize the phone and will not let me flash factory recovery firmware. I am pretty sure my phone is irreparable due to so many software issues. Is there any way to get a factory file system Image restored onto the phone. I have tried everything even installing TWRP and removing everything that way, but I have the strangest feeling it doesn't clear some of the flash partitions used for recovery and flashing where this Virus may be hiding it's malicious code and executing it every time I flash factory firmware. I'm on 4.4.4 FNK 16gb Galaxy S4 black model SGH-M919
Any advice I have not mentioned would be greatly appreciated because I do not feel like shelling out another 400 bucks for a new phone.
Thanks for taking the time to read that!
Click to expand...
Click to collapse
Could be it's not a virus, but just a lot of apps, or even one rogue app. But, just to be sure, you can do the following. :
1) Download one of these Firmwares to a Windows PC- either one of the top two:
http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
2) Make sure you have ODIN 3.07 or newer installed on the PC, and that you have the Kies drivers installed. You may have to install Kies to get these.
3) If you have TWRP installed or other recovery, do a full NAND backup to you external SD card
4) Use Advance Wipe in TWRP to wipe Dalvik, System, Data, Cache
5) Use ODIN to flash the firmware you downloaded in step 1. Look here for info:
http://forum.xda-developers.com/gal...odin-thread-return-to-stock-fix-soft-t2915530
This will get you back to full stock. You could make another NAND backup at this point, in case you run into something else.
Don't let the system download/restore any applications. Let it settle in for a few days. If it is working, then allow it to restore your apps.