[Q] Boot Loop after Update - Focus General

Hi guys, I recently received this Samsung Focus from my friend, it's very used, but still works. Anyways, I went to try to update it, and about half-way through, Zune software said "waiting for reboot" or something like that, and it'd been going overnight. So I tried my Google Fu, but the only tricks were to restart the phone by holding down the power button manually, or unplugging it and taking out the battery. Now the phone gets about 10s on the SAMSUNG logo, when it then decides "nope, fsck it", and proceeds to reboot. I'm new to the Windows phone platform, so please be gentle. I've tried searching on the forums, but nothing really matches my exact case.
Thanks guys!

Bump!
Sent from my Nexus 7 using XDA Free mobile app

Related

[Q] Problem my LG E900 not boot only LG logo!

Greeting
I ask someone for help. My Samsung E900 has worked perfectly until yesterday ... After changing the Regional Settings sought to be restarted to accept new settings. After that phone at the time of ignition appears LG logo and the fit is a few seconds the screen clears and the LG logo appears again, and so constantly ..
Any ideas?
Thanks
Update - Problem resolved
Hi
I resolved the problem ... means COOLD START is on the keys...
Hold down the VOLUME + - and the CAMERA button and turn the POWER button the phone ...
Phone back to factory settings
Samsung? LOL. And I think this will work even if you don't hold the camera button, but I must try it again...
LG
sorry LG not Samsung LOL
Reset want do the job
Any other ideas?
After a reset i have the same symptoms again.
thx anyway
That's weird!
solved?
did u solve the it?
i have the same problem, it freezes on the "LG" screen, nothing more happens....
i tried the cold boot thingy but then it just sais "cold boot" and then nothing happens...
any one knows if there is something that can be done to make it work?
lamanfluff said:
did u solve the it?
i have the same problem, it freezes on the "LG" screen, nothing more happens....
i tried the cold boot thingy but then it just sais "cold boot" and then nothing happens...
any one knows if there is something that can be done to make it work?
Click to expand...
Click to collapse
Pulling the battery for 10-30 secs and then boot seems to be the universal problem solver for WP7 phones.
/J
my phone was delivered without the battery inserted, it it was out for like a couple of days. Still gets stuck at the "LG" screen...
lamanfluff said:
my phone was delivered without the battery inserted, it it was out for like a couple of days. Still gets stuck at the "LG" screen...
Click to expand...
Click to collapse
Then return it as faulty as it should load unless borked somehow.
/J
Yes i Will return it on monday unless someone knows a way to restore it.
It's possible to start it in 3 modes.
1. Hold down the volume buttons + camera + power button. It then sais cold boot and then nothing more.
2. Vol down + camera + power. Then it sais emergency download, and my computer finds it
3. Camera + power. Shows a phone, cord and computer.
I tried the lg phone support tool and it sais the phone already are up to date.
Isn't there a way to load the windows phone 7 software onto the phone somehow?
Would really like to do it so I won't have to return it. I bought it of eBay, it is a customer return, so guess the guy before me tried messing with it to update it. And the company that sold it to me did not check if it was functioning before selling it to me..
lamanfluff said:
Yes i Will return it on monday unless someone knows a way to restore it.
It's possible to start it in 3 modes.
1. Hold down the volume buttons + camera + power button. It then sais cold boot and then nothing more.
2. Vol down + camera + power. Then it sais emergency download, and my computer finds it
3. Camera + power. Shows a phone, cord and computer.
I tried the lg phone support tool and it sais the phone already are up to date.
Isn't there a way to load the windows phone 7 software onto the phone somehow?
Would really like to do it so I won't have to return it. I bought it of eBay, it is a customer return, so guess the guy before me tried messing with it to update it. And the company that sold it to me did not check if it was functioning before selling it to me..
Click to expand...
Click to collapse
You could of course flash the phone with new firmware and see if it fixes the problem, sounds like someone managed to mess up with your set.
There are some information around here how to flash the phone if you feel up for it.
/J
Ok but do u think The firmware is The problem? The LG tool showed that it was up to date, isn't it just the windows phone 7 software that is missing? I am not sure, but wouldn't the phone not show the lg logo if the firmware was bad?
A reward of € 10 will be given to the person helping me with this, and makes it work as supposed to.
lamanfluff said:
Ok but do u think The firmware is The problem? The LG tool showed that it was up to date, isn't it just the windows phone 7 software that is missing? I am not sure, but wouldn't the phone not show the lg logo if the firmware was bad?
A reward of € 10 will be given to the person helping me with this, and makes it work as supposed to.
Click to expand...
Click to collapse
You could probably try a different version of the OS depending on what you have now (I bet you wrote what version you had, I just missed it).
There are a few threads about that under the WP7 hack and dev. And as far as the firmware goes it's hard to know if it's actually ok just because it loads to the logo, I don't know where in the boot sequence the logo appears etc. there could be problems with the firmware too.
My first step would be to see if it's possible to get a new version of the OS in and if not, I'd try some new firmware.
And if nothing works return it as faulty.
/J
jontatas said:
You could probably try a different version of the OS depending on what you have now (I bet you wrote what version you had, I just missed it).
There are a few threads about that under the WP7 hack and dev. And as far as the firmware goes it's hard to know if it's actually ok just because it loads to the logo, I don't know where in the boot sequence the logo appears etc. there could be problems with the firmware too.
My first step would be to see if it's possible to get a new version of the OS in and if not, I'd try some new firmware.
And if nothing works return it as faulty.
/J
Click to expand...
Click to collapse
I dont know what version there is on my phone, it received it like this, the only thing I see when trying to start it is "LG" and it shows right away.
I tried everything I stumbled upon when it comes to trying to put windows phone software in the phone, but Nothing works... I will send it back tomorrow monday if I cant find a solution to this.
I got the same problem before.
I just turn it off, and leave it for a night
Next day, all the things are ok
yeeaah well, nothing helped, whatever I did to it...
I received no less than 3 broken phones and now finaly I have a working one yaaaayyy
Congrats,
I just sent my phone to LG for the same problem....
My phone can boot up in very low rate...
Lg optimus e900 start issue
Hi,
I have the same issue, I can't restart my phone.
I can see only the logo and the LG caption.
Pls help,
Laszlo
I've got almost the same problem
I just bought this phone via local site, several days ago i'm so much happy with its smoothness but 2 days ago this problem appear, i spent several hours just to find it hanging on LG logo, i've waited for hour to hour just to see nothing happened that time. I left it for bed, and the next day the phone back to normal. But then, at least the device hanging 3 times a day, its just restarting itself and it seems the phone is unable to boot itself to the homescreen. Need help! I've done many way, from restoring, cold boot, softreset, upgrade(when it comes normal) etc but all don't work till now.
Unfortunately, this product doesn't release officially in my country, so i guess i won't be able to get replacement unit. I became so desperate cause i often use it, i need to get this phone back to normal, soon! Thankyou and sorry for my bad english

