[Q] Froze in factory data reset - Xoom Q&A, Help & Troubleshooting

Ok, so I just got my Moto XOOM LTE today. Now, it was working fine. I updated the software and was still working fine. Went to work and when I came home, I was playing with it and it started freezing. Once, then twice then I couldn't use it without it freezing. I turned it off and booted into recovery. Did a factory data reset and it froze. Twice in the middle. Here is what is says.
-- Wiping data...
Performing BP clears...
E:finished unsuspend
Epen mdm_ctrl ok
E:Finished boot BP to normal mode
E:from flash to normal mode
Epen dev
E:engine init finished
E:Successfully wrote 13 bytes.
E:Transferred 13 byte(s) CMD opcode = 0x0012 to aux engine succeeded.
E:write finished
E:Attempted to read 12 bytes and read 12 bytes.
E:Successfully read 12 bytes.
BP clear failed.
Formatting /data...
and this is where is freezes. 1 min... 5min... 15min... 30min... and I restart the tablet and it stays in the boot animation for well over a half hour before I try again.
If there is anyone with any information on this matter, please let me know. I have never seen this and I have rooted my DROID Inc. and HTC TB and flashed ROMs, kernals, radios, etc and have never seen this issue.
Also, I AM NOT ROOTED, but am running that latest software 3.2.
Again, anyone with information, please let me know. Thank you.

Related

[Q] Wifi XOOM 3.2 boot loop help!

First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Have you tried to reinstall firmware?
Regards.
GReddySetGO said:
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Click to expand...
Click to collapse
No need to panic.
When you rooted, did you install CWM Recovery, and if so, do you have a recent nandroid backup? Have you tried rebooting into recovery?
What steps have you followed to get out of your bootloop?
Yes, I have Clockword Mod Recovery 3.2.0.0 R4c 100611-1150
Upon attempting a restore everything appears to work properly until the end when it gets to restoring data, I get an error, regardless of which restore image I use(I tried all the ones I have). It reads as follows:
"Restoring data...
Error removing /data/data/com.noshufou.android.su/cacheError while formatting /data!"
I also attempted a clean wipe/factory reset with similar unsuccessful results. I get an error during formatting data, which reads:
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheFormatting /cache..."
The rest of the formatting appears to run successful for /sd-ext and /sdcard
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
jerrycycle said:
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Can you please provide me with more detailed instructions?
From the advanced menu I see:
Reboot Recovery
Wipe Dalvik Cache
Wipe Battery Stats
Report Error
Key Test
Partition SD Card
Fix Permissions
Sorry, we're forgot talking about Cwm. It's under mounts and storage.
Still the same result as before... I went to mounts and storage > format /data
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheError formatting /data!"
Try format system first then data and cache.
My suggestion would be to go back to stock and then re-root. You can find the stock download on the Moto Dev home page.
+1. Restocking link. MOTODEV > Produ / Software http:/.ly/sQtpKQ bit cts > Device. Then use universal root method reroot.
Sent from my Xoom using Tapatalk
Thanks everyone! I was hoping I would be able to fix it without going back to stock, but since I was unable to I just went that route.
Going stock worked, and I am back to where I was before, so thank you for the advice! In case anyone else may have this problem, this is what I did:
Went back to stock using this: http://forum.xda-developers.com/showthread.php?t=1049485
Then rooted using this: http://forum.xda-developers.com/showthread.php?t=1242241
Then got back to 3.2.1 using this: http://forum.xda-developers.com/showthread.php?t=1278214

Stuck at "erasing" when doing a factory reset?

