Database Users

[Q] [q] lg l3 e405 start-up problem

Hi everyone, I'm new here. I have a problem with my LG L3 E405. Last night, I dropped my phone from the second floor of my house. When I reinserted the battery and restarted the phone, a error screen came up
{
"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"
}
....Then I could not use my phone anymore. I searched on forum for my problem. Luckily, I found a post about "UNBRICK YOUR LG OPTIMUS L3 E405". I followed the instructions and my phone worked after that. However, when I restart the phone, the error screen
comes up again. Please help............:crying::crying::crying:

Just to be sure, and not, god forbid, to insult you, when you performed the unbricking procedure, you were familiar with the fact that unbricking is not unbreaking?
I'm asking since I myself wasn't aware of the definition of brick / soft-brick / hard-brick until recently, and until I learned about these, whenever I heard "brick" I thought the meaning was "break".
If you were familiar, will you please explain when the phone worked during the unbricking procedure?
Is it really worked regularly until you restarted it?

need4steer said:
Just to be sure, and not, god forbid, to insult you, when you performed the unbricking procedure, you were familiar with the fact that unbricking is not unbreaking?
I'm asking since I myself wasn't aware of the definition of brick / soft-brick / hard-brick until recently, and until I learned about these, whenever I heard "brick" I thought the meaning was "break".
If you were familiar, will you please explain when the phone worked during the unbricking procedure?
Is it really worked regularly until you restarted it?
Click to expand...
Click to collapse
Yes, my phone worked normally until I restarted it. Only when I restart the phone, the srceen message that I mentioned above will appear. . I look forward to your help.

I'll be glad if I'll manage to help you out.
Please explain in detail the procedure of the unbricking, and elaborate in detail what happened to your phone in the appropriate steps of it.

Here is hoanganspk comment:
hoanganspk said:
Sorry for border you. Because I'm a new member in this forum, I cannot post threat with outside link.
I carefully followed this instruction to unbrick my phone.
http://krazeefly.blogspot.com/2012/09/how-to-unbrick-your-android-phone.html
a
Then, my phone worked well until I restarted. Hope to hear your rely
Click to expand...
Click to collapse
@hoanganspk: You''re not bothering me at all. I hope I'll be able to help you out.
Did you try to enter emergency mode and then flashing your firmware?
If not, please do so - power off your phone, clicking volume up + volume down + power button simultaneously, entering "emergency mode" and only then connecting your phone to your PC.
If you did so, please explain what happened after you received the "FINISHED" status in Software update [KDZ]?
Did your phone was able to enter your stock firmware after all the restarts that Software update [KDZ] did during the flash procedure?
If so, you can root you phone, install CWM, try booting into CWM within the app, when you're already inside you stock ROM, and before you're restarting yourself, and then trying wiping data/factory reset, formatting /system, wiping Dalvik Cache, and then retrying flashing the stock firmware in emergency mode.
I hope I was clear enough.
The most important thing for me to know is if you flashed your stock ROM inside emergency mode, and not, as written in the link you provided, in your OS. BTW, the phone mode setting should be DIAG and not some other setting.
Anyway, I look forward for your reply.
Feel free to ask guidance to any step of the procedure I posted above.

need4steer said:
Here is hoanganspk comment:
@hoanganspk: You''re not bothering me at all. I hope I'll be able to help you out.
Did you try to enter emergency mode and then flashing your firmware?
If not, please do so - power off your phone, clicking volume up + volume down + power button simultaneously, entering "emergency mode" and only then connecting your phone to your PC.
If you did so, please explain what happened after you received the "FINISHED" status in Software update [KDZ]?
Did your phone was able to enter your stock firmware after all the restarts that Software update [KDZ] did during the flash procedure?
If so, you can root you phone, install CWM, try booting into CWM within the app, when you're already inside you stock ROM, and before you're restarting yourself, and then trying wiping data/factory reset, formatting /system, wiping Dalvik Cache, and then retrying flashing the stock firmware in emergency mode.
I hope I was clear enough.
The most important thing for me to know is if you flashed your stock ROM inside emergency mode, and not, as written in the link you provided, in your OS. BTW, the phone mode setting should be DIAG and not some other setting.
Anyway, I look forward for your reply.
Feel free to ask guidance to any step of the procedure I posted above.
Click to expand...
Click to collapse
Hey guy. T tried to unbrick my phone with your instruction again and again then my phone have worked. Million thanks for your help :good::good::good:

