Hi my mobile is now stuck on elephone logo will not go further I can access recovery but there are no flash able rom in recovery flash tool doesn't work anyone got any ideas?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Same ...
Hi,
Same problem for me.
Blocked on Elephone logo, sometime blocked on "optimizing add 96 or 115, nothing more and very hot temperature
Don't know what to do ...
Potential Fix
This happened to me today.. literally 3 days after getting the phone. Not sure if it'll work for everyone, worth giving a go.
1 - You want to plug charger in while that message("Android is starting optimizing apps x of y") is still on the screen..
2 - Hold the power button till it restarts.
3 - This will then restart the phone and it should get the phone to boot up.. at this point my launcher kept restarting or flickering... so i held the power button until the reboot menu came up and selected shutdown and unplugged the charger from the phone..
4 - After this I waited 5 mins to let the phone cool down.
5 - Then I plugged the charger back in and pressed the start button to boot up the phone and its been work well since.
If this works then go ahead and post this where u see anyone else having the same issue.
should be fine if you just reflash the rom with sp flashtool
I had to go into recovery turn off mobile them refash all okay now just could only do it if I went into recover and turned mobile off then flashed
Sent from my GT-I9505 using XDA Premium 4 mobile app
try holding power and volume up
I got My elephone m2 after a couple of weeks it started to freeze, eventually it froze and I could not unfreeze it. Tried everything. It seems elephone have this problem on all their phones. It's a shame because it is a nice phone. Have sent it back for a refund.
Today, mine rebooted for some reason. I had it in my pocket and when I pulled it out I probably hit the button on the side for the power. I could just see that it said; "android is starting... optimizing app 116 of 148", then it went off.
After that it started with the moving Elephone logo and after a minute or so the Elephone Logo just stayed still and nothing happened anymore(waited more than 5 minutes).
All this time the charger was pluged in.
I held the power button untill the phone rebooted and after that it started again with the "android is starting... optimizing app x of y", and started correctly after the optimization was done. @shahr77 thanks for the tip!.
---------- Post added at 06:20 AM ---------- Previous post was at 06:20 AM ----------
Today, mine rebooted for some reason. I had it in my pocket and when I pulled it out I probably hit the button on the side for the power. I could just see that it said; "android is starting... optimizing app 116 of 148", then it went off.
After that it started with the moving Elephone logo and after a minute or so the Elephone Logo just stayed still and nothing happened anymore(waited more than 5 minutes).
All this time the charger was pluged in.
I held the power button untill the phone rebooted and after that it started again with the "android is starting... optimizing app x of y", and started correctly after the optimization was done.
@shahr77 thanks for the tip!.
Related
http://forum.xda-developers.com/showthread.php?t=1751065
http://forum.xda-developers.com/showthread.php?p=23181182#post23181182
Being a new user of android phone and a noob, I followed all the instructions in the above posts, EXCEPT the INSECURE KERNEL part.
I used the Unsecure kernel for LT28i 6.0.F.0.72 (found out after boot loop that my phone is actually LT28h)
After I entered all those commands (which appeared successful with 0 bad blocks and rebooting finished), my phone booted, showed the sony icon and turned off just to show that icon a few secs later (loop starts). After various attempts in restarting it, I somehow managed to press the power and vol up button at the same time for secs, and it vibrated once. The loop continues. Shortly after that, I tried again, and held the two buttons longer. This time, the phone vibrated once, then after a short while, it vibrated thrice in a row, and the loop stopped. Now my phone cannot be turned on, and is unresponsive.
Can someone please help save my baby:crying:
Meaning your device is now softbrick. Read the thread in General
Sent from my LT28at using Tapatalk 2
accts said:
Meaning your device is now softbrick. Read the thread in General
Sent from my LT28at using Tapatalk 2
Click to expand...
Click to collapse
But my computer cannot detect the phone, so i cannot reset it via the computer
Galaxim said:
http://forum.xda-developers.com/showthread.php?t=1751065
http://forum.xda-developers.com/showthread.php?p=23181182#post23181182
Being a new user of android phone and a noob, I followed all the instructions in the above posts, EXCEPT the INSECURE KERNEL part.
I used the Unsecure kernel for LT28i 6.0.F.0.72 (found out after boot loop that my phone is actually LT28h)
After I entered all those commands (which appeared successful with 0 bad blocks and rebooting finished), my phone booted, showed the sony icon and turned off just to show that icon a few secs later (loop starts). After various attempts in restarting it, I somehow managed to press the power and vol up button at the same time for secs, and it vibrated once. The loop continues. Shortly after that, I tried again, and held the two buttons longer. This time, the phone vibrated once, then after a short while, it vibrated thrice in a row, and the loop stopped. Now my phone cannot be turned on, and is unresponsive.
Can someone please help save my baby:crying:
Click to expand...
Click to collapse
By the way, my xperia ion's factory setting is ICS
Have you waited for the battery to die?
Sent from my LT28i using xda premium
King Cole said:
Have you waited for the battery to die?
Sent from my LT28i using xda premium
Click to expand...
Click to collapse
no. but there is no light at all when it's connected with the charger, so i have no idea if its charging
Galaxim said:
no. but there is no light at all when it's connected with the charger, so i have no idea if its charging
Click to expand...
Click to collapse
It usually takes a long time before the red led comes on.
It took me 36hrs, before I could get my phone back to normal.
So be patient.
ganeshbiyer said:
It usually takes a long time before the red led comes on.
It took be 36hrs, before I could get my phone back to normal.
So be patient.
Click to expand...
Click to collapse
Took me about 28 hours once. I wish there was a battery kill switch under one of the covers.
jeriku said:
Took me about 28 hours once. I wish there was a battery kill switch under one of the covers.
Click to expand...
Click to collapse
I do not wait for battery to die, if it is a boot loop. just press power + Vol Up buttons simultaneously and hold till the phone vibrates 3 times. Then connect the charger and let it charge.
The problem arises when the screen is on and nothing happens. Then you need the battery to die. But Doomlord told me just to plugin the charger and wait for a long long time.
I have done it all.
ganeshbiyer said:
I do not wait for battery to die, if it is a boot loop. just press power + Vol Up buttons simultaneously and hold till the phone vibrates 3 times. Then connect the charger and let it charge.
The problem arises when the screen is on and nothing happens. Then you need the battery to die. But Doomlord told me just to plugin the charger and wait for a long long time.
I have done it all.
Click to expand...
Click to collapse
Exactly, screen was on but no response from the phones hardware. Took almost 28 hours for the phone to discharge.
I was lucky though, after the recharge I was able to catch CWM, wipe everything and restore a good back up. This was by accident, as I turned the phone on by mistake, I meant to put it in flashmode.
Galaxim said:
http://forum.xda-developers.com/showthread.php?t=1751065
http://forum.xda-developers.com/showthread.php?p=23181182#post23181182
Being a new user of android phone and a noob, I followed all the instructions in the above posts, EXCEPT the INSECURE KERNEL part.
I used the Unsecure kernel for LT28i 6.0.F.0.72 (found out after boot loop that my phone is actually LT28h)
After I entered all those commands (which appeared successful with 0 bad blocks and rebooting finished), my phone booted, showed the sony icon and turned off just to show that icon a few secs later (loop starts). After various attempts in restarting it, I somehow managed to press the power and vol up button at the same time for secs, and it vibrated once. The loop continues. Shortly after that, I tried again, and held the two buttons longer. This time, the phone vibrated once, then after a short while, it vibrated thrice in a row, and the loop stopped. Now my phone cannot be turned on, and is unresponsive.
Can someone please help save my baby:crying:
Click to expand...
Click to collapse
Hello
I'm having the same problem applied a file *. Elf in my xperia ion and so now he is in the boot loop.
I wonder if you could reconfigure to make the correction of the error if you have any response possitiva please share with me so I can follow the same procedure on my xperia ion.
Thank you.
Antonio Rodrigues
I was using my phone normally today and it suddenly died on me and rebooted. Now it won't boot at all and it's stuck on the Galaxy Note II N7100 logo and it'd die out again and then show the Galaxy Note II N7100 logo again, never reaches the samsung boot up logo even. Pressing volume buttons for recovery mode does not work at all, it just keeps on rebooting. Pressing for the download page works but if you press volume up or volume down or do nothing even for a few seconds it reboots again!
My battery was at 60 percent prior to this and I was not doing anything at all. I was using Wanam's rom with adam kernel + s4 theme for two weeks now with no hitch.
Another weird thing about this whole thing is that if I pop the battery at the back it automatically boots up without me having to press any buttons. I've tried EVERYTHING now and I really hope my phone did not just die on me. Charging the phone sorta works but Im not to sure because I have a feeling it reboots without having any actual charging done.
kingofthebraves said:
I was using my phone normally today and it suddenly died on me and rebooted. Now it won't boot at all and it's stuck on the Galaxy Note II N7100 logo and it'd die out again and then show the Galaxy Note II N7100 logo again, never reaches the samsung boot up logo even. Pressing volume buttons for recovery mode does not work at all, it just keeps on rebooting. Pressing for the download page works but if you press volume up or volume down or do nothing even for a few seconds it reboots again!
My battery was at 60 percent prior to this and I was not doing anything at all. I was using Wanam's rom with adam kernel + s4 theme for two weeks now with no hitch.
Another weird thing about this whole thing is that if I pop the battery at the back it automatically boots up without me having to press any buttons. I've tried EVERYTHING now and I really hope my phone did not just die on me. Charging the phone sorta works but Im not to sure because I have a feeling it reboots without having any actual charging done.
Click to expand...
Click to collapse
It seems like that power button got stuck.
Simonna said:
It seems like that power button got stuck.
Click to expand...
Click to collapse
HOLY COW YOU'RE RIGHT!! I CAN'T BELIEVE THIS!! It works now after one hour!
Should I sell my phone now before it goes bad or do you think this is just a random occurance?
You probably hit the power button without knowing it and got stuck. This could be just a simple occurance. Or it got damaged in which case you have to change the power button contact. Not easy but it can be done.
Sent from my GT-N7100 using Tapatalk 4 Beta
Was doing some research and some people have also experienced this when they accidently dropped liquid unto the power button. I was washing my case awhile ago and there's a remote possibility that this happened albeit only a little. After I got it working it only happened once again and it's been working perfectly since.
I was getting really frantic awhile ago because I really needed my phone at that time lol
Sent from my GT-N7100 using Tapatalk 4 Beta
Hi guys. I'm in trouble. I have a rooted nexus 7 2013 which was working just fine for a couple of months. Then abruptly it seems to have bricked itself.
After checking my mail, I closed my magnetic case as usual. Then when I opened the case as usual a few hours later I discovered it had powered itself off. Strange! But I just pressed the power button and it started booting up. However it got to the X screen and just stayed there. I rebooted several times always with the same result.
So I tried powering up with the down volume and power button pressed and it took me to a screen with "restart bootloader" which I did, and then 'start". But no difference : it stays at the X screen and no further.
I then went to the recovery screen and got the open android robot with a RED triangle and explanation mark. Going power up or down did not bring up any other options
Looks like I'm really bricked!
Trouble is that I'm away from home and will not be back for 3 weeks. I therefore don't have a computer to connect to and try to do something. Only the nexus 7 to work with.
The nexus is rooted and I have TWRP recovery backups on it but no way to access them.
Is there anything I can do to recover from this brick? I really need help and I'm an android newbie.
Ok, so here's the deal. Bought the watch and charged it to 100% before turning it on. Fired it up, synched with android wear fine and it wanted to update. I ran the update but it kept getting to the end and complaining about how there was an error and to try again. I threw it back on the charger and it had dropped all the way down to 64%!
I charged it back up and did the update. I was stuck on the android icon for about 10 min then it rebooted and was stuck at "Just a minute" for a good 15 min or so. I did a hard reboot. Since then I have performed a hard reboot multiple times. For awhile there it was giving me the option to reset, which I tried 3 times. I kept getting stuck on "just a minute" when trying to sync.
Now, after the last reset, I can't get past the big motorola logo when it boots. Usually it shows the logo and then has the gears moving through the logo. But now, it just shuts off and comes back on to that logo.
GaresTaylan said:
Ok, so here's the deal. Bought the watch and charged it to 100% before turning it on. Fired it up, synched with android wear fine and it wanted to update. I ran the update but it kept getting to the end and complaining about how there was an error and to try again. I threw it back on the charger and it had dropped all the way down to 64%!
I charged it back up and did the update. I was stuck on the android icon for about 10 min then it rebooted and was stuck at "Just a minute" for a good 15 min or so. I did a hard reboot. Since then I have performed a hard reboot multiple times. For awhile there it was giving me the option to reset, which I tried 3 times. I kept getting stuck on "just a minute" when trying to sync.
Now, after the last reset, I can't get past the big motorola logo when it boots. Usually it shows the logo and then has the gears moving through the logo. But now, it just shuts off and comes back on to that logo.
Click to expand...
Click to collapse
sounds like a boot loop, which sucks because i don't think there's a known way to get into recovery or if the watch even has one. i'd email motorola if i were you.
Ok, I left it off for about 30 minutes and finally got it to power back on so I could reset it again. Once again, it reset and wants to download an update. It downloads, reboots, installs, reboots and then just sits at "just a minute..."
This thing is a serious pain to get up and running. Any ideas? I don't know what else to try. Ive tried pairing it with a HTC One and a Galaxy Note 3.
*EDIT*
Ok, after 2 more tries I finally got it to the point where I saw a new boot screen. I figured that was good news. Now its been sitting on the Android boot screen. By that I mean the green, blue, red and yellow orbs have been flying around for 10 minutes.
wiredout46 said:
sounds like a boot loop, which sucks because i don't think there's a known way to get into recovery or if the watch even has one. i'd email motorola if i were you.
Click to expand...
Click to collapse
It looks like if I press and hold the power to shut down, then press and hold for a good 10 sec or so when booting back up it will boot me to a screen that shows:
"Bootloader version: 940
Device is LOCKED. Status Code: 2
Battery OK
Connect USB Cable"
Thats about as far as I can get now. It refuses to go past the android screen now.
*EDIT*
OMG... so I decided to fire it up and start trying to power it down immediately. I did that 3 times in a row and it booted up to the Android Wear pairing screen. I paired it and... its trying to download something again. I can't win. I may have to take this thing back and wait for the next LG watch. I can't figure this out.
GaresTaylan said:
It looks like if I press and hold the power to shut down, then press and hold for a good 10 sec or so when booting back up it will boot me to a screen that shows:
"Bootloader version: 940
Device is LOCKED. Status Code: 2
Battery OK
Connect USB Cable"
Thats about as far as I can get now. It refuses to go past the android screen now.
*EDIT*
OMG... so I decided to fire it up and start trying to power it down immediately. I did that 3 times in a row and it booted up to the Android Wear pairing screen. I paired it and... its trying to download something again. I can't win. I may have to take this thing back and wait for the next LG watch. I can't figure this out.
Click to expand...
Click to collapse
Try to get it to reset not restart. Then leave it go until it's fully charged again and retry.
dottat said:
Try to get it to reset not restart. Then leave it go until it's fully charged again and retry.
Click to expand...
Click to collapse
Got it to 100%, reset it. Rebooted a few times and it sat on the motorola logo for about 25 minutes, never moved. Powered down and on, now I'm in this damn android logo boot loop again. What a PoS.
GaresTaylan said:
Got it to 100%, reset it. Rebooted a few times and it sat on the motorola logo for about 25 minutes, never moved. Powered down and on, now I'm in this damn android logo boot loop again. What a PoS.
Click to expand...
Click to collapse
Is possible you got a dud.
So this morning I made s trip back to best buy and luckily they had 2 left in stock. I wasn't that aggravated because my last 360 had a dead pixel anyway.
With the replacement I did everything the same as I did last time and this time around it updated and did its thing flawlessly. So yea, sounds like I just have bad luck and got a dud.
GaresTaylan said:
So this morning I made s trip back to best buy and luckily they had 2 left in stock. I wasn't that aggravated because my last 360 had a dead pixel anyway.
With the replacement I did everything the same as I did last time and this time around it updated and did its thing flawlessly. So yea, sounds like I just have bad luck and got a dud.
Click to expand...
Click to collapse
Lucky to get one first round. Lucky to get a replacement the day you took it in. Glass half full. Enjoy your new watch!
GaresTaylan said:
It looks like if I press and hold the power to shut down, then press and hold for a good 10 sec or so when booting back up it will boot me to a screen that shows:
"Bootloader version: 940
Device is LOCKED. Status Code: 2
Battery OK
Connect USB Cable"
Click to expand...
Click to collapse
Just picked up my moto 360 and this is the screen I see when I first booted it up, so I have no idea what the battery level is or what to do for that matter.
---------- Post added at 10:24 AM ---------- Previous post was at 10:06 AM ----------
Ok maybe I acted too quick but I forced it off then put it on the charger for several minutes and automagically it booted up and seems to be working.
This is embarrassing, but I was trying to install Pokemon Go on my G4 and the phone got really hot and rebooted. It never came back. Just went into a boot loop. I found instructions online on how to do a master reset with the power button and volume down letting it up briefly when seeing the logo and then pressing it again and letting it boot. I answered the question about deleting all user data and then answered it again. It said it was erasing data, then froze for a few hours at "optimizing apps" on one of the steps while I left it plugged in. I eventually pulled the battery to get it to respond again and now it just shows the LG logo and then goes dark. While dark it doesn't respond to button presses or let me try again to power it on, etc.
Any chance of me getting this phone working again? Is there anything else I can try aside from the master reset that I've already tried?
Hello if you look under the battery and your serial number starts with 505 or close its dead.
Sent from my LG-H815 using XDA-Developers mobile app
Eudmin said:
This is embarrassing, but I was trying to install Pokemon Go on my G4 and the phone got really hot and rebooted. It never came back. Just went into a boot loop. I found instructions online on how to do a master reset with the power button and volume down letting it up briefly when seeing the logo and then pressing it again and letting it boot. I answered the question about deleting all user data and then answered it again. It said it was erasing data, then froze for a few hours at "optimizing apps" on one of the steps while I left it plugged in. I eventually pulled the battery to get it to respond again and now it just shows the LG logo and then goes dark. While dark it doesn't respond to button presses or let me try again to power it on, etc.
Any chance of me getting this phone working again? Is there anything else I can try aside from the master reset that I've already tried?
Click to expand...
Click to collapse
send it back for reapir.
hi, mine was 509. It died 2 weeks ago, showing only "LG life is good" if trying to boot it. No way into recovery. (did boot one time very slowly to lockscreen before the definitive death)
This seems to be the same for you.... dead CPU I suppose. I'm still waiting for the repair.
(curious about the 505 asserted here, since mine was higher)
Hello the first 3 digits of serial number indicate date of manufacture, and the early ones have a manufacturing defect.
Sent from my LG-H815 using XDA-Developers mobile app
Hello,
mine was 510 and died on me 4 weeks ago, (boot loop with only LG logo) as it died from overheating (or at least was very hot when die occured), I tried to cool it and it was "succesful"
It put it in the freezer for some time and then could boot it on TWRP and make a full backup (I left it in the freezer the whole time)!
boot at normal temp lead to black screen in 10-15secs. I sent it back for repair (motherboard replacement was made in less than 1 week by Lg France), I am now waiting the answer from Lg developer to unlock the bootloader again.
I guess you can at least try and see if you can have the same result as me.
Marc
G4 bricked, possibility of resurrection?
Click to expand...
Click to collapse
No.