Anyone else had issues performing factory resets? My Nexus 5 seems incapable of completing it. So far I have tried doing a factory reset from the settings menu 4 times. Every single time it locks up on the erasing step. I don't mean it takes a little longer. I have let it sit for almost half an hour and the little android robot sits there taunting me.
Every time I have had to manually go into the bootloader and sideload a factory image, which works fine.
Any ideas why this problem is occurring? Faulty memory maybe?
Same issue here, phone is getting nice and warm but the little robot just sits there twiddling his antennae. Forced restart either normally or into recovery mode lands me right back on the erasing screen, looks like nothings going to happen unless I intervene another way. Any ideas?
Try pushing the system.img using fastboot. Might be best to start over and do a clean install.
Have you tried doing a factory reset in recovery instead?
Sent from my Nexus 5 using Tapatalk
Same problem
I have the same problem with the loop at the erasing screen. It will not go into recovery so that I can fix it. I tried flashing the Stock Rom again but no use. Please help me or at least give me some pointers what to try next.
jizkidjnr said:
Same issue here, phone is getting nice and warm but the little robot just sits there twiddling his antennae. Forced restart either normally or into recovery mode lands me right back on the erasing screen, looks like nothings going to happen unless I intervene another way. Any ideas?
Click to expand...
Click to collapse
martinancevski said:
I have the same problem with the loop at the erasing screen. It will not go into recovery so that I can fix it. I tried flashing the Stock Rom again but no use. Please help me or at least give me some pointers what to try next.
Click to expand...
Click to collapse
I have the same problem
I'm sure you wait a long time...but if not, mine probably took 10-15 minutes to finish...
Sent from my Nexus 5 using xda app-developers app
i have the same problem
What is your recovery? Version # also? How did you root? <--- this goes to the rest of you guys too because it seems like its happening to more than one person.
Follow this: Maybe flash the stock recovery found in here http://forum.xda-developers.com/showthread.php?t=2513701
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
^^ the command
edit: on second thought start over.
lpforte said:
Anyone else had issues performing factory resets? My Nexus 5 seems incapable of completing it. So far I have tried doing a factory reset from the settings menu 4 times. Every single time it locks up on the erasing step. I don't mean it takes a little longer. I have let it sit for almost half an hour and the little android robot sits there taunting me.
Every time I have had to manually go into the bootloader and sideload a factory image, which works fine.
Any ideas why this problem is occurring? Faulty memory maybe?
Click to expand...
Click to collapse
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
iori said:
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
Click to expand...
Click to collapse
ADB sideload: place the rom you want to flash in the fastboot folder and in the phones recovery select adb sideload, then on the pc in cmd type: adb sideload namerom.zip and it will start flashing.
gee2012 said:
ADB sideload: place the rom you want to flash in the fastboot folder and in the phones recovery select adb sideload, then on the pc in cmd type: adb sideload namerom.zip and it will start flashing.
Click to expand...
Click to collapse
thanks
but i finally found out that the stock recovery was somehow corrupted after factory reset
then I unlocked the bootloader and flashed TWRP recovery, and voila! my device booted normally
Nexus 5 hung at reset
iori said:
hello
I have the same exact problem
I'm completely stock and I want to reset all so I do factory reset from menu setting, backup & reset
And since, my nexus stucked in "erasing...."
I have tried flashing factory image according to this guide, succeeded, but then still stucked in android logo with endless progress bar (but this time without "erasing....")
Need help how to restore it
All I want is to factory reset
How did you actually sideload factory image?
thanks
Click to expand...
Click to collapse
Exactly the same problem here. Nexus 5 running 4.4.2 kept powering off randomly roughly once a day. Attempted a factory reset and it got stuck at erasing. Having unlocked the bootloader and following the steps to unlock and reboot, I have a progress bar with the animated android icon, apparently stuck at the same stage, but without the "erasing" caption.
As far as I'm concerned, I can nothing with the phone at present short of taking it back, though they'll likely take issue with my attempts to rectify myself
mannschaftpag said:
Exactly the same problem here. Nexus 5 running 4.4.2 kept powering off randomly roughly once a day. Attempted a factory reset and it got stuck at erasing. Having unlocked the bootloader and following the steps to unlock and reboot, I have a progress bar with the animated android icon, apparently stuck at the same stage, but without the "erasing" caption.
As far as I'm concerned, I can nothing with the phone at present short of taking it back, though they'll likely take issue with my attempts to rectify myself
Click to expand...
Click to collapse
I'll add that I've also tried the Nexus Root Toolkit v1.8.0 to flash stock. Appears to go fine, recreating the file system and loading software, then as soon as it gets to the "erasing cache" step it just sits there for hours and makes no progress.
I know I probably shouldn't promote toolkits but you can always try this. Seems to have worked for a lot of people.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from The Deathstar
Same thing happened to me yesterday. My N5 is rooted, running stock rom and recovery. I had some corrupted app date showing in Titanium that I could not remove that were causing a Play store issue for me. I backed up my phone with TB and ran a factory reset in settings. The phone was stuck on the 'erasing' screen for maybe 20 minutes, so I put the phone in fastboot and from there back into recovery. This took me back to the 'erasing' screen to my dismay. I put the phone down and started searching for a solution online, but then I noticed after about 7 minutes the erase process had finally finished on its own and the phone rebooted normally again.
Based on what others are saying in this thread it appears the factory reset process via settings or stock recovery can hang sometimes. If you power off, start the phone in fastboot and select recovery again, I'm guessing the factory reset process restarts and hopefully it will then work properly the next time, like it did for me.
Well when I did a factory reset from settings, it took nearly 20-25 minutes to finish. The next time I did a reset, it completed within 10 minutes
I guess this problem occurs randomly.
Be patient
My guess is that you just need to be patient -- my device took nearly 45 minutes to reset. It seems to me that the time required is proportional to either the amount of data or the number of files you have on the device. My device had a mix of large files (such as musics and photos) and many many small files (sensor data log files), so it's hard for me to say which of those contributed more to the long reset time.
Based on what others are saying in this thread it appears the factory reset process via settings or stock recovery can hang sometimes. If you power off, start the phone in fastboot and select recovery again, I'm guessing the factory reset process restarts and hopefully it will then work properly the next time, like it did for me.
Click to expand...
Click to collapse
This worked for me too. On the initial 'Return to factory defaults' it got stuck for about 45 minutes. I then follow the advice above:
- Put the N5 in Fastboot by pressing: Vol. Up + Vol. Down + Power
- Select: Recovery and press on Power to proceed
- Phone reboots, still into the 'Androidman' but it seems that the 'Return to factory defaults' also restarts.
- Wait about 10 minutes and the Phone powers down automatically. Upon startup you enter the 'Initial configuration menu' so the factory reset has been completed.
Still stuck on Erasing screen, running out of options
Hello,
I am a newbie with zero developer knowledge and received my Nexus 5 in the mail yesterday. I liked the phone specs and that is the only reason I got it. I left it alone while it charged up and the first thing I did once it was finished was perform a Factory Reset (it was a "like new" phone so I just wanted to be safe) and have been stuck on the Erasing screen ever since. Pressing Vol- and Power button does take me to the bootloader screen, however, any option I choose by pushing the power button, such as Recovery Mode, sends me back to the Erasing screen. Pushing Vol+, Vol-, and Power shuts the phone off completely. Holding the Power button down does nothing more than restart the phone into the Erasing screen. I have also let the phone die twice and as soon as it has enough juice to come back on, it goes straight to the Erasing screen. Everything on the phone is stock and it is completely unrooted. The bootloader screen also indicates it is unlocked. I have attempted to flash it as per instructions I have found on here but I am unable to download the stock factory images. It gets to about 90% before the install fails and I have tried to install three times already. I do have the 15 Second ADB installed, however. I assumed the install of the factory images failed because I don't have WiFi and I'm running completely off of limited 3G data (I live in the middle of no where with no high speed internet to speak of). So in lieu of all that I have attempted, is there ANYTHING at all that can be done to get the phone off of this Erasing screen? Or do I just need to try and return it because it's useless at this point? I did at first let the process run but it's now been 24 hours stuck on this Erasing screen with no improvement. I'm fairly certain it runs KitKat 4.4.0.

[2016]Random Reboots on my ONE. Please help.

Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").

Wokeup to my phone stuck in a bootloop... [SOLVED]

UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!

Galaxy tab 2 p5113 rebooting by itself

The tablet can turn on for a few seconds, but it reboots once again.
I tried to factory reset as fast as I can throu settings, but it just doesnt work
I tried to factory reset using recovery, it says that it worked, then I reboot system and it says error, and the device is just like before, with all the apps and such.
I tried flashing stock rom and it was installing system, and then it failed.
I dont know what to do now, it got stuck at like 30%
I dont know if I should just try again, or maybe the file I used was wrong, or what do I need to do?
Edit: I just turned it on, and its just like before, it turns on for a few second, and then it reboots itself. I dont understand
Sounds like the emmc sudden death.
Search android andi's github page. It explains that the emmc goes to read only and the end of life. Only fix is a new motherboard.

Categories

Resources