[Q] Continuum, what have I done?

Hi everyone, I'm new to this forum (first post), I've owned my Continuum for a few months now happily with no problems. I actually love the phone! But recently I ran into a pretty big problem...
Let me give you a little background on my phone first, I have used SuperOneClick on it, to grant super user permissions, I've used the program to grant me access to the phone tethering apps that are out (currently using Open Garden), and the AdFree app in the market. I havn't used anything else in regards to 'hacking' my phone so I'm a bit confused as to why I'm getting trouble.
Anyways here's my problem, lol! Well the other day I turned off my phone and tried turning it back on and I would get a grey battery with the spinning disk, and it wouldn't turn on :\! I tried holding all the buttons, for over 10 seconds, no avail. It still turned on to the battery and nothing. I tried taking the battery out for a whiiiile and nothing. Eventually I plugged in my phone to the wall and it magically worked. Actually that's the only way I've been able to get my phone to turn on lately. It works fine once it's on but every time I turn it off the same thing happens .
So that's truly why I'm here... Is my phone 'bricked', or are these some symptoms of being 'bricked'? Are there any fixxes I can go about taking to you know...fix the problem ?
Any help would be Greatly appreciated,
Thanks everyone,
-Matt
Oops, I forgot to mention that my phone has been acting strange sometimes in the sense that I plug it into the wall and the 'Mass Storage/ Media player' option comes up, even though it's not plugged into the computer, just into the wall.
Pretty strange huh?
Anyways thanks again everyone who helps!!!
Can you try taking out the battery, then putting it back in...
Then hold down the volume down key as you power it back on?
I would try un-rooting and doing a factory reset... that should eliminate software issues... If you're still having issues then take it to VZW and let them give you a new one.
This is not "bricking"... If a phone is "bricked", it does nothing, absolutely nothing, and the only way to make it useful is to use it to build something.
Sure, right now it says "Downloading... Do not turn off Target!!!".
Thanks for letting me know it's not bricked, that's a little reassuring .
After a while I just took out the battery and stuck it back in and attempted to turn on the phone the usual way, and it turned on just fine. I'm guessing it's fixed and hopefully it won't do that again.

[Q] Is it possible to retrieve files from N7 whilst dead/bricked?