Thanks a lot for your confirmation.
BTW, you did it the exact same way again and again, and after a few times of it, it just worked?
If you changed something, please explain so others, including me, will know for the sake of solving this kind of a problem.

[Q] Cannot flash Galaxy S4 GT-I9502?

Hey Guys,
I am trying to return a Galaxy S4 Duos GT-I9502 back to stock, for someone who attempted to root the device, which failed. I am however experiencing some difficulty doing so, and would appreciate some help, if anyone has any suggestions.
This is the screen on the device:
{
"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 am able to put the device into download mode, though I keep getting this error message when I try flashing the device in Odin.
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I am pretty confident that I have the correct Samsung drivers installed, and I have tried completely closing all of the Samsung Kies processes on the computer. I have even tried using a different computer, and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUBMG2_I9502CHUBMG2_CHU
I9502ZNUAME3_I9502CHUAME3_CHU
I have also tried the 'Firmware upgrade and initialization' option in Samsung Kies, though I keep on getting this error message, before it closes (I do not know what it says, Google translate doesn't give a good translation).
"Binary files are not registered U.S. Congress gyeongmu mouth mid-sprocket
Bow can proceed
Please check the binary file registration myeobu"
Does anyone have any suggestion / idea of what is going wrong? Any help would be highly appreciated!

Never mind, I was able to resolve the issue by re-flashing CWM recovery!

same problem
i have exactly same problem with I9502ZNUBMH4 version , does anyone know how to flash this device because i tried 100 time with different versions of odin , and every time i failed repaird it with cwm .
oh and the device won`t do a full wipe , every time i full wiped it my files didn`t deleted ?!

Samsung S4 GT-I9502 root / flash failed - HELP
Hey Guys,
I tried to root my Samsung S4 GT-I9502 (OS Android 4.3), for that I found this website:
http://marrkdaviid.com/2013/08/fix-caller-id-install-google-play-on-the-galaxy-s4-i9502/
But it failed (see more Information below) and I had the following error message and no wifi.
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I live in China and I just bought the phone, I needed 5 days to download the necessary files, because most download pages are blocked in China. So I am loosing my last nerve right now.
I am pretty confident that I have the correct Samsung drivers installed. I don’t have Samsung Kies installed. I have even tried using a different computer (Laptops), and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUCMG2_I9502CHUCMG2_I9502ZNUCMG2_HOME.tar.md5
I9502ZNUEMK3_I9502CHUEMK3_I9502ZNUEMK3_SVA.tar.md5
Someone with a the same problem tried the 'Firmware upgrade and initialization' option in Samsung Kies, but it didn’t work, so I didn’t try. (Here the link: http://forum.xda-developers.com/showthread.php?t=2382979)
Instead I tried a recovery. I used Odin 3.07 and the following file:
i9502-cwm-recovery.tar.md5
I got my phone back to work for a while, I reset the phone, just in case. But know I can’t switch the Wifi on and the phone wants to Reboot.
So I allowed the phone to Reboot, I clicked on “reboot system now” and then on “Yes – (I forgot what was written behind the Yes, but I didn’t just click on the normal Yes, I clicked on the Yes - …)
The problem here: The Phone changed to a China Unicom Screen and stayed like that. After 5 h I took the battery out, but I couldn’t restart the phone.
So I did an cwm recovery and know I am afraid to reboot. The Wifi is not working and I can’t find any information about how to fix it.
So please help me. Do I reboot? Can I already install SVA ROM, although I couldn’t flash the Stock Firmware? Do I send the phone back and give up?
Please let me know if you need any other information to be able to help me.
PS: This is the first time that I flash a smart phone. And although I already spent several days now, searching the internet for how-to-dos, tips & tricks, guidelines, Q&As and god knows what, I still do not fully understand what exactly I am doing here. Hence, I would be very happy to receive somewhat easy understandable answers.
Thank you so much for your help!
Anna

Philz 6.00.2
I have a similar problem.
I tried to install philz _touch_6.00.2-i9505.tar, by uisng Odin 3.09
Everything went OK. I got PASS! and my Samsung S4 i9505 rebooted into the stock ROM
However I cannot enter Philz. I tried to keep pressed volume Up + Home + Power but the phone goes immediately into the main Samsung screen. I have tried many combinations...the only working combination is:
volume Down + Home + Power > which leads to download mode (for Odin)
Thank you for your suggestions!
SA

Same problem, how did you fix it?
I have the same issue, how did you fix it? It's been a day that I've been trying to fix it. I've got the Exynos version I9500

[Q] Need Help restoring Nexus 10!!

Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
{
"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 I finally figured out the problem... I had to completely flah the stock image from fastboot, but my drivers were not up-to-date... so I guess it was kinda my own fault... sorry.... but let it be a cautionary tale for everyone, DRIVERS DO MATTER!!

Mancini_Rafael said:
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
View attachment 2410610
View attachment 2410611
View attachment 2410612
View attachment 2410613
Click to expand...
Click to collapse
Pm'ed you.
Sent from my Galaxy Nexus using XDA Premium HD app

I like wugfresh's Nexus Root Toolkit.

I had the same problem.
As suggested above, get the wugfresh nexus root toolkit. That has the option of flashing a stock rom from a soft-bricked device so long as you can get to the bootloader (which is where you are).

I had the same issue - I'm wondering how many others are getting this too. I'm in no way conversant with this kind of technical challenge so I had a few hours of stress thinking my tablet was knackered.
I tried mskips and wug's toolkits on my bootcamp partition in but couldnt get them to work. I tried following the manual fastboot recovery then ADB sideloading the image but that kept failing too.
In the end, I use the mac toolkits (here: http://forum.xda-developers.com/showthread.php?t=2063042) to get back to android 4.2, then let the device receive OTAs. The 4.4 OTA installed fine this way around.

Problem during flashing firmware

Hi All,
This afternoon I was trying to upgrade my LG G2 from KitKat to Lollipop using the how-to in this thread.
I have the D802 model and downloaded the German stock Lollipop (16 GB) for the D802 (which should be similar to what they are going to give Dutch users) and followed the manual step-by-step. So far so good. After 23% the phone gave me the error (ASSERT) in the Firmware Upgrade mode. I retried to install the upgrade a few more times, but every time it gave me the same error at different percentages.
{
"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 can enter the mode where I can restore the factory settings and delete everything, but for example the download mode didn't work (or I am doing something wrong). Every time I restart the phone it automatically goes into the firmware upgrade mode.
Does someone know how I can fix this?
Everyone's help is much appreciated!

Hi
I had the same problem, or something similar.
And i wrote it here:
http://forum.xda-developers.com/showpost.php?p=59891571&postcount=8
The only difference - is in our "ways of updating"
My LG G2 gave me message that there is available software update and that i should conect my phone to PC.
1. So i conected it with my PC through LG PC Suite, and went on "check software update"
2. After that, it started downloading update and instaling it, while G2 went to "Update firmware screen"
3. It stopped arround 23 % with "ASSERT" message.
4. I changed PC machine, and went to lap top because i thought it was driver related problem
5. I conected my G2 to laptop, this time with "LGMobile Support Tool", but before that i instaled all drivers again
6. Then used "Options > Recovery upgrade"
7. "LGMobile Support Tool" then downloaded update and started instaling it, while G2 was in an "Update firmware screen" mod, and stopped again like on PC around 23% with ASSERT message.
8. I put out my USB cable from phone and inserted again, and used "RETRY" option in "LGMobile Support Tool".
9. This time i got to around 30% of upgrading when ASSERT message came up.
10. I did all again and got around 40%, and again ASSERT message came up
11. So I was very persistant and I was reapiting this and I got to 50%, then 60%, then 70%. then, 80%, then 90%, then 92% and finaly got 100% of upgrading
After that, G2 rebooted, app were optimazing, and I got LG G2 working again, but i got messages "proces android.com has stoped" on every 3 seconds and i was without network.
12. Factory reset was solution, now everything is working very smooth, i am running lolipop 5.0.2 and i instaled now all my app and added my accounts.
My advice is, don't stop, repeat proces of updating for several times until you get to 100 % of upgrading software
This is very unusual, and I dont know what is causing this to happen, but it worked from 10th time

Gradjevinac said:
Hi
My advice is, don't stop, repeat proces of updating for several times until you get to 100 % of upgrading software
This is very unusual, and I dont know what is causing this to happen, but it worked from 10th time
Click to expand...
Click to collapse
It took a while, but eventually your suggestion worked Thank you!

Glad to help you.

thanks a lot! took 3 hours but worked ! you saved my day...

Had the same problem and lost a lot of time trying to figure it out. This thread finally put me on the right direction. Thank you!

Thanks for this topic! Saved my wall from my phone...

Bootloop Android 10: enablefilecrypto_failed boot issue after recent update

I got an OTA security update few days back. The update was done successfully. Then I ran out of charge and the phone switched off during usage. When I charged and tried turning back it on, the phone got stuck in the android one screen and it rebooted. It again got stuck in the android one screen and the following message opens up in android recovery mode.
Code:
Android Recovery
Nokia/Dragon_00WW/DRG_sprout
10/QKQ1.190828.002/00ww_4_10D
user/release-keys
Use volume up/down and power.
Code:
Cannot load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this device.
Then it shows options to select either Try again or do Factory data reset
The following code is shown at the bottom
Code:
Supported API: 3
Boot Reason: enablefilecrypto_failed
I found a similar issue in Nokia 7.1 after January update. The phone does not boot up. Is there a way to solve this issue?
I have some important data in my phone. Is there a way to recover them before resetting the phone?
Note: The phone is in stock condition with only usb debugging on.

Change slot, boot the device make sure there's enough storage available and then apply update.

same probelm , it return to recovery mode , any help

On these phones. If phone stuck on Android One screen.
And when doing factory reset from recovery, if device stuck at wiping data.
Then it is a dead EMMC.

Same problem, can anyone help?

today i tried to flash OSt service tool this type problem facing device... than find [15:15:42::203][03964] [FB]: [Recv] FAILError flashing partition : Write Protected this error.... thats mean motherboard damage.
Sent from my TA-1054 using Tapatalk

D-Mi said:
Change slot, boot the device make sure there's enough storage available and then apply update.
Click to expand...
Click to collapse
Tried it and no improvement. Could you explain in detail so that I'll check whether proceeded correctly or will try again.
Is there any way in which I can recover the data even before the problem being solved?

Jenish_SweetRascal said:
Tried it and no improvement. Could you explain in detail so that I'll check whether proceeded correctly or will try again.
Is there any way in which I can recover the data even before the problem being solved?
Click to expand...
Click to collapse
At this point there's no way to recover your data, and the guide to change the current active slot you can find in the below link
https://www.google.com/amp/s/www.te...-stuck-on-download-mode-after-ota-update/amp/
The issue mentioned might not be similar but the solution you're looking for could be it I had a similar problem with a 7.1 that can't boot after a security patch update and everytime the update will download and after restart the phone will throw error and ask to factory reset I couldn't test this method on that phone as the person had set it up for work after a reset and willing to hold till he can visit a service center. And he said he didn't have much storage at the time of update so it got corrupted somehow

I tried the method I mentioned by changing the slot, my current slot is b and update is supposed to install on a, a is corrupt or something as soon I changed active to a the device will bootloop in android one screen and go to failed page and ask for reset after which it will boot on slot b, also tried to install the Feb SP manually which installed fine via adb but again after reboot it will act same, so the only way is to visit a service center or better pay it directly for a bootloader Unlock service to avoid any future software problems

?
juwelrana091 said:
On these phones. If phone stuck on Android One screen.
And when doing factory reset from recovery, if device stuck at wiping data.
Then it is a dead EMMC.
Click to expand...
Click to collapse
R u sure bro....ost is detecting my phone though

emmc damaged device also detect fastboot... when u try to flash through ost tool u will get those error. check ost tool log data... if it say write protected than u should be sure emmc damaged
{
"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"
}
Sent from my TA-1054 using Tapatalk

Same issue I was facing but is fixed
So what did I do?
Downloaded stock ROM and installed using OST LA.
Then the update was installing but failed. [I was trying from last 1-2 months but getting same enablefilecryto_failed message but finally I solved it]
I downloaded OTA from website of same update and installed via ADB.
After installin OTA, It said it needs to "Format data" upon reboot.
I formated and mobile now has "Stock ROM".