Develop Bugs

Galaxy Neuxs Encryption woes!!!

Hey All,
New to XDA but been using this site years so my level of Android knowledge is not bad.
I am currently having a huge problem with my Nexus. I used Google Apps encryption on it recently and that seems to have bricked my phone. I am unable to reset to factory settings to wipe the encryption as recommended by Google and I am stuck now with a bricked Nexus.
I also tried flashing stock roms with Odin which appears to work but the encryption still remains. All I am trying to do is put the stock back on my phone and re-root but I am having no joy. When using CWM to flash a new rom the system does not mount in recovery mode so I can't load any other roms. I have also tried the fastboot method but it stalls on waiting for device all the time.
If anyone has seen this and can help or if anyone just knows how to fix it please help me! I am stuck now with a useless Nexus. I should have just left it alone but as usual I couldn't.
Any help would be so appreciated. Thank you.

By some chance is your phone both rooted with CWM?

Hey, yeah it was so when I did a factory reset it could'nt use the stock bootloader so it didn't know how to wipe it. Unfortunetly once you apply encryption from a Google Apps the only way to remove is to factory reset.
I got around it by fastbooting the stock bootloader, radio and image from Google. Then I completed a manual reset using the original bootloader.
A world of hurt really! I have learned a lot but never going near Google Apps encryption again. It also slowed down the phone too.
Anyhow all sorted now, re rooted and running revolution rom now.

theres another thread with a guy who had the same problem. I wonder if vzw nexus has an issue with encrypting...

If the phone wasn't rooted I would have had no issues. It is simply a problem when it comes to loading roms. In CWM the recovery cant mount the data/system so you can't flash anything. Also doing a factory reset from settings doesnt work because the phone is looking for a stock bootloader which it doesn't have once you root. So I ended up in a loop and could do nothing. Fortunetly I learned all about adb and fastboot this morning, never heard of them before and that allowed me to reload stock and unroot. I still had to wipe the phone using the bootloader as I couldn't get into the phone or past the encryption.
If anyone is having issues with this I will gladly help as I really thought that my phone was bricked and was very frustrated. The only way I got help was from a guy on this tread http://forum.xda-developers.com/showthread.php?t=1392037&page=3

Nexus 7 2013 not going past boot animation

My Nexus 7 2013 running stock 4.4.4 is not able to boot up to the lock/home screen. It just stays at the four dots or petals boot animation indefinitely. It does not freeze(animation goes on smoothly) nor does it go back to the bootloader again.
I have done cache wipe and factory reset.
I have flashed stock 4.4.4 factory image again and in the process unlocked the bootloader as of now.
But there is no change in the situation. I love this tablet and I am desperate to get this sorted out. Please help me.

I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....

ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
Ya I can understand. All we can do is wait for useful suggestions.

bump

Clonazepam said:
bump
Click to expand...
Click to collapse
If the tab gets to the spinning dots, it means the bootloader is not corrupt, so there must be a way to restore. Since there's nothing else you can do, why don't you back up the tab, then erase everything, especially formatting the internal storage (using the format button in TWRP) twice, and re-flash a rom. It seems some residue is preventing the thing from booting up. It happened to me on the TF300 a few times when the new bootloader was incompatible with the old one. Good luck.

graphdarnell said:
If the tab gets to the spinning dots, it means the bootloader is not corrupt, so there must be a way to restore. Since there's nothing else you can do, why don't you back up the tab, then erase everything, especially formatting the internal storage (using the format button in TWRP) twice, and re-flash a rom. It seems some residue is preventing the thing from booting up. It happened to me on the TF300 a few times when the new bootloader was incompatible with the old one. Good luck.
Click to expand...
Click to collapse
I tried that but I had no luck. Any other suggestions?

Clonazepam said:
I tried that but I had no luck. Any other suggestions?
Click to expand...
Click to collapse
Depending on the TWRP version, some claim it would fail to format completely. Phil's Touch (Arter's version 6.58.9) however would. You might want to try that. I personally haven't experienced it with this model, so I just pass the information along. Unless the EMMC physical structure is damaged somehow and cannot be written to, in which case the only solution is a replacement motherboard since you cannot find an OEM Emmc, let alone replace and program it.

ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
So you sent your tablet to ASUS to have the screen replaced and they sent it back to you unable to boot? That's not something you should have to deal with, I'd call ASUS and demand that they repair it.