Hi all
Apologies at coming on here and immediately asking for help, but....
I've had my Nexus 7 since July and have been very happy until NOW!
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
I've tried all the methods of long push of buttons/multiple buttons/etc but to no avail.
I can bring up the factory restore option so I know I can get it working again, but....
I have an exam in a week which foolishly had work stored for on my n7 without back up (yes fool) so....
Please is there anyway to retrieve my files via PC etc before factory resetting
All help genuinely appreciated
Mark
rooted vs unrooted (or unlocked bootloader even if not rooted) makes a huge difference in the answer.
Please state which.
Sorry about that
Not rooted.
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
pleading said:
Sorry about that
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
Click to expand...
Click to collapse
I believe you are SOL in that case. Sorry.
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Sent from my Nexus 7 using xda app-developers app
bigbop said:
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Click to expand...
Click to collapse
pleading mentions the battery, but then says "stalls" - not "shuts down", which is what you might expect if the battery was drained:
pleading said:
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
Click to expand...
Click to collapse
But, bigbop could be correct if pleading meant "low battery shutdown"
One other very long shot - assuming that that the device is hung - is to see if either adb or MTP are available. Normally that happens very late in the boot & I have to imagine that he has already tried that though.
Hi again guys
Firstly thanks for not giving up on my situation!
Bad explanation by me I guess....
The battery went flat/dead (my bad)
Plugged in to charge and screen lit up again but showing the 'powering off' script
Left over night on charge, wouldn't switch on again next morning
Left on charge all day still no joy but if I try switching on whilst plugged in I first get the Google name, then the Google X but then gets 'hung' (probably a better description than freezes etc as it still pulsates the colours)
Only way to get out of this is to keep power button pressed which switches n7 off and starts the cycle again
If during the recycle I keep the volume down pressed then it accesses the option screen to recover/reboot etc
Hope this helps, and again thanks (desperate to recover course work)
Mark
Hi again
Update...
Battery is showing full now
But still same 'hung' situation
Regarding the 'ADB'
I can get to the 'apply update from ADB' option
And if I choose it states.... 'now send the package you want to apply to the device with "adb sideload <filename>"'
As always thanks for any help or suggestions
Mark
Mark,
It sounds to me like what you are describing is ADB in the stock recovery, not a ADB when the regular operating system is running. (Is that right?)
Unfortunately, the stock recovery is only good for 2 things: applying an OTA update, and doing a factory reset. Even if your tablet needed an OTA update (and it probably doesn't if it is up to date), it probably wouldn't fix the looping/wedged phenomenon: usually that is caused by stuff in the userdata partition.
Doing the stock recovery factory reset might cure the wedged/looping problem - but only if it wipes all the data from your tablet. (Including the /sdcard area too).
The only hope I held out was if your tablet was reachable via a ADB or MTP with the wedged operating system sitting there looping. Usually those facilities start up quite late in the boot sequence, however so probably you don't have that.
Sorry. I think you are still SOL when it come to retrieving files.
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
I had same sort of problem N7 went flat tried to charge but would not power on
Took back panel off and disconnected battery for 10 mins reconnected battery and put back on charge
it then booted up as normal
pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
Uhhh ... what?
The OP was about a tablet that you couldn't get into because
[a] it had a correctable soft-fault
you didn't want to exercise an available soft-fault recovery method because of a desire to reclaim user files not backed up
... and so far as we know the soft-fault recovery mechanism still is available to you.
How did that morph into "this is the end"?
You need to re-do your homework, perform a factory reset, and move on with your life.
You have used either software or hardware in the past haven't you? That thing isn't a toaster or a waffle-iron! No backups of important stuff? Come on!
OK, well then. Pack it up and send it to me with the charger and I'll pay for the shipping - UPS ground.
Doesn't the Nexus have a safe-boot mode?
Sent from my Nexus 7 using xda app-developers app
bigbop said:
Doesn't the Nexus have a safe-boot mode?
Click to expand...
Click to collapse
Just tried right now - held the Vol-down button down continuously from about 2 secs after the Google B&W splash screen appeared until the lock screen appeared. That worked. (Stock 4.2.2)
"Safe mode" appears in the lower left corner. I had access to all the market apps (that I tried), but did not see a toast notification from StickMount after the boot - suggesting that safe mode only inhibits apps from starting on boot.
I suppose this could work (although the OP's deadline has probably come and gone) for bypassing a hung boot - but only if the hang is due to a market app that normally starts on boot.

[Q] Samsung Note 2 stuck on strange screen. Pls Help.

Helo Forum,
You must have noticed I'm a new member. This forum came highly recommended by every site and every other forum I had visited in search of a solution to my uniquely strange problem. It amazing what wonderful job you guys are doing solving people's problems for free.
Phone status: Samsung Galaxy Note 2, upgraded to android 4.3, rooted but not yet flashed a custom rom, hard reset a couple of weeks ago.
Without warning, my note 2 started acting up. I picked it up after an hour of receiving a call only to notice that it was stuck on the samsung logo screen. Prior to that, I can confirm that I did not tamper with it in any way. I turned it off and on again, this time around, all I could see is a screen filled with strange tiny ash colored horizontal lines from top to bottom. It simply got stuck on this unresponsive screen and refused to boot any further. I turned it off and on several times and even pulled the battery several times but there was no change. When I connect it to a pc, it appears as "local disc Q" and when i try to open it, I get the error message "Access denied". I also tried a hard reset using the volume up + home + power on several times, not a single change was noticed. I've attached a picture of the strange phone screen.
If anyone has encountered a similar problem or if anyone has an idea of how this can be fixed, and kind enough to take me through the step by step process of fixing it, I will be super grateful!
Pls let me mention here that my IT skills are not very advanced, so please use simple terms. Let me also apologise if it turns out that a similar thread has been posted on this forum, I searched but couldnt find any with my kind of problem before I decided to post.
Here's my email: [email protected]
Thanks in advance.
It seems to be a hardware problem rather than a software one
Try taking it to the service centre and get your motherboard fixed
Sent from my GT-I9300 using Tapatalk
Can you boot in download mod? Its showing any image? Or only this? I mean if you can see samsung logo or bootanimation maybe the problem its software...
If you can enter download mode and you can see any image...in your place I will flash a new rom using ODIN.
Saludos! And please let us know how its goes.
Thanks guys for your prompt response.
@Cocolopes, I cant see anything but the unresponsive weird looking screen. Every effort to clear it up has failed so far. The phone has refused to respond to any command including volume up + home + power. Not even a sound. Like I said in my earlier post, it started with the appearance of the samsung logo which refused to go away, so I pulled the battery and then this weird screen appeared.
@jay5204.abd, yeah I also suspect it could be a hardware problem but I always choose to make the service center option a last resort. I prefer to share with wizards in the forums first, just in case someone had experienced a similar problem and solved it.
busycash said:
Thanks guys for your prompt response.
@Cocolopes, I cant see anything but the unresponsive weird looking screen. Every effort to clear it up has failed so far. The phone has refused to respond to any command including volume up + home + power. Not even a sound. Like I said in my earlier post, it started with the appearance of the samsung logo which refused to go away, so I pulled the battery and then this weird screen appeared.
@jay5204.abd, yeah I also suspect it could be a hardware problem but I always choose to make the service center option a last resort. I prefer to share with wizards in the forums first, just in case someone had experienced a similar problem and solved it.
Click to expand...
Click to collapse
Well....so its a hardware issue..... good luck with the service center.

5 month old Nexus 6P (stock Nougat) bricks itself while on my desk?

I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
BrickOfNexus said:
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
Click to expand...
Click to collapse
Hi... There is no available fix for the moment. Check this thread. You are not alone
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page19
BrickOfNexus said:
... Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android....
Click to expand...
Click to collapse
Unfortunately @5.1 is right. The common denominator of the BLOD (many threads on this) is the inability to get into recovery mode by any means. ADB doesn't work unless in recovery. Without ADB you will not be able to pull anything off the phone. At least you are unlocked so you can try some tools and/or manually attempt to fastboot boot or fastboot flash a custom recovery and get ADB working, but chances are almost non-existent. Some ppl have been able to briefly get back into recovery on completely full charge, but it seems to start boot looping again shortly afterwards from recovery. Hopefully you were using Photos and synced recently. If you bought direct from Google, contact them even if out of warranty. If they won't help you or you didn't buy from Google, approach Huawei for an RMA.
I was in your situation and was able to flash the full stock image (flash-all.bat command) even though my device didn't show up on ABD--but maybe I just got lucky. I thought there was no chance it would work but it did. Some people reported getting out of the boot loop using Skipsoft's tool but most likely you will need to RMA the device if it's still under warranty from Huawei. Sorry to hear you have been added to this club. There are a lot of lemon 6Ps that die because of hardware issues (according to Google) and they clearly don't care because they never recalled the affected devices. I was hoping it was just the early generation phones but if yours is 5 months old that means the problem is persisting. None of these things might still be running in a couple years which is ridiculous for a premium phone. Makes you think twice about buying another phone from Google since they threw 6p owners under the bus rather than offering 6P owners a credit or something for their defective 6Ps. Good luck. At this point I think people need to create a class action suit against Google. That's the only way people got repairs or compensation from Apple the numerous times they pulled stuff like this with defective products. Why should Google get away with selling what they themselves admit is a defective phone?

Categories

Resources