Flash to boost - or repair - Sprint Samsung Galaxy Note II

So.... Can anyone confirm if the steps are the same like s3?

Shouldn't be in this section, you should know that...
Sent from my SPH-L900 using Tapatalk 2

Thread moved to Q&A.

can you do this without rooting?

No need for root to repair.
As long as the default samsung password works, it should be the same.
But I don't have my phone in hand yet. So I cannot confirm if default password work

So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns

trim81 said:
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
Click to expand...
Click to collapse
Trim, how were you able to get in and repair MEID? I used *#7284# to set the UART and USB to modem, but once I do that, Windows won't recognize the device. I do see a notification about "Qualcomm CDMA Technologies MSM" but no driver can be found.
If I set UART/USB back to PDA I can get Windows to recognize the device using mskip's device drivers.

trim81 said:
I had to manually insert everything in qpst.
Click to expand...
Click to collapse
by that you are referring to the data profiles, right? but how did you get your ESN allowed on boost, were you able to have customer service do it for you or did you actually spoof the ESN?

##3424# use that ibstead
After youre in everything is straifht foward

trim81 said:
##3424# use that ibstead
After youre in everything is straifht foward
Click to expand...
Click to collapse
What version of QPST are you using? I have build 378 and it's only good enough to establish the com port for QXDM. If you have a more recent version could you share it with us?

I'm not at home now... But look into the s3 forum, the repair method is the same, I used alpineman method.
But this phone is easier, in that no dfs is needed... Everything is repairable with qpst.
Like mentioned tho. I'm not sure if the towers or down or not.. But it will never take an ota activation both via profile 0 or wifi.
I ended having to input the settings manually via qpst
I won't go into spoon feeding, and step by step, it's already published - - look into the galaxy s3 forum
I used the same program versions as that thread

Edit
I used qpst 2.7 build 378

Can someone with knowledge please help create a voicemail. Apk hack for boost?

Still having problems
trim81 said:
Edit
I used qpst 2.7 build 378
Click to expand...
Click to collapse
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.

Chanman said:
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Click to expand...
Click to collapse
Yes!!! I did it. I thought I would share what worked for me in hopes that this will help others.
I ended up using *#7284* and then putting UART and USB both on MODEM. As I mentioned in my previous post, this causes the device to be detected as "Qualcomm CDMA Technologies MSM". I had to install a specific generic Qualcomm driver, which I have included in this post. After that, since I was only able to use QXDM/QPST/DFS to write the voice specific settings and HA profile (not passwords), the thing that ended up working for me was CDMA Workshop's free NVItem writer. Using this tool I was not able to read the crucial NVItems (466 and 1192), but I was able to write them. I did a byte-for-byte identical write, cloning the NVItems from the original phone (which I was able to read from). After the tool indicated the items were successfully written I rebooted the phone and everything worked!

guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.

I used all drivers and programs in the galaxy s3 post.
Follow that guide

iwin2000 said:
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
Click to expand...
Click to collapse
The driver I included in my post is a Win32 driver only. If you have Windows 7 64-bit it won't work. I had to use this particular driver on a 32-bit Windows XP machine. Sorry for not including that information in my post. You might be able to make a virtual machine to get the driver to load. I wasn't able to find a 64-bit Qualcomm CDMA MSM driver.

Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.

iwin2000 said:
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
Click to expand...
Click to collapse
Happy this worked for you. I believe this is the standard way to get into the phone (these instructions are all over Youtube and the S3 forum). The reason why I had to do things differently is that when I tried that approach, even though the devices show up as "Samsung" without any errors in Device Manager, QPST and DFS show "no phone" or can't connect to the port, even though it's there. Maybe I just got unlucky, or you got lucky, or both

Related

[How to] change your Slot Cycle Index for faster incoming/outgoing calls!

