Hi xda. I need some advice. I wanted to encrypt my phone. I plugged the charging cable in and put in my password. That was about 9 hours ago, when I was going to sleep.
The phone then rebooted repeatedly and showed a lock with a animated loading circle in it
The problem is it still showing the lock which should mean it is still encrypting. But from what I read it should only take up to an hour.
Z3 Compact D5803
Boot loader wAs unlocked not sure of now
ROttp://androiding .how/rooted-xperia-z3-compact-5-1-1-rom-with-xposed-installed-and-bloatware-removed/[/url]
The internal storage was about 90% full maybe that's the reason it takes so long?
The sdcard about only 3GB full
Or it really just failed. Anyone have an idea how long encrypting takes? And how long with nearly full internal storage? Did it fail? Should I wait longer or make it go off?
Bump. Still at loading lock screen.
Mine took about 20 minutes with storage about one-half to two-thirds full. I did not attempt to encrypt the SD card.
Thanks for the reply.
Its very strange.. Any idea what causes encryption to just not finish? I'm interested why that happened.
I now remember that I couldn't check the box for SD encryption. So that's probably not part of it.
Any suggestions what to do? Recovery and then factory reset? If yes how do I get there because there is no option for turning off. And battery can't be removed.
Edit: I removed the charger nothing happened. Then I pressed randomly camera+on/off+volumedown all three at the same time and then it restarted. Then again lock screen. Reboots again and again and again and always shows that screen.
I can access recovery. So I'm over that. But still I wonder why this happened.
Although being connected to the charger which works!!. And being at ~90% battery in recovery now I have 1%. Shouldn't it load the battery during this?
What recovery are you using, XZDR? Could it possibly interfere with the encrypted boot?
Sent from my D5803 using Tapatalk
Related
My Tilt was low on battery so I went to plug it into my computer. Turns out my brother took my USB cable, so I went to my room and found a USB power plug for an old iHome.(Only after plugging it in did I realize it wasn't standard USB voltage, it was 9v) Well I plugged it in, and my phone immediately turned off, and now it constantly reboots to the Smart Mobility boot screen, vibrates, and restarts again. I left it with the battery/microSD card/ SIM card out for 24 hours, but still nothing. I've tried Hard Resetting, and re-flashing through the microSD card, but nothing seems to work. Any ideas?
erik29gamer said:
My Tilt was low on battery so I went to plug it into my computer. Turns out my brother took my USB cable, so I went to my room and found a USB power plug for an old iHome.(Only after plugging it in did I realize it wasn't standard USB voltage, it was 9v) Well I plugged it in, and my phone immediately turned off, and now it constantly reboots to the Smart Mobility boot screen, vibrates, and restarts again. I left it with the battery/microSD card/ SIM card out for 24 hours, but still nothing. I've tried Hard Resetting, and re-flashing through the microSD card, but nothing seems to work. Any ideas?
Click to expand...
Click to collapse
Have try another battery?, probably your battery was the one that really got smashed with those 9v.
I don't think its the battery, because it still holds a charge, and can boot into the boot loader and hard reset screen fine. Is it possible that the battery just can't provide enough power for the full OS? Is there anyway to boot off of USB alone? I don't have another battery (currently) so I can't really test that.
erik29gamer said:
I don't think its the battery, because it still holds a charge, and can boot into the boot loader and hard reset screen fine. Is it possible that the battery just can't provide enough power for the full OS? Is there anyway to boot off of USB alone? I don't have another battery (currently) so I can't really test that.
Click to expand...
Click to collapse
Try to reflash, since you can get in bootloader and see if that solves the problem.
erik29gamer said:
I don't think its the battery, because it still holds a charge, and can boot into the boot loader and hard reset screen fine. Is it possible that the battery just can't provide enough power for the full OS? Is there anyway to boot off of USB alone? I don't have another battery (currently) so I can't really test that.
Click to expand...
Click to collapse
Same thing happened to me, it had enough power to get and remain in bootloader but not enough to boot OS. Put in a new battery and has run perfect ever since. 3 mon.
denco7 said:
Same thing happened to me, it had enough power to get and remain in bootloader but not enough to boot OS. Put in a new battery and has run perfect ever since. 3 mon.
Click to expand...
Click to collapse
Agree with mate
Sorry for reviving my own post, but i finally got a replacement battery and it still just vibrates, smart mobility screen, then repeats. I just tried flashing it with the stock att rom and the only difference is att screen instead of smart mobility. Any other suggestions?
EDIT: Also tried flashing android but does the same thing, vibrates, flashes boot screen, repeats
Using CM7, had no isses since I got everything working.
However, my NC's battery ran out last night. When I plugged it in today and let it charge, it went to "Touch the future of reading."
I cannot get it to boot past this point. I haven't changed anything recently. So what gives?
a quick search and i found this:
http://forum.xda-developers.com/showthread.php?t=943201
I was having the same issue when i ran my nook out of power. i rebooted into recovery, ran the CWR-removal.zip and rebooted and i was back up.
So how do I boot into CWM? Put it on an SD card from PC? I just had it on an SD to put CM7 on the Nook.
PGibbons999 said:
So how do I boot into CWM? Put it on an SD card from PC? I just had it on an SD to put CM7 on the Nook.
Click to expand...
Click to collapse
Yes. If you still have it on sd from when you flashed CM7, use that.
eyecrispy said:
Yes. If you still have it on sd from when you flashed CM7, use that.
Click to expand...
Click to collapse
I don't I've wiped the SD and been using it as storage. Is there a way to put CWM on the card without wiping it?
I'm running froyo on the emmc and had the battery drain out - got stuck at the future of reading screen. I wound up reloading froyo from the sd.
Peter
pwlorraine said:
I'm running froyo on the emmc and had the battery drain out - got stuck at the future of reading screen. I wound up reloading froyo from the sd.
Peter
Click to expand...
Click to collapse
Did you have to use CWR?
I have the same exact problem.
Me and my girlfriend just bought a Nook Color each, and rooted it with CM7.
We have the 3.0.0.6 bootloader/recovery thing.
The problem occurs when we drain the battery (we usually do before charging to preserve the battery), when we connect the power (the Nook is off) it says "battery charge to low to power on, try again in 15 minutes", and after a couple of minutes, it turns on, showing "Touch the future of reading." Normally after this we would see "Loading", then "Android_", but instead it is locked on "Touch the future of reading."
If I turn it off, it turns it self on again, and it is stuck on the same place. I let it be for 1 hour, still the same. As I'm not to fond of having the screen on all the time, I tried turning it off, then quickly press "Power + Volume Up + n". This started the nook in recovery mode, giving me the message that "install failed, turn off and on again" (which I guess is because I have deleted the original nook partitions). After this, I turned it off, and then it was completely off, not booting up again. Then I tried holding power to power it on normally, and it worked.
The power was connected at all times.
What is wrong here? It seems like the nook doesn't like being off when charging, meaning you have to be careful to never drain the power 100 %, or turn it off when it's below 10 %, because then it won't turn on.
Strange thing.
nordemoniac said:
I have the same exact problem.
Me and my girlfriend just bought a Nook Color each, and rooted it with CM7.
We have the 3.0.0.6 bootloader/recovery thing.
The problem occurs when we drain the battery (we usually do before charging to preserve the battery), when we connect the power (the Nook is off) it says "battery charge to low to power on, try again in 15 minutes", and after a couple of minutes, it turns on, showing "Touch the future of reading." Normally after this we would see "Loading", then "Android_", but instead it is locked on "Touch the future of reading."
If I turn it off, it turns it self on again, and it is stuck on the same place. I let it be for 1 hour, still the same. As I'm not to fond of having the screen on all the time, I tried turning it off, then quickly press "Power + Volume Up + n". This started the nook in recovery mode, giving me the message that "install failed, turn off and on again" (which I guess is because I have deleted the original nook partitions). After this, I turned it off, and then it was completely off, not booting up again. Then I tried holding power to power it on normally, and it worked.
The power was connected at all times.
What is wrong here? It seems like the nook doesn't like being off when charging, meaning you have to be careful to never drain the power 100 %, or turn it off when it's below 10 %, because then it won't turn on.
Strange thing.
Click to expand...
Click to collapse
A couple quick observations--
The 3.0.0.6 recovery thing, also known as clockworkmod recovery, is an older version, so you'll want to update that when you can (via Rom Manager probably as that's the easiest way).
You're misusing some terms. You don't "root" with CM7-- rooting is the process of enabling the root/superuser account, typically on the stock firmware. CM7 is an alternative software/ROM/operating system that includes an enabled root account, but is probably best known for the other additional features it includes beyond standard Android.
The wait-for-more-power message comes from the bootloader, called "u-boot". After you see that "Touch the Future" message, you should be seeing "A N D R O I D _" which is the kernel loading up and the boot starting. If you don't see that at all, I'm guessing one of the following files are missing/messed up on your boot partition (p1, the first partition on your device):
uImage -- the kernel file
uRamdisk -- a small "bootup" file which includes several files bundled together that is necessary for a successful full boot.
Both of these should have been installed when you installed cm7. Assuming you have tried previously, you might again try reinstalling the latest cm7 update.zip from scratch. As of now 7.02 is the latest stable version. I believe there is a thread by eyeballer that walks you through the steps, or if your'e a Windows user, you could watch this video.
Good luck!
funny _ i have the same issue but my battery never ran out - just started happening after I transfered some music to my SD CARD.. If I take the SD Card out upon a reboot, the NC boots fine.
Not sure but when I keep the SD card in - the boot stays at Power of Reading?
The newest update bricked the device and i'm looking to get some files off the phone before using the sbf to restore. Is there a way to have ADB access if you are not able to successfully boot into the OS?
Hey, as an avid flasher (gosh i believe i did it over 15 times just this month =O), I noticed that even if you reflash everything on your phone, only your apps are erased as well as some data. If you're looking to back up stuff in the internal SD card, you should be fine as flashing won't touch that. As for if you're looking to grab some user data, I don't believe there's a way to do that, but I could totally be wrong. Sorry if that didn't help =\
if you reboot holding arrow down, it seems like I saw a USB enumeration option if you keep pressing down volume through the option. That may be a way to get the stuff off, depends what you want to do though.
I can also confirm SBF'n back to factory will retain SD info. I did it this morning to update to latest OTA.
Accidentally rooted and bricked ... but now the battery won't charge ... so RDS says battery is too low to flash ... any suggestions?
My only thought is to go to the ATT store and ask if they can swap batteries, but I don't see why they would.
If you plug it into the wall it should charge with the phone turned off. If the battery is completely dead- it will appear nothing is happening. Just leave it plugged in for a while, drink a beer, do something around the house, then come back. It should show a charging light at this point or have tried to turn itself on.
I will also 2nd that SBF flash will keep the files on /sdcard/ level intact.
Thanks for the quick reply...I feel silly asking, but how do you turn it off? As soon as I plug it in it turns on and gives the message "Failed to boot 2 / Starting RSD mode / Battery too low to flash." I press power, nothing happens. I hold down power, nothing happens. I hold Vol Down and press power, nothing happens. I charge overnight 12+ hours with the screen on, it gets warm, but otherwise nothing happens. I charge with the USB to the computer, the screen stays off, and it seems to get a little bit of charge (enough so that it doesn't shut off as soon as it's unplugged), but hours of trying to charge this way nets the same error message. She's bricked. I guess you can't flash without a battery in place?
Edit: Or just buy this spare battery desktop charger
My next best suggestion for you is to find a way to get 3.7 volts of power to those battery pins. Either with a regulated power supply or another lithium cell battery. I'm not sure whether or not the detection circuit will allow the phone to boot or not or if that is charge-related only, but it would be an alternative to keeping a bricked phone. If you choose to try to run this without a battery keep in mind wall wart type power is unstable (read: voltage changes) at different current draws.
Went to the store near closing time (10 min) and they gave me a fresh battery instead of going through warranty, said that could take days with no phone. Fortunately he didn't test the battery and, upon putting a new one in, he only looked at it long enough to see the dual core logo and not the Failed to Boot message.
Flashing worked perfectly after I had a fresh battery, thankfully. No longer bricked, no longer using 6-yo crackberry!
Yesterday, my phone just shut off. It wouldn't boot back up after multiple attempts. Finally, it booted back into CM7, but I was missing half of my applications and my SD card wouldn't finish checking. After reinstalling everything twice (the first round didn't work), my phone still won't get past error checking the SD card and the battery will no longer fully charge. Regardless of how long it's plugged in, it doesn't get past the mid-50% mark. Ideas? THoughts?
When you did the reinstall did you do a system wipe? If not I would try that. Now has the phones suffered any physical damage (drop, water, etc)?
I noticed today that my phone has maintained a 100% charge, even hours after being unplugged. I tried rebooting, but that didn't fix it. I tried to boot into recovery (I have TWRP) to see if I can wipe battery stats, but once I selected recovery, an empty battery icon appeared and the phone shut off. I tried to boot up normally again, and the phone crashed outright during the boot animation and shut off.
After a minute the phone started up by itself, and went through optimizing apps (I plugged it into a charger out of curiosity). Now that the phone was able to boot, the battery is at 5% and finally charging again.
Has anyone else had this happen with their N6, or have any idea as to what might cause this? For reference, I'm running the latest stock image (LMY48I), just unlocked, rooted, and with custom recovery.
Only thing I have seen is apparently wireless charging screws it up. Go into bootloader>bootloader logs and reboot from there. May reset it.