PA w/ Bacon WIPED Itself - ONE Q&A, Help & Troubleshooting

Earlier today, I noticed that my phone died. I charged it, and when I tried to start it, it was boot looping. It did this twice, then when it restarted, it told me that it was "installing 110 apps." When I read this, I knew that my phone had been spontaneously wiped as I have way more than 110 apps.
What HAPPENED? BTW: I had ParanoidAndroid 4.6 Beta 5, and TWRP 2.8.1

There is a chance of this happening when the phone shuts down unexpectedly. Are your pictures and other stuff safe?

I remember something like this happened to me on a previous device I had, out of no where the phone just died and whipped itself, had to return it to manufacturer because of bad memory, don't know if this is your case.
Sucks, hope your phone doesn't have bad issues and it was just a fluke

Nice, your phone is toilet trained
Assuming you didn't encrypt it, can you see & mount /sdcard in recovery?

Related

My TB is dead...

My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
ZBoater said:
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only thing I would've suggested would be flashing the signed ruu.
You could try reverting to the pre-OTA firmware, but I'm not sure you'll be able to use ADB if you're stuck bootlooping. Check out the "NOT FOR ROOT USERS" section.
ZBoater said:
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
RIP poor TB
How long did you wait for the screen to clear?
Just curious because I know usually when I do any type of update or rom change, etc, since you normally wipe the data and cache, the boot up can take quite a long time on the initial boot up.
I know some people report as long as 10 minutes or so to get past the screen. I don't think mine ever took that long, but there have been times I think it's stuck and then a minute or so later, it gets past it.
Just my two cents.
This has happened to a few people already after the update. I don't know what is in this update but HTC screwed up majorly.
Sounds a lot like what happend to mine, but mine was rooted.
See here...http://forum.xda-developers.com/showthread.php?t=1090531
LOL, I welcome the breaks when I can't find my phone for the day.
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
will9512 said:
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
Click to expand...
Click to collapse
What would that accomplish?
Yeah your lucky you got a guy to order your phone because I wouldn't have because even the new ones are rebooting, when you get it I would suggest postponing the update if it comes without the Mr1 update, as far as your wives phone yeah I would check out the forum uptop on going back to old software other than I have had a few people come into the store with same problem and couldn't do anything( mainly because I have no access to anything), but ship a replacement, oh and one suggestion is if you don't want your wife to borrow your phone your local store does have emergency stock Android loaners that you use until you get your replacement in, and then you just send your phone and the loaner back in the FedEx box so if you really need a phone you can do that.
Sent from my ADR6400L using Tapatalk
I believe your random reboots are due to the new radio which is tied into the OTA. If you apply the OTA again your still going to have random reboots. I ever used the newer radios and have never had a random reboot.

Having SERIOUS Issues