EDIT EDIT EDIT!!
Ok, it appears we finally got this working! Thanks very much to Megatr0n for figuring out how to get QPST to recognize our phone! Couldn't have done this without this/him and everyone else's hard work for who actually figured it out!
Please note, I take NO credit for this discovery, just passing along info from amazing hard work of others!
I got most of my info from this thread (thanks to youngstatus)!
http://forum.xda-developers.com/showthread.php?t=703104
Information on getting QPST to recognize your phone is from the PRL flashing thread--all credit goes to whomever came up with how to do this (and Megatr0n, who found this thread): http://forum.xda-developers.com/show....php?t=1267893
Also thanks to cnstarz for figuring out some steps on this as well!
What this is:
Sometimes when my friends text/call me, it takes anywhere from 3-5 rings on their end until my phone receives the call, and it was a little annoying. I remember I did this trick on my hero, and thought I'd share.
What this does is changes the frequency the phone checks the towers for incoming calls, If you are like me, you have probably had times where you will have phone calls that only ring for like 5 secs and then the person hangs up. So i came across this little trick and it works as follows
The default Value 2=3.015434secs
The value i use is 1=1.507717secs
You can change this to how you see fit, I have tested and noticed there is no considerable drain on the batter at 1 and theoretically speaking putting it higher will conserve battery as your phone isn't constantly pinging the towers but i have never tried that
0= edit: (from jazzneel) I think this is reserved for emergency vehicles, so please do not use this in case! (not 100% sure)
1= 1.507717secs
2= 3.015434secs(Default)
3= 4.523151secs
etc.....
How to do it:
1. Install QPST
2. Make sure you have your phone drivers installed.
2.5 Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging
3. On your Epic, with the touchscreen dialer, dial ##8778#
4. Change the setting from AP to CP, then hit Home.
5. Connect your phone to your computer with the usb cable.
6. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”
7. Open QPST Configurations. Start>All Programs> QPST> QPST Configuration.
8. Click on the “Ports” tab and “Add a new port”
9. Select the “COMXX – USB\QC Diagnostic” and click ok, in my case the port number was 10, your port number will be different, if you see more than one, disconnect all your external devices such as external HDDs, phones, Bluetooth dongles, ect. If you don’t see a port. Disconnect your phone, restart your computer, connect your phone and try again, you might want to remember your Epic’s port number for future use. If you still don't see a port uncheck the box for "Show Serial and USB/QC Diagnostic ports only" and add all of the USB/Unknown ports. One of them should show an active phone.
10.Open up QPST > Service programming. Select your phone in the "Select an active phone" box and click on "Read from phone" and enter your MSL when prompted.
11.You will see the Slot Cycle Index is at 2. Change it to 1 and click "Write to Phone". Then reboot phone.
12. Once you're finished be sure to set your settings back to normal (go to ##8778# and change it back to AP and re-enable debugging mode)
-Your Slot Cycle Index is now changed to 1. You can verify after rebooting the phone by launching Service Programming and clicking "Read From Phone" again.
*I take no responsibility for your actions on this post, I am just copying/pasting the work of others. If anything happens to your phone, not my fault!
I didn't see index anywhere in the menus.
phatmanxxl said:
I didn't see index anywhere in the menus.
Click to expand...
Click to collapse
Same issue here. OP might want to recheck your steps to make sure it's relevant for this phone.
Sorry about that! I have updated the OP for doing the same method as the epic 4g. Hopefully that method works for people that want to use this.
Just to be clear, is this for rooted phones only?
Download QPST.
edit: i dont get prompted "Charging, mass storage, or tethered modem" when i plug in my usb cable.
cnstarz said:
Download QPST.
edit: i dont get prompted "Charging, mass storage, or tethered modem" when i plug in my usb cable.
Click to expand...
Click to collapse
Same issue here.
What's the tradeoff on this? Increased battery drain?
Sent from my SPH-D710 using XDA App
i went to settings>wireless and network>tethering and enabled usb tethering there, but QPST doesnt see the phone. i dont know what other drivers i need installed if i the phone is recognizable in odin, kies, and windows (mass storage).
EL TEJANO said:
Just to be clear, is this for rooted phones only?
Click to expand...
Click to collapse
No, this is for all phones, rooted and unrooted.
cnstarz said:
i went to settings>wireless and network>tethering and enabled usb tethering there, but QPST doesnt see the phone. i dont know what other drivers i need installed if i the phone is recognizable in odin, kies, and windows (mass storage).
Click to expand...
Click to collapse
One thing I tried on my epic 4g when I did this trick was install PDA net. For some reason that worked for me...
Hopefully I didn't give you all bad info, I'm looking into this, sorry!!
limeaid said:
What's the tradeoff on this? Increased battery drain?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
If i can figure out how to get it working on our touch, there could be a tiny bit of battery drain, but it will be somewhat negligible. However, if you are at a place that gets almost no service, then your battery will drain faster than it would without the trick. That is really the only drawback of this.
installed PDA Net, still no go. Are we supposed to actually do something with PDA Net, or just install it?
cnstarz said:
installed PDA Net, still no go. Are we supposed to actually do something with PDA Net, or just install it?
Click to expand...
Click to collapse
Just install it. For some reason, the drivers on my epic 4g wouldn't work, but PDA net would (for a lot of people), so I was hoping it would help....I know there is a way to do this, but I may need some help from someone who is a little more advanced.
I thought the method of the epic 4g and the epic 4g touch would be the same, but apparently its not....
Ok guys, I have it working.
Steps to get it to show your phone:
1. Install QPST
2. Make sure you have your phone drivers installed.
2.5 Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging
3. On your Epic, with the touchscreen dialer, dial ##8778#
4. Change the setting from AP to CP, then hit Home.
5. Connect your phone to your computer with the usb cable.
6. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”
After this you can follow the steps provided by the OP and it'll work fine.
Once you're finished be sure to set your settings back to normal (go to ##8778# and change it back to AP and re-enable debugging mode)
Information pulled from the PRL flashing thread--all credit goes to whomever came up with how to do this (which, obviously, isn't me): http://forum.xda-developers.com/showthread.php?t=1267893
Megatr0n. said:
Ok guys, I have it working.
Steps to get it to show your phone:
1. Install QPST
2. Make sure you have your phone drivers installed.
2.5 Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging
3. On your Epic, with the touchscreen dialer, dial ##8778#
4. Change the setting from AP to CP, then hit Home.
5. Connect your phone to your computer with the usb cable.
6. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”
After this you can follow the steps provided by the OP and it'll work fine.
Once you're finished be sure to set your settings back to normal (go to ##8778# and change it back to AP and re-enable debugging mode)
Information pulled from the PRL flashing thread, all credit goes to whomever came up with how to do this (which, obviously, isn't me): http://forum.xda-developers.com/showthread.php?t=1267893
Click to expand...
Click to collapse
ah thanks so much! Do you mind if I put this on the OP? I will give you credit of course!
jazzneel said:
ah thanks so much! Do you mind if I put this on the OP? I will give you credit of course!
Click to expand...
Click to collapse
No problem, go ahead.
Megatr0n. said:
Ok guys, I have it working.
Steps to get it to show your phone:
1. Install QPST
2. Make sure you have your phone drivers installed.
2.5 Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging
3. On your Epic, with the touchscreen dialer, dial ##8778#
4. Change the setting from AP to CP, then hit Home.
5. Connect your phone to your computer with the usb cable.
6. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”
After this you can follow the steps provided by the OP and it'll work fine.
Once you're finished be sure to set your settings back to normal (go to ##8778# and change it back to AP and re-enable debugging mode)
Information pulled from the PRL flashing thread--all credit goes to whomever came up with how to do this (which, obviously, isn't me): http://forum.xda-developers.com/showthread.php?t=1267893
Click to expand...
Click to collapse
usb tethering doesn't work in CP mode, and QPST still doesn't detect when you switch back to AP.
cnstarz said:
usb tethering doesn't work in CP mode, and QPST still doesn't detect when you switch back to AP.
Click to expand...
Click to collapse
You're using incorrect settings. USB tethering isn't supposed to work and everyone has already confirmed that QPST doesn't work in AP mode.
The instructions specifically tells you to disable USB debugging mode (which gives you the USB option) and change the setting from AP to CP. After that, connect it to your computer and wait until it installs your modem drivers. Then, open up QPST and it will work.
Megatr0n. said:
You're using incorrect settings. USB tethering isn't supposed to work and everyone has already confirmed that QPST doesn't work in AP mode.
The instructions specifically tells you to disable USB debugging mode (which gives you the USB option) and change the setting from AP to CP. After that, connect it to your computer and wait until it installs your modem drivers. Then, open up QPST and it will work.
Click to expand...
Click to collapse
but you have to enable usb tethering in order to do this... you can't enable it if it's in CP, at least mine isn't enabling even with usb debugging turned off.... in fact, tethering can only be enabled while usb debugging is turned on.
cnstarz said:
but you have to enable usb tethering in order to do this... you can't enable it if it's in CP, at least mine isn't enabling even with usb debugging turned off.... in fact, tethering can only be enabled while usb debugging is turned on.
Click to expand...
Click to collapse
Did you actually try the instructions or are you just arm-chairing it? Because, I already did it and I used the same method to flash a custom PRL.

[Q] brand new Sprint S3 (LJ7) could not connect to DFS

So I'm playing with the brand new Sprint S3 with LJ7 stock rom and is stuck at the very first step. Managed to get the COM port opened in the PC for Samsung USB diag mode, however, the DFS 4.0.2 and QPST failed to connect. I can choose the right port to open in DFS, but whenever I try to read from the phone, it shows researching device forever, and I'm certain the spc code is correct (got from the app getmymsl, and I could use it to edit the data file). In QPST, there is no device listed under that COM port (normally you should see the phone listed as SURF****)
Searched and followed this instruction: http://forum.xda-developers.com/show...7&postcount=14 but still not working for me.
Just now I tried install the samsung usb driver and DFS 4.0.2 in a freshly installed windows 7 (64bit) machine, so the only COM ports installed/opened are the samsung's, but still the same symptoms.
I've heard people talking about downgrade ROM and radio for those software to work, but I also saw people directly using DFS for the newer ROM. What did I do wrong then? Please help.
BTW, I dial ##3424# to bring out the diag mode panel, and tried different combinations such as:
Modem / dm+modem+adb
PDA / dm+modem+adb
modem/ rmnet+DM+modem
pda/ rmnet+DM+modem
all gave me the same issue: having the COM port opened but the device could not be recognized.
However the phone was recognized fine as a media device.
procter said:
BTW, I dial ##3424# to bring out the diag mode panel, and tried different combinations such as:
Modem / dm+modem+adb
PDA / dm+modem+adb
modem/ rmnet+DM+modem
pda/ rmnet+DM+modem
all gave me the same issue: having the COM port opened but the device could not be recognized.
However the phone was recognized fine as a media device.
Click to expand...
Click to collapse
Try doing a factory reset. I find that after you flash the phone once using ##DIAG#, you won't be able to flash it a second time after the firmware upgraded. That's just been my experience though. You would still be able to see the port, but it won't read/write. Instead use *#PATH# instead.

Fixed: No Phone showing in QPST

This assumes you DO have the drivers installed correctly and the phone configured right. Those two things aren't that hard to do - if you've done them and still get "No Phone" this may help.
I spent a lot of time on this the last few days, searched and searched and all I found was that a lot of people ran into this problem but I never saw much of a solution other than "get the drivers installed correctly." After going through the whole driver process on a 2nd PC and running into the same issue, I looked back at the phone itself and what fixed the issue for me (on both PCs now) was sort of odd.
I had flashed from ParanoidAndroid 03-07 release back to UVALJ1 - I chose to go this far back because that old stock is where I was able to do the free unlock via dialer code menus. I was still on baseband UVALL4.
I got the most recent Samsung drivers directly from Samsung and I'm working with QPST 2.7.378. The drivers were installed, the phone was in PDA mode on USB & UART and Qualcomm USB settings were DM + Modem + ADB. A COM port was showing up in device manager with a working driver (no unhappy devices at all in my device manager, all working.)
Given all of that, when I'd go into QPST I could add the port that showed up in device manager but it always said "No Phone".
It dawned on me when I had flashed all the way back to UVALJ1 to do the unlock, I did it with Odin and it put the modem on the came with that old stock. I downloaded just the modem for UVALJ1 and installed it via TWRP. That fixed my "No Phone" problem. Whats even more strange is that I've since gone back to UVALL4 baseband (installed via TWRP) and...the "No Phone" is still fixed.
I have no clue what flashing the modem did but it kicked something into communicating with QPST. I figured I'd get the problem back when I went back to UVALL4 but apparently not. Working fine now on that modem with the older stock ROM on top of it.
Hope this helps someone and saves them the many hours it took me to try this - flashing the modem only took a few seconds. Installing and removing and rebooting and trying different drivers on two different PCs took a good long time!
I have de same problem with my Samsung Galaxy Light and my Samsung Galaxy Note 3.
Can someone help us please?
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.

Cant update to Marshmallow

I have spent litterally all day trying to update my mrs g3 d855 and i have had no luck, how much of it because my computer i dont know. Im running a chromebook with a full linux distro gallumos installed, got virtual box running 32 bit windows 7. Android sdk, adb etc and got lg drivers installed to recognise the device in its various states, ptp, mtp, download. all that is working. got the official lg mobile support tool and the lg 2014 flash tool.
the problem im having is neither of these will update the phone, if i try to manaully flash the kdz using the flashtool or updating using the official one, it wont update recover either. if i try different region or enter the imei number it always fails at 4%. Iv tried different usb cables, different ports, the phone was at 100% battery the whole time, the laptop was on charge the whole time. I really dont know what else to do, i have no access to another windows machine here and its the mrs phone and she wouldnt want me to take it to work to try on another pc there. As i said earlier the drivers all seem installed correctly, the firmware downloads and extracts as it should but I really am at the point i dont know what else to try
Hello,
Did you try LGUP method? Link is here.
It's easy to use. All you need is there, try it and reply
Just TIP: Do you really have correct drivers for download mode? If LGUP see you device as "unknown", change your COM port to #41
Do "FULL WIPE AND INSTALL MM"
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
The Gingerbread Man said:
I think I might of, how ever before work I did download a version of lg up and some kind of other installer for it. I also got a kdz file to try and flash. The drivers should all be fine, it gets recognised in all the various modes. My fiance is on nights this week, the soonest il be able to try again is tomorrow so I will let you know it goes. Thank you for replying
Click to expand...
Click to collapse
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
halekhonza said:
You can send me a PM, or just reply to this thread.
It's a common problem with various solutions. We will look at it.
Click to expand...
Click to collapse
Thanks buddy il let you know after I can try it again. If it was a Nexus it would be fine, I know all about fastboot, unlocking bootloaders and rooting and stuff for the Nexus line. So much easier to work with
So I think I might know where I'm going wrong, i thought I had all the drivers set up but there's one I missed, for download mode
Under device manager I see when the phone is turned on with adb on
Android device- lge mobile adb interface-google Inc 4.0.0.0-working properly
Portable devices-g3-lg electronics 4.0.0.0-working properly
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
In download mode device manager
android device isn't there, no adb which is fair enough
Portable devices-g3 with yellow warning triangle-lg electronics 4.0.0.0- the device cannot start code 10
Ports (com & lot)-lg mobile USB serial port (com 4)-lg electronics 4.0.0.0-working properly
So I need to trouble shoot why the device cannot start. I have downloaded 2 packs of Lg drivers, lg united mobile driver & lg mobile driver. Both of which contain loads of drivers inside.
If I guide windows into either of the folders it won't install any new drivers giving an error saying that the driver software is already up to date.
I'm going to Google to find out what's going on with device cannot start error, if I'm missing something obvious please jump in
Can you please post complete screenshot with windows device manager (with open ports menu) and adb console with command "adb devices" ?
In your chromebook, do you have disabled all USB power saving bull****s? Also check VM software to see if there is such a possibility to enable/disable USB power plans.
At least, sorry for my bad english Still a lot of things to learn.
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
The Gingerbread Man said:
Your English is fine I understand perfectly, in fact I wouldn't of guessed it's not your native language so don't worry! Iv taken photos of my screen. You will see when the phone is turned on normally the host and client can both see the device and adb shows the device is detected and returns the serial number, all good there. The last photos shows when it's in download mode and that the driver isn't working properly, it can not start the device with a code 10 error. If I can fix that I know the lgup programming will run. The problem is because the PC can't communicate with the PC in download mode because of some driver issue.
I'm going to have to carry on tomorrow as I have to go to work and the Mrs needs her phone here while she sleeps
Click to expand...
Click to collapse
Please, enter download mode and change in Windows COM port from #3 to #41 and try LGUP method . It's up to you what method (upgrade, full wipe) you choose.
OK sounds straight forward enough. As I say il have to try tomorrow as I'm at work now and left the Mrs with her phone at home asleep, she will be working night shift so it will have to be when she is back home. I really appreciate the help and il post again to update how I get on
Where I am now is no further, iv tried changing the port to 41 through device manager. Iv set the port 0041 in virtual box for USB settings. Iv tried several sets of drivers. What keeps happening no matter which set of drivers I use when the phone goes into download mode mtp stops working and stops the phone communicating with the PC. When I restart it will work normally for a while but go wrong again. If I try lg up and starting the upgrade in download mode it gives me an error saying it can't change to download mode if I choose refurbish or upgrade. Lg PC suite just hangs at 0% and returns an error after a while. The 2014 flash tool will get as far as trying to flash but hangs at 4% and returns an error but doesn't specify what. I really don't know what else I can do. When these programs reboot the device into download mode it disconnects the device from the virtual machine and I can't get it connected again quick enough before errors are returned or mtp stops working which requires me to reboot the VM or phone. The only thing I can think to do is try on another machine. If it was my phone I would of thrown it out the window or under a bus. Lg software is unusable through virtual machines and I am not buying a new PC just for this lol Il see if I can use someone else's. I hate being defeated, iv have spent probably some 16 hours and got no where! Why can't they just release an ota? It only strengthens my belief in nexus and fastboot. Sorry for the rant but this really has got under my skin and I don't like giving in
Edit
I'm just as annoyed with windows as lg at this point. I really don't like using it. Grrrr

LG G3 855 Imei/Baseband and QPST Problem

Hi Everyone,
I am new to this Phone had the maybe unfortunate opportunity to buy a lg g3 855. It has the Imei Null Problem and the baseband is showing as unknown. I thought well that shouldnt be to hard to fix (silly me).
Phone works fine except 2g/3g so no signals at all ofc.
Downloadmode,TWRP,Root is available. Stock Rom MM 30b.
So now the Problem, i thought i can just replace the Imei with QPST/RF_NV_Manager and in the worstcase flash the 855.qcn file from the forum. BUT
I just cant get QPST to recognize my phone. I installed all Drivers LG/LGMulti/Qualcomm/ADB, and it shows in device manager ast certain things but if i try to get them in QPST, they always show NO Phone/ NO ESN and therefore no connection possible. I flashed older and newer Stock Roms and i start to think that guy i bought the phone from had a major screwup ^^.
When I try to get into Diag Mode with the hidden menu,usb debugging and so on the phone doesnt really show up anymore. With Mtp i have 3 entrys in Device Manager(but they dont work either)
LGE Mobile ADB Interface
LGE Mobile USB Composite Device
LGE Mobile USB SerialPort
LGE Mobile USB Modem
With Load only there is none
I also dont get the option to choose Software Download option from Start clients menu when i insert the USB Cable
I Hope someone can help me i literally tried everything except wiping partitions because the tools always shutdown somehow.
Thanks for Reading and Help your Tritratrulala
tritratrulala390 said:
Hi Everyone,
I am new to this Phone had the maybe unfortunate opportunity to buy a lg g3 855. It has the Imei Null Problem and the baseband is showing as unknown. I thought well that shouldnt be to hard to fix (silly me).
Phone works fine except 2g/3g so no signals at all ofc.
Downloadmode,TWRP,Root is available. Stock Rom MM 30b.
So now the Problem, i thought i can just replace the Imei with QPST/RF_NV_Manager and in the worstcase flash the 855.qcn file from the forum. BUT
I just cant get QPST to recognize my phone. I installed all Drivers LG/LGMulti/Qualcomm/ADB, and it shows in device manager ast certain things but if i try to get them in QPST, they always show NO Phone and therefore no connection possible. I flashed older and newer Stock Roms and i start to think that guy i bought the phone from had a major screwup ^^.
When I try to get into Diag Mode with the hidden menu,usb debugging and so on the phone doesnt really show up anymore. With Mtp i have 3 entrys in Device Manager(but they dont work either)
LGE Mobile ADB Interface
LGE Mobile USB Composite Device
LGE Mobile USB SerialPort
LGE Mobile USB Modem
With Load only there is none
I also dont get the option to choose Software Download option from Start clients menu when i insert the USB Cable
I Hope someone can help me i literally tried everything except wiping partitions because the tools always shutdown somehow.
Thanks for Reading and Help your Tritratrulala
Click to expand...
Click to collapse
Everyone with the same Problem have a look in this Post Page 19
https://forum.xda-developers.com/lg-g3/general/request-3g-2g-lte-d850-t3300908/page19#post79462351

Categories

Resources