I cross-flashed my v405ua (ATT) to the V405EBW30b_00_OPEN_EU_DS_OP_0806.kdz in an effort to get rid of the start-up error (current version) but the error still remains. Now I'm unable to flash back or to any other Kdz file, I get this notice Not support cross model download. It's not the start up error that concerns me, it's that I can not flash any other variant. I got the start up error after flashing from pie to Android Q (error: Current version not available for user. can't find matched carrier)
What can I do to fix this not being able to flash another Kdz file? Any ideas?
Gabriel51 said:
I cross-flashed my v405ua (ATT) to the V405EBW30b_00_OPEN_EU_DS_OP_0806.kdz in an effort to get rid of the start-up error (current version) but the error still remains. Now I'm unable to flash back or to any other Kdz file, I get this notice Not support cross model download. It's not the start up error that concerns me, it's that I can not flash any other variant. I got the start up error after flashing from pie to Android Q (error: Current version not available for user. can't find matched carrier)
What can I do to fix this not being able to flash another Kdz file? Any ideas?
Click to expand...
Click to collapse
Yes, to do a crossflash, u need the 1.14 dll version of patched lgup. U probably have that as you've already done a crossflash. To flash back, u need the patched lgup with dll 1.16. It's newer and recognizes the newer rom u crossflashed to.
The other issue u mention, the error on startup. I've found that if I crossflash (partition dl) to the rom I want, let it finish (which means it reboots), then shut it off and use lgup to do a 'refurbish' with the exact same rom u crossflashed to, then u won't get the message.
It sounds kind of convoluted, I know. But it seems the 'refurbish' propagates some of the values from partition to partition, where the part dl does not.
cheers
Yes I have been using patched 1.14, I'm looking for patched 1.16 now. Thanks
The EBW30b works well, I will try the method you mentioned to get rid of the start up error. (If I understand it correctly)
I cannot find patched lgup with dll 1.16. anywhere?
I did fine the patched 1.16 however I still get the cross flash error "CrossDL"
Gabriel51 said:
I did fine the patched 1.16 however I still get the cross flash error "CrossDL"
Click to expand...
Click to collapse
hmmmm, try doing it with the 1.14 version, choose part D/L and select everything but the ftm partition. Then do a refurbish with same kdz. See if that works.
I tried every option with the patched 1.14 version as well however I selected all items with the D/L option. Will omitting ftm be that much different?...
It seems no matter what I do with any lgup file it gets to 4% and then gives me the crossDL error. I wish it would just ignore what ever version I'm using. Thanks
Gabriel51 said:
I tried every option with the patched 1.14 version as well however I selected all items with the D/L option. Will omitting ftm be that much different?...
It seems no matter what I do with any lgup file it gets to 4% and then gives me the crossDL error. I wish it would just ignore what ever version I'm using. Thanks
Click to expand...
Click to collapse
Here's a thread, and another one to look in for a version of 1.14 that should work. In this thread there's talk about the start up error.
Should have mentioned earlier, the startup error doesn't hurt anything, and you only see it briefly after rebooting the phone. Others have just lived with it.
But, as said, it's the part d/l and then do a refurbish that gets rid of it, so check the other threads to find a version that will work. The ftm exclusion isn't necessarily critical, but some have lost their imei / and or serial due to cross flash and excluding ftm usually avoids that.
hopefully you've read the threads about doing this prior, as they do suggest to backup your boot, abl, laf, ftm, fsg, modem, modemst1 and modemst2 partitions first.
cheers
One of those options I had already tried but no success until about an hour ago.
https://mylgphones.com/how-to-flash-stock-pie-kdz-firmware-on-lg-v40-thinq-with-lgup.html?amp
These instructions got me where I needed to be with ease. It seems that some KDZ files cross flash easy but cross flashing from them is difficult as I have tried everything from everywhere.
I appreciate you effort to help.
====================================================
Attachment contains process
Related
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Cor-master said:
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes I have tried a different sim card. I don't believe thats the issue though being that it worked with the same sim after I let the phone sit overnight. From reading about others experience, it doesn't seem that the sim is the issue but more the baseband version and imei information missing.
centro7710 said:
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Click to expand...
Click to collapse
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
Click to expand...
Click to collapse
I found the download link, but the website says they're updating their drives, so who knows how much longer that will take.
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
centro7710 said:
I tried finding a download link for the AIO kit on the link provided, but I must be blind?
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
Click to expand...
Click to collapse
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
centro7710 said:
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
Click to expand...
Click to collapse
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
centro7710 said:
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
Click to expand...
Click to collapse
And I have a question, if the radio/baseband files are included in the RUU flash, what is happening as to why it is not being reflashed, or if it is being reflashed, why it is disabling the mobile network and providing an Unknown version to Baseband and clearing the IMEI number?
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Here's where I am:
I successfully unlocked my bootloader, downgraded to GB, rooted. Tried to gain root access through adb terminal but it was not working properly.
I relocked my bootloader. Installed the ICS RUU AT&T ROM update. Unlocked my bootloader, rooted.
I see the commands you ran in your previous post. I am also receiving the same message of N/A when running the getprop ro.baseband
I tried the second command setprop ro.baseband 3.26.5XXX and then restarted the phone. I have tried it as posted, and also with swapping out the version that is located in my android-info.txt file: 3.26.502.56
Still no luck with setting the baseband version. IMEI still is cleared out.
Am I doing something wrong?
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
Click to expand...
Click to collapse
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
ayulatins said:
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
Click to expand...
Click to collapse
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it.
centro7710 said:
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it, as is, on ebay instead to get a few bucks out of it and getting a new phone.
Click to expand...
Click to collapse
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
ayulatins said:
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
Click to expand...
Click to collapse
Exactly. It was my sister's phone. The sh*tty thing is we bought two off of ebay at the same time, 1 for me, 1 for her. Well, her phone was not in the box (either never shipped or stolen) so I had to file a claim through eBay which took 3 weeks to get the money back. Meanwhile, I gave her my phone (which is the phone in reference) to use instead. I bought her an iPhone instead now, along with purchasing one myself. I loved Android, but the bugs and fragmentation is getting too much for me to handle.
Dude, if you don't have an IMEI showing up, something is WAY wrong. That goes beyone the RIL not working... The RIL is probably fine. If your phone doesn't have an IMEI somehow, the cell towers are NOT, NO WAY, NEVER EVER going to register your phone on their network. You can put a billion SIM cards in there, or flash a billion stock ROMS, and if you don't have an IMEI, you will never be able to connect.
Something is probably corrupt or broken in your firmware or the hardware itself. I think your device is probably screwed.
My advice, is follow the steps to put your phone back to stock (including changing the bootloader message back to **LOCKED** and S-ON), and get it back to the phone company. They will be able to tell something is boned on the phone right away since it isn't displaying an IMEI.
Sorry to be the bearer of bad news and for your many wasted hours... But on the plus side, you now know a LOT about flashing and how your phone works now
Good luck with everything man! Hope they get you up and running soon!
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
anyone got the Radio.img?
inick73376 said:
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
Click to expand...
Click to collapse
That's weird..you try creating the apns again? I don't see how a factory reset would do that. Try toggling airplane mode too
Sent from my De-Sensed HTC Vivid using xda premium
I am currently having the same issues right now, it works if i leave the phone off for 1 hr it will work until i reboot then its down again, tried every thing possible, airplane mode will crash, reflashing the radios from gb and ics does nothing, setprop does nothing really. from this point it feels like a hardware issue.
sorry to revive an old thread, i just wanted to know if anyone came across this issue and had it fixed
i will get a log to see if there is errors showing up
Return it.
Sent from my HTC Holiday using Tapatalk 2
Hi
I have gone through the forums and can't seem to find solution for my problem with my Optimus L90 phone.
I have recently flashed the CM13 on my phone without any errors but below are the issues that I am facing
1. No cellular network signal after inserting SIM card.
2. I read in a different forum that this could happen due to using a wrong version of TWRP, so installed a newer version 2.8.7.0 but things worse.
3. Now I am not able to boot into recovery mode and phone just stays idle with the LG logo screen and few commands appearing like fastboot_iniy() and udc_start().
4. I have tried hard reset and soft reset and both are not successful.
5. I cannot root my phone either. Tried all ways like towelroot, purpledrake, lg root by avicoh etc but in vain
Now my phone, even though has a latest CM version I cannot use it for anything else.
Any help is greatly appreciated.
No SIM is hardly related to TWRP, probably you needed a different bootstack (there is a thread about it).
On CM you don't need anything to root, it's already rooted just not visible to common users, you need to activate Developer Options (it's also explained elsewhere)
Finally, if you cannot reach recovery but still can boot CM13 simply use adb, Flashfy or Hashr to flash another version or TWRP. 2.8.7 is kinda old and not recommended for Marshmallow, you can try 3.0.2 by SlimShady or DarkBlue version from shoxxy's thread.
Thanks for the reply, let me try options you have specified and get back if I am still facing issues
hvramanan said:
Thanks for the reply, let me try options you have specified and get back if I am still facing issues
Click to expand...
Click to collapse
I was able to unblock my phone finally and loaded the stock ROM but the phone is still isn't recognizing cellular network . I am on T-MOBILE. I have tried to insert different SIM, turned off wifi calling but still the phone is not catching any cellular network.
[lfom]: you indicated earlier that a different bootstack might be needed. I am not that knowledgeable about bootstack so can you help me through this or point me to different thread where users might have a similar issue.
Sorry, I meant to say unbrick above
Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
lfom said:
Everything one needs or wants to know about bootstack is here:
http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632
Click to expand...
Click to collapse
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.
hvramanan said:
Hi,
I followed the steps mention in the above thread to change the bootstack and was able to complete it without any issues, however the problem still persists and my phone is not recognizing the SIM and does not catch the cellular network.
Previously I used to use this phone with my t-mobile number and after I took a new phone haven't been using it for sometime. I want to sell this phone and was trying to ensure that it works fine and thats when I saw that the phone is not catching any cellular networks.
Please help. Let me know if you need any other details to better diagonize the problem.
Click to expand...
Click to collapse
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.
lfom said:
You didn't say what model you have, maybe you flashed the wrong bootstack for your model (hardware version)? Be very careful, you can hart brick your device, and if it's a D415 it's very hard to unbrick. I'd suggest that first you make sure what model you have by removing the battery and looking in the label below, it says what model you have. Then, use LG Flash Tool to flash stock ROM (KDZ) to latest KitKat, then flash Lollipop or use OTA to update to latest version. The only requirements are that you make sure what model you have and flash the corresponding version, and the phone is still able to enter download mode.
Click to expand...
Click to collapse
[lfom]: thank you for responding. My phone model is LG-D415 . Actually my phone was bricked but I was able to get into download mode and then I used the L90 Hardbrick tool to flash stock ROM (KDZ) to latest kitkat like you have specified above. Then with the OTA update I was able update it to latest lollipop. Then I followed this forum below to to change the bootstack to KK 10C version as the issue specified in the below thread was similar to mine.
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-12-lg-l90-t3049512/page235
Image of the label inside my phone attached.
Do you think I should have used the LG flash tool to flash stock ROM. Should I repeat the steps with the LG flash tool ?
Thank you again for helping me on this.
Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...
lfom said:
Do you see your IMEI in the about phone page? Does it match the one in the label? Maybe when you bricked you've lost the phone's IMEI, and you can't get it back just flashing ROM...
Click to expand...
Click to collapse
Yes I checked and it matches. There two fields IMEI which has the number and then there is another field which says IMEI SV and it has a value of 02 in it.
Hello All,
November update... It took a whole time to get my phone booting again but I don't have SIM or WIFI anymore.
I think my IMEI's are gone, even as MAC for WIFI.
I tried recovery image (that's what solved the boot problem).
I took backups but some parts seems to be corrupted so I can't recover from there.
Does someone have the (x)qcn available for flashing over QPST (or even over TWRP to change afterwards over QPST)?
I found different versions online but I think it's checked against model number; mine is: M1804D2SG (SI doesn't work)
Yes... I will change your IMEI!
Thanks!
honda4life1 said:
Hello All,
November update... It took a whole time to get my phone booting again but I don't have SIM or WIFI anymore.
I think my IMEI's are gone, even as MAC for WIFI.
I tried recovery image (that's what solved the boot problem).
I took backups but some parts seems to be corrupted so I can't recover from there.
Does someone have the (x)qcn available for flashing over QPST (or even over TWRP to change afterwards over QPST)?
I found different versions online but I think it's checked against model number; mine is: M1804D2SG (SI doesn't work)
Yes... I will change your IMEI!
Thanks!
Click to expand...
Click to collapse
Did you try to flash older build of stock rom?
Flash via MiFlash Tool, that worked for me
MiFlash tried,
I tried most recent version that was available, but yes that's an older version.
The corrupted data isn't even in the recovery rom.
https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885 I saw a few people on telgram that fixed wifi and sim with flashing persist partition.
mariosenta said:
https://forum.xda-developers.com/mi-a2/how-to/how-to-fix-sensors-camera-stock-pie-10-t3914885 I saw a few people on telgram that fixed wifi and sim with flashing persist partition.
Click to expand...
Click to collapse
Does not work unfortunately, just tried. In that topic it's more about sensors etc. not working.
Try flashing global firmware via twrp.
Reven jeremiah said:
Try flashing global firmware via twrp.
Click to expand...
Click to collapse
Also tried without errors but problem not solved.
Please someone upload.
My phone is still bricked :crying:
How may I help you? Give me instructions. Also specifically tell me how to remove my original Imei in that file. I'll then upload the files.
I tried flashing a sea region firmware but when I finally boot it up, the signal bar shows nothing. Everything else works as it should do. Another weird thing is the netword mode is stuck on "22".
Need more information to help you. What region is sea region and did you mean network stuck in 2g? Network mode is either Global or LTE/CDMA or LTE/GSM/UMTS. If I remember correctly from the one time i wiped the modem and IMEI number from a phone, it did that. Did you accidentally do 'ChipErase' in LGUP? Please provide more information, may be a screenshot to get help. Thanks.
Android# said:
Need more information to help you. What region is sea region and did you mean network stuck in 2g? Network mode is either Global or LTE/CDMA or LTE/GSM/UMTS. If I remember correctly from the one time i wiped the modem and IMEI number from a phone, it did that. Did you accidentally do 'ChipErase' in LGUP? Please provide more information, may be a screenshot to get help. Thanks.
Click to expand...
Click to collapse
I used a lgup cmd to crossflash.
The mobile radio power is off, I cant seem to turn it on. It just reset after I leave the window.
ultoramansaga said:
I used a lgup cmd to crossflash.
The mobile radio power is off, I cant seem to turn it on. It just reset after I leave the window.
Click to expand...
Click to collapse
Make sure you are using most compatible LGUP, the Dev patched dual LGUP from this post has never failed me, download it at bottom of post# 168 and don't forget to hit the thanks button for Chazzmatt and other contributors:
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
Also, make sure you have the right KDZ for your phone, what was the phone's original model number and which KDZ did you flash to it? Make sure you use 'Partition DL' in LGUP.
Did you cross-flash by jumping from Oreo to Sea region Pie? I have read that jumping straight to Pie like that can cause issues. First try to fix by using 'Partition DL' in LGUP as i just mentioned, if that doesn't work, download your original model Oreo, reflash that using 'Refurbish' or 'Partition DL', then download and cross-flash to Sea region Oreo using 'Upgrade' option in LGUP, from there try flashing Sea region Pie using 'Upgrade' option.
Android# said:
Make sure you are using most compatible LGUP, the Dev patched dual LGUP from this post has never failed me, download it at bottom of post# 168 and don't forget to hit the thanks button for Chazzmatt and other contributors:
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
Also, make sure you have the right KDZ for your phone, what was the phone's original model number and which KDZ did you flash to it? Make sure you use 'Partition DL' in LGUP.
Did you cross-flash by jumping from Oreo to Sea region Pie? I have read that jumping straight to Pie like that can cause issues. First try to fix by using 'Partition DL' in LGUP as i just mentioned, if that doesn't work, download your original model Oreo, reflash that using 'Refurbish' or 'Partition DL', then download and cross-flash to Sea region Oreo using 'Upgrade' option in LGUP, from there try flashing Sea region Pie using 'Upgrade' option.
Click to expand...
Click to collapse
How do you use partition dll? I don't know which partition to install
My model number: LMV405EBW (From HK to SG)
ultoramansaga said:
How do you use partition dll? I don't know which partition to install
My model number: LMV405EBW (From HK to SG)
Click to expand...
Click to collapse
'Partition DL' is a flashing option in LGUP. When you pick this option and it starts flashing, pick 'Select All' option in the new window that opens.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Android# said:
'Partition DL' is a flashing option in LGUP. When you pick this option and it starts flashing, pick 'Select All' option in the new window that opens.
Click to expand...
Click to collapse
First try flash Pie (Sea region firmware that you already downloaded) using 'Partition DL' option in LGUP. That should work, if that doesn't work:
Download and flash Oreo (LM405EBW version firmware) using 'Partition DL', set up the phone, enable developer options, then download and cross-flash Oreo (Sea region firmware) using 'Upgrade' option in LGUP, then try 'Upgrade' again to flash latest Pie for Sea region.
---------- Post added at 02:26 PM ---------- Previous post was at 02:14 PM ----------
Did you download the Sea region KDZ file from LGFirmwares website? It seems it is not a complete KDZ, it is probably an update file as it is only 340MB and a normal KDZ for LG V40 is around 4GB. If nothing above works, you need to download and flash Pie for LM405EBW (original software you had on this phone) using the 'Partition DL' option. Then flash the Sea region update KDZ using 'Upgrade' option.
Android# said:
'Partition DL' is a flashing option in LGUP. When you pick this option and it starts flashing, pick 'Select All' option in the new window that opens.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
First try flash Pie (Sea region firmware that you already downloaded) using 'Partition DL' option in LGUP. That should work, if that doesn't work:
Download and flash Oreo (LM405EBW version firmware) using 'Partition DL', set up the phone, enable developer options, then download and cross-flash Oreo (Sea region firmware) using 'Upgrade' option in LGUP, then try 'Upgrade' again to flash latest Pie for Sea region.
---------- Post added at 02:26 PM ---------- Previous post was at 02:14 PM ----------
Did you download the Sea region KDZ file from LGFirmwares website? It seems it is not a complete KDZ, it is probably an update file as it is only 340MB and a normal KDZ for LG V40 is around 4GB. If nothing above works, you need to download and flash Pie for LM405EBW (original software you had on this phone) using the 'Partition DL' option. Then flash the Sea region update KDZ using 'Upgrade' option.
Click to expand...
Click to collapse
I followed your instruction but it created a whole new problem with that being the wifi is now not operational, which means that getting through the setup is now impossible
ultoramansaga said:
I followed your instruction but it created a whole new problem with that being the wifi is now not operational, which means that getting through the setup is now impossible
Click to expand...
Click to collapse
If you can't finish setup no worries, just turn phone off. Then hold volume up button and plug in the USB cable to enter download mode and you can use LGUP to flash again. But, make sure you flash a full KDZ as I suspect you are flashing partial file and having all these problems. First recover from these errors then worry about flashing Sea region. go to LGFirmwares website, download a full 4GB KDZ for LM405EBW model. I feel that you didn't download full KDZ since last post because LGFirmwares website is very very slow and it takes many hours to download a full KDZ...
Edit: And whatever you do, do not use any options in LGUP that you don't know about, especially the 'ChipErase' option, it will permanently break/brick your phone. Once you flash a full KDZ and run setup and if still have issues, please go into settings, 'System', 'About Phone', and 'Status' and do you see your IMEI number shown or not? If it is not showing you may have used 'ChipErase' and there is no easy way to recover from that.
Android# said:
Make sure you are using most compatible LGUP, the Dev patched dual LGUP from this post has never failed me, download it at bottom of post# 168 and don't forget to hit the thanks button for Chazzmatt and other contributors:
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
Also, make sure you have the right KDZ for your phone, what was the phone's original model number and which KDZ did you flash to it? Make sure you use 'Partition DL' in LGUP.
Did you cross-flash by jumping from Oreo to Sea region Pie? I have read that jumping straight to Pie like that can cause issues. First try to fix by using 'Partition DL' in LGUP as i just mentioned, if that doesn't work, download your original model Oreo, reflash that using 'Refurbish' or 'Partition DL', then download and cross-flash to Sea region Oreo using 'Upgrade' option in LGUP, from there try flashing Sea region Pie using 'Upgrade' option.
Click to expand...
Click to collapse
Thank you very much. You helped me solve my problem !!!!:good::good::good::highfive:
Android# said:
If you can't finish setup no worries, just turn phone off. Then hold volume up button and plug in the USB cable to enter download mode and you can use LGUP to flash again. But, make sure you flash a full KDZ as I suspect you are flashing partial file and having all these problems. First recover from these errors then worry about flashing Sea region. go to LGFirmwares website, download a full 4GB KDZ for LM405EBW model. I feel that you didn't download full KDZ since last post because LGFirmwares website is very very slow and it takes many hours to download a full KDZ...
Edit: And whatever you do, do not use any options in LGUP that you don't know about, especially the 'ChipErase' option, it will permanently break/brick your phone. Once you flash a full KDZ and run setup and if still have issues, please go into settings, 'System', 'About Phone', and 'Status' and do you see your IMEI number shown or not? If it is not showing you may have used 'ChipErase' and there is no easy way to recover from that.
Click to expand...
Click to collapse
In this particular case, the ChipErase did help me get the signal for cellular data and wifi back for me. Eventhough the IMEI is gone but everything now works for me.
ultoramansaga said:
In this particular case, the ChipErase did help me get the signal for cellular data and wifi back for me. Eventhough the IMEI is gone but everything now works for me.
Click to expand...
Click to collapse
It is funny that I suspected right away this is what you have done even though you were not very forthcoming. If you are looking for help from others on this forum please be considerate of others' time and effort by providing all the necessary details so we can help you effectively and efficiently.
Just know that (and let it be a warning to others reading this) ChipErase not only erases IMEI numbers but i think it also erases MAC addresses, EFS partition etc.. In many countries if your device doesn't have IMEI number or other identifiers, sim networks are not allowed to let you register with them, in other words, in most cases your sim will not work in this phone and you will have no cell service. You seem to be lucky if network you are using is letting you connect with them. With most networks you will not have cell service. You will even have issues with Wi-Fi networks as without MAC addresses for your Wi-Fi will either be greyed out or network might not let you connect.
Also, know that in many countries around the world knowingly tampering with or changing your phone's IMEI numbers is against the law. IMEI number is how networks and ultimately law enforcement identify the device and their owner.
---------- Post added at 11:18 PM ---------- Previous post was at 11:05 PM ----------
kodein said:
Thank you very much. You helped me solve my problem !!!!:good::good::good::highfive:
Click to expand...
Click to collapse
Glad something I wrote helped you.
Hello. After using the DL partition in lgup, my S / N and IMEI SV disappeared ... The phone now does not pass the safety net check. Would you know how to fix S / N and IMEI SV?
kodein said:
Hello. After using the DL partition in lgup, my S / N and IMEI SV disappeared ... The phone now does not pass the safety net check. Would you know how to fix S / N and IMEI SV?
Click to expand...
Click to collapse
Partition DL wouldn't do that, are you sure you didn't do 'ChipErase'? If you didn't, download KDZ again and try reflashing?
I'm 100% sure the dl partition did it for me. I didn't use chip erase at all. Reflashing didn't help me. I didn't miss the IMEI, but the IMEI SV and S / N ... And when I looked into the system, the phone wouldn't load build.prop ... Maybe it's related
After tinkering around in the setting I found that my model turned into V405UB instead of the real model V405EBW along with the second sim tray doesn't work anymore
kodein said:
I'm 100% sure the dl partition did it for me. I didn't use chip erase at all. Reflashing didn't help me. I didn't miss the IMEI, but the IMEI SV and S / N ... And when I looked into the system, the phone wouldn't load build.prop ... Maybe it's related
Click to expand...
Click to collapse
Partition DL does not mess with your IMEI number or Serial number. I dont know if a corrupt or incomplete KDZ could cause this? I suggest that you download different KDZ and make sure it is around 4GB in size, md5 match up, and flash that and see if IMEI numbers return.
After tinkering around the settings, I found that my model went from EBW to UB and the second sim tray no longer works
I don't have a S/N for mine either. Don't know if there was one there before I cross-flashed. Does it make a difference?
[NG]Owner
Android# said:
Partition DL does not mess with your IMEI number or Serial number. I dont know if a corrupt or incomplete KDZ could cause this? I suggest that you download different KDZ and make sure it is around 4GB in size, md5 match up, and flash that and see if IMEI numbers return.
Click to expand...
Click to collapse
Hi Android #. I downloaded several FW and after reflash the result of the meetings is the same. IMEI SV and S / N are missing ...
But it's weird that Lgup from this post: https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168 helped me fix the signal loss and LGUP from this: https://forum.xda-developers.com/lg-v40/development/lg-1-16-t3967559 did not fix it for me ...
I also don't have S/N after cross flashing but I do have IMEI
I bought a LM-V450ebw Dual SIM with android 8x, probably HongKong distribution. I've beed trying to flash it to EU/Polish ROM (android 10) with no possitive effect (I want to have volte and wifi calling - that's the main reason to update).
I've beed trying LGUP 1.14-1.16 with different LGDLL but no way to overcome "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
Finally I tried to update to android 10 Hong Hong version and I succeeded (v30b-lao-yt). But still no success in moving to EU/Polish ROM (android 10) via LGUP - "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
It looks like, there is no problem to move between HK version but no way to move from HK -> UE/Polish.
Of course LG Bridge doesn't help much.
What's wrong? Is there any way to do it without rooting?
pjgadek said:
I bought a LM-V450ebw Dual SIM with android 8x, probably HongKong distribution. I've beed trying to flash it to EU/Polish ROM (android 10) with no possitive effect (I want to have volte and wifi calling - that's the main reason to update).
I've beed trying LGUP 1.14-1.16 with different LGDLL but no way to overcome "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
Finally I tried to update to android 10 Hong Hong version and I succeeded (v30b-lao-yt). But still no success in moving to EU/Polish ROM (android 10) via LGUP - "error: 0x6004, crossdl open_hk_ds>open_eu_ds"
It looks like, there is no problem to move between HK version but no way to move from HK -> UE/Polish.
Of course LG Bridge doesn't help much.
What's wrong? Is there any way to do it without rooting?
Click to expand...
Click to collapse
For most of the variants all that's needed to crossflash is to use 1.14 and choose 'partition download'. But the HK dual sim variant is a pia. You can lose one or both sims if not done correctly.
I'd suggest, in rom forum see initial thread for lineage os and find invite to join v40 tele group. Ask there as those guys have much more international experience especially with dual sim variants.
cheers
Similar problem wit a new LM-V405EBW running Android 9 sec patch 1 June 2019
It is supposed to be an European version, came with a EU charger ...
Current software V20a-LAO-YT
Checked with a IMEI checker that said it is a DEC region phone.
It seems LG has removed V40 Thinq from the supported devices,
cannot get any OTA updates :-(
I want to install V405EBW30d_00_OPEN_EU_DS_OP_1223.kdz
latest DEC firmware I think.
When I try LGUP i get the same error mess as above
"error: 0x6004, crossdl open_hk_ds>open_eu_ds"
Tried both "refurbish" and "update" same error.
I don't mind to wipe the phone clean,
but when i select the "Partition DL" i get more than 10 options,
which one(s) should i select ?
Hope I can get some advice.
LG_User_42 said:
Si
I don't mind to wipe the phone clean,
but when i select the "Partition DL" i get more than 10 options,
which one(s) should i select ?
Hope I can get some advice.
Click to expand...
Click to collapse
all of them except ftm. Then, when it finishes and reboots, do the refurbish (twice) with the same kdz.
cheers
Evening! I bring you a solution, it seems a strange solution, but after weeks of trying anyway, the only one that did not occur to me, is to disconnect it while I was flashing the rom that I put wrong to downgrade it, i cause a provocated brick, what is my surprise when insert the IBR rom (before it had the TIM) it started flashing without problem.
Mobile to repair: Lg K41S (LMK410EMW)
Use this version of the LGUP flash tool: LGUP_Dev-1.14 (patch)