Ok my atrix is acting very weird, sometimes it freezes when trying to unlock (slider gets stuck). Today i was unable to send a text (i had all bars), when i hit send i got a message saying 'unavailable'. Sometimes when i try to power off, it freezes during the 'powering off...' popup. Sometimes when i turn it on, it takes like 2-3 minutes on the at&t logo.
The keyword is SOMETIMES. unpredictable behavior.
I was running cm7 (rooted and unlocked bootloader), and i restored to the latest at&t firmware via the motohelper on my pc (not ota). i read that you could restore that way and it will unroot you.
So the restore seemed to be successful. I didn't test to see if i was actually unrooted, but the 'unlocked' text on boot was gone (but i could still hold down vol down and get the fastboot menu, but was unable to get into android recovery.)
So im getting random freezing that i need to fix. The original purpose of restoring was so i could receive ota updates as needed.
im on firmware 4.5.141.mb860.att.en.us
android 2.3.6
any ideas??
Any advice on what I should do would be great. I just need it to become usable again.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Related
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
First let me talk about how I got into this mess. I had used the thunderbolt as my phone previously and had rooted it, installing custom roms often. After getting a new phone, I decided to unroot my thunderbolt and give it to a family member. At first, everything was working fine; I had no problems unrooting the phone. However, a month or so later it started having problems.
Upon booting, the phone goes straight to hboot where it displays a security warning. But this only happens occasionally. Sometimes it will actually boot but take about 20+ minutes to start up where it come to the homescreen with a solid black background, soon to freeze and turn off.
I have tried fixing the phone based off methods others used to fix similar issues, but to no avail. For example, I have tried flashing the 2.11.605.19 firmware through hboot only to have the same problems occur. Perhaps I did not use the right version. Do you guys have any idea on how I can fix this? Could flashing an ruu (if there is one) for the latest ics build solve this?
When I try to unlock the bootloader through htcdev, everything works fine up until the confirmation screen on my phone asking if I want to unlock the bootloader or not. For some reason, the power button won't work to press yes. It does work normally for saying no and everything else though. I have tried using the adb to force it to use the power button, but in its "unlock the bootloader" state it isnt connected.
some relevant info for the phone:
hboot version - 1.05.0000
radio - 1.49.00.0406w_1 - should be the radio from 2.11.605.19
Good afternoon all,
I have recently updated my Samsung Galaxy S3 via kies to Android 4.3. I couldn't do the update over the air as it was rooted. I had to go through and root my phone again through Odin and again all that went fine.
However since doing this I have had to restore my device 2 times as it shuts down every now and then and I find I 'lose' some apps...mainly games, which I find annoying. It also wipes any saved text messages.
At first I thought it was only losing apps that I'd downloaded through other means (i.e. not Play) but it appears not. I still have the apk files stored on the phone and have tried to re-install them but I get a message of 'app not installed'
Can anyone tell me why this is the case? As I have previously said it has only been since updating to Android 4.3. Not sure if it is due to rooting my phone (i'm guessing not).
Any help will be greatly appreciated
Chris
!!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED
Please use the red report button and ask a mod to move the post.
See multiple posts re OTA and root problems.
Suggest factory reset if that does not fix then flash stock 4.3 through Odin .
I know that I can't do OTA updates... My problem is that the phone will restart, without warning and when it reboots I have lost all my text messages and a few apps. Trying to reinstall the apk files gives me the error 'app not installed'
I have tried factory reset both through the recovery mode and the system settings, but nothing resolves it.
My phone is rooted and runs Android 4.3 which was updated through kies.
The apps it loses are games so that's not a major issue... It's all the text messages.
I have a very similar problem, phone always shuts down and restarts on it's own. A couple of times it has lost some apps but usually it just starts up again fine but it's very annoying. Sometimes it gets stuck in a boot loop too.
A Google search for random reboot or random shut down brings up a lot of results but no solution's, so it seems to be a common problem. It's not just the stock rom either as it still does it when rooted and running other roms.
So I've been running KitKat via CM11 nightlies for quite a while now and about every other week the I lose signal and have to reflash stock. I Use Razr Utility (http://www.droidrzr.com/index.php/t...-verizon-droid-razr-and-droid-razr-maxx-only/) to flash stock, get signal, reroot, and reinstall SafeStrap. Have done it I think like 80 times or so now.
Today when I did it, when I pressed start at the Setup Wizard it said "Preparing may take a few minutes ... blah blah" then it reboots. I rebooted and tried again, over and over it won't get past the language selection, and if I leave it alone for a few minutes w/o pressing anything it will reboot on its own still; it continually reboots over and over. Also I am no longer getting service back on a fresh stock flash. I have tried 1.8/1.82/newest of RAZR Utility, all received the same result. So I tried House of Moto with 2 different VZW firmwares (2 newest JB) and still same result.
I was able to get root w/o having to mess with Smart Actions and then use ADB w/ su and PM to disable all the setupwizard BS so I could install SS and get back to CM11. (Setup Wizard is locked and no way to bypass, even tried build.prop tweaks to turn it off and nothing) Now on CM11 it is liking to randomly reboot whenever it feels like it too; that is if it even boots back into CM11 after rebooting, sometimes it makes it all the way to CM11, sometimes it doesn't.
Does anyone know WTF is going on with my device and how to fix it. I'm going to try and get a new SIM tomorrow and see my SIM fried or something (though I never received the "No SIM" error). I'm honestly about to chuck this phone through the friggin wall....
Update: Was finally able to get CM11 to stop rebooting, upgraded to newest nightly and wiped Dalvik & Cache, and Fix Permissions. Signal has sort of come back, it goes in and out; very finicky.
Update 2: Service is completely gone and can't get it back now.
I have had my S4 (SCH I545) rooted for at least a year now, and today while I was walking down a sidewalk to my house I felt my phone vibrate. Thinking I received a message, I pulled it out, and was greeted by the white "Samsung Galaxy S4" boot splash. 5 minutes before, I was using my phone normally. Battery was on at least 50%. Since then, I have been completely unable to boot up my phone. I can only turn it off by removing the battery - it is completely frozen. Booting into (TeamWin) recovery works, and I backed up my phone to an SD card before completely wiping it. Even after the wipe I am still stuck on the splash screen. Again, I was not attempting to change anything, only using the phone normally. Nothing OS-related on my phone has changed since I rooted it a year ago. Have never even updated .Any ideas? I've been looking for hours.
EDIT: Plugging the phone into either an outlet or a computer will cause it to freeze on a picture of an empty battery with a (non-moving) loading circle. It is still completely unable to be interfaced with in any way (Other than recovery booting).
What battery percentage does twrp say?
Sent from my OtterX running AICP using Tapatalk.
---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------
You should charge it in twrp, then push a ROM or backup to your phone.
Sent from my OtterX running AICP using Tapatalk.
So I got it working fine after flashing from odin. Today I flashed a Google Play edition ROM and it seems to be working fine with one exception, messages are not being received. The default messaging app will not open at all (Crashes immediately). Using Hangouts will allow me to send messages (confirmed with another device) but even after wiping messaging data and clearing cache I cannot receive texts. Any ideas?
EDIT: I tried flashing to a more updated version of the Google Play edition and apparently now my bootloader is locked because I got message saying to go to a verizon store for help. Guessing I now need to use Odin install a default to re-unlock the bootloader?
UPDATE: Tried to use ez-unlock considering I am on android 4.2.2 with MDK and I hard bricked my phone. Why did that just happen?
___Pyro___ said:
So I got it working fine after flashing from odin. Today I flashed a Google Play edition ROM and it seems to be working fine with one exception, messages are not being received. The default messaging app will not open at all (Crashes immediately). Using Hangouts will allow me to send messages (confirmed with another device) but even after wiping messaging data and clearing cache I cannot receive texts. Any ideas?
EDIT: I tried flashing to a more updated version of the Google Play edition and apparently now my bootloader is locked because I got message saying to go to a verizon store for help. Guessing I now need to use Odin install a default to re-unlock the bootloader?
UPDATE: Tried to use ez-unlock considering I am on android 4.2.2 with MDK and I hard bricked my phone. Why did that just happen?
Click to expand...
Click to collapse
I'm not completely sure but from the looks of it ez-unlock was made to unlock the s3 bootloader