Related
Hi guys,
This is all about developing the Focus S, since we are on our own on this one I thought id start the ball moving but it would be great if others can help, my first target is to try and download as much of the device as possible
Can I promise anything at all? nope
Have I achieved anything yet? well id say 1 step above doing nothing at all, if you can call that progress then yes, there is progress
Is it even possible to do anything? i dunno
Could i brick my device? possibly, i honestly don't know
in short, this is me blindly wondering in the dark with absolutely no direction what so ever!
So what have i done, well, i managed to get the Focus S talking to Qualcomms diagnostic utility, QPST and RevSkills CDMA Workshop
I cant get QXDM to install on Win 8 x64 and im not sure we need that one anyway
it is possible to edit stuff on the phone at a very low level, NOT OS level, it should be possible to download the various images on the phone, but ive yet to have any luck with that, it keeps coming up with "Arm9 fatal error"
ive been able to download and backup various phone settings but this is still outside of the OS#
I can play about with the EFS but there are several folders that i cant get in to yet
So far,both the samsung download mode and the ARM9 (?) download mode IS visible and installes as a com port, but there is no response on that port, i can only get a response within windows when i enable USB diag mode....
i decided not to link to the various tools ive mentioned here, i dont know the legalities of it all so use google, they are all easy to find.
Samsung studio 3 drivers
http://downloadcenter.samsung.com/c...813082717640_Samsung_USB_Driver_Installer.exe
Install it with compability for windows vista.
Samsung Focus info (note that most of this doesn't work, its for the older focus but some does)
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
Handy Diagnostic codes
*#7284# - USB Path control (select to change how your phone communicates with your computer)
*#197328640# - The Root Menu (seriously, don't get too cocky, you could bugger up your device)
Samsung USB Download mode
Turn off Device
hold the camera button and the Volume UP
Whilst holding those two push and hold the power button until it vibrates
Samsung Device Hard reset
Turn off Device
hold the camera button and the Volume Down
Whilst holding those two push and hold the power button until it vibrates
Follow on screen instructions
Enable Diagnostic mode and Connect to QPST or other GSM/CDMA software
Download and install the Samsung drivers above
open the diagnostic app and dial code *#7284#
Select Modem,USB Diag
Reboot
When you plug the phone in you should see a COM port install and appear in device manager
load QPST configuration
Click on the Ports Tab then Click add new port
Select your Phone com port
Click OK then select the phone from the list, hit enable
Click on start clients then you can play with a bunch of options
Please note that this is a serious piece of kit, its designed for low level editing, what I mean by that is that it couldn't care less about if it works or not after you finish playing, a couple of other software options to play with are CDMA tools and RevTools both have the potential to paperweight your phone!
NOTE: Zune will not connect and whilst connected to PC you may lose all GSM connectivity whilst connected as well.
Enable FTM (Factory Test Mode)
open Diagnostic app and dial code*#197328640#
select 6 (common)
Select 1 (FTM)
Select 1 (on)
Click return save (it doesn't always persist unless you do)
Hit Back until you back to the main menu then win key to Windows
REBOOT to enable
NOTE: You will lose ability to connect to GSM with this enabled, a reboot is required to enable it after its set and to deactivate it, ive not found a noticeable difference with this on
If im not wrong, WP uses arm v7.
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
tayfelix said:
If im not wrong, WP uses arm v7.
Click to expand...
Click to collapse
yes your right, but that's what it says, it reboots in to some sort of QC download mode, QPST is the waiting for it to talk to it which it doesn't do, it just sits there with this error message.
I have been able to backup the Important bits that make the phone work, and I have access to the EFS, I can change all sorts at a very low level but any time I try and download some of the various "partitions" it reboots to this special download mode. because we don't have any form of ROM I thought the first priority should be to see if we can make a backup of it, outside of MS encrypted zune backup I mean
the software is old so perhaps it doenst work with newer hardware, but then it does with android soooo.....
LudoGris said:
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
Click to expand...
Click to collapse
don't hold your breath, I still don't really know what im doing, consider this playing.....in a mine field
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
tayfelix said:
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
Click to expand...
Click to collapse
That depends what you mean by work, will the focus flash connect to various diagnostic tools? yes probably, will it be possible to download the ROM? maybe, beyond that I haven't got a clue
starting to run out of ideas, I think either the download mode via QPST is disabled or, and more likely, the driver isn't correct, when it enters the arm9 fatal error screen it is still using same driver, the same driver samsungs download mode uses, but both won't talk to QPST unless I enable diagnostic mode within windows phone OS, the prob with that is that it won't then allow access to the file systemSent from my fake Lumia 900 using XDA Windows Phone 7 App
It also have diagnostic tools .
tayfelix said:
It also have diagnostic tools .
Click to expand...
Click to collapse
be careful, you can bugger up your device!i will write a more detailed guide later
First things first, you will need to make sure you have the samsung diagnostic tool install
bring up the phone dialer and dial
##634#
you will now see a diagnostic app on your app list, run it and type in
*#7284#that will enable you to change the USB connection mode,select
Modem USB diag
OPTIONAL - Typing in the following code will bring up the diagnostic root menu
#197328640#you can find a full list Here Many of the codes on that list just run functions found in the root menu
Bare in mind that pissing around with some of the things in there will bring about a swift crappy end to your day!
plugging in your your phone at this point will install a Samsung COM driver
next download and install QPST on your computer, run the config part of that, it will ask you to select your phone, you will need to add a com port, it should then list your phone to connect to it
you can then edit the EFS, service/phone settings, download settings
you will need to know your SPC number, mine was already 0000000, there are ways of working out your number if leaving it all at zeros doesnt work.
use the service editor to read the phone settings, it will ask for your SPC, once loaded,you can save those settings to a file, very important ifyou screw something up
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
tayfelix said:
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
Click to expand...
Click to collapse
as reported in windows phone about screen, note that the Focus S and Omnia 7, has a firmware update that will stop any interop unlocking, i had it installed but it killed my battery life and my phone reception so i took it off, id suspect the bootldt vs will be different between devices, even though they were released at the same time
bootldr 6.5.16.0
firmware 2103.11.10.1 (not the Samsung update that breaks interop)
diagnostic 0923 (not the Samsung update that breaks interop)
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
tayfelix said:
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
Click to expand...
Click to collapse
I made a backup before I installed it
I think we can get an xap of my version of the diagnostic tools, but the firmware update also changes drivers an a few other things, those cant be changed, if we could send custom cabs to the device we are laughing, but we cant, to cab send requires the cab to be signed, and the device would need to have that certificate, which cant be put on whilst its all in use
:S don't think so as diagnostic tool is based on firmware I think.
tayfelix said:
:S don't think so as diagnostic tool is based on firmware I think.
Click to expand...
Click to collapse
try this, remove your existing diagnostic app and install this xap
How can u install a xap..
Is your device still unlocked? The Samsung update will stop you applying the unlock but if you had it already installed it will still work, if it is unlocked then use an cap deployed, my link to the wee guide details how to do it, if it's interop unlocked but you can't install an xap deplorer the use the xap deplorer included with the WP SDK
Sent from my Lumia 900 using XDA Windows Phone 7 App
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
tayfelix said:
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
Click to expand...
Click to collapse
well there isn't anyone working on unlocking it as far as I know, so if its going to happen then we need to do it ourselves.
Ive exhausted just about every avenue I can think of getting access to the device, ive been able to dump parts of the RAM but still not the ROM,
EFS is writable but I cant get in to the secure folders. The only way I can think of for getting the ROM is to get it working in one of the two download modes, both will not talk to anything tho, perhaps if I had the commands to copy the ROM I could just send them in the hope it will reply but it sure as hell isn't saying anything to the commands I have sent.
Hmmm. Must there be a exploit? Zzz there's are very little/no hackers having a focus s or a focus flash/omnia w. they all have 1st gen devices I think.
I've installed all kinds of motorola drivers including the one that the device manager from motorola website, still I cannot read the qc diag serial port. Does anyone have these drivers?! I'm working on sim unlocking the sprint moto x and I gotta be able to get into the modem and see what I'm dealing with. Get me usb serial access to issue QC commands and hopefully I'll be able to post instructions for simunlock and cricket/metropcs flash (that opens up pretty much every carrier except verizon for the sprint model). I wont know until I can qxdm to it, I wish I had a radiocomm version that supported the msm8960 but the version I have goes up through the 6x00 not even close. I still think I can get done what I need to do with qxdm.
Thanks in advance.
+1,did you find then?
thundercles said:
I've installed all kinds of motorola drivers including the one that the device manager from motorola website, still I cannot read the qc diag serial port. Does anyone have these drivers?! I'm working on sim unlocking the sprint moto x and I gotta be able to get into the modem and see what I'm dealing with. Get me usb serial access to issue QC commands and hopefully I'll be able to post instructions for simunlock and cricket/metropcs flash (that opens up pretty much every carrier except verizon for the sprint model). I wont know until I can qxdm to it, I wish I had a radiocomm version that supported the msm8960 but the version I have goes up through the 6x00 not even close. I still think I can get done what I need to do with qxdm.
Thanks in advance.
Click to expand...
Click to collapse
looks like you're booted into bp tools for those interfaces to be dectected, correct? i'm not sure whether or not the moto device manager has drivers for these interfaces as i always use the standalone drivers. here's a link to the latest available as of this posting:
http://batakang.com/ftp/?dir=devs/mhous33/drivers
whichever driver installer you use, the drivers have to be installed manually. iirc motorola qc diag interface is the only one you need to communicate with qpst/qxdm.
in device manager, right click on motorola qc diag interface > update driver software > browse my computer for driver software > let me pick from a list of device drivers on my computer > ports (com & lpt).
under manufacturer, select motorola.
under model, select motorola qc diag port.
click next, driver should be installed successfully.
looks like you're using windows 8, so you may have to temporarily disable driver signing for it to install.
hope this helps.
Q9Nap said:
looks like you're booted into bp tools for those interfaces to be dectected, correct? i'm not sure whether or not the moto device manager has drivers for these interfaces as i always use the standalone drivers. here's a link to the latest available as of this posting:
http://batakang.com/ftp/?dir=devs/mhous33/drivers
whichever driver installer you use, the drivers have to be installed manually. iirc motorola qc diag interface is the only one you need to communicate with qpst/qxdm.
in device manager, right click on motorola qc diag interface > update driver software > browse my computer for driver software > let me pick from a list of device drivers on my computer > ports (com & lpt).
under manufacturer, select motorola.
under model, select motorola qc diag port.
click next, driver should be installed successfully.
looks like you're using windows 8, so you may have to temporarily disable driver signing for it to install.
hope this helps.
Click to expand...
Click to collapse
Lmao I posted this same rant on facebook and a phone flashing friend did these things with team viewer and went ahead and helped me retrieve my MSL code as well. It is all coming down to the UICC unlock, this is what is holding back our ability to sim unlock the sprint version of this phone (because without the UICC unlock it wont read any other Sim cards anyways) I'm working on that right now but I have a headache so it will be later.
ok,please if you have sucefully unlock gsm i will love to pay you if you give me the way.
MSL code
thundercles said:
Lmao I posted this same rant on facebook and a phone flashing friend did these things with team viewer and went ahead and helped me retrieve my MSL code as well. It is all coming down to the UICC unlock, this is what is holding back our ability to sim unlock the sprint version of this phone (because without the UICC unlock it wont read any other Sim cards anyways) I'm working on that right now but I have a headache so it will be later.
Click to expand...
Click to collapse
Does this mean getting the MSL code is useless in unlocking the device for GSM use?
do you have that moto x drivers? i dont find it anywhere.. will you please reupload it some where.. Thanks.
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)
Hello,
I have a LM-V409N here. It has some Korean bloatware but worse than that, even though the phone is set to English, a lot of things are still in Korean. For example an available software update description is in Korean. Buttons in the phone app show Korean text, etc.
Can I flash a European firmware on to this model? Will that 'just work'?
I hope someone can help me with this.
Thank you,
Rooted? you won't get far otherwise. Had the same problem on my korean G5.
On a rooted device though, you can edit the build.prop locale to your native region to turn off the korean elements of the UI and obviously remove the bloat.
some of the bloat can be disabled even if uninstall isn't allowed. Carrier specific ones can't unfortunately.
Flashing wise, iirc that's a no go as it will break radio. No signal afterwards. At least that was the problem on the V35.
Thank you so much for your reply. This makes me worry a bit less
No I don't have it rooted (yet). I will go figure out how to do that for this phone model and then if I can't find out how to do the build.prop changes I will come back here to ask for help
Do you have any idea why WiFi HotSpot is not working properly? Laptops and other phones just don't see the SSID and when trying to setup a 5GHz hotspot, the slider hangs when you turn it on (turns gray and freezes) and you have to reboot the phone to get it enabled again. But it will only turn on when on 2.4GHz.
If I can get all the Korean stuff to disappear, flashing won't be necessary anymore So let me get to finding that out!
Let's first see if flashing fixes anything.
Thank you so much once again!
Edit: Come to think of it, when I turn on the phone it shows an SK Telecom animation and sound (some Korean carrier I guess) and I would like that removed as well..
I guess the only way to get that removed is to flash another firmware? Would you know a firmware version for this LM-V409N which is just 'LG original' without any carrier/provider customization?
Thank you!
Edit2: OK, I found out how I can flash a stock firmware using the LGUP tool. However, this fails at the beginning of the process because of an 'Initialize' error.
I suspect I need the device to be rooted before flashing..? I could find how to flash pretty easily, but how to root..?
Can anyone point me to a guide for rooting the V40?
Thanks!
No, you don't need root. Just search here on xda for crossflash word. In the g7 forum I have made an tutorial. You will need lg drivers, com port, lg up and common. DLL for v40. For g7 it works like a charm. Be sure to check and compare GSM bands from Korea to EU. For g7 they was the same.
Inerent said:
No, you don't need root. Just search here on xda for crossflash word. In the g7 forum I have made an tutorial. You will need lg drivers, com port, lg up and common. DLL for v40. For g7 it works like a charm. Be sure to check and compare GSM bands from Korea to EU. For g7 they was the same.
Click to expand...
Click to collapse
OK, did all that. LGUP starts up, detects my LM-V409N correctly.
I select the KDZ file, set it to UPGRADE and click START.
Now it gives me the error 'LGUP Framework must be 1.16'. I have 1.14 apparently and I can't find 1.16 anywhere.
I read something about "If you do have some knowledge to bypass the LGUP Version Check on this DLL, then You can sideload kdz firmware onto your LG V40 ThinQ with LGUP 1.14." on this site: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
But again, I can't find anything about how to bypass that version check.
I tried with LGUP_common.dll versions 1.9.39.7 and 1.0.39.10. Both same result (need 1.16).
Also tried with 0.0.3.23 but that one gives the "Initialize" error after clicking START.
Any other tips or tricks you can suggest?
Thank you,
AzzKickah said:
OK, did all that. LGUP starts up, detects my LM-V409N correctly.
I select the KDZ file, set it to UPGRADE and click START.
Now it gives me the error 'LGUP Framework must be 1.16'. I have 1.14 apparently and I can't find 1.16 anywhere.
I read something about "If you do have some knowledge to bypass the LGUP Version Check on this DLL, then You can sideload kdz firmware onto your LG V40 ThinQ with LGUP 1.14." on this site: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
But again, I can't find anything about how to bypass that version check.
I tried with LGUP_common.dll versions 1.9.39.7 and 1.0.39.10. Both same result (need 1.16).
Also tried with 0.0.3.23 but that one gives the "Initialize" error after clicking START.
Any other tips or tricks you can suggest?
Thank you,
Click to expand...
Click to collapse
Hello.
I told you to look in g7 forum for crossflash. You will need lg up 1.15 and follow the exact steps. Beware it may brick your device, so I'm not responsible.
Link here https://forum.xda-developers.com/lg...ash-oreo-pie-firmwares-lg-g7-g7-t3915303/amp/
Warning!!! Pay attention not to download the common. DLL from there as it is for lg g7. You must download for your v40. Also for your firmware. Also you will loose your data, so backup first if you have important files, sms, etc.
Inerent said:
Hello.
I told you to look in g7 forum for crossflash. You will need lg up 1.15 and follow the exact steps. Beware it may brick your device, so I'm not responsible.
Link here https://forum.xda-developers.com/lg...ash-oreo-pie-firmwares-lg-g7-g7-t3915303/amp/
Warning!!! Pay attention not to download the common. DLL from there as it is for lg g7. You must download for your v40. Also for your firmware. Also you will loose your data, so backup first if you have important files, sms, etc.
Click to expand...
Click to collapse
OK so for my clarification, this method is how to bypass the version check? (If yes, I will go try this).
Or is this a separate method? (If it is separate, I'm afraid to brick it and I will not try it).
Thank you so much for your help. It really is very much appreciated.
AzzKickah said:
OK so for my clarification, this method is how to bypass the version check? (If yes, I will go try this).
Or is this a separate method? (If it is separate, I'm afraid to brick it and I will not try it).
Thank you so much for your help. It really is very much appreciated.
Click to expand...
Click to collapse
Yes, this is for bypassing the obsolete lg up 1.14.
But 1.15 will not work if you open it, it will ask you for developer user and password. But there is a hack with using cmd line. Follow my steps.
I repeat again, if there is a working DLL for lg v40 and if 40 supports crossflashing (highly it does) then you're good to go. Don't forget to check what is your com port when your v40 is connected in download mode.
---------- Post added at 11:39 AM ---------- Previous post was at 11:33 AM ----------
If you're connected to a USB 3.0 port and have quality USB c cable, it should install it in less than 1 minute
---------- Post added at 11:47 AM ---------- Previous post was at 11:39 AM ----------
Here is a little tutorial for V40
Easy commands for this new LGUP v1.15.06
If using powershell from win10:
1. Install USB drivers and put V40 in download mode - connect it to USB cable then go and check your COM port in windows device manger
2. Open powershell from C:\Program Files (x86)\LG Electronics\LGUP (shift + right mouse) and type cmd and hit enter.
3. Type this command: lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "(path to your kdz firmware)"
Example: (if your phone is under com5 and your kdz is located in D:\ and has this name XXX.kdz)
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "D:\XXX.kdz"
Links:
LGUP new version - https://drive.google.com/file/d/1dJZ...jumm5mtKp/view
LGUP common.dll for V40 - you must download it.
Firmwares: https://lg-firmwares.com/
European firmwares for V40 - https://lg-firmwares.com/lg-lmv405ebw-firmwares/#tab=firmwares
[/COLOR]Here is a little tutorial for V40
Easy commands for this new LGUP v1.15.06
If using powershell from win10:
1. Install USB drivers and put V40 in download mode - connect it to USB cable then go and check your COM port in windows device manger
2. Open powershell from C:\Program Files (x86)\LG Electronics\LGUP (shift + right mouse) and type cmd and hit enter.
3. Type this command: lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "(path to your kdz firmware)"
Example: (if your phone is under com5 and your kdz is located in D:\ and has this name XXX.kdz)
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "D:\XXX.kdz"
Links:
LGUP new version - https://drive.google.com/file/d/1dJZ...jumm5mtKp/view
LGUP common.dll for V40 - you must download it.
Firmwares: https://lg-firmwares.com/
European firmwares for V40 - https://lg-firmwares.com/lg-lmv405ebw-firmwares/#tab=firmwares
Click to expand...
Click to collapse
It worked!! :laugh:
You are the best. THANK YOU for your help!
Damn that was scary to watch that percentage creep up towards 100%
AzzKickah said:
It worked!! :laugh:
You are the best. THANK YOU for your help!
Damn that was scary to watch that percentage creep up towards 100%
Click to expand...
Click to collapse
What dll did you used? and from where did you find the information that the dll is correct? please links. :angel:
Inerent said:
What dll did you used? and from where did you find the information that the dll is correct? please links. :angel:
Click to expand...
Click to collapse
DLL: https://drive.google.com/file/d/1qKRlOFVZMIanphD-jp6dxenCqkaZP2Zc/view?usp=sharing
Information/details: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
Firmware: https://lg-firmwares.com/lg-lmv409n-firmwares/#tab=firmwares
AzzKickah said:
DLL: https://drive.google.com/file/d/1qKRlOFVZMIanphD-jp6dxenCqkaZP2Zc/view?usp=sharing
Information/details: https://www.mylgphones.com/lgup-dll-for-lg-v40-thinq-version1-9-39-7.html
Firmware: https://lg-firmwares.com/lg-lmv409n-firmwares/#tab=firmwares
Click to expand...
Click to collapse
So you didn't flashed the European firmware?
Inerent said:
So you didn't flashed the European firmware?
Click to expand...
Click to collapse
No I didn't. Neocyke told me that radio wouldn't work that way so that would have been useless then. This is the post: https://forum.xda-developers.com/showpost.php?p=80177222&postcount=2
Or did he mean FM Radio......? Because I could live without FM Radio.
The one I did flash is still Korean, but it has no carrier customization. No cellular provider specific apps, no Korean company logo's at startup.
Only thing I noticed is that there still are Korean characters showing right below the numbers in the phone dialer app. But it also shows ABC, DEF, etc.
Oh, and a second clock showing Korean time on the lock screen :silly: which I can't find out how to turn off
AzzKickah said:
No I didn't. Neocyke told me that radio wouldn't work that way so that would have been useless then. This is the post: https://forum.xda-developers.com/showpost.php?p=80177222&postcount=2
Or did he mean FM Radio......? Because I could live without FM Radio.
The one I did flash is still Korean, but it has no carrier customization. No cellular provider specific apps, no Korean company logo's at startup.
Only thing I noticed is that there still are Korean characters showing right below the numbers in the phone dialer app. But it also shows ABC, DEF, etc.
Oh, and a second clock showing Korean time on the lock screen :silly: which I can't find out how to turn off
Click to expand...
Click to collapse
I also have that clock on my V50.
For me it worked with my g7+ Hong Kong international to European and also got volte amd vowifi.
Yes, he was referring to the GSM radio. So this will be risky.
Maybe you should not try. You can check if someone did it with G7....
I also have remembered that I cross flashed my G7 from HK to European, to Korean, back and fourth between them and all was fine.
---------- Post added at 06:16 PM ---------- Previous post was at 05:58 PM ----------
Maybe the V line from LG is risky about radios. Or maybe that was on V35. My point is that this is very risky an you should assume responsibility if flashing. Maybe it's better do not try it.
Inerent said:
I also have that clock on my V50.
For me it worked with my g7+ Hong Kong international to European and also got volte amd vowifi.
Yes, he was referring to the GSM radio. So this will be risky.
Maybe you should not try. You can check if someone did it with G7....
I also have remembered that I cross flashed my G7 from HK to European, to Korean, back and fourth between them and all was fine.
---------- Post added at 06:16 PM ---------- Previous post was at 05:58 PM ----------
Maybe the V line from LG is risky about radios. Or maybe that was on V35. My point is that this is very risky an you should assume responsibility if flashing. Maybe it's better do not try it.
Click to expand...
Click to collapse
You seem to contradict yourself, or do I misunderstand?
You can check if someone did it with G7....
I also have remembered that I cross flashed my G7 from HK to European, to Korean
Click to expand...
Click to collapse
Why check if someone did it if you already did?
I will see how it goes with this firmware for a week or two. If it is all fine, I'll leave it like this.
I don't suspect it will brick the phone though if I flash a European firmware.. As long as you can get into Download-mode, there is not much to worry about I think
AzzKickah said:
You seem to contradict yourself, or do I misunderstand?
Yes, I am also confused.
Why check if someone did it if you already did?
I didn't do it from Korean to European.
I will see how it goes with this firmware for a week or two. If it is all fine, I'll leave it like this.
I don't suspect it will brick the phone though if I flash a European firmware.. As long as you can get into Download-mode, there is not much to worry about I think
For this I was confused. I do believe 50% that it can be done without problems.
Click to expand...
Click to collapse
Anyway, the benefits for European are many. Volte, vowifi, less bloatware, faster speed.
Half of me is screaming to DO IT, while the other half is paranoic!
Inerent said:
Anyway, the benefits for European are many. Volte, vowifi, less bloatware, faster speed.
Click to expand...
Click to collapse
Faster speed..? Please elaborate.
It shows LTE in the status bar though. But I don't know if that is VoLTE.
Now you're making me doubt if I should try a European firmware....
Half of me is screaming to DO IT, while the other half is paranoic!
Click to expand...
Click to collapse
I'm feeling exactly the same right now :laugh:
AzzKickah said:
Faster speed..? Please elaborate.
It shows LTE in the status bar though. But I don't know if that is VoLTE.
Now you're making me doubt if I should try a European firmware....
Click to expand...
Click to collapse
Yes, for my G7 it was faster speeds. Better battery life also.
Inerent said:
Yes, for my G7 it was faster speeds. Better battery life also.
Click to expand...
Click to collapse
What do you think, would this be a good one to try?
V405EBW20a_00_OPEN_EU_DS_0524.kdz
LM-V405EBW...? On my LM-V409N, would that go..?
AzzKickah said:
What do you think, would this be a good one to try?
V405EBW20a_00_OPEN_EU_DS_0524.kdz
LM-V405EBW...? On my LM-V409N, would that go..?
Click to expand...
Click to collapse
I'll search what country has better laws regarding government spying on people. And that firmware I'll choose. Maybe it's the UK, I know that it has forbidden StingRays. Also Deutschland seems OK.
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
77an said:
Hi, possible remove simlock after crossflash? Thanks.
P.S.
To remove message "WARNING!
Current version is not available for user. Can't find matched carrier......"
You must have root and edit file cust_path_mapping.cfg
Click to expand...
Click to collapse
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
abokamel said:
thank you so much, i overcome it by crossflashing the latest EU Android 10.
and, about sim lock, it can't be done with cross flashing.
Click to expand...
Click to collapse
Can you share the rom that you use?
Also, were you root?
oscarillo said:
Can you share the rom that you use?
Also, were you root?
Click to expand...
Click to collapse
no, it's stock, not rooted.
the current rom i use now is here
abokamel said:
no, it's stock, not rooted.
the current rom i use now is here
Click to expand...
Click to collapse
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
oscarillo said:
Thanks a lot for your reply.
One more question.
Did you do a Refurbish or Upgrade option?
Click to expand...
Click to collapse
used the command line, i think it's making refurbish
This is a bit of an older thread, but just recently did the same crossflash from pie on att device to korean open Q.
Decided on the KR instead of EBW because KR, I thought, had more of the t-mo LTE bands I needed. Unfortunately, the different sites with firmware specs aren't always accurate (which LTE bands supported). One site has EBW supporting every LTE band of every LG phone! Def inaccurate.
So I tested both EBW and KR Q versions. Use LTE Discovery (from playstore) to view LTE bands in your current location. One thing to note about that, the LTE bands it shows u are going to be the nearest towers it's using. Which means that another tower, a little farther away, won't show up.
So to verify a particular band, that you think the phone might be capable of, but you aren't sure, you have to go into the svc menu and select 'field test' and enable only that LTE band you're searching for. Then use LTE Discovery and see if it's connected with that band. If it isn't connected with it (usually it will default to a 3G band if that one u selected isn't available), that means 2 things; 1) either that band isn't used in your area 2) Your device doesn't support that band (or both 1 and 2).
But in my case, I know band 71 works in my area (from previous testing), but I have to select enable for only that band for it to show up, because other nearby towers with band 66 will 'drown it out'.
Thus, the point here, the KR firmware Band 71 **DOES WORK**. And, btw, no site indicates it included in supported bands. The following screenshot shows it connected to 71 and the KR 409 at the bottom.
Cheers
abokamel said:
Hello all, been a little while with LG V40 as my second device, and loved it so much but tried to follow the crossflash procedures as mentioned here:
https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and I succeeded with it, only few notes wanted to share as experience/question about them:
- wifi, 3G and 4G are working as it should and no other problem found.
1. after flashing, phone booted successfully to Android 10, giving strange error message :
"WARNING!
Current version is not available for user. Can't find matched carrier. Check NT-Code: 310410310150 310170,311180,310560,310030,3 10280,310950,313100,312670: FF,FF,FF,FF,FF,FF,FF,FF,FF,FF
2. there's no SN for the phone in the settings!
- attached some screenshots for errors, looking forward to seeing some feedback or help if possible with how to fix those problems.
thanks in advance for all for such great efforts done here.
Click to expand...
Click to collapse
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
<snip brevity>
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
AsItLies said:
Wow thanks for that. First I've seen this idea to fix that issue. Other methods didn't work. Will try soon.
There are some other values you can change in cust.prop that can help also. Get's rid of most of the KR language in unexpected places. Will jot them down and add them here shortly.
cheers
Click to expand...
Click to collapse
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
advancedtekniqs said:
I've only been using this rom for about 6 hours. I haven't really noticed any KR except on the phone dialer. Doesn't really bother me, but if you have a way to set that to ENG, I'd like to know as well.
Click to expand...
Click to collapse
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
advancedtekniqs said:
Just bought an unlocked AT&T V405UA I'm running on T Mobile. I've spent the last two days trying flashing and reflashing different roms and trying to root my phone and ran into the NT code errors as well. I'm now finally running V409NO30d_00_OPEN_KR_OP_0716 with Magisk root and no NT code error. Here's how I got rid of the NT code error.
You need to have root access to so you can open your /oem/OP/cust_path_mapping.cfg and a hex editor. I use HxD.
Write down the number you have in the beginning, in my case "FFFFFF,60"
Reboot into 9008, open QFil and backup your FTM by choosing "READ" option
File will be stored at C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_9
Rename file to FTM_original.bin and open in HxD
Press ctrl + G to go to offset 14000
and replace first section with number you wrote down from cust_path_mapping earlier while deleting everything after
Also, if you're missing a serial number you can add that in as well, located at offset 12000 in the FTM file
Replace the red FFFFFFFFFFFFFF with your serial #
Once done, hit "SAVE AS" so you have a backup of the original if things go wrong and rename to FTM_fixed.bin
Flash FTM_fixed.bin in QFil and reboot. Should be no more error.
Click to expand...
Click to collapse
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
AsItLies said:
Yes u need to change the cust.prop in OP. Change the target region country to US (from KR) and same for target country. Change language prop to en_US.
Additionally, change featureset prop to OPENUS from OPENKR.
these changes disable most KR elements in firmware, most noticeably dual clock and call recording in dialer. They **may** also enable volte if supported by carrier.
This is from nice guy Neo on tele group who's played with this much more than I have
Cheers
Oh yeah, lol, just remembered, the main reason I was asking for the info above was to get the 'field test' selection (so you can select LTE bands) in the SVC Menu from dialer. By default, it doesn't show up, but above changes fixes that also.
Click to expand...
Click to collapse
that's terrific and brilliant to be honest! thank you so much for information you shared.
So, just found something additional that works on open 409N. The 'buffer fix' can be a bit of a pain. Tried a magisk module supposedly for v40 Q but that didn't work. So did what I've done before and just copy the .so fix to the appropriate directory, but that didn't work, even the oem camera stopped working after that.
So, even though this says it's for 'custom roms' tried it, and boom, works in magisk and does what's needed to fix buffer.
cheers
abokamel said:
thank you so much for sharing such detailed fix for that strange problem., as a work around, I managed to flash OPEN US kdz, then reflashed the open KR, then it's gone now, but i can't find mt phone's serial number when showing it on settings.
thanks again for such amazing tutorial. keep up
Click to expand...
Click to collapse
Try this website to find your seriel# by IMEI
So, interesting updates, for anyone using this Rom.
I went back to my AT&T rom, android 9. Then, just a few hours later... decided to go back to KR Open Don't ask, it's too confusing
But, the point, this time, when flashing the KR rom, I did part DL, and then after booting did Refurbish. Had read on tele that doing that fixes some of the issues crossflashing causes. Sure enough, my NT-code issue went away (couldn't fix that even with hexedit of ftm)!
So, that was cool. But now, my S/N disappeared! IMEI was still okay though. So tried the hexedit ftm and added S/N, boom, now it's fine also. But the funny thing was, with the refurbish and no NT-code problem, I looked at what was in the newer ftm at that address, and it had nothing, no info at that address at all.
One thing to be aware of, attesting to why this is difficult to deal with, these values (IMEI, S/N - and others) get propagated from one partition to another, I don't know the chain of events or criteria involved, but it adds to the difficulty of trying to fix issues. Which specific place it looks for something is confusing also, and if it's doing compares of 2 or more places is a mystery.
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
AsItLies said:
But anyway, do a Part DL to crossflash, then do a Refurb and it appears to fix some of the issues.
cheers
Click to expand...
Click to collapse
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
fireblade20 said:
Awesome work, fellas!
What program and files do you all have success with during the flashing? Perhaps share a link to it?
Also, is a serial number necessary? For using the phone and having service? Seems you guys are taking the blank serial number very seriously. Thanks!
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
So for an old sprint v40 running oreo, Just crossflash to the korean Q rom via partition DL, then again, with Refurb option? Or swap between different roms? Haven't done any crossflashing yet..hoping to avoid errors. Serial number loss won't stop the phone from working, right?
Click to expand...
Click to collapse
Mine is an AT&T, but afaik, Sprint should be the same. Yes, do the part DL, let it reboot as normal, then shut off and do refurb. Is S/N a big deal? no, everything works, and the S/N is still in the phone, just not displaying properly. It's an individual thing how much effort you put into fixing that. Some people have lost either / or IMEI or dual IMEI (some roms have that), when cross flashing. That's a problem because they get no cell signal, but that's on a different rom.
Look in this thread for how to LGUP / crossflash.
cheers
Thanks man!