graphdarnell said:
Depending on the TWRP version, some claim it would fail to format completely. Phil's Touch (Arter's version 6.58.9) however would. You might want to try that. I personally haven't experienced it with this model, so I just pass the information along. Unless the EMMC physical structure is damaged somehow and cannot be written to, in which case the only solution is a replacement motherboard since you cannot find an OEM Emmc, let alone replace and program it.
Click to expand...
Click to collapse
I just tried with Philz recovery but still had no luck. i formatted everything and then flashed a factory image but still it's the same.

_MetalHead_ said:
So you sent your tablet to ASUS to have the screen replaced and they sent it back to you unable to boot? That's not something you should have to deal with, I'd call ASUS and demand that they repair it.
Click to expand...
Click to collapse
That's what I've done now, but I was hoping to avoid sending it off for 2-3 weeks after already not having it for the last 2 1/2 weeks

ems328i said:
That's what I've done now, but I was hoping to avoid sending it off for 2-3 weeks after already not having it for the last 2 1/2 weeks
Click to expand...
Click to collapse
Yeah, that sucks. I'd probably try and fix it myself too. But with what ASUS charges for repair you'd think they'd send it back to you on perfect working order. I called yesterday to see what it cost to replace the screen because mine is all scratched up and they wanted $200. Ridiculous. Might as well just buy a new one.

Any other methods to fix this problem anyone?

Clonazepam said:
My Nexus 7 2013 running stock 4.4.4 is not able to boot up to the lock/home screen. It just stays at the four dots or petals boot animation indefinitely. It does not freeze(animation goes on smoothly) nor does it go back to the bootloader again.
I have done cache wipe and factory reset.
I have flashed stock 4.4.4 factory image again and in the process unlocked the bootloader as of now.
But there is no change in the situation. I love this tablet and I am desperate to get this sorted out. Please help me.
Click to expand...
Click to collapse
Clonazepam - Our sincerest apologies in regards to the issues you're having with your Nexus 7. Please send us an emailed description of the issue along with your Nexus' serial number to [email protected] and we will assist you as best as possible.

Asus_USA said:
Clonazepam - Our sincerest apologies in regards to the issues you're having with your Nexus 7. Please send us an emailed description of the issue along with your Nexus' serial number to [email protected] and we will assist you as best as possible.
Click to expand...
Click to collapse
I bought the tablet in India and I still live in India. Will you be able to assist me here?

ems328i said:
I am in the same situation. I got my device back from Asus repair today, it was unlocked and running a custom KitKat rom, but only the screen was broken and that was what was repaired (at my own expense).
I turned it on and it was stuck at the 4 swirling dots for more than 20 mins, so I wiped the device completely in TWRP and tried to flash a stock factory image (Lollipop) - same problem. I tried flashing a factory KitKat image, also stuck at boot animation.
I then re-flashed TWRP since it had been replaced by the stock recovery, and then sideloaded a custom Lollipop rom (Screwd) - still same problem.
It is strange that I can use adb and fastboot, but nothing gets past the swirling dots. Hopefully someone can point us both in the right direction....
Click to expand...
Click to collapse
Did you update the bootloader to 04.14 ? It is required to update the bootloader to run lolipop. Try flashing the new bootloader.IMG and then installing stock or custom lolipop ROM.

str1ker0ne said:
Did you update the bootloader to 04.14 ? It is required to update the bootloader to run lolipop. Try flashing the new bootloader.IMG and then installing stock or custom lolipop ROM.
Click to expand...
Click to collapse
Yes, I had updated the bootloader. I have now RMA'd again....

ems328i said:
Yes, I had updated the bootloader. I have now RMA'd again....
Click to expand...
Click to collapse
All I can suggest right now is try a different ROM like aosp or cm official. You seem to be doing everything correctly. You can also try flashing the original 4.3 factory image with 03.14 bootloader maybe it'll boot. Then revert back to lolipop.

str1ker0ne said:
All I can suggest right now is try a different ROM like aosp or cm official. You seem to be doing everything correctly. You can also try flashing the original 4.3 factory image with 03.14 bootloader maybe it'll boot. Then revert back to lolipop.
Click to expand...
Click to collapse
Thanks but as I mentioned I have RMA'd it again so i don't have it anymore...

