I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
Related
So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.
Bump
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.
This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?
I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2
Hello to all. First, thank to the devs for all the fantastic work done, and to all the people willing to check and answer these threads. So down to my problem.
When I first got my S5 (SM-G900F) I immediately rooted with cf-autoroot. Tripped knox but worked well. From there I went on to install Twrp and then CM 11. The bugs drove me off, so I wanted a tw based rom. At the time I chose XtrStoLite (spelling?) And that worked a treat.
So after a while I found alliance rom and thought wow, this is great. So I installed it as per the instructions in the OP. Now we get to problem one: I got stuck at the Samsung boot screen. No boot logo, nothing, no matter what I did, even formatted /system, still nothing. I tried a few suggestions from the extremely helpful dev, @Goldie, none of which worked, such as flashing another rom first, so I tried with cm and slimkat. Didn't work. Tried updating supersu, didn't work. Tried different TWRP version, nothing. Tried Philz. Tried different Kernel with and without SELinux set to permissive and still it would need a battery pull at the Samsung "powered by android" screen.
Okay, last resort, flashed stock for my country (south africa), flashed TWRP, installed towelroot, rooted, flashed newest supersu, installed busybox and retried. This time something changed. Instead of freezing at the first Samsung screen, it now showed "Set Warranty Bit: kernel" in yellow at the top. Then the screen would go black, phone would vibrate twice and then reboot. So now I had a boot loop.
It was suggested to try omega, to see what happens. Well, it works fine. To date I've tried 5 different working roms. Was told to flash via omega, so I did, but same issue. At some point when I was on stock I even did a factory data reset, effectively wiping sdcard. Just in case. Formatted the external sdcard too. Formatted everything from /system to dalvik to /cache and /data, and eventually /data/media, and still that didn't work.
I'm really at a loss here. I'm the only one of all the other users with this issue. The devs have gone way over and beyond to help me, and that makes me happy. I donated because they've done more than others would. But basically I just need ideas of what the problem could be and why this is happening, if anyone has any ideas.
Find a screen shot of my "About" page here.
My 2 year old pushed the wrong pin 5 times and locked up my encrypted S4. Now when it asks for pin after restart and I put in the right one, it says it's wrong. I tried to Odin a fresh mk2 stock rom, but I kept getting errors. Write being enabled might be the problem, but, I don't know. Thanks!
sether52 said:
My 2 year old pushed the wrong pin 5 times and locked up my encrypted S4. Now when it asks for pin after restart and I put in the right one, it says it's wrong. I tried to Odin a fresh mk2 stock rom, but I kept getting errors. Write being enabled might be the problem, but, I don't know. Thanks!
Click to expand...
Click to collapse
Hate to say it but I think trying a factory reset might be your best best. Good luck..
BIGSAMDA1ST said:
Hate to say it but I think trying a factory reset might be your best best. Good luck..
Click to expand...
Click to collapse
Wish I could. I keep getting the "restart kies" screen. The one time I was able to get into recovery mode and tried a factory reset/wipe, cache wipe I thought I was successful. When it booted up I thought I was golden and then realized my wifi wasn't working and neither was bluetooth. So, I went back into ODIN download mode and tried to flash the MK2 at that point and it failed and failed and failed. Any suggestions on factory resetting it?
I used to have my S4 encrypted but I don't anymore because I have heard it creates issues. I don't have a suggestion outside what you have tried, when you are flashing a new ROM, there should not be any issues once it has been completely wiped. Another option is to wipe and try flashing a custom ROM instead. Good luck let us know what happens.
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
FlinderMouse said:
I looked around and couldn't find a solution for this.
I flashed to the GPE ROM upon getting my new S4; everything went smoothly and the ROM worked. However, when I went to activate it with Ting this evening, I learned that I should have activated on stock firmware then flashed the custom ROM. I used ODIN to attempt to restore to stock and I ended up at a screen that said something along the lines of "Firmware upgrade has encountered an issue". I rebooted several times into download mode, but this message appeared every time I tried to boot to either revovery or Android. Conveniently when I went to see the error to provide the exact wording, it booted straight to the GPE ROM.
I still need to restore to a stock ROM though to activate on Ting. What is the process for this (even a link to a thread/post I overlooked will do)?
Click to expand...
Click to collapse
Try a factory reset and then install stock ROM
i7vSa7vi7y said:
Try a factory reset and then install stock ROM
Click to expand...
Click to collapse
Could you point me in the right direction for that? Everything I have tried so far seems to fail...
Edit: I got back to the NAE stock rom, but I can't downgrade the modem from NG2 back to NAE...
Edit2: I didn't need the correct modem to activate, I guess. Flashing back to GPE, will update this again.
Final Edit: Once I activated on the stock ROM, everything seems to work perfectly on the GPE. Thanks for the suggestion, i7vSa7vi7y!
Ok, I think I'm in a deeper trouble than usual.
I've made a nandroid backup like usual and flashed the latest Dirty Unicorns ROM (http://forum.xda-developers.com/nex...-dirty-unicorns-v10-0-official-6-0-1-t3326798). It didn't work as well as I had hoped - was getting force-closes on practically everything. So I wanted to restore the backup. It restored, but didn't load. Odd, so I thought let's restart the phone. So I did, but the phone just kept sitting on the DU logo and not load at all. Ok, so let's clear both Dalvik and Cache. Still doesn't boot, just sits on the logo. Ok, let's factory-reset the phone, re-download, re-install the ROM, clear everything and try again - still the same, never boots. Ok, super weird by now, never happened to me before. Already took out the trusty old Nexus 5 as the backup, as things are getting more complicated.
So I tried flashing two other ROMs (CM13 and Exodus), but the same thing happens - it just sits on the respective ROM's logo. Can anyone tell me what's happening? I'm including a pic of my bootloader. Looking at the BL and Baseband values, they looks different - are they supposed to be the same?
Might be worth going back to the latest stock build to get all your firmware in order then flash a different rom afterwards.
Ok, don't know why or how it happened, but my TWRP version was still on 2.8.x.x, even though I'm sure I flashed the newest one. I flashed the 3.0.2.0 again, but the situation is still the same.
brichardson1991 said:
Might be worth going back to the latest stock build to get all your firmware in order then flash a different rom afterwards.
Click to expand...
Click to collapse
From here? http://forum.xda-developers.com/nexus-6p/development/rom-nexus6p-stock-roms-t3234067
From here sorry: https://developers.google.com/android/nexus/images#angler
if you get stuck follow Heisenberg's guide step 10 :
10. How To Flash The Factory Images (And Return To Stock)
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Yep, all good now. Followed all the steps, loaded stock images, flashed custom recovery, followed by the ROM, all good now. Thanks a bunch!
Was too quick to report success - now my SIM doesn't work. It populates the APNs, says LTE from the quick slide menu, but stays on no signal in the status bar, plus errors out when refreshing web pages, etc.
I've tried flashing different (including the latest) vendor images as well as different radios.
EDIT: never mind; the freaking Mobile Data was turned off (why the **** does it happen?). Turned it back on; all good now.