Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Bubblewhip said:
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Click to expand...
Click to collapse
Are you using a custom recovery - TWRP or CWM? You need to be using the stock recovery image to encrypt your phone. The nexus toolkit will allow you to re-flash the stock recovery.
One the stock recovery has been re-flashed, you should be able to encrypt your phone. I had to re-flash stock recovery, reboot the phone, then reflash the stock recovery again.
Once the device has been successfully encrypted using the stock recovery, you can re-flash either the TWRP or CWM as your recovery. TWRP supports reading data from encrypted devices, so it is probably the way to go (not sure if CWM dows now, but it didn't last time I looked).
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
randomvector said:
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
Click to expand...
Click to collapse
I haven't noticed a difference in speed, however technically there will be a little bit of a slowdown.
I'm running stock Android, so I don't know how well it plays with custom ROMs, but you can re-flash a TWRP recovery after encrypting your phone with stock Android on it.
If the custom ROM installation wipes the data partition, it would remove the encryption.
I've tried flashing stock recovery using Nexus 4 Toolkit and recovery is back to stock. However the phone is still just rebooting when I press encrypt device. What am I doing wrong?
For some reason I had to reflash the stock recovery, reboot, then reflash the stock recovery again. No idea why, but it worked for me!
Sent from my Nexus 4 using Tapatalk 2
Booted back into stock recovery device is still rebooting itself after hitting the encrypt button, Encryption did not happen.
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Bubblewhip said:
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Click to expand...
Click to collapse
The android with a warning symbol is the normal symbol of stock recovery.
However, I wonder, if you could solve the problem? My nexus doesn't want to encrypt itself too. Flashed stock recovery already twice and it just keeps rebooting when I start the encryption process.
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
c_m_l said:
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
Click to expand...
Click to collapse
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
JohnnyBBB said:
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
Click to expand...
Click to collapse
Old thread, same issue, HTC One w/ OmniROM (m7att). My Nexus 10 did it as well.
The person saying to reflash stock? DOn't listen to that. Doesn't need to be done. Encrypted all my devices w/ TWRP installed.
Airplane mode DID work, though.
I just had this issue with my N4, too. I read on the Google Product Forum that this was because a process prevents from unmounting the /data partition. ("Nexus 5 is not going through encryption process" - can't post link due to being new)
With that in mind, I rebooted into safe mode and then tried again and it worked on the first try (At least it started the encryption process, it's at 10% now)
I had this problem for a looooong time. Thankfully, I seem to have discovered a solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)
Whenever I install a new rom, whether its cm10.2, GE 4.3, etc, the screen off animation stops working after I reboot the phone. It just turns off normally. Not a big deal, but I couldnt find any info on this. Was wondering if anyone else has experienced this or even have the issue solved.. I clean install everytime I flash any rom. So im not sure whats causing this. Iniitially I thought i was freezing a wrong app or something, but I tried rebooting the phone without making any changes and it stops working. This has been happening for the past 10 or so flashes and I believe it started when i started flashing 4.3 roms.
You have to be in latest CWM or TWRP in order to flash Android 4.3 ROMs.
Update the recovery and you'll be ready to flash again.
Search for the recoveries in official websites.
Cheers.
Sent from my GT-I9505 using Tapatalk 4
So today my nexus 4 shut off at around 20 percent batter i didn't really think any of it because that happens often and i just reboot and its back on after charging it. This time however it was different it wouldn't boot it was just stuck on the paranoid android boot animation. I searched online and found out that clearing cache and data all that works so i tried it to no avail. I did the same this again but this time re flashed the rom and still nothing. I then pushed cm 11 into the nexus 4 flashed that rom and nothing. So then the last thing i though about was fully unrooting and going back stock with nexus root toolkit. I tried it and went through but then when good ol kitkat animation started it continued forever. Im out of options now and i don't even have custom recovery anymore what can i do.
I was running Paranoid Android build version 4.45 with hells core kernel.
EDIT---------------------------------------------------
I have clockwork mod recovery back up were do i go from here please help.
Please Help Thanks
skype:ApexDreamZ