ems328i said:
Thanks but as I mentioned I have RMA'd it again so i don't have it anymore...
Click to expand...
Click to collapse
Hopefully they won't charge you this time.

bump to original question

Boot Looping Help Please

I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks

So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...

Why did you bought a bootlooped phone?

Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.

When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.

See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/

khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.

Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...

khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?

Hardware bootloop can't be fix by software.

Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk

Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....

I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state

bricked nexus 5x out of nowhere

hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers

trier09 said:
hi everyone
after an afternoon of googling I decided I need more help
so this is what happened (at that moment I was running on PureNexus and TWRP:
at some point I noticed that my phone was off, I tried to reboot it, it showed the google logo for a moment, but then the screen went black.
after a while I tried to reboot again, with the same effect...and again
so I decided, hm maybe a factory reset helps and tried to boot into TWRP. tried to boot into recovery, but with the same result as before: google logo appears then screen turns black
next I booted into bootloader and flashed TWRP through adb. but this didnt help either. still everything just as before.
at that point I got a little nervous. then I deleted cache and userdata through fastboot, still nothing.
after some googling I stumbled over a thread which suggested to use the Nexus Root Toolkit for reflashing Stock.
I followed all the instructions in NRT and according to the log (and fastboot), all the images were successfully flashed, but when I booted the screen turned black after the google logo again.
since I was able to boot into bootloader, I decided to lock and unlock the bootloader (at that point I was just trying to see some effect), but nothing worked
any suggestions on what else I could try?
thanks! cheers
Click to expand...
Click to collapse
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.

indian84 said:
If this is not the dreaded bootloop, unlock the bootloader and flash factory image manually.
That should help.
Click to expand...
Click to collapse
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend

trier09 said:
thanks, I was afraid it might be....
I flashed the factory image first with the sh_all option and then manually. both methods didnt work and I couldnt get past the google logo.
Right now Im not even able to boot into the bootloader.
Im assuming theres nothing else the try besides contacting LG support?
Maybe its time to say goodbye to a good friend
Click to expand...
Click to collapse
LG Support it is for you. They have know to replace units that have passed the warranty period by one or two months. Give it a shot

HTC One M9 keeps turning off while in bootloop. Can't connect ADB.

Hello, I've ran into an issue where my phone keeps turning off while in the boot screen. I'm using stock 7.0. What makes it worse is that I can't seem to get ADB connection between PC and phone.
Now I regret my decision of not flashing TWRP earlier, as I wouldn't be making this thread if I had and I could've tried flashing a different rom.
This happened after the phone felt a bit slow, I restarted and then it wouldn't boot anymore.
I have S-OFF if that helps with anything.
Thank you for your help!
_____________________________
Edit:
Right, apparently I can get the adb to work in download mode, but the battery is a bit too low to flash TWRP. I'll see if I can do when it charges a bit.
Edit: So I flashed TWRP, tried flashing a rom and twrp rebooted during the flash.
Edit: I can't even get into download mode anymore. Phone's rebooting and vibrating all the time.
Edit: Welp, can't even get in recovery now. Only place I can access really is the bootloader. Is there anything I can do about it now or is bricked?
So, I tried flashing ruu, getting this -
load_file: could not allocate -2093772439 bytes
error: cannot load 'update.zip'
Click to expand...
Click to collapse
Tried flashing recovery, which did work but I can't boot to it. Getting reboot loops before getting to TWRP.
So I suppose this is it then for this phone unless anyone can help me with it. It's been definitely the most frustrating phone I've owned.

Seems buggered to me. If no download mode then there's not a lot you can do.
Beamed in by telepathy.

Ehh... It's kinda weird how the phone just did that. Tried to flash ROM and it just went.
I kinda feel like it could've been faulty flash all along as I had issues with it where "app has stopped working" was spammed. I factory reset it and it was unusable. Went to O2 for repairs (note that I hadn't meddled with software yet) and they still charged me for it. It worked fine for two weeks and then same issue appeared. Stupid me thinking that trying to fix it by myself could've worked, which I thought I managed to do for a month. Then this happened.
Is there really nothing I can do from the bootloader? fastboot seemed quite functional from it.
Either way, thank you for this answer, even though it was one nobody likes to hear...