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
Related
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Tuerkay said:
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Click to expand...
Click to collapse
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
brumgav said:
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
Click to expand...
Click to collapse
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Tuerkay said:
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Click to expand...
Click to collapse
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
brumgav said:
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
Click to expand...
Click to collapse
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Tuerkay said:
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Click to expand...
Click to collapse
Have you done a factory reset during any of the above?
brumgav said:
Have you done a factory reset during any of the above?
Click to expand...
Click to collapse
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Tuerkay said:
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Click to expand...
Click to collapse
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
brumgav said:
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
Click to expand...
Click to collapse
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
i currently have no permission manager and no mobile data manager
Tuerkay said:
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
Click to expand...
Click to collapse
I think I wrote CRR-L09C432B114
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
bgx said:
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
Click to expand...
Click to collapse
tried many different things but nothing worked. Now i´m back at C433B114 until someone finds a solution.
I´m missing so many functions but i won´t change back to C00B160 because my main language isn´t supported well enough
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Iverom said:
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Click to expand...
Click to collapse
European version only supports 1 SIM
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
plantunes said:
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
Click to expand...
Click to collapse
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Tuerkay said:
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Click to expand...
Click to collapse
Do you have a CL00 converted into a L09?
If you do, you could change that string "ro..dual.sim.phone" into TRUE and see what happens. It would be absolutely great if that was possible!
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Lightofdarkness666 said:
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Click to expand...
Click to collapse
Flashed all files and then tried a clean update. Didn´t work. My Mate S shows the right Build and Vendor but i´m still not able to use the C432 Update.app´s.
Are you able to update manually?
Is your phone originally an L09 or UL00 device? If it´s an UL00 Mate S, could you tell me exactly what you did?
My phone is originally an L09, but i broke it in UL00C00, can't get back to L09, recovery don't boot, flash via fastboot lead to freeze at boot
hi every one my moto g2014 is showing no service actually i unlocked bootloader for flasing twrp boot loader unlocked but recovery not flashing it is running on android 6.0 and when i tried to flash recovery wifi is not working now i installed a stock os now wifi is working but sim network is not working although sim card is detecting but no service please help me
JAY8042 said:
hi every one my moto g2014 is showing no service actually i unlocked bootloader for flasing twrp boot loader unlocked but recovery not flashing it is running on android 6.0 and when i tried to flash recovery wifi is not working now i installed a stock os now wifi is working but sim network is not working although sim card is detecting but no service please help me
Click to expand...
Click to collapse
Which country? Is your phone a dual sim model? Please send full details of your phone.
No service error can be resolved by these following steps:
First of all make sure your phones Aeroplane mode is turned off
1) Reinsert your sim cards and restart
2) Factory Reset your phone
3) Use *#*#4636#*#* on your phones dialer and then select the phone information option, try to turn on the radio manually
4) If none of the above works please check the phone status by clicking about phone>Status>Sim1 or 2>Service Status, If your service status is showing Radio Off then you have to Reinstall The STOCK ROM on your phone or you have to flash only the MODEM Files of Original Stock Rom via mfastboot
yeah its indian mobile xt1068 dual sim model can u give me modem files
JAY8042 said:
yeah its indian mobile xt1068 dual sim model can u give me modem files
Click to expand...
Click to collapse
I believe that you know how to connect your phone to your PC in adb fastboot mode, so i am skipping that part.
Please check you have downloaded "XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7_CFC.xml". This is Stock Rom Version of India.
If yes Please copy only NON-HLOS.bin and fsg.mbn files form that STOCK ROM zip into the installation folder of adb fastboot in your PC.
Once you connect your phone in bootloader to PC open mfastboot cmd and type and run only two commands mentioned below 1) mfastboot.exe flash modem NON-HLOS.bin
and
2) mfastboot.exe flash fsg fsg.mbn
Then exit cmd and restart your phone.
If any confusions you have please feel free to write down here. (regrets for replies may take longer, please be patient)
I hope this will surely solve your problem.
Don't forget to leave a reply if your problem get solved
---------- Post added at 07:26 PM ---------- Previous post was at 07:12 PM ----------
I couldnt upload the modem files here due to some technical errors. If you dont have that stock rom please send your mail id, I will send you the zip of modem files before tomorrow 9:30am
not working bro tried everuthing
Have the same problem. Moto g 2
Hi guys. I just rooted my moto g2 and everything worked fine except the sim cards. My imeis are correct, i dont know what else to do. can you help me pls?
JAY8042 said:
not working bro tried everuthing
Click to expand...
Click to collapse
Is your IMEI showing?
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
thomascale12 said:
Hi guys. I just rooted my moto g2 and everything worked fine except the sim cards. My imeis are correct, i dont know what else to do. can you help me pls?
Click to expand...
Click to collapse
Did you flash any ROMs on your phone?
---------- Post added at 04:07 AM ---------- Previous post was at 03:59 AM ----------
JAY8042 said:
not working bro tried everuthing
Click to expand...
Click to collapse
If your phones IMEI showing correctly, then its only problem of modem files.
I think what you have flashed is not a correct ROM. Otherwise that should have worked.
Please check your IMEI and then tell me is that IMEI SV slots are showing some value or showing null? Not only Main IMEI solt. There is another IMEI slot called SV slot check that also in about phone-status-imei information
sumashash said:
Is your IMEI showing?
---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------
Did you flash any ROMs on your phone?
---------- Post added at 04:07 AM ---------- Previous post was at 03:59 AM ----------
If your phones IMEI showing correctly, then its only problem of modem files.
I think what you have flashed is not a correct ROM. Otherwise that should have worked.
Please check your IMEI and then tell me is that IMEI SV slots are showing some value or showing null? Not only Main IMEI solt. There is another IMEI slot called SV slot check that also in about phone-status-imei information
Click to expand...
Click to collapse
My imeis are ok and the sv values are ok too... probably i installed the wrong rom... can you guys tell me wich is the correct rom for Portugal or europe?
thomascale12 said:
My imeis are ok and the sv values are ok too... probably i installed the wrong rom... can you guys tell me wich is the correct rom for Portugal or europe?
Click to expand...
Click to collapse
Sorry dont know which is the Stock Rom for your country, please try to search on the net you will find it, i am from india so dont know whats the right rom for your device, sorry
hey sumashash..!!!
Pls help me.
my XT1068 india wont show notifications and nothing happens when i tap the build no. i.e. developer options are not enabled.
Plus I wont receive any call. it says the user is busy although my fone is idle with full network..
for these problems i thought to unroot my fone by using stock firmware and fastboot by i wont become developer due to which i cannot enable usb debugging...
Pls HELP me.....
No service
sumashash said:
Which country? Is your phone a dual sim model? Please send full details of your phone.
No service error can be resolved by these following steps:
First of all make sure your phones Aeroplane mode is turned off
1) Reinsert your sim cards and restart
2) Factory Reset your phone
3) Use *#*#4636#*#* on your phones dialer and then select the phone information option, try to turn on the radio manually
4) If none of the above works please check the phone status by clicking about phone>Status>Sim1 or 2>Service Status, If your service status is showing Radio Off then you have to Reinstall The STOCK ROM on your phone or you have to flash only the MODEM Files of Original Stock Rom via mfastboot
Click to expand...
Click to collapse
hi bro
im facing the same problem for my moto g2 xt1068 indian version .
i tried to manually on the radio as u said but its not getting on can u suggest my something
and if u can send modem files to my mail it will be a great help [email protected]
thankyou
I followed a guide by XDA User applepay from this link, but just wanted to try and simplify it because i found it pretty complicated to understand at first.
It would be worth reading that thread before this even if it doesn't make sense. Please also read this complete thread before you attempt it.
I have only followed the guide so i can't answer any questions to help. I am not responsible for any problems you run into. This is just a guide of what I did to get mine to work.
I was successful using my SM-N960F going from CSC XME to TEL.
I cannot confirm that this method will work on other models, but i don't see why not considering the guide was originally for a S9.
Make sure you select your exact model when downloading files and flashing files. Using other model firmware may brick your phone.
Backup your files! I used Smart Switch on windows. This method will wipe your phone in the process.
Use the original usb cable you got in the box and install the Samsung USB drivers if you haven't already.
I have confirmed on my device that OTA updates work fine after this procedure.
Please comment if you think there is a better way or there is an error in this guide.
Download your combination file from here
Download your new CSC firmware from here
Download Samsung Odin 3.13.1 from here
Download RealTerm from here
1. Open Odin.
Click AP and select your combination file.
Put your Note 9 into download mode by turning it off completely, then holding the volume down and bixby buttons while inserting the usb cable. Confirm that you want to enter download mode.
Click start in Odin.
Once this is complete, your phone should boot into the combination firmware and show your model number. Close Odin.
2. Open RealTerm and go to Port tab.
Set Baud to 230400 and Select Port to ssudmdm0000 or very similar name.
Click the change button.
Go to Send tab.
Enter "AT" and click Send ASCII.
If you get a response like
"+USB READY
BOOTING COMPLETED
AT"
or
"AT"
or
"OK"
or
"BOOTING COMPLETED
AT"
Proceed to the next number.
If you didn't get a response click +CR and send again.
If you get a response like "ERROR" proceed to the next number.
Still if you didn't get a response check your phone status and cable status.
If everything is normal proceed to the next number.
If still you didn't get a response it means your phone or cable is not normal status.
3. Enter "AT+PRECONFG=1,0" and click Send ASCII.
You will get this response.
AT+PRECONFIG=1,0+PRECONFG:1,???
OK
-??? is your current CSC.-
4. Enter "AT+PRECONFG=2,???" and click Send ASCII.
Enter ??? you want to change to another CSC.
You will get this response.
AT+PRECONFG=2,???+PRECONFG:2,OK
OK
-??? is your changed CSC.-
5. Enter "AT+PRECONFG=1,0" and click Send ASCII.
You will get this response.
AT+PRECONFIG=1,0+PRECONFG:1,???
OK
-??? is your changed, current CSC.-
6. CSC change is now complete. You can now close RealTerm.
7. Open Odin again.
Turn your phone off and then put it into download mode again by holding the volume down and Bixby buttons, then plugging the usb cable in.
Fill each field (BL, AP, CP and CSC) with their respective files from the firmware which has the new CSC.
Use the CSC file in the CSC field, not HOME_CSC.
Click start. This will now wipe your phone completely.
8. Your phone should boot into android and everything should be complete!
Enjoy using VoLTE, VoWiFi and RCS!
Many thanks! Will give it a go.
Sent from my SM-G955F using Tapatalk
Work on sm-n9600 hong kong variant?
Enviado desde mi SM-N9600 mediante Tapatalk
Thanks. Worked on my n960f/ds
@laneyyy I guess this is for unrooted device right? There are much easier ways of doing it in rooted device
Techvir said:
@laneyyy I guess this is for unrooted device right? There are much easier ways of doing it in rooted device
Click to expand...
Click to collapse
Yeah this is for unrooted devices
Hmm, will this allow my unrooted n960f/ds to flash the TMB CSC and work? Or does this just let you change to another CSC within the multi CSC?
SystematiQ said:
Hmm, will this allow my unrooted n960f/ds to flash the TMB CSC and work? Or does this just let you change to another CSC within the multi CSC?
Click to expand...
Click to collapse
I'm not sure. I hope someone else can answer that
using n960f with n9600 csc
I have read about this procedure but i dont se any info from other providers than us, Im new about this procedure, i hope you can just help me to understand, i have a n960f and i like to have the csc info from a n9600, im from mexico so it will be great to get all my providers features (telcel) but im kind of lost because i have read about usa providers but no more info, thank you.
SystematiQ said:
Hmm, will this allow my unrooted n960f/ds to flash the TMB CSC and work? Or does this just let you change to another CSC within the multi CSC?
Click to expand...
Click to collapse
Odin still won't let you flash firmware files from an other phone model. which is a good thing since csc.md5 contains a pit file that is very much phone model specific....you dont want that. home_csc.md5 dosent but regardless Odin should still throw an error. I wouldint be game to test with the prince Comey edition of Odin that allows you to do this forcefully apply wrong model firmware file. might work... or not
how about future OTAs after ? if I flashed TMO csc will I get all TMO OTAs in future ?
@laneyyy i need to select combinations file Odion in AP right ? I guess I have to downgrade my firmware first Odin don't let me flash I have the last one firmware
arturodfw said:
@laneyyy i need to select combinations file Odion in AP right ? I guess I have to downgrade my firmware first Odin don't let me flash I have the last one firmware
Click to expand...
Click to collapse
My phone was up to date before I used the latest combination file for my model on that site. I didn't get any errors about downgrading.
As far as OTAs, I'm not sure yet, but worst case is you just need to flash new firmwares by Odin. I think it's definitely worth the trade off to get volte, vowifi and RCS if that's the case
laneyyy said:
My phone was up to date before I used the latest combination file for my model on that site. I didn't get any errors about downgrading.
As far as OTAs, I'm not sure yet, but worst case is you just need to flash new firmwares by Odin. I think it's definitely worth the trade off to get volte, vowifi and RCS if that's the case
Click to expand...
Click to collapse
@laneyyy so the combination file it's on AP option in odin right
arturodfw said:
@laneyyy so the combination file it's on AP option in odin right
Click to expand...
Click to collapse
Ooooh yes. I just saw that I accidentally wrote AT in the guide.
laneyyy said:
My phone was up to date before I used the latest combination file for my model on that site. I didn't get any errors about downgrading.
As far as OTAs, I'm not sure yet, but worst case is you just need to flash new firmwares by Odin. I think it's definitely worth the trade off to get volte, vowifi and RCS if that's the case
Click to expand...
Click to collapse
Agreed
someone please confirm that N9600 chinese snapdragon variant can have working Volte after changing CSC to any US version.
Why the Heck Samsung put region lock! if they do same thing on S10 then I must say goodbye to Samsung for ever!!
we cant even buy a mobile in a foreign country! ?
ran816 said:
someone please confirm that N9600 chinese snapdragon variant can have working Volte after changing CSC to any US version.
Why the Heck Samsung put region lock! if they do same thing on S10 then I must say goodbye to Samsung for ever!!
we cant even buy a mobile in a foreign country! ?
Click to expand...
Click to collapse
what odin you use for the N9600 variant does not work for me, none of them give me fail or port close
laneyyy said:
Ooooh yes. I just saw that I accidentally wrote AT in the guide.
Click to expand...
Click to collapse
@laneyyy works on my S9 plus SM-G9650 but the AT+PRECONFG=2,??? the ??? Its the new CSC U want to change lol that's why my phone no change anything the first time sorry but I figured out now thanks
I can confirm it worked to replace the hedious Hong Kong CSC with a Costa Rica CSC, but just as others, I would like to see if I can use a firmware from US, meaning using a SM-N960U variant on a SM-N9600. Can someone please confirm?
I have two s10+ devices, one has received software updates a few days after the release, however, my other device does not receive software updates. When the device was purchased, it received one software update, I had to factory reset the device not too long after that. After factory resetting I haven't had any updates, I had to flash the April update via Odin, the other device has already received the May update, and this one even after searching says software is up to date. I've tried Samsung smart switch as well, and it says the same. Is there any way to fix this? Thanks for any assistance.
Gdefreitas said:
I have two s10+ devices, one has received software updates a few days after the release, however, my other device does not receive software updates. When the device was purchased, it received one software update, I had to factory reset the device not too long after that. After factory resetting I haven't had any updates, I had to flash the April update via Odin, the other device has already received the May update, and this one even after searching says software is up to date. I've tried Samsung smart switch as well, and it says the same. Is there any way to fix this? Thanks for any assistance.
Click to expand...
Click to collapse
I wonder if both of your devices are from the same region. You can go to Sammobile website and check the firmware info for your device that rarely gets updates. It will show the latest update available for that region/device
Charkatak said:
I wonder if both of your devices are from the same region. You can go to Sammobile website and check the firmware info for your device that rarely gets updates. It will show the latest update available for that region/device
Click to expand...
Click to collapse
Both are from the same region, I flashed the April update via Odin after downloading the firmware from Sammobile. I just would rather not have to flash updates all the time via Odin. It only received one update, and then nothing ever since. The only thing I did after receiving the one update is factory reset the device and eventually switching carriers. I'm wondering if that could be why, but the other device I purchased is on the same carrier, and it gets the updates very quickly, both are factory unlocked devices.
Gdefreitas said:
Both are from the same region, I flashed the April update via Odin after downloading the firmware from Sammobile. I just would rather not have to flash updates all the time via Odin. It only received one update, and then nothing ever since. The only thing I did after receiving the one update is factory reset the device and eventually switching carriers. I'm wondering if that could be why, but the other device I purchased is on the same carrier, and it gets the updates very quickly, both are factory unlocked devices.
Click to expand...
Click to collapse
Interesting. Haven't had that happen to me.
1) Which carrier are you using right now?
2) What is the model # of your phone and which CSC code, XAA or another one? - how can I locate your phone's firmware on Sammobile site?
Software
Charkatak said:
Interesting. Haven't had that happen to me.
1) Which carrier are you using right now?
2) What is the model # of your phone and which CSC code, XAA or another one? - how can I locate your phone's firmware on Sammobile site?
Click to expand...
Click to collapse
I'm currently on the Bmobile network as I'm from Trinidad. The device that gets updated, the Software service provider is listed as TPA/TTT, TPA/TPA. The device that doesn't get it is listed as TTT/TTT, TTT/TPA. Both are on the same network. I downloaded the April update from Sammobile, the one listed here: firmwares/galaxy-s10-plus/SM-G975F/EON/download/G975FXXU1ASD5/267193/
I hope I provided all you asked about, if you need anymore info to assist, let me know.
Gdefreitas said:
I'm currently on the Bmobile network as I'm from Trinidad. The device that gets updated, the Software service provider is listed as TPA/TTT, TPA/TPA. The device that doesn't get it is listed as TTT/TTT, TTT/TPA. Both are on the same network. I downloaded the April update from Sammobile, the one listed here: firmwares/galaxy-s10-plus/SM-G975F/EON/download/G975FXXU1ASD5/267193/
I hope I provided all you asked about, if you need anymore info to assist, let me know.
Click to expand...
Click to collapse
Use attached SamFirm tool to search and download what you need and in your case it is either EON or TPA. You can start from flashing EON firmware and see if it will help you get updates or from TPA, your choice.
1) I would advice you to remove sim card from your phone
2) Use backup/restore in your phone's settings(if you need it) to back up your phone. Then do "reset" option in your phone settings to wipe it
3) After phone comes to "welcome screen", turn it off and put it in download mode for Odin and put 4 files where they belong and the rest you know...I personally use CSC files instead of HOME_CSC as I like to wipe the whole phone(you can try home_csc first if you so desire)
I also included the screenshot with your model and CSC code in it. Just check for update in the tool and you can change the EON to TPA if you need another firmware.
If you could take a screenshot of your software info screen, where it shows TTT/TTT/.... stuff and also after you click check for update on your phone, I wonder how the screen looks like where it tells you "software up to date"
Charkatak said:
Use attached SamFirm tool to search and download what you need and in your case it is either EON or TPA. You can start from flashing EON firmware and see if it will help you get updates or from TPA, your choice.
1) I would advice you to remove sim card from your phone
2) Use backup/restore in your phone's settings(if you need it) to back up your phone. Then do "reset" option in your phone settings to wipe it
3) After phone comes to "welcome screen", turn it off and put it in download mode for Odin and put 4 files where they belong and the rest you know...I personally use CSC files instead of HOME_CSC as I like to wipe the whole phone(you can try home_csc first if you so desire)
I also included the screenshot with your model and CSC code in it. Just check for update in the tool and you can change the EON to TPA if you need another firmware.
If you could take a screenshot of your software info screen, where it shows TTT/TTT/.... stuff and also after you click check for update on your phone, I wonder how the screen looks like where it tells you "software up to date"
Click to expand...
Click to collapse
I'll try using the Samfirm tool and do as you said. After flashing ,will I be able to receive OTA updates? These are the screenshots of the present software info on both devices. The night mode is the device that doesn't update, the other the one that does.
Charkatak said:
Use attached SamFirm tool to search and download what you need and in your case it is either EON or TPA. You can start from flashing EON firmware and see if it will help you get updates or from TPA, your choice.
1) I would advice you to remove sim card from your phone
2) Use backup/restore in your phone's settings(if you need it) to back up your phone. Then do "reset" option in your phone settings to wipe it
3) After phone comes to "welcome screen", turn it off and put it in download mode for Odin and put 4 files where they belong and the rest you know...I personally use CSC files instead of HOME_CSC as I like to wipe the whole phone(you can try home_csc first if you so desire)
I also included the screenshot with your model and CSC code in it. Just check for update in the tool and you can change the EON to TPA if you need another firmware.
If you could take a screenshot of your software info screen, where it shows TTT/TTT/.... stuff and also after you click check for update on your phone, I wonder how the screen looks like where it tells you "software up to date"
Click to expand...
Click to collapse
I'll try using the Samfirm tool and do as you said. After flashing ,will I be able to receive OTA updates? These are the screenshots of the present software info on both devices. The night mode is the device that doesn't update, the other is the one that does.
Gdefreitas said:
I'll try using the Samfirm tool and do as you said. After flashing ,will I be able to receive OTA updates? These are the screenshots of the present software info on both devices. The night mode is the device that doesn't update, the other the one that does.
Click to expand...
Click to collapse
I see that on the night mode device, the firmware is TTT and on the other is TPA. I think the TTT doesn't get the update, so use the tool and download TPA and flash your phone. If everything is good, I believe you should be receiving updates.
Charkatak said:
I see that on the night mode device, the firmware is TTT and on the other is TPA. I think the TTT doesn't get the update, so use the tool and download TPA and flash your phone. If everything is good, I believe you should be receiving updates.
Click to expand...
Click to collapse
So instead of searching for EON, search for TPA in the samfirm tool and use that to install? Also, I've never used this particular program, is there a guide to using it to make sure I don't mess up the process?
Gdefreitas said:
So instead of searching for EON, search for TPA in the samfirm tool and use that to install? Also, I've never used this particular program, is there a guide to using it to make sure I don't mess up the process?
Click to expand...
Click to collapse
Correct, search for TPA instead of EON firmware and once the firmware is found, click download and the rest is the same. After that you would just unzip files to the folder and use Odin. Don't forget about the steps I provided before flashing
Charkatak said:
Correct, search for TPA instead of EON firmware and once the firmware is found, click download and the rest is the same. After that you would just unzip files to the folder and use Odin. Don't forget about the steps I provided before flashing
Click to expand...
Click to collapse
That would be factory resetting the device, then once it boots on to the welcome screen boot into download mode and then do the flash? Thanks for all the help, I'll try it out and see how it works whether it switches to the correct thing.
Gdefreitas said:
That would be factory resetting the device, then once it boots on to the welcome screen boot into download mode and then do the flash? Thanks for all the help, I'll try it out and see how it works whether it switches to the correct thing.
Click to expand...
Click to collapse
Remove the sim, factory reset the device. After that it will restart and boot to welcome screen. Put phone into download mode, start Odin, connect your phone, add files, flash firmware. After your phone restarts, it should be at the welcome screen. Now put your sim and see if you get any message that tells you something about "carrier settings..." which is good, then it will restart
Charkatak said:
Remove the sim, factory reset the device. After that it will restart and boot to welcome screen. Put phone into download mode, start Odin, connect your phone, add files, flash firmware. After your phone restarts, it should be at the welcome screen. Now put your sim and see if you get any message that tells you something about "carrier settings..." which is good, then it will restart
Click to expand...
Click to collapse
So I downloaded the TPA firmware and flashed it, I also followed your instructions with regards removing the sim. When I reinserted the sim, no carrier settings showed up, and the software version still shows TTT, so I'm guessing the lack of software updates will continue.
Gdefreitas said:
So I downloaded the TPA firmware and flashed it, I also followed your instructions with regards removing the sim. When I reinserted the sim, no carrier settings showed up, and the software version still shows TTT, so I'm guessing the lack of software updates will continue.
Click to expand...
Click to collapse
I just saw the image. Flash again. For my phone, I had to flash 3 or 4 times before it changed the SW version. I used 3 different Odin versions as well.
Use Odin version that I attached here too. You need to flash and make sure the SAOMC_SM-G975F_OXM_TTT changes to TPA
Charkatak said:
Where does it show TTT? In the software version?
Click to expand...
Click to collapse
Yeah, the software version still shows the CSC as TTT/TTT, TTT/TPA. And it shows as SAOMC_SM-G975F_OXM_TTT.
Gdefreitas said:
Yeah, the software version still shows the CSC as TTT/TTT, TTT/TPA. And it shows as SAOMC_SM-G975F_OXM_TTT.
Click to expand...
Click to collapse
Just letting you know that I edited my previous message a bit where I included another version of Odin for you to try
Charkatak said:
Just letting you know that I edited my previous message a bit where I included another version of Odin for you to try
Click to expand...
Click to collapse
Do I need to flash it clean once again with the CSC, or can I use Home_CSC to keep my settings as I've already started to set the phone up again. And mind if I ask what the difference in the versions of Odin are?
Gdefreitas said:
Do I need to flash it clean once again with the CSC, or can I use Home_CSC to keep my settings as I've already started to set the phone up again. And mind if I ask what the difference in the versions of Odin are?
Click to expand...
Click to collapse
1) I mostly use regular CSC file as I like to clean everything, but try Home first, then regular csc if you don't like setting up the phone. Don't setup the phone next time until you get positive results
2) So I used "Odin3_v3.13.1_3B_PatcheD" that I included in the thread and also used Odin 3.13.1 and 3.13.3
3) If after flashing again, it won't change the firmware, then do this: get EON firmware, flash on your phone following the list of steps as you did previously.
4) Put the sim card in and see if there are any messages about carrier updates. This message is a good indication that firmware is getting changed(unless on international model message is different from US version)
5) Check the SW version in settings and then you will need to flash TPA firmware again, which should give you proper results.
I had to flash XAA firmware, then TMB to make my phone change to TMB and it took me multiple tries
Charkatak said:
1) I mostly use regular CSC file as I like to clean everything, but try Home first, then regular csc if you don't like setting up the phone. Don't setup the phone next time until you get positive results
2) So I used "Odin3_v3.13.1_3B_PatcheD" that I included in the thread and also used Odin 3.13.1 and 3.13.3
3) If after flashing again, it won't change the firmware, then do this: get EON firmware, flash on your phone following the list of steps as you did previously.
4) Put the sim card in and see if there are any messages about carrier updates. This message is a good indication that firmware is getting changed(unless on international model message is different from US version)
5) Check the SW version in settings and then you will need to flash TPA firmware again, which should give you proper results.
I had to flash XAA firmware, then TMB to make my phone change to TMB and it took me multiple tries
Click to expand...
Click to collapse
Ok, I'll try flashing a couple times. To be honest, I only started setting up the phone as I thought that was all that could be tried, didn't know there was some hope of it working after all. If I don't get to flash the EON firmware tonight, I'll be sure to try it tomorrow in hope that it actually changes. I think once it changes it should work, because the other s10+ and even the s8+ both have TPA and they're both unlocked on the same carrier. I have no idea why this one would have switched. As far as I can tell there isn't any TTT firmware for the S10+, there is one for the normal S10 however, so I'm really not sure.
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