Related
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
The only way was to reflash from Odin, fresh firmware. Download different version of your firmware, other than the one you stated. And reflash back with Odin, make sure your steps using Odin is correct.
Thanks for the reply. I finally got it working after my third time flashing it and formatting the cache a few times. Scary stuff!
Alas, the sporadic reboot still continues, so I'll have to work out how to fix that problem again now.
Thanks again.
Simpler fix from at&t device support center
c0dewana said:
Hi all,
I'm hoping someone may be able to help me. Here's the situation:
A few weeks ago, I updated and rooted my SGS4 to 4.4.2 using Odin. Worked alright, but kept getting random restarts. Did a factory reset, and all was good.
A few days ago, PlayStore had an update for SuperSU, so I applied it. The random restarts returned, so I considered doing a factory reset, but found that Titanium Backup wasn't allowing me to do any new backups because I had insufficient space. I didn't really - I had plenty of space. A little googling lead me to here: http://forum.xda-developers.com/showthread.php?t=2675778
I followed the instructions, rebooted my phone, and was bombarded with [app] has stopped working right away. Thinking this was no good, and I had somehow messed something important up, I did a factory reset anyway with the hopes of just restoring back to my backups from a few weeks ago.
Things got even worse - I'm now stuck on the Samsung welcome screen, where it wants me to put in my wifi password, but Myscript Resource Manager keeps failing, making the keyboard disappear. I now have no way to get back into my phone.
The TL;DR version:
I factory reset my phone, but can't get past the 'Enter Wifi Password' part of setting it up becuase Myscript Resource Manager keeps failiing.
Things I've tried:
* Wiping Cache data
* Factory Resets (again)
* Reflashing my phone with the 4.4.2 update that worked for me a few weeks ago
Does anyone have any other ideas?
Click to expand...
Click to collapse
I just had the same problem, spontaneously, from an unidentified source. Went to my carrier's, AT&T, local Device Support Center on a Sunday at noon, and one of the techs fixed the problem in under 3 minutes, impressively simply.
You will have to keep clicking OK when the error message repeatedly appears to continue with this process. That is normal.
Go to Settings > Application Manager > (scroll right to: ) ALL > (scroll down to: ) My Script Resource Manager (which should not be running) > Turn Off
Problem solved without Factory Reset. She impressed me and saved me a lot of time.
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
Hey, I just woke up, and I have to get to work, but I just wanted to let people know that I charged my phone last night and this morning it was dead. Pulled it off wireless charger and plugged into OEM charger and attempted to boot phone, got stuck at AT&T logo. Restarted into recovery and it tried to install an update!!! My phone is rooted, debloated, and should have been OTA blocked!!! Still having access to ADB on boot logo, I pulled my text messages (still had root?) and went for a factory reset. This restored functionality. As far as I can tell, its still debloated?!? Assuming Samsung or AT&T tried to screw the customization...
Has this happened to anyone else? I really haven't done anything weird minus root and eng boot fixes...! Waiting on Google Play app restoration so I can poke around and gather more details... but device build is still PE1 and I am still on eng boot.
I have a similar issue. My phone was on this morning, but I started getting lots of force closes from random applications. Tried to make a call and it closed phone, then I hear someone through the speaker. Kept force closing but a call was stuck open. I couldn't end it without restarting the phone. On reboot I'm stuck at the ATT logo and phone is hot as hell right now. Going to shut down until I have time to deal with it, as I'm at work right now.
I'm on lunch, whatever happened it forced me to factory reset, unfortunately I didn't back up my device storage, and only pulled mmssms.db so restoring my messages is even a pain right now. Was forced to rerun root.bat. doesn't look like it changed my stock rom any, but a major pain in the ass. Lost my flashfire backup and everything else I didn't bother to sync to my PC. Anyone else have any insight or issues?
madsc13n41s4 said:
I'm on lunch, whatever happened it forced me to factory reset, unfortunately I didn't back up my device storage, and only pulled mmssms.db so restoring my messages is even a pain right now. Was forced to rerun root.bat. doesn't look like it changed my stock rom any, but a major pain in the ass. Lost my flashfire backup and everything else I didn't bother to sync to my PC. Anyone else have any insight or issues?
Click to expand...
Click to collapse
Once you rooted did you use titanium and freeze the AT&T updates. Also being as flash fire isn't a custom recovery (meaning you have to boot your phone up to use it) if never leave my backup on the phone, at least move it to your external SD.
Yes, and I have learned. I didn't previously have an SD card for this phone
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
EDIT/SOLVED: I managed to get it working by going into TWRP, wiping cache and dalvik, installing a new build of lineageos i had already downloaded, not installing superuser, wiping the cache and dalvik again, and rebooting system, and a fresh start of lineage finally loaded. Doubt that's relevant to many people but thought I'd share anyway.
brokemyG2 said:
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
Click to expand...
Click to collapse
you can access the twrp with the power off button and volume less when the lg logo looses the power on and you press again:fingers-crossed:
---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------
brokemyG2 said:
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=HL1wOPe5pLc