Hello guys.
I have an LG L5 (E610) that is having a very strange behavior.
It started by throwing a lot of ANR with different applications (Google Play Store, Play Services, Facebook, and others).
So, seeing this, I decided to do a factory reset. After reboot, what is my surprise that I see everything as I had before. All the applications, all the data, everything.
With this, I tried almost everything at the moment. And by saying that, I mean:
- Tried to follow the key combination for the recovery, it goes to recovery, I see the Android and some progress bar moving, but after the reboot, the system remains with no change;
- When on the system, I uninstall applications, they seem to be uninstalled, but after a reboot all the applications are back.
- Tried to root the phone with more than one process, no success. I cannot install any application. Not via play store, not via adb install, there is no way;
- Tried to flash a recovery img, to try to clean cache partition from there, no luck. From Fastboot it says everything went well, but when I reboot, everything is the same;
- In fastboot, I tried to erase cache and userdate partitions, no luck. When I try, i have a message saying "FAILED (status read failed (Too many links))". This happens with all the partitions. I even tried to erase the system partition, and I have the same response. Strange thing is that after this error, the phone reboots and goes directly to the system;
- Tried with KDZ images and tools to install different versions, I receive errors during the deployment and at the end the phone reboots. Again, the same system is installed as before. No changes.
As of now, I was trying to understand if there is any problem with the internal flash system. Maybe it is corrupted and is causing all these issues.
The thing is, as the phone is not rooted, I cannot launch a e2fsck to the maybe faulty mmcblk0pXX
The phone has a stock ROM based on Android 4.0.3 (build IML74K / LG-E610-V10e-JUN-30-2012)
I am out of ideas, I've looked around here at XDA, Google and I have no other ideas to try.
Does anyone have another suggestion?
Is there something else I can do to try to make the phone live again?
Any help someone can provide will be very much appreciated..
Now this is what I call a coincidence.
About 2 years ago, a friend of mine asked me for help with her E610. Almost all actions were giving us ANRs. Whatever you do, i.e. unsinstall, install, change, delete... after reboot/reset were all there, even notifications! Tried KDZ updater, and, while the update was OK without signs of errors or so, after reboot - nothing, everything was like before. After trying to find a solutions by hundreds of ways, with adb and fastboot commands (all partitions&folders were locked, no read, no write, and you can't see any file, tried root to no avail), L5 got bricked. She already got a new phone and this LG was laying there without any use.
Three days ago I decided to try again, with no hope tbh No screen, no vibration, nothing, apparently dead. But, I could install Qualcomm drivers and my Windows can see it in download mode. I think that the only way is to flash the phone with LGFlashTool and using COM port. I already extracted *.dz from *.kdz but I need the dll for FlashTool. Found 2 or 3 webs with this dll, but you need a 100 bucks subscription :crying: If anyone can upload that dll I'd be very happy to try to flash this phone I'm really big n00b in this, just a plain phone user, nothing more, so don't blame me if I said something wrong
Many thanks in advance.
same problem
Hello! Same problem...
My L5 is making me crazy... It has CyanogenMod 10 nighlty. A friend of mine was using it and he tried to install the GAPPS after he did a factory reset. I have no idea what guide he used but it got soft bricked... It's constantly showing a "stopped working" message and after a while reboots by itself.
I tried to do a factory reset but it always returns to the same point, same apps installed, everything like the reset never happened. I even used CWM to reset it and it allways goes back to the same recovery point.
After a while I decided to flash a stock room but here's the problem: I can't get into emergency mode.
After reading ALL post about it I found that there's at least three ways of entering EM, (1) down VOL and plug in usb cable without battery; (2) down+up VOL and plug in usb; (3) down+up VOL + power botton.
Conclusions:
(1) - gives me a screen full of code like a command line
(2) - White screen
(3) - White screen
I've read ALL the unbrinking post on the internet, including xda, and none of them helped.
The KDZ Updater never recognizes the phone. I installed all the drivers but everytime I plug in the phone it installes the same LGE MTP drive...
Can anyone help, please?!
How to enter Emergency mode? How to flash another rom?
Alright so here's what happened. Last night I decided to update to the latest Cyanogenmod nightly. Turns out that was a bad idea, because it blackscreened on me. Ok, so I flashed the stock firmware, it was working. I decide to reinstall TWRP back on it. It didn't seem to take so I just said "**** it" and went to sleep. I wake up the next morning and what do I see? "Secure booting error Error: Boot Certification Verify!" No download mode, no recovery. So alright, I've followed the guide here: http://forum.xda-developers.com/showthread.php?t=2582142 but I hit a roadblock. Now this is where things become weirder. When I plug my phone in to USB in its current state, it's kind of hard to explain, but here's what it does: The backlight flashes on and off constantly. In Windows (currently in Linux right now as per the guide) it acted as if it kept trying to mount itself. Windows didn't like this at all because apparently it was doing it constantly, and bringing up a lot of dialog windows with multiple drive letters telling me to format it. Now I suspect the problem has carried over to Linux as well, meaning I can't push the images I need to to my phone in order to fix it, since it won't mount itself properly. Yes, I even tried disabling automount like the guide suggested and that didn't help. I'm guessing it's a bootloop issue? I dunno. I'm completely stuck, frustrated, and I really hope I don't have to buy a new phone. Any suggestions? I really need help with this. Thanks.
The long list of tons of drives (and no Download mode) is fairly easy to fix thanks to the solution at:
http://forum.xda-developers.com/lg-g...6#post56739916
To simplify, just download his premade package for the D800 (he lists other versions in the description of his YouTube video) at https://mega.nz/#!mN0SkDpb!1R36L-F05...88X5OuIqwNdezM
and also download and install the Qualcomm drivers from here:
http://www.mediafire.com/download/pb...SB+Drivers.rar
In the instructions he shows Computer Management, a Windows tool. If you are unfamiliar, you can find it under Control Panel -> System and Security -> Administrative tools (click on it)
Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!
Hello guys, I have this weird A3000-H problem.
So the tablet boots normally, it loads in one particular state every time, like it's booting an image. After a while or if you try to do something, running a program, uninstalling, changing settings it's starts the cascade of pretty much "every has stopped working" and it's like that until you restart it and it's all over the same again.
So far I've tried everything I could scour from the internet, XDA forums included.
• I've tried to flash new stock rom 4.2.2, then I tried the 4.4.2 from Hesham.
If I use an older, version 3 SP Flash Tools it gives me this error at the end:
imgur com a5oKTLw.png
If I use version 5+ of SP Flash Tools it gives me an "OK" download or upgrade, but when I disconnect and turn on the tablet it's in it's same previous state, it didn't change anything.
• I tried full format - it did absolutely nothing despite SPFT giving me the okay
SPFT memory test returns this error : .imgur com / jbSUwV5.png
• I tried writing memories - nothing changes despite getting on OK message.
• I tried to fastboot CWM - I can't make the tablet to enter the mode, it just restarts and boots in it's previous state.
• I've tried to connect it to PC and delete folders manually, despite windows saying the folders are deleted and not showing them anymore, as soon as I reconnect the tablet again they show up as they were. It's like the on board memory is locked to writing anything on it.
• Of course I tried manually resetting to factory settings, uninstalling software from the tablet and so on, but that just makes the errors of "stopped working" to pop and restart to same condition.
I would appreciate any help at this point, I'm about to give up on it.
P.S.: I can't post whole links yet so I had to improvise a bit.
I think I have an unsolved problem. I know it doesn't exist, but it's very hard to find it.
I know it's not the Plus, but the Model is the Moto C XT1754 (NAMATH) Android 7.0 Nogaut - NRD90M.060
And there is no specific topic for it, but they are very similar and I thought I could post it here.
It's a very complicated problem, so I'll explain in detail what happened and why I had to come here to solve it.
(translated)
- STARTING:
I installed a TWRP through the app, without unlocking the Bootloader.
Whenever I turned it on, at boot still, the message appeared:
'red state
Your device has failed verification and may not work properly
Your device will boot in 5 seconds'
But it called normally.
I installed 'Magisk Manager 24.2' by zip and app afterwards.
I activated 'Zygisk' and in DenyList I activated/hidden from Google Play Services completely. All.
I restarted the smartphone and Sitema started having numerous errors. Most of the apps that I opened, closed with error, and other apps in the background too, mainly Google Play Services.
I tried to solve this but I couldn't because the smartphone was unusable.
I decided to format by TWRP.
But when I tried to restart the device, I always entered TWRP and continued that message in Boot ('Red State Your Device...')
I decided to reinstall Stockrom from Moto C XT1754.
When I tried to install Stockrom through flash_tool, I couldn't.
It always gives error.
'BROM ERROR : S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early.
[HINT}:'
or this one is the most common:
'BROM ERROR : ?? (0x1)
[HINT];'
I even tried installing a Custom Rom via Sdcard , 'Viper-namath-20171206-Coral-v3.1.1-UNOFFICIAL' with the GAPPs, etc.
I can install the ROM. (but the GAPPS gives an error at the end of the installation) 'open_gapps-arm64-7.1-micro-20220215'
But I think this case is because it is not installing the Custom ROM correctly. (Because of the Locked Bootloader? Maybe... I'm kind of a layman on the subject)
Because when I restart the device after installation it goes back to TWRP.
I can't get into Fastboot mode with the command by the buttons on the device, only by TWRP when I access 'Reboot>Bootloader'.
Reboot and go to fastboot (Black screen, down there written '=> FASTBOOT mode...'
I've already tried to recover/rescue the device by Motorola/Lenovo's 'Rescue and Smart Assistant'. But when I try to rescue it (with it connected to TWRP) it asks to accept the message to enable USB debugging.
But I don't have access to this window through TWRP.
Here comes the big question, why I am not able to solve my problem:
I think my 'USB Debugging' was off/disabled before I erased everything (formatted).
I'll try Stockrom's Flash through TWRP to see if it solves the problem, but I don't think it will.
I think the problem may be with the 'USB Cable' as well. He's old. I tested with a non-original USB cable that I had to see and I can't either, the errors persisted.
I plan on getting another original to test as well.
Just an observation.
My device is being recognized as 'USB MTP Device' (under 'Portable Devices')
If anyone can save me, I'd really appreciate it!
Thanks in advance for all the help! Every opinion matters!
And when I give the command 'ADB Devices' my device appears 'unauthorized'
'ZW3223CGWK unauthorized'