Hello,
Firstly I want to apologies for creating new thread for a thing on which there already number of threads here. However when I was in this big trouble (at least it was for me) on Saturday evening I searched everything and couldn't find a working solution.
And I would like to request moderator or someone who has better knowledge of what did happen and how it got fixed can make it guide with his thoughts if there is a need to .
Let's start with my story. I unlocked bootloader first time and flashed CWM. While restarting I tried to wiped data as told in one of the tutorial and then I restarted. As long as I remember it said you would not be able to boot in CWM again and I said Yes. That's the time when it got stuck to X logo. I flashed CWM again and then tried to restart still nothing happened. I got further and flashed CM 10.1.2.
Then it got stuck to CM logo. I wiped cache, data, dalvik cache before and after; nothing helped. Then I managed to Power off phone and planned to go for sleep. I thought I have ruined my phone
This is how I fixed it:
At the last moment I thought to give it a last try before sleeping. I could not have went to sleep with that I thought Then I rebooted my Nexus 4 in CWM and went to 'Mount and Storage'. Mounted everything which were in unmount state. Formatted data. Went back a step then wiped data. And restarted. And there it got rebooted in CM 10.1.2 :highfive:
Related
Hey guys. I'm trying to figure out what's going wrong with my Transformer. I'm not experienced with Android development/ROM's so please bare with me.
Rooted my first Android device about a month ago. Made a stupid mistake placing the ROM I was planning to use on the external SD card & didn't backup the install I wiped. Recovered with an official Asus ROM & after about two hours fiddling around I managed to root & load my first ROM (Revolver, whoot!). Very pleased with myself!
Have been using the Revolver ROM for a month without any problems. No deep sleep etc, everything worked perfectly. Using the latest version of Clockworkmod, also no issues so far. Strange thing is that since last monday everytime I (re)boot the device it loads CWM instead of the Android OS. I can get back into Android bij holding volume down during boot & choose to cold boot. Not a big issue but very annoying & can't seem to find the fix.
Searched Google & XDA for a solution. Updated Revolver to 1.3.1 beta, also found the repack by Koush for CWM. Tried fixing permissions, clearing cache, clearing dalvik, wiping & starting over, etc. Everything I tried so far does not fix the CWM-loop I seem to be stuck in.
Would really appreciate some help, I'm probably looking in the wrong direction here. Thanks in advance.
Found something
Finally got out of the CWM loop, found a solution here: http://forum.xda-developers.com/showthread.php?t=1622814&page=2
Strange thing is that after I flashed it with the fix CWM changed to the touch mod I recently installed but never seemed to work. If I understand correctly the fix only deleted the first few lines in the config where the boot in recovery flag should be.
Afterwards I factory wiped the unit & flashed it with a clean ROM. Currently re-installing my apps. I do not have a good feeling on this, tablet seems sluggish last couple of days & I can hear a soft click when the unit reboots. Same sort of click a laptop hdd would make.
Think it's dying on me...
The title says it: My TPT is bootlooping and when I try to wipe the cahce/Dalvik-cache in recovery, it just won't finish.
I'm running ICS (OTA3), but the same thing has happened to me before with Honeycomb.
I don't want to wipe data! Any ideas?
You qualify for a new motherboard if you want it.
But that would not preserve my data
My understanding, and I could be wrong, is that once you start boot looping you need to have made great backups prior to the issue because all you can do is send it in for repair. Hopefully you have such backups if you have root.
Not good news so I hope I'm wrong. Wishing you luck.
I pulled some of the data via adb and then did a factory reset (in recovery). Now it boots again.
I just hope it won't happen again. This was the second time already: Once it started bootlooping in Honeycomb and now ICS. It just came out of nowhere (it booted up fine many times before).
Excellent news. Didn't think you could pull anything with adb while bootlooping. Should have tried that straight away.
I still could enter the recovery mode. Strangely, wiping cahe/dalvik cache alone didn't work (it wouldn't wipe), but wiping everything (which also includes dalvik cache) worked...
I still lost some important data, but at least my tablet works again. I just hope it won't start bootlooping again... but I'll definitely make sure to have an automatic backup solution set up just in case.
Good show. At least you're not bootlooping. Too bad about the data.
Hi,
I have a nexus 10, rooted running latest nightly CM (19/12) and has been running fine without issues.
I turned it on this morning and its sat at the Google boot logo (and doesnt go any further).
I booted to recovery and did a reflash, wiped cache, wiped dalvic etc ... no joy.
tried a complete factory reset still no joy, is not booting past the google screen.
what next?
thanks
Dan.
DanielGwalter said:
Hi,
I have a nexus 10, rooted running latest nightly CM (19/12) and has been running fine without issues.
I turned it on this morning and its sat at the Google boot logo (and doesnt go any further).
I booted to recovery and did a reflash, wiped cache, wiped dalvic etc ... no joy.
tried a complete factory reset still no joy, is not booting past the google screen.
what next?
thanks
Dan.
Click to expand...
Click to collapse
Sounds like its something in the /system or /boot partitions, maybe. You might need to download the official, completely stock N10 firmware that the device came with and flash that to fix the problem. You can probably just google search for 'stock Nexus 10 firmware' and find a download link somewhere. Of course, if you have a backup file of before you flashed the CM nightly, then you could just restore that and it would work in much the same way don't panic, there is always a way
I got seemingly the same problem. Was copying a movie to the tablet and it crashed as usual. Probably ****ed up the file system or something. Now im traveling for the first time since I bought the tablet and it doesn't work. Grrrreat. :/
Edit: while I was sulking on the way to the airport (actually I wasnt sulking as I just got a new job 20 minutes ago yay) the tablet decided to boot up just fine when I wasnt watching.
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