My Pixel 3 XL shows Invalid IMEI and not connecting to any network? How can I flash the original IMEI...I tried resetting, flashing Stock ROM everything but no luck...I found a method to do it via QPST I have connected my phone with QPST but when I restore QCN file it goes till end but IMEI is still the same.
Also when I try QPST Service programming it gives NV_read_s error
Which mode is your device in when trying to restore your QCN?
Andrologic said:
Which mode is your device in when trying to restore your QCN?
Click to expand...
Click to collapse
Diag
Andrologic said:
Which mode is your device in when trying to restore your QCN?
Click to expand...
Click to collapse
QFIL also detects the Com port and recognizes the phone but when I restore or try to backup QCN file it says "checking if phone is connected" and keep saying until it stops and gives error message while QPST is backing it up fine
Daniyal48 said:
QFIL also detects the Com port and recognizes the phone but when I restore or try to backup QCN file it says "checking if phone is connected" and keep saying until it stops and gives error message while QPST is backing it up fine
Click to expand...
Click to collapse
Strange if your device is confirmed to be in Diag mode (not EDL).
Andrologic said:
Strange if your device is confirmed to be in Diag mode (not EDL).
Click to expand...
Click to collapse
I also tried removing modemst1 and modemdst2 but no luck....am I doing something wrong....what is the proper way to do it via QPST
Daniyal48 said:
I also tried removing modemst1 and modemdst2 but no luck....am I doing something wrong....what is the proper way to do it via QPST
Click to expand...
Click to collapse
Which mode is your device appearing as on your computer? Assume you're using below in QFIL?
Andrologic said:
Which mode is your device appearing as on your computer? Assume you're using below in QFIL?
Click to expand...
Click to collapse
Yes....it is detected as a modem SD845 something ...can the QFIL version be a problem?? I am using the lastest
Related
Here's my case:
I've got a LG G3 F400L (Korean LGU Variant), its on Marshmallow(6.0), and for all I know I used the Autorec program for Lollipop, and apparently got my bootloader corrupted; No led flashing, no display. But the Qualcomm 9008 serial port is shown on the device manager and I can use Boardiag to detect it. I know, irony and idiocy made this dilemma.
Diagnostics:
I've used Boardiag 2.99a by willcracker and yes I've checked "AP check" and "EMMC TEST" and both are tagged as "Pass", but when it comes to the "SDRAM TEST" it throws off an error indicating that there is a flash error on partition "boot" along with a 0x3000 and I can't progress beyond that, I've also tried to use the "Restore Device" option to revive it but still the later error still persists.
I've also tried Smart Boot Diagnostics but the problem is that my device's AP Chip doesn't exist on the current version of the tool.
What I would like to press on:
I would want to resolve this on my own and that no amount of suggesting on sending this to the service center would yield fruit. Please do understand, I would also like this to be a thread that can help me and other on resolving their corrupted bootloader units.
Please, can someone help me on my dilemma. Thank you very much. Any amount of help is appreciated.
Try using board diag with the battery unplugged.
Sent from my SM-G935T using Tapatalk
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
FeitX said:
Already tried that but still nothing works.
Current situation:
Alas, I've accessed fastboot and had wiped the boot partition, but now the USB is detected as "LGE AndroidNet USB Serial Port."
Click to expand...
Click to collapse
You need to short with a cable internet connection I do this last night and changes for Qalcomm USB in the same time...After that, you need to open BoarDiag and do the process. If you can´t enter in download mode, you need in BoarDiag pass the USERDATA
I follow this link: http://open-freax.fr/guide-unbrick-your-lg-g3/
Hi,
I accidently use wrong sbl3 file to unlock lumia and my lumia 525 is dead, it is not booting up and my pc can't even recognize it, I tried to use WDRT but nothing happened. WDRT can't detect it. Please help me...
A Hassan said:
Hi,
I accidently use wrong sbl3 file to unlock lumia and my lumia 525 is dead, it is not booting up and my pc can't even recognize it, I tried to use WDRT but nothing happened. WDRT can't detect it. Please help me...
Click to expand...
Click to collapse
You have to unbrick it using thor2
Search on http://forum.xda-developers.com/windows-phone-8/development
ngame said:
You have to unbrick it using thor2
Search on http://forum.xda-developers.com/windows-phone-8/development
Click to expand...
Click to collapse
download latest WDRT,Click on my device not detecting ,select your device ,download emergency files
after downloading emergency files,your device can be detected in dead state too, flash it if it detects
or go to command prompt type below code &change 525 vpl file path
cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
thor2 -mode vpl -vplfile "D:\downloaded535flashfiles\lumia535-vplname.vpl "
thor2 -mode rnd -bootnormalmode
Click to expand...
Click to collapse
Flash wrong sbl3 file
raghulive said:
download latest WDRT,Click on my device not detecting ,select your device ,download emergency files
after downloading emergency files,your device can be detected in dead state too, flash it if it detects
or go to command prompt type below code &change 525 vpl file path
Click to expand...
Click to collapse
This process shows this error, and no response yet
"THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT
THOR2 1.8.2.18 exited with error code 84003 (0x14823)"
A Hassan said:
This process shows this error, and no response yet
"THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT
THOR2 1.8.2.18 exited with error code 84003 (0x14823)"
Click to expand...
Click to collapse
does it vibrate while holding vol down+power?did you check cable/usb port changing?if it vibrate then sure it can flash easily
Flash wrong sbl3 file
raghulive said:
does it vibrate while holding vol down+power?did you check cable/usb port changing?if it vibrate then sure it can flash easily
Click to expand...
Click to collapse
No vibration while holding these both button together, cable , usb everything is all right but phone is still dead...
A Hassan said:
No vibration while holding these both button together, cable , usb everything is all right but phone is still dead...
Click to expand...
Click to collapse
charge your battery full and insert it
after downloading emergency files WDRT looks for device usb connection so make it perfect
plug/unplug pc usb cable several time with 1min time interval with all ports one by on
also check cable of bottom USB board to main board .
The trick to shortcut 2 pins on mainboard...? exist?
ngame said:
You have to unbrick it using thor2
Search on http://forum.xda-developers.com/windows-phone-8/development
Click to expand...
Click to collapse
Take the battery out, then plug it into computer via usb. WDRT should recognize it in emergency mode. About 3 seconds after it says 'flashing' insert battery. Or it might fail. Took me a few attempts on that one. WDRT should download the emergency files. Look in C:\ProgramData\Microsoft\Packages\RM-xxxx. X being the device name. emergency file is called 'emergency_flash_config.xml
Oh yeah, might need to enable 'hidden files' in Folder options. ProgramData a hidden folder
when my 925 went crazy i downloaded latest WDRT and tried..just got error all the time..then unstalled it and downloaded the NOKIA version of WDRT...dident work either..then i reinstalled the latest WDRT without unistall the nokia verion...WHEN it worked for me
Hi,
I searched a lot,but couldn't find a specific answer.
Is it possible to do QCN backup and restore using QPST successfully?Can anyone please confirm it?
or is it just not supported by QPST tool like nexus devices?
none?
Jongla said:
none?
Click to expand...
Click to collapse
You can use this guide here, to get the drivers and the QPST. Then maybe QPST will work, but I am not so sure.
http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
Here some more info
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Sturdymush said:
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Click to expand...
Click to collapse
more drivers here
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
---------- Post added at 10:40 AM ---------- Previous post was at 10:26 AM ----------
Sturdymush said:
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Click to expand...
Click to collapse
Can you try with QXDM instead of QPST ?
I would really appreciate.
cheers.
PS: this is a guide for OP2 (http://forum.xda-developers.com/showpost.php?p=65456106&postcount=16 )
to set it to diag mode dial
*#801# and then select the Engineering mode.
I used QXDM Pro 3.14.594 to get the QCN in xml format (more readable).
Good Luck
Sturdymush said:
The method above almost works, well at least for me. Unless I'm just doing something wrong. My phone shows in QPST now but it's stuck in a downloading state for some reason.
Click to expand...
Click to collapse
you have to find a way to put the phone in diagnostic mode. I think there is a combination of keys,
these are for OP2
http://mobilespecs.net/phone/codes/OnePlus/OnePlus_TWO_64GB.html
*#9090# � Diagnostic configuration
maybe it works
or with adb
setprop sys.usb.config diag,adb
this one for OPO
http://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
I tried using adb yesterday but after I do it I can't install the drivers
[/COLOR]
Sturdymush said:
I tried using adb yesterday but after I do it I can't install the drivers
Click to expand...
Click to collapse
Ok, found this...
It is from the OP3 forum, here http://forum.xda-developers.com/showpost.php?p=67470602&postcount=2
And it should work
If you switch a device into a hybrid mode like "diag,adb" it will dish out a new custom product id over the usb interface, one that combines both devices into one new one.
There are however no fitting diag drivers that match that product id.
If you want diag to work properly, switch your phone into single-diag mode by executing setprop sys.usb.config diag via a rooted terminal emulator from the phone itself, rather than doing it via an adb shell from a computer.
This will result in the proper diag product id being reported to your computer, allowing you to install the right driver.
As for the driver download, a simple google search will yield you the results.
Just search for "Qualcomm Diag Driver x64".
Edit: Oh one more thing... last time I checked I couldn't find a properly signed Diag driver for 64bit systems...
You will probably have to boot your computer smashing the F8 key repeatedly, and picking "disable driver signature enforcement" from the boot menu to temporarily disable the driver signature check, allowing you to install and use the Diag driver.
I have a LG G3 D855 I've been looking at for about a week now, it wont boot no matter what is flashed onto it. Tried as many guides as I could find but still nothing.
Anyone got any ideas?
Tried Flash tool with KDZ direct from LG, tried installing TWRP but it won't install, tried LG PC suit recovery and nothing. na-da.
jettonx said:
I have a LG G3 D855 I've been looking at for about a week now, it wont boot no matter what is flashed onto it. Tried as many guides as I could find but still nothing.
Anyone got any ideas?
Tried Flash tool with KDZ direct from LG, tried installing TWRP but it won't install, tried LG PC suit recovery and nothing. na-da.
Click to expand...
Click to collapse
Is it recognized in the device manager of your PC? If yes - what does it say?
*When I'm in download mode it shows up as "LGE Mobile USB composite device" under USB controllers.
startswithPendswithOOH said:
Is it recognized in the device manager of your PC? If yes - what does it say?
*When I'm in download mode it shows up as "LGE Mobile USB composite device" under USB controllers.
Click to expand...
Click to collapse
Yep that's exactly what this one shows up as.
I can boot into download and I can boot into stock recovery mode.
gyazo.com/1a09d74b4ae3a04d6587eb9096438ffc
jettonx said:
Yep that's exactly what this one shows up as.
I can boot into download and I can boot into stock recovery mode.
gyazo.com/1a09d74b4ae3a04d6587eb9096438ffc
Click to expand...
Click to collapse
Actually...it's not what it's showing up as. Under "Universal Serial Bus controllers" it should be listed, but yours is listed as LGE AndroidNet USB serial port(com 41) under "ports". That is looking like a soft brick. I had a similar problem occur when I unplugged a phone while it was flashing/upgrading. You'll need to TOT back to stock since KDZ has failed you. Scroll down to the TOT method... https://forum.xda-developers.com/showthread.php?t=2785089
I see you are on com41 - have you already tried TOT? If yes and it fails, what is the error?
*Also, you may need to uninstall any mobile device drivers and reinstall just the LG drivers for things to work right.
startswithPendswithOOH said:
Actually...it's not what it's showing up as. Under "Universal Serial Bus controllers" it should be listed, but yours is listed as LGE AndroidNet USB serial port(com 41) under "ports". That is looking like a soft brick. I had a similar problem occur when I unplugged a phone while it was flashing/upgrading. You'll need to TOT back to stock since KDZ has failed you. Scroll down to the TOT method... https://forum.xda-developers.com/showthread.php?t=2785089
I see you are on com41 - have you already tried TOT? If yes and it fails, what is the error?
*Also, you may need to uninstall any mobile device drivers and reinstall just the LG drivers for things to work right.
Click to expand...
Click to collapse
The TOT went on fine but it still won't boot, it's a strange one this phone..
Hello, everyone.
I have this moto G5 which power button doesn’t seem to work and it doesn’t let me enter fast boot mode (I think). Using adb in Linux, is there a way I can do it? I attached pictures of it when powering it on through USB and after pressing volume down.
Thank you in advance!
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
PhotonIce said:
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
Click to expand...
Click to collapse
I tried, but it didn’t work. The software, on windows (the Lenovo/motorola recovery tool) said it didn’t recognized it and asked to enter in fast boot, which takes me to what I said in my first post.
Haven't you entered fastboot in the second image?
My first answer would be yes, but whe recovery tool doesn’t recognize the phone on windows and it’s also not listed on Linux with the adb command, so my last answer is I’m really not sure.
try installing the correct drivers and checking that your cable does indeed support data transfer
PhotonIce said:
Clearly the software is corrupt. Try using the "Software restore tool" which it suggests to restore your device, then give it a go
Click to expand...
Click to collapse
Hello again.
I tried checking the cable, like you suggested, and then I was able to go a step further: the cell phone communicates with the computer. But I’ve got an error message from the restore tool (it’s in Portuguese) when I try to recover that, briefly, says my models name is all “0”, what doesn’t seem normal.
Any ideas about where I can go from here? Thank you!
did you say that your device is a motorola? why are you using a lenovo tool?
PhotonIce said:
did you say that your device is a motorola? why are you using a lenovo tool?
Click to expand...
Click to collapse
Leneovo own Motorola