My phone was acting strange these past few days. I had my friend look at it to try to fix it, so he did a "fix permissions" and tried wiping the cache. (I am a noob at this still, so he knows way more on what he's doing than I do)
Nothing he seemed to try ended up working, so in the end I ended up wiping the entire phone and reflashing the same CM7 ROM on my phone to get it back to a fresh start and to just restore everything after. I ended up recovering a few of the apps I had through Titanium.
Long story short, I woke up this morning and looked at my phone and it was back to my old setting about 4 days ago, when I made the NANDROID backup.
What happened here? and is there a way to get it back to the setting I had the night before?
Related
I tried restoring the stock battery icon using ACS 1.1 and my phone got stuck in an endless reboot cycle. I kind of started freaking out as my phone had been acting flawlessly prior to this and I was scared of corrupting my data. I had a recent restore point saved (I have MyBackup make one every morning while I'm sleeping) but that would mean I'd have to wipe my phone and after everyone complaining about how hard it is for them getting ACS 1.1 to work on there phone I was scared to test my luck a second time. I thought the only other option would be a battery pull which would lead to bad data with bad backups. So instead of following one of those two options I three finger rebooted out of the loop and immediately three finger booted into CWM. I wiped only my cache and dalvik and then reflashed 1.1 over the existing one. I then rebooted and the only things I had to do were reflash my Vision kernel and delete a few apps that I did not want that come with the ACS rom that got reinstalled. I assume none of my data got corrupted and I know this probably won't save everybody from corrupted data due to endless reboots but just thought I'd share my method. So far everything has been running just as good as ever.
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?
My G2 has been acting really funky lately, hanging on boot and not being able to "hold" recovery flashes. I'll start from the beginning of my little story.
On Saturday, I wanted to do a nandroid backup from TWRP (not sure which version, an older one but not terribly old). It failed several times. I went back into the OS (CM 12.1) and backed up all apps and app data to an OTG USB via Titanium Backup. This was successful. I tried to go back into TWRP a second time. Nothing. Recovery is not even there, I get a security error from what I believe is fastboot. I went back to CM and tried to re-flash TWRP. Now I get a security error on the LG screen. Nothing would boot, no recovery mode, I did have download mode although I had no PC with me so I didn't know this at the time. I was away last weekend so I had to go without a phone for a day... which was actually... kind of pleasent. Don't ask me why I carried two 32GB USBs and an OTG adapter on my keychain but no laptop, because I have no idea why I would do this, lol.
Came home Sunday afternoon and decided to nuke the whole phone with a TOT flash. Since I always wanted to try CloudyG2 since we all know AOSP-based ROMs don't do the camera justice, I went ahead and TOT flashed, re-rooted, re-AutoRec, etc. Everything worked wonderfully; I did a full wipe in TWRP, flashed in Cloudy, then the KK radio, then Xposed. Played around with things like XCam and a few Xposed modules. Everything was working awesome, so I did my restore in Titanium. Took a few hours, but Titanium says everything went fine (sans for a few CM apps which did not restore by design I guess). I checked out a few apps, all my data is there, wonderful. Titanium told me to restart so after poking around a bit, I went for the restart. Hang on boot. For several hours. Tried to go to recovery, fastboot security error. Seems it can't "hold" recovery or something else that I'm flashing?
Clearly I am doing something incorrect here with flashing and all that, but I can't figure out what. I'm not new to flashing and modding, and I've flashed regular CM updates and other goodies onto this G2 for quite a while with no issues. I'm going through the same steps I would normally with CM, and I've had plenty of success with that. Any ideas what I am doing wrong here?
Had same issue and know I hard bricked it trying to get it fixed ... Off to a different phone I guess .. Not sure why it wouldn't hold a recovery either after a few hours ... I gave up .. Good luck
Sent from my SCH-I535 using XDA Premium 4 mobile app
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!
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted