Hello, I came here in a need of quick help. I have rooted Optimus L7 II and I tried editing media_profiles.xml
After editing it and rebooting it got stuck on a LG boot animation. I can't get a logcat during boot but thankfully I have full rooted ADB access in stock recovery mode, Could any fellow L7 II owner give me his unmodified "media_profiles.xml" so I can replace it although I have a bad feeling that it's not causing the problem because I (think) I reverted all the changes in it before pushing it back with ADB. So someone with L7 II post their media profiles file or tell me how to get adb while booting so I can diagnose this problem myself.
Reflashing kdz's is a LAST resort.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the screenshot of some of the files in /system/etc and underlined one is the presumably correct media_profiles.xml that I pushed back using adb in hopes of fixing the bootloop.
Could the different date be the problem?
CrashBandicootX said:
Hello, I came here in a need of quick help. I have rooted Optimus L7 II and I tried editing media_profiles.xml
After editing it and rebooting it got stuck on a LG boot animation. I can't get a logcat during boot but thankfully I have full rooted ADB access in stock recovery mode, Could any fellow L7 II owner give me his unmodified "media_profiles.xml" so I can replace it although I have a bad feeling that it's not causing the problem because I (think) I reverted all the changes in it before pushing it back with ADB. So someone with L7 II post their media profiles file or tell me how to get adb while booting so I can diagnose this problem myself.
Reflashing kdz's is a LAST resort.
This is the screenshot of some of the files in /system/etc and underlined one is the presumably correct media_profiles.xml that I pushed back using adb in hopes of fixing the bootloop.
Could the different date be the problem?
Click to expand...
Click to collapse
try to reinstall your stock rom
open this thread for step by step
---------- Post added at 10:47 PM ---------- Previous post was at 10:47 PM ----------
CrashBandicootX said:
Hello, I came here in a need of quick help. I have rooted Optimus L7 II and I tried editing media_profiles.xml
After editing it and rebooting it got stuck on a LG boot animation. I can't get a logcat during boot but thankfully I have full rooted ADB access in stock recovery mode, Could any fellow L7 II owner give me his unmodified "media_profiles.xml" so I can replace it although I have a bad feeling that it's not causing the problem because I (think) I reverted all the changes in it before pushing it back with ADB. So someone with L7 II post their media profiles file or tell me how to get adb while booting so I can diagnose this problem myself.
Reflashing kdz's is a LAST resort.
This is the screenshot of some of the files in /system/etc and underlined one is the presumably correct media_profiles.xml that I pushed back using adb in hopes of fixing the bootloop.
Could the different date be the problem?
Click to expand...
Click to collapse
try to reinstall your stock rom
open this thread for step by step
http://forum.xda-developers.com/showthread.php?t=2524466
Hello nasheich, thanks a lot for replying. After making this thread I decided "f**k the data" and went with the full kdz reflash.
I was trying to reflash by following the tutorial from this thread which goes is pretty detailed. This is the page I got my KDZ from. Since the link for V10A is broken I used V10B. I used that one because I am from Croatia and I assumed the "CRO" part of the kdz name is short for Croatia. I got stuck at the actual flashing process, the software just gives me this message shown below. I am in emergency mode (yellow screen) and I am pretty sure I have installed every LG driver I found.
Would you mind helping me reflash this? Log is in the attachment.
Thanks man.
Never mind, I somehow managed to update it using that LG updater thing and now I'm on latest firmware (yay) but it can't be rooted because LG f**king fixed the exploits framaroot was using. So top priority, how do I root it using latest firmware? Anybody? Also could somebody tell me could flashing firmware from, let's say, UK to a Croatian phone brick it. There are no Croatian firmwares on the net so I must know this if I get in a situation where I absolutely must flash new firmware.
tl,dr
1. How do I root LG P710 on latest firmware?
2. Can flashing a different country firmware brick the device?
Root problem solved, huge thanks to user Dejan990 for finding a way to root it and to guys at Kingoapp for doing the actual work behind this.
Just install the application, activate the debugging mode for usb and connect the phone to the pc.
Code:
http://www.kingoapp.com/index.htm
Related
Hi all,
I thin I´ve bricked my device...after the error message the V10 is not responding to any button pushes and won´t start. HELP!!!!!!!
I´m from Germany and I do use a H960 running 10a. I tried to flash the turkish KDZ file with the name H960TR20b_00_0226.kdz.
Here is the screenshot from the erorr that I receive at 80% progress of flashing:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me!
Sup
@muehLe82. I also have h960a 32gb European version bought from Czech Republic. The problem is that the Turkish version of marshmallow is not supported by European model. Whn u try to flash it the system detecting as a incompatible version maybe something to do with regional country based lock set by lg. The solution i can think of it is you need the original firmware kdz for the German version and try flash it and see what happens. I didn't find on xda any original firmware kdz file for European version. I m still a newbie so maybe someone else have better solution.
salman4877 said:
@muehLe82. I also have h960a 32gb European version bought from Czech Republic. The problem is that the Turkish version of marshmallow is not supported by European model. Whn u try to flash it the system detecting as a incompatible version maybe something to do with regional country based lock set by lg. The solution i can think of it is you need the original firmware kdz for the German version and try flash it and see what happens. I didn't find on xda any original firmware kdz file for European version. I m still a newbie so maybe someone else have better solution.
Click to expand...
Click to collapse
Hi,
as I´m not able to enter download mode, a different kdz or tot-file wouldn´t help I´m afraid
@muehLe82 instead of using lg UP. Try using lg bridge software and see if it enters download mode. Pull out the battery for couple of minutes and try entering download mode using lg bridge software and see if it detects ur phone. I understand your frustration completely as i was also tempted to flash the Turkish kdz update on my h960a model. At last minute i decided not to as i thought i spend so much money on a new phone and marshmallow isn't something huge update to take the risk.,
same boat
im on the same boat. Patience is a virtue but hey im in this now. Ive tried ADB, LG PUP and LG Bridge. the issue i think is that the phone is not detected, ive installed the drivers but im getting a device descripter issue on device manager. If I can get ADB detect the phone i could probably re flash it but i cant turn it on nor can I put it on download mode.
any other ideas before i send this to service center of LG?
jvgeli said:
im on the same boat. Patience is a virtue but hey im in this now. Ive tried ADB, LG PUP and LG Bridge. the issue i think is that the phone is not detected, ive installed the drivers but im getting a device descripter issue on device manager. If I can get ADB detect the phone i could probably re flash it but i cant turn it on nor can I put it on download mode.
any other ideas before i send this to service center of LG?
Click to expand...
Click to collapse
I had to sent the device back to Amazon Germany and they´ve repaired it for free (mainboard was replaced)
I have posted about my problem in several threads now, but I didn't get an answer yet, so I hope I can finally save my phone with your help here... It's been a major pain the cojones for two weeks already.
In short, here is what happened:
I unlocked the bootloader, installed TWRP and after flashing superSU (once I found out how to get into TWRP), I got a bootloop.
So I wanted to do a full wipe. But I messed up and wiped literally everything, even the OS
Then I went on to look for a stock ROM zip file. I found one, but I didn't read the whole article which said it was for H901. I installed it and found out it's branded T-mobile version on top of all.
Now I'm trying to get back to a H960A stock ROM, but no luck so far.
I have tried both methods from the LG V10 Stock Firmware (Go Back to Stock) KDZ & TOT Method thread
Then there was a shed of hope when I stumbled upon this thread, where the OP managed to do the same
http://forum.xda-developers.com/lg-v10/help/flashed-h901-h960-comrade-to-help-t3429025
I downloaded the modified Switzerland file mentioned in one of the comments, but it didn't do through for me.
I also tried to run the chkdzdev tool to change my EU version KDZ file, but agian, I got the same error (possibly I didn't do it right, since there is no manual whatsoever and the author doesn't reply)
Here is a screenshot of how it went:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So now, my only hope is to:
a) find a zip with H960A stock ROM (probably none exists on the interwebz)
b) find a TWRP backup that I can "revert" to (not sure if this would work, but if anyone would be so kind, I could find out...)
c) find someone who can modify the KDZ file and tell me how to do it
Anyone?
I messaged a good source about your problem, with any luck he will provide us with a nandroid for you to restore. I'll let you know as soon as I hear back.
If I helped you, please hit the "like" button. Thank you.
RealWelder said:
I messaged a good source about your problem, with any luck he will provide us with a nandroid for you to restore. I'll let you know as soon as I hear back.
If I helped you, please hit the "like" button. Thank you.
Click to expand...
Click to collapse
Any news?
Or anyone has any idea how do I fix this?
Anyone has any idea where to turn for help with this issue? If not on xda, where can I look for a solution?
Try this. There is some instructions here that might be different from what you've been trying.
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
It's saying after you load the firmware into LGUp, you have to close it and then open it again, select refurbish, and then make sure bin file is checked. Hopefully this can get you going. Good luck.
If I helped you, please hit the "like" button. Thank you.
RealWelder said:
Try this. There is some instructions here that might be different from what you've been trying.
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
It's saying after you load the firmware into LGUp, you have to close it and then open it again, select refurbish, and then make sure bin file is checked. Hopefully this can get you going. Good luck.
If I helped you, please hit the "like" button. Thank you.
Click to expand...
Click to collapse
I've tried this one... it wouldn't even let me load the kdz file without doing this...
Problem is, the firmware version is coded somewhere deep in the file and it won't let me install it on a device that has a different version (unfortunately mine was overwritten by the stupid stock ROM i've managed to install)
Hello all,
I have a LG 850, bought in Belgium (carrierless), it was running latest LG nougat stock software when I started fiddling. (This was on the 6th of Jan)
TL;DR: What I did: rooted, installed TWRP and custom ROM (on Nougat 7.1). Worked fine. Then wanted to revert back to stock since it didn't solve the issues I had beforehand. Tried to figure out LG UP, LG Bridge, LG Flash Tool, in the end I managed to install a KDZ file through LG UP (using Uppercut), but it must've been the wrong one because the phone always defaults to recovery mode when booting.
How do I solve this? I can access download mode (LG UP sees the phone), I can use fastboot, and managed to reflash TWRP recovery so I have that too.
Long version: I had GPS and screen burn-in issues. I tried sending the phone back for repair , but LG simply put my phone on an earlier software version, no help. I can't really miss my phone for work (takes 2 weeks) so dealt with it. In the end it bugged me a lot, so decided I should try a custom ROM: installing this went fine. I ran Fulmics for a while, but it didn't solve my problems: must be a hardware issue. That's when I decided to revert back to stock and relock the bootloader to be able to send it back again (I'm using a nexus 5X as backup now). I'm not sure if they'll accept the return (since I've unlocked the phone's bootloader by using LG's dev website), but it's worth a try.
The process in the other direction went south really quickly: I think I accidentally erased the wrong partitions, so I ended up with a phone that only had download mode. I managed to install a KDZ file through LG UP (used the upgrade button, not refurbish, as it was the only one that worked). This didn't help, so I used fastboot to reflash recovery with TWRP.
After this, I tried a bunch of different KDZ files, as I'm not sure how to figure out which one is the correct one for my phone... When I begin to install a KDZ file the log in download mode shows me LG H85020a on the third line, is this the value representing my phone? IMEI lookup tells me: Location code: N, Network Code: NLD, Carrier: NLD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The refurbish button has never worked, I always get the error "Refurbish is not available for this device". Refurbish often ends in "Invalid command response code".
Can anyone point me in the direction of the correct KDZ file, or a way to reset the phone? If not, it's going to be one expense frisbee...
Thanks all!
Greetz from Belgium.
so you successfully flash the KDZ to the phone using LGUP and when it finishes the phone reboots itself, right?
and when it boots.. it boots into stock recovery each time.. which is wiping data? and then it reboots and goes right back into stock recovery?
I'm confused as to what's happening EXACTLY after the KDZ flashes and the phone reboots.
and once you install TWRP... no matter what the phone just reboots back into TWRP and never into Android?
in TWRP try the following:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
reboot
and see if android boots this time after the reboot.
Okay. Weird stuff happened.
I'd like to thank you for your answer, but I ended up not using it.
I decided, while waiting for an answer, to retry all KDZ files in my possession. I started LG UP through Uppercut, and tried H85020a_00_VDF_COM_OP_1030.kdz which in theory shouldn't work, because it's a lower android version than the one I had before. Refurbish didn't work, but the Update button did the trick! Not sure what happened differently this time...
He reset everything, gave me stock software. He did the same thing as before: erasing phone (round shiny ring), message about unlocked bootloader, show LG logo, then the moving logo with music, and rebooted. But right after the moving logo it showed a white screen with text I couldn't read fast enough before it rebooted again. After a while I figured out it was something about an encrypted phone and a pasword mismatch, and that my device needed to be wiped. It did that (had to be quick to click it), it erased itself, and the thing booted up just like that.
I relocked the bootloader using fastboot and it works fine. Ready to be shipped back to LG
I'm running V20a-EUR-XX it says in the settings, I guess that's fine.
Thank you for the help anyway. I hope this explanation helps other users too...
You can find the KDZ files for most H850s at the following link: http://lg-firmwares.com/lg-h850-firmwares/
While I don't see Belgium as one of the many listed regions, you might be running the NEU (Northern Europe) version. Good luck!
thanks for your reply. You can see above i retraced the steps I already tried, and somehow now the phone works.
I ended up using H85020a_00_VDF_COM_OP_1030.kdz which did the trick!
Help! I just unbricked my Le Max 2, it reboots with the screen splitted into two, the left half on the right and the right half on the left. Please can anyone kindly help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after unbrick.
I use FlashOne 1.9 and a QFIL rom to unbrick it.
unbrick it again.
AhmadSant said:
unbrick it again.
Click to expand...
Click to collapse
re-unbricked, same result.
ok, can you do firstly reset factory, then try to install another rom.
AhmadSant said:
ok, can you do firstly reset factory, then try to install another rom.
Click to expand...
Click to collapse
factory reset and flashed another rom via fasboot, but reboot stuck at the start screen, just like the left one on the photo I submitted.
Do another unbricking, and everything back to the state I reported.
It's confirmed to be a hardware problem, when the monitor is replaced, everything back to normal.
I think there is problem with build.prop .. try google ... To restore build.prop
It seems that the Kernel is also affected so it must be hardware problem
hi did you solve this?
I have the same problem
KM141 said:
Click to expand...
Click to collapse
Hi, I have exactly the same problem after following the tutorial in here to get rid of the vendor encrypted god damn rom. Everything was working right before it so I don't buy the hardware issue. After flashing using flashone 2.0 I did ended up with my screen like this.
I tried several qfill file from severals sources and always the same result. I even try to go on and flash TWRP and RR rom but screen stay that way.
Please, I'm seriously desperate right now... I need your help guys and looks like i'm not the only one.
KM141 said:
Click to expand...
Click to collapse
Bambulbizarre said:
Hi, I have exactly the same problem after following the tutorial in here to get rid of the vendor encrypted god damn rom. Everything was working right before it so I don't buy the hardware issue. After flashing using flashone 2.0 I did ended up with my screen like this.
I tried several qfill file from severals sources and always the same result. I even try to go on and flash TWRP and RR rom but screen stay that way.
Please, I'm seriously desperate right now... I need your help guys and looks like i'm not the only one.
Click to expand...
Click to collapse
It was solved without replacing the screen!
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!) and not from one installed
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
For complete version :
https://forum.xda-developers.com/showpost.php?p=74890577&postcount=138
Bambulbizarre said:
It was solved without replacing the screen!
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!) and not from one installed
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
For complete version :
https://forum.xda-developers.com/showpost.php?p=74890577&postcount=138
Click to expand...
Click to collapse
To put a file on the phone while in twrp just use adb push
KuranKaname said:
To put a file on the phone while in twrp just use adb push
Click to expand...
Click to collapse
That's what I tried but as stated in the last link, I had no connection to adb while in twrp after cleaning up.
Anyway that's settled for me, it's mor for other that have encountered this as well. Replacing screen is not the only way.
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...