Hello everybody. The thing is this. I have an Optimus L5 e615F (dual sim), and I was using it, when suddenly the phone rebooted. Since then, the phone is in a loop but NOT in a common boot loop. I mean, it's not stuck on the LG logo or similar. The phone boots to the screen when Android is checking the sd card. And probably it last 2-3 seconds and just reboot, and so on the same process infinitely. I hope somebody here knows some answer to my problem. Thanks everyone.
PD: I have already installed another original firmware with kdz and done a hard reset. But it's still the same.
carlosevides said:
Hello everybody. The thing is this. I have an Optimus L5 e615F (dual sim), and I was using it, when suddenly the phone rebooted. Since then, the phone is in a loop but NOT in a common boot loop. I mean, it's not stuck on the LG logo or similar. The phone boots to the screen when Android is checking the sd card. And probably it last 2-3 seconds and just reboot, and so on the same process infinitely. I hope somebody here knows some answer to my problem. Thanks everyone.
PD: I have already installed another original firmware with kdz and done a hard reset. But it's still the same.
Click to expand...
Click to collapse
have you tried taking the sd card out?
also do a hard factory reset (yes, although you flashed kdz)
mircea89fzr said:
have you tried taking the sd card out?
also do a hard factory reset (yes, although you flashed kdz)
Click to expand...
Click to collapse
Yes. I've done the same process with and without the sd card in the phone. But right now I noticed something very curious. For example, I installed a firmware from a different device, the same L5 but another kind, not the e615f but the e610 which is not dual sim. And the firmware jellybean has NOT the reboot-loop problem. But, anyway, that firmware is useless because the phone loose the touch-capability and doesn't recognize any sim. So I returned to ICE-Cream and to a original firmware designed to e615f but it's still the same.
Having that in mind, I think that is not a hardware problem, because the phone only reboots when android is loaded, but if I am installing some new firmware in the Download Mode, the phone has not rebooted (unless I want it happen). It's also very rare that when in JellyBean the phone doesn't reboot. So probably it could be a problem with IceCream but it's not very logical due to I've been using this version since I got the L5.
carlosevides said:
Yes. I've done the same process with and without the sd card in the phone. But right now I noticed something very curious. For example, I installed a firmware from a different device, the same L5 but another kind, not the e615f but the e610 which is not dual sim. And the firmware jellybean has NOT the reboot-loop problem. But, anyway, that firmware is useless because the phone loose the touch-capability and doesn't recognize any sim. So I returned to ICE-Cream and to a original firmware designed to e615f but it's still the same.
Having that in mind, I think that is not a hardware problem, because the phone only reboots when android is loaded, but if I am installing some new firmware in the Download Mode, the phone has not rebooted (unless I want it happen). It's also very rare that when in JellyBean the phone doesn't reboot. So probably it could be a problem with IceCream but it's not very logical due to I've been using this version since I got the L5.
Click to expand...
Click to collapse
If JB doesn't have the reboot problem, it must be software related. But I still don't understand how flashing a new ICS firmware still doesn't fix it. Definitely ICS encounters a system error and reboots. Maybe something at hardware-level (that only ICS accesses and not JB) doesn't function correctly. That is why flashing ICS from another device doesn't cause the reboot problem (that ICS doesn't have drivers for that particular hardware that causes problems). Try flashing JB and see if everything, I mean everything, works properly.
Related
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!
Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.
i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.
Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.
gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.
Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.
If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.
What's currently happening is my phone will boot and work normally except it appears the radio is not working then after 60-120 seconds freeze for a second then reboot. Wifi does work but I just see an x for the cell network signal and if I take out the SIM I get no notification. Curiously if I'm using the camera it seems to delay the rebooting by a few minutes.
I've tried http://forum.xda-developers.com/showthread.php?t=2432476 LG G2 Stock Firmware (Go Back to Stock) to no success, I was able to flash, it removed TWRP but I get the same symptoms anyway.
I've tried flashing the Rogers modem and this did not make a difference.
When I noticed this problem was when I was installing/testing some xposed modules, although it seems strange that they could break the phone in this way.
I've run out of ideas and although my phone isn't bricked per say it's near useless if it's going to reboot every minute or two. The phone doesn't reboot if I leave it in download mode or TWRP so this makes me think there's some hope.
Assuming it's not against the rules I'll PayPal anyone who comes up with the fix $50 CAD because right now I'm hooped.
Did you download and try flashing the exposed disabler zip file?
Sent from my LG-D803 using XDA Premium 4 mobile app
Of course there is hope!
All you gotta do is just download this ROM...
http://forum.xda-developers.com/showthread.php?t=2451592
Download it with your PC, then connect your phone to the PC to transfer the file.
The TWRP and flash it and that should fix it all.
Good luck
Do you have a gmail widget on your lockscreen? (Was worth a shot since others have reported varying issues with gmail widgets on the lockscreen).
I lost my recovery when I tried to go back to stock, and I can't seem to install any apps. I'm trying "upgrade recovery" from the LG Mobile Support Tool to see if that works. Otherwise I guess I have to find out how to root and flash a recovery entirely over ADB
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
mrsocksfox said:
I was able to restore the stock recovery and factory reset but that still didn't resolve the issue. Can someone provide a /system/ partition dump of a d803? I'm assuming there's something broken in there but I don't think flashing a ROM will solve that since flashing stock didn't seem to.
Click to expand...
Click to collapse
If flashing to stock didn't work then your phone may as well be defective...
crzykiller said:
If flashing to stock didn't work then your phone may as well be defective...
Click to expand...
Click to collapse
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
EFS. Flash or push your backed up EFS.
Steamer86 said:
EFS. Flash or push your backed up EFS.
Click to expand...
Click to collapse
I don't have one. I made a backup in TWRP but ended up losing it when trying to fix things :silly:. I believe I can still see my IMEI if that's any sign of things not being completely ****ed.
Hi I have LG G2 D802 . My problem is that my phone hangs a lot . I did hard reset but problem didnt go. After hard reset i tried to install custom built rom but still same problem. Then I re installed lolipop 5.0.2 still the same problem .. now
i have downgraded to kitkat and again same problem .. Even now when it hangs It turn off completely like it got bricked or something but it work some time and again after some use it hang.. now i have hardreset my device and putted on standby mood but phone was working fine after some use phone hanged again . I dont understand what is the problem with my LG G2
I am having the exact same problem on stock 4.4.2 with my D803. I have random reboots every few minutes. I suspect it is a hardware issue since the problem persisted even after returning to stock using kdz. Unfortunately, I don't have an EFS backup.
I have tried multiple other ROMS (CM12.1, DU, Cloudy 3.2 and 3.3) and all are even less usable than stock (reboots while I am doing the initial setup).
Any suggestions? I don't know what else to try and am ready to buy a new phone now as this G2 is basically unusable... I'd greatly appreciate any help.
mrsocksfox said:
It's not a paperweight yet, I can adb. I rooted it through adb I'm just not sure what the xposed module broke. It has to be something that persists across flashing stock but I don't have anything to compare against.
Click to expand...
Click to collapse
If you have restored it to stock ....... and you still have the problem, u may have a short somewhere in the phone. The only thing that remains the same is the hardware .... u have changed the software
Hi guys! I have been using [L5/L7][4.4.4][KTU84P][FINAL]Unofficial Paranoid Android 4.4 rom build by Cr3pT and yesterday i installed android tweaker 2, messed around with it a little bit and when I restarted my phone to apply the changes i got into a bootloop. Since then I tried literally EVERYTHING. I tried flashing the rom again, flashing the stock rom by making a zip out of kdz file, adb, wiping and formatting everything (except external sd), and many more (I can't even remember). The only available part of my phone is CWM 6.0.3.2. The one thing that is strange to me is that no matter what the computer doesn't recognise my device (I've tried on two different computers). This makes everything difficult, I can't use kdz updater etc. I have tried reinstalling the usb drivers several times and it's always trying to recognise the device with no success. Does this mean that the internal sd is damaged? Or I messed things up while formatting? I hope someone can help. Thank you.
EDIT: I was able to solve a problem, but it the solution is weird. So I had the stock rom and kdz updater, connected the phone in emergency mode without battery, then plugged the battery back. Although the pc didn't recognise my phone, I started the kdz update with default settings and here is the trick: I had to shake the phone while kdz was flashing the rom (I'm not joking).
thomekk91 said:
Hi guys! I have been using [L5/L7][4.4.4][KTU84P][FINAL]Unofficial Paranoid Android 4.4 rom build by Cr3pT and yesterday i installed android tweaker 2, messed around with it a little bit and when I restarted my phone to apply the changes i got into a bootloop. Since then I tried literally EVERYTHING. I tried flashing the rom again, flashing the stock rom by making a zip out of kdz file, adb, wiping and formatting everything (except external sd), and many more (I can't even remember). The only available part of my phone is CWM 6.0.3.2. The one thing that is strange to me is that no matter what the computer doesn't recognise my device (I've tried on two different computers). This makes everything difficult, I can't use kdz updater etc. I have tried reinstalling the usb drivers several times and it's always trying to recognise the device with no success. Does this mean that the internal sd is damaged? Or I messed things up while formatting? I hope someone can help. Thank you.
EDIT: I was able to solve a problem, but it the solution is weird. So I had the stock rom and kdz updater, connected the phone in emergency mode without battery, then plugged the battery back. Although the pc didn't recognise my phone, I started the kdz update with default settings and here is the trick: I had to shake the phone while kdz was flashing the rom (I'm not joking).
Click to expand...
Click to collapse
3.....
2.....
1.....
LOL!!!!
Really bro i'll quote you
Sent from my LG-E400 using XDA Free mobile app
Hi all,
Been using these forums for awhile to get help rooting devices, but I've finally got a problem I can't get resolved after searching for days. My T-Mobile S4 (testing with CM12) randomly froze last Friday, and upon rebooting it wouldn't stay in the OS for more than a few seconds before freezing and rebooting again. I went into recovery and cleared cache/dalvik but it didn't make a difference. It got to the point where it would freeze before letting me even unlock the screen. I chalked it up to running CM12 before it was stable so I wiped the phone and tried CM11. The flash succeeded fine, but the phone froze right after going through the initial setup wizard. Since then, I've tried:
Flashing various recoveries (CWM, TWRP)
Various ROMs (CM10, CM11, Paranoid Android, Samsung Stock)
Sideloading ROMs without an SD card inserted in case mine had issues
It seemed to be the most stable when I booted up a new ROM without a SIM card or SD card inserted, and left WiFi off. It still froze, but not as fast. I've since bought a used HTC One m7 to get by with but would really like to get the S4 straightened out so I can sell it. I managed to install logcat and get it running before a freeze but after inspecting the logs I couldn't find any trace of kernel panics or other errors.
Should I assume the phone has a hardware error? I'm open to any suggestions anyone might have. Thanks guys.
Well, since it happesn on various roms then it is most probably a hardware problem.
Or it has a fault in a partition that is unaffected by rom flashing.
GDReaper said:
Well, since it happesn on various roms then it is most probably a hardware problem.
Or it has a fault in a partition that is unaffected by rom flashing.
Click to expand...
Click to collapse
That's what I was afraid of. Couldn't find any kind of bootable hardware diags for the phone either
drew_t said:
That's what I was afraid of. Couldn't find any kind of bootable hardware diags for the phone either
Click to expand...
Click to collapse
Don't know if it might help, but try a different bootloader and modem
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?