Last night, while I was reading a text message, my phone rebooted itself. When it came back on, it told me that my memory card was invalid and that I would need to reformat my phone. It gave me two options: Emergency Call and Reboot. I pressed Reboot, and it turned back on normally.
Everything was fine until it rebooted itself yet again. This time, when it came back, none of my apps/games/anything work. The phone is on, but I can't do anything with it. The only apps that open are 3rd party apps that I sideloaded.
I tried connecting to Zune to roll back to a restore point, but all I get is connection errors. I even tried going into my Settings>about>reset your phone. This told me it would reset my phone back to factory settings. After doing this and having it reboot, my phone is still the same. All the apps are still there and not working, and even my custom theme is still there.
Someone please help me.
AT&T Samsung Focus
I just did the hard reset by holding Power+Camera+Volume. It seems to have worked.
Any idea what could have caused this? I mean yeah I did a lot of registry tweaks, probably making it somewhat unstable, but this isn't cool...now I have to re-unlock it, re-force NoDo to install, etc...
EDIT: Well, the factory reset is still...resetting. It's just sitting on the Samsung splash screen not doing anything. I'll report back if it never leaves this screen.
im guessing you are usig a samsung focus? if you are you would have better luck posting is the focus forum but it sounds like you are using or you used an incompatible sd card with it.
check this thread out http://forum.xda-developers.com/showthread.php?t=834144
and im personally using a samsung 16gig sd card bought from ebay seller nikolai1778(or something like that) since december and i havent had any issue so that card is certified. hope that helps
Yes, I am using a Focus, but I have had this card in my device for months and months. It has never given me any issues.
I took the card out, factory reset it again, and it is giving me the same "Storage card not working" message. The card isn't even in my phone anymore.
rmcgraw said:
Yes, I am using a Focus, but I have had this card in my device for months and months. It has never given me any issues.
Click to expand...
Click to collapse
what size is the sdcard? you probably just now recently used up all the space on the card and thats when you started getting the random reboot and data loss. read the thread i pointed out to you a lot of the issues you are having are documented there and the only known fix is to get a certified sd card or take out that sd card and hard reset the phone.
Again, I took the card out, hard reset it, and it's just stuck on the Samsung screen.
It's an 8 GB Sandisk Class 4
rmcgraw said:
Again, I took the card out, hard reset it, and it's just stuck on the Samsung screen.
It's an 8 GB Sandisk Class 4
Click to expand...
Click to collapse
im out of ideas here, thats the 1st time i have heard of that hopefully someone else can help u out. you can try calling or taking your phone to at&t
Yeah, I still have my warranty (I think?). I left it sitting on the Samsung boot screen for about half an hour and it wouldn't budge. Seems to be bricked, although if I just try to turn the phone on normally, it shows the storage card error (without the storage card present). It gets stuck while reformatting.
if you can go to settings/about/reset your phone do it whitout your sd and again with your sd card
Sent from my WP7 Trophy
I don't think that is the problem. From what rmcgraw has described, it sounds like the phone is bricked, with or without the card installed. I don't think this is something that is a user-serviceable problem. My guess is that the phone needs to be replaced.
Yeah, I can't even get into the phone to go to the settings. As I had said, I tried hard resetting from the settings menu twice, to no avail. I have no idea why this happened, it was completely out of the blue. Hadn't changed any registry values that day or installed any new apps. At the time it happened, I had my phone plugged into my PC to charge and I was reading a text message.
I'm leaving for the AT&T store right now, I'll let you know how it goes.
Well, after about an hour of standing in the AT&T store on the phone with the warranty department (they couldn't even do anything in the store to help me), they told me they had no idea what was wrong and that they'd send me a replacement. I have to send my original phone back to them obviously, and if they determine that it's my fault, I have to pay $410. Oh yeah, and I have to wait a week for my phone.
I am having the same problem with my surround. Got my first one warrantied out because it was bricked at the HTC splash screen after getting the memory card error. Now my second surround is giving the error every couple of days and has needed a hard reset for the same reason you mentioned. I haven't done anything to my phone. No jailbreaking or whatever. And both have the original sd cards.
Sent from my T8788 using XDA Windows Phone 7 App
Maybe your computer over volted in some way and the memory card ( not the removable one, the internal one) got damaged. I know that when I plug my Samsung focus into an Apple usbwall adapter that the touchscreen doesn't work (capacitive buttons do tho?) and it may reboot its self. I assume this happens because the Apple charger releases an incorrect voltage to the phone- ie; more or less than the phone needs and it causes the device to stop working properly. Never had any lasting effects on my phone, but I just can't use an Apple USB adapter
Sent from my mailbox
UPDATE
Received my new Focus on Monday. Everything was fine until a couple of days ago. Just so you know, I did NOT re-install my 8 GB Sandisk Class 4 microSD, and I did NOT unlock my new device. Everything is stock on it, except for the apps I've installed.
Now back to the issues: It started crashing randomly a couple of days ago. It would do it when I plugged my phone in, as I entered apps, and sometimes just completely out of the blue. Yesterday, I got the "Storage card isn't working" error, even though a storage card has NEVER been in this device. That error actually froze, the phone re-booted itself, and has been working normally since. This is how the my other Focus was acting before it bricked.
So, my question: Is it the battery or my SIM card (those were taken from the other device)?
rmcgraw said:
UPDATE
Received my new Focus on Monday. Everything was fine until a couple of days ago. Just so you know, I did NOT re-install my 8 GB Sandisk Class 4 microSD, and I did NOT unlock my new device. Everything is stock on it, except for the apps I've installed.
Now back to the issues: It started crashing randomly a couple of days ago. It would do it when I plugged my phone in, as I entered apps, and sometimes just completely out of the blue. Yesterday, I got the "Storage card isn't working" error, even though a storage card has NEVER been in this device. That error actually froze, the phone re-booted itself, and has been working normally since. This is how the my other Focus was acting before it bricked.
So, my question: Is it the battery or my SIM card (those were taken from the other device)?
Click to expand...
Click to collapse
If i had to guess is the battery .....
This may be completely unrelated, but I found it interesting...
I had installed the "Drive On" GPS app on my old device. I didn't like it so I never used it. I had made a list of all of my installed apps right before my phone bricked to reference for when I got a new one. When I got my new Focus, I did not install Drive On.
After I started having problems with my new device, I noticed that Drive On had appeared in my app list without me installing it. However, it wouldn't open. I uninstalled it and my phone hasn't crashed since. I haven't gotten the storage card error since then, either. In fact, my phone has been running flawlessly and maybe even better than before.
I could be crazy, but Drive On seemed to be a rogue, phone bricking app that I will never install again.
Phone was acting up again last night.
5-7 crashes/reboots, and I got the "Storage card not working" message again.
It's strange how these problems seems to come in waves. The phone will work perfectly for days straight, then will go crazy and have tons of reboots and errors within half an hour, and then will go back to working perfectly fine for a while.
I want this to stop.
Ugh, it just restarted itself and is now showing the "Let's get started" screen, as if it formatted itself. I took the battery out and I'll try to boot it back up in a few...
Why am I having such bad luck with these phones?
EDIT: Yep, the memory is completely wiped and everything is back to stock. All I did was plug my phone in because the battery was about to die. Every single one of these problems has occurred while the battery was extremely low and the icon would stay at the top of the screen reminding me to charge it. As soon as I plug it in while on low battery, the problems begin.
rmcgraw said:
This may be completely unrelated, but I found it interesting...
I had installed the "Drive On" GPS app on my old device. I didn't like it so I never used it. I had made a list of all of my installed apps right before my phone bricked to reference for when I got a new one. When I got my new Focus, I did not install Drive On.
After I started having problems with my new device, I noticed that Drive On had appeared in my app list without me installing it. However, it wouldn't open. I uninstalled it and my phone hasn't crashed since. I haven't gotten the storage card error since then, either. In fact, my phone has been running flawlessly and maybe even better than before.
I could be crazy, but Drive On seemed to be a rogue, phone bricking app that I will never install again.
Click to expand...
Click to collapse
A day after re-formatting itself, my phone suddenly fully re-installed (by itself) Drive On again. It opens and runs. I uninstalled it again. It is the only app that keeps reappearing after I have issues with my phone.

[FIXED] Stuck at S/W Updater Screen

I was slow around flashing to the latest baseband but finally took the dive today and the program locked up at 5% for like 2 hours before I yanked it. Now it just gets to the "S/W Updater" screen regardless of what I do (NVFlash recoveries, roms, kernels, format, hard reset, etc). When I try to update it again, it just immediately says it's already the latest version. Why won't it just flash over it like most flashing programs.
Tmobile is pinging me $20 for a replacement but I have a really good G2x. Is there anything I can do to revive mine or is it toast? ADB commands or something? I have clockworkmod on there now, but I'm not really getting anywhere.
[Update]
Use this NVFlash method to completely format your phone, re-setup your partition tables, and flash the stock GB rom:
http://forum.xda-developers.com/showthread.php?p=17258229
Dead
It's dead. Same thing happened to me and to many many others. Turn it back to TMo and take the hit--it's not worth the time playing around with it any more.
Call TMo and ask to be forgiven the $20. If you've been a long and loyal customer they might even do it.
Your new phone should come with 2.3.3 installed. Mine did and I've had no trouble with it--it's finally settled down into a very usable and fast phone. Stock ROM. But I won't buy another LG phone again for a very long time--not until they hire a few software engineers who know what they're doing.
No my friend. I got revived!
http://forum.xda-developers.com/showthread.php?p=17258229
It totally erased everything, formatted everything, reset all the partitions, and flashed the GB Stock rom.
Booted up, NVFlashed CWM, Restored my Nandroid backup, viola!
Thought it would be a good thing to make more available. It was in the Android development thread but the title is tricky as its listed as a rom (which I guess it kinda is).
Sent from my LG-P999 using xda premium
i dont understand why people get stuck on this. ok
when i did it. the LG Tool stop responding on half the period % and my phone had the S/W updater screen so what i did i click on closed unpluged my device then open the LG Tool again plug my device and the LG TOOL said that there was a problem if i wish to continue with my update i click yes and it kept doing till it was done and my phone was fine with 2.3.3
The mistake you made was just stopping the update. Mine did the same thing. Instead of listening to the stupid message about removing the battery, etc. I just removed the usb cable, waited for the beep, put the cable back in, waited for the beep and then pressed "restart" on the update. It completed perfectly after that.
Well I've gone through all of those scenerios and it would attempt to reflash it, but the last time it got stuck on 5% for about 2 hours... no error message or anything. After 2 hours at 5% I pulled the plug. When it is in the middle of "flashing" and gets locked up, there is no Cancel button or Restart button like when it errors out.
I had no errors, just a locked up program. Regardless the posted link really fixed me up and got it working again.
I changed the title and updated the OP with the solution.

Samsung Galaxy S2 Recovery mode/reboot loop issues

Hi
I have a problem with my Galaxy S2 where it's in a constant reboot loop and the only way to stop it is by taking the battery out.
I'm sure that if I do a factory reset it'll go back to normal.
The problem is, I can't back anything up because as soon as the phone boots up it restarts.
Is there ANY other way to back up my photos and videos etc?
I have NOT rooted the phone
Cannot find any solutions online
I'm currently having this problem too. A couple of days ago it kept rebooting in a loop. I took the battery out and left it for a while, then let it charge. It seemed okay afterwards. Now today it keeps rebooting, and the past couple of days it has refused to charge the battery because apparently the battery was "too hot or too cold" (don't quote me on that) so I'm very confused. Just now though the battery was about half-charged and it still went into the reboot loop.
Something else you should know is that like the OP it has the stock OS on. It isn't rooted or modified. I don't want to factory reset it because I have spent so much time customising it (with apps) and it would be a pain in the ass if the problem still existed afterwards. One thing I must ask the OP is, did you recently get a 64GB MicroSDXC card for your S2? I ask this because I did a couple of weeks ago and it's been working fantastically and was said to work fine with the S2, but I'd like to explore any possible reason this reboot loop is happening.
Thanks.
Edit: To confirm I deleted the cache and this didn't help. I don't want to hard reset...
I've just done a factory reset - I hadn't realised that it only affects my apps and not my files.
The phone is ok now.

