Have any of you done a factory reset straight after you had turned on the OneX for the firs time out the box?
Just to sort of settle things down. Just a thought I had.
Ta
nope... im afraid when i do factory reset... some of the stock scene/skin/wallpapers may went missing.. i rather install from the official RUU of my particular region so that the ruu will wipe everything and all stock files are there exactly like when you first turn it on
Related
Hello, all. I've had this problem for about a year, but I just kind of put the KF away once I got it replaced instead of fixing it.
Last year, I put my KF into a softbrick, factory reset bootloop. On boot, the KF warns:
Your Kindle has detected a problem and must clear App storage. The recovery process will erase some apps and data from your device.
Click to expand...
Click to collapse
The rest is the generic factory reset info. Press power to proceed. This looks like it goes through the process, restarts, and just boots back up into this message. Thus, bootloop. I've tried looking up others with the same problem, but no one has had the same one I mention. I don't have a custom bootloader or TWRP.
As for what caused this, if i can remember correctly I was having trouble with google apps permissions and changed a folder in /system/ to something else. The fire freaked out and I rebooted it. The above has happened ever since. So the only modification is being rooted. I've tried getting access to adb, but it hasn't listed the device. Maybe I installed the drivers wrong or something, but I didn't mess with it for long because I don't like being in Windows if I can help it.
Any help would be greatly appreciated. Not in too big of a hurry, though, as I have a Nexus 7 currently. ^.^
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Thepooch said:
Get a factory cable to force it into fastboot so you can flash a new bootloader and twrp , then flash a new rom. You can also attempt to race it to factory reset and reset it some have success.
Click to expand...
Click to collapse
I knew about fastboot, I should have mentioned. I just don't have the money to spend on one currently. What do you mean by attempt to race it to factory reset and reset it?
Just what I said you have just a little time to race to settings and factory reset it before it fc`s and shuts down some people manage to pull it off.
i know alot of people are going to hate on me for this. ive been at this for the past 9 hours. i tried to upgrade my xperia s to 4.1 CMOD 10. in order to do that i had to unlock bootloader and install doomRecovery for clockwork mod. in the process i was confused and thought that id be able to restore my phone back to its normal self by clicking on factory reset. that ended up wiping everything. everytime i try to go to flash and 'fastboot devices' it doesnt even say waiting for devices anymore...it just does nothing. i think ive completely wiped out everything on my phone except for doom Recovery. ive been searching for the past 9 hours, but no one has had the same problem as me. oen other person accidently factory reseted his tablet, but there was not much help there. no one was stupid enough to press factory reset. If anyone out there can relate to my problem, or at least offer some advice, can you please do so. i use to be good with computers...but i guess not anymore... im an idiot.
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.
OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.
The background story: Was having a lot of FC issues with Beanstalk 4.4, along with other things like battery life/signal that I was growing to be unhappy with and decided to flash one of the 4.3 ROMs with Note 3 features on the fly. I didn't have signal after doing so (didn't read all the comments so I do know this is all my fault) and thought that I would have needed to flash the 4.3 bootloader that was suggested in the OP since using the modems I had on hand did not help.
End result, phone was perpetually stuck in bootloop.
Symptoms: Doesn't go past the Samsung splash screen with the logo flashing. Even when plugging it in it's stuck on the empty battery with the loading wheel.
Attempted solutions:
I have tried the EFR attempt but could not get Kies to recognize my Note II in downloading mode. Kies is currently updated to the lastest 2.6.1.x.x.x
The emergency code option isn't viable since I don't have one(?)
Flashed the appropriate stock ROM (for Bell SGH-I317M) through Odin as it was recognized, but still cannot get past bootloop.
Tried firmware upgrade and initlization instead, PC cannot download firmware to device
Attempted to flash other ROMs both stock and whatnot through CWM. Doesn't seem like it'll take anymore AOSP mixed/based ROMs as they all fail?
With all of these attempts I have pulled out the battery for a little bit prior to actually performing the restoration.
Hopefully somebody can point out a mistake or something I need to do instead.
And as a side note, the Galaxy S2 is too damn small and Windows phones (Lumia 1020) kind of....suck.
Bump. Hopefully somebody can point something I missed.
Have you tried Odin to stock then wiping all user data/ factory reset?
bbrennan said:
Have you tried Odin to stock then wiping all user data/ factory reset?
Click to expand...
Click to collapse
Attempting to wipe anything other than cache in CWM gives me an error mounting.
If you Odin to stock it would have factory recovery on it, not cwm, Odin to factory then under stock recovery wipe data factory reset
bbrennan said:
If you Odin to stock it would have factory recovery on it, not cwm, Odin to factory then under stock recovery wipe data factory reset
Click to expand...
Click to collapse
You sir, deserve the rest of the day off with a pat on the back and a beer in hand. Many thanks!
Hi, I have a very strange problem on my DHD. I started to have a lot of FC, making the phone unusable. I tried to make a factory reset from settings but the phone got stucked at HTC logo, and nothing was wiped. I made a factory reset from bootloader, but the phone vibrated three times and also got stucked at logo. I made a factory reset from recovery and the process was completed, but with some errors. Then I rebooted and nothing was wipe, and the FC's were still there.
So I decided to flash an RUU, the process was completed and now I have exactly the same! Same ROM, same data, nothing wiped, nothing flashed.
So it seems like the memory is corrupted and not writable at all or something like that?
The phone is completely stock, never rooted or debranded (it's from Vodafone Spain)
Yes, it's problem with eMMC.
http://forum.xda-developers.com/showthread.php?t=2602786&page=18
This is not my thread but I have lot of post in it.
Explaining about exactly the same problem.
In link is final page in which you can see what i have done for now.
I'm trying to repair it without changeing eMMC.
I recomend reading the whole thread.
Woah, seems complicated... Thank you very much, I'll try and report!