[Q] RAZR MAXX HD boot loop

Hey all,
First of all, forgive me if this has already been covered, but I couldn't find any threads that had a solution to this specific problem that worked for me.
That said, I have a Droid RAZR MAXX HD that I rooted and flashed to page plus just about two years ago. I have since unrooted the phone. It was running on jellybean 4.1.2 if I recall correctly. The phone has been great and I've been very happy with it till today. I shut it down, nothing out of the ordinary, just decided to turn it all the way off. When I later went to turn it on, it got stuck in the middle of the little boot animation where the robotic iris opens to reveal the red eye. It froze there for 3-5 seconds and then rebooted only to do it again. Funny thing is, it freezes at a different point every time. Some times the red eye is completely visible and sometimes the iris hasn't even started to open. I tried booting without the sd card and when that didn't work I tried all the other typical stuff: simulated battery removal, cache wipe, factory reset-wipe-format. I also tried a stock system data wipe as well as a stock recovery, both with mattlgroff's Doid RAZR utility from AP Fastboot mode. Still nothing.
At this point I'm at a loss. I bought this phone for $300 back when it was the phone to have and it's been a great phone, I don't want to lose it if I don't have to. Any help would be greatly appreciated.
Just a quick update.
I decided to take my phone apart and see if there were any loose connections that might be causing issues with booting. I didn't find any loose connections so I put it back together, and decided to try booting it on a whim. To my surprise, it booted perfectly. A few weeks ago I installed ancleaner, and app that claims to clean your cache, yada yada. I'm guessing that somewhere along the line, it managed to corrupt a deep system file or the cache or something. Regardless of what really happened, my phone is alive again, and I think that it was probably due to physically disconnecting the battery. So moral of the story is, don't trust the simulated battery pull, and physically disconnect it for a time instead.

Categories

Resources