So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Same issue
---------- Post added at 10:08 AM ---------- Previous post was at 09:58 AM ----------
try this
n your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
This is the TWRP thread... How can it help in my situation?
I flashed the dm-verity and forced encryption disabler zip, wiped all data and a custom rom. It doesn't help.
Primokorn said:
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Click to expand...
Click to collapse
In twrp: Advanced->Terminal
In Terminal type wipe_misc and press enter. Reboot to system.
EDIT: this erases misc partition by dding /dev/zero to misc partition. (I've tested both, wipe_misc sceipt as well as dd by hand - it's safe; you will not loose anything [if there would be something on data... SCNR ])
---------- Post added at 19:18 ---------- Previous post was at 19:14 ----------
networx2002 said:
Same issue
[...]
Go to [Reboot] -> [System].
Click to expand...
Click to collapse
Very true, but that answers not his question...
nvertigo67 said:
In twrp: Advanced->Terminal
In Terminal type wipe_misc and press enter. Reboot to system.
Click to expand...
Click to collapse
Already tried. Is there something else to do after entering this command? (wipe data, flash rom again..)
EDIT: flashing the stock recovery and full 4.0.2 OTA might help?
Primokorn said:
Already tried. Is there something else to do after entering this command? (wipe data, flash rom again..)
EDIT: flashing the stock recovery and full 4.0.2 OTA might help?
Click to expand...
Click to collapse
Stay on twrp (3.0.3-1). Wipe art, system, data and cache. Flash full 4.0.2. Go to twrphome->mount and check if system is unmounted (*)- if so: boot to system; if system is mounted reboot to recovery and dirty flash (without any wipe) full 4.0.2 again; boot to system.
Whenever I had this boot to recovery but not to system, wipe_misc was allways sufficient.
BTW: disconnect usb before rebooting. otg-sticks as well charger result sometimes in unpredictable reboot behavior.
(*) I've still not found what's triggering this, but if after flashing system is mounted, you can't boot directly into system, and twrp tells you on reboot, that no system is installed, even if you just flashed a rom...
Primokorn said:
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Click to expand...
Click to collapse
I ran into a similar problem with mine yesterday / today with 3.0.4-0....after countless tests, it came down to holding down the power button for 20s and releasing (hard shut down)...wait 20s, hold power for it to come back on, ROM loaded up.
I tried every boot option from TWRP, and just kept looping.
Give this a try, as trivial as it seems, fixed it for me.
stephlal said:
I ran into a similar problem with mine yesterday / today with 3.0.4-0....after countless tests, it came down to holding down the power button for 20s and releasing (hard shut down)...wait 20s, hold power for it to come back on, ROM loaded up.
I tried every boot option from TWRP, and just kept looping.
Give this a try, as trivial as it seems, fixed it for me.
Click to expand...
Click to collapse
How could it be possible?
It works! Thanks for your help.
I've flashed Tesla ROM and the phone boots. I'm charging my phone to enable encryption then I'll see how to set a boot password (without any issues this time lol).
I set a password to encrypt my data and flashed TWRP 3.0.1-0 again.
I'm not able to decrypt my data in TWRP...
After a reboot, the ROM doesn't recognize my password anymore. I'm fed up with encryption!
Primokorn said:
I set a password to encrypt my data and flashed TWRP 3.0.1-0 again.
I'm not able to decrypt my data in TWRP...
After a reboot, the ROM doesn't recognize my password anymore. I'm fed up with encryption!
Click to expand...
Click to collapse
imo just the unbrick tool to go back to fully stock and start the whole process again
I had this issue with the password.
I had to flash the stock recovery, go into stock recovery, it will ask you for the password, just choose forgot password and it will prompt to format everything. Click yes to accept. After it formats, flash the custom twrp recovery. Once it flashes, load recovery and flash the 3.5.4 bootloader here:
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
OR you can boot into bootloader/fastboot and type in these commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
m0d hipp¥ said:
I had this issue with the password.
I had to flash the stock recovery, go into stock recovery, it will ask you for the password, just choose forgot password and it will prompt to format everything. Click yes to accept. After it formats, flash the custom twrp recovery. Once it flashes, load recovery and flash the 3.5.4 bootloader here:
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
OR you can boot into bootloader/fastboot and type in these commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Thanks but I'll just enjoy my phone for now. Encryption can wait.
Only these two fastboot commands will avoid the wrong password issue? It seems to be helpful to remove the dm-verity error and I don't have it.
Sorry I guess I misinterpreted the issue. I thought that the dm-verity and the encryption issue were somehow linked. Anyway, the first few steps I took with flashing the stock recovery and wiping everything from stock recovery is what fixed the immediate encryption issue for me.
this is what i've done.
lenovo k3 note with twrp 2.8.7.2_K3_CUOCO92 and rom K3_LOLLIPOP_5.0_ROW_v1.12
i wanted to install one of the latest nougat rom. so i downloaded a twrp 3.1.1.1 made for the k3 note. i flashed the image from my old twrp and replaced choosing the RECOVERY partition.
Flashed ok, i tested a rom, AospExtended-v4.4-aio_otfp-20170708-1051- i flashed it and it worked.
OK BUT.............. i did not wipe the data partition because i received AN ERROR. the new nougat rom was ok but it was a superdirty flash with all the old apps that were crashing. what to do?
i enter into twrp, i REMEMBER that i had the data partition ENCRYPTED so i format it and after doing this i was able to do every wipe i want, included data.
OH PERFECT...... THIS IS WHAT I THOUGHT. i made a full wipe of the rom wiping 4 thinkg : data , internal storage, cache and dalvik cache.
reboot and BOOM. black screen. i press 3 or times the power button and the creen goes on... i am into twrp. from this moment i never returned to see my SYSTEM!
i tested other roms, same problem. i thought it was a twrp problem.... so i installed from the twrp an IMAGE of other twrp... i tested 2 or 3 other twrps specific for my phone k3 note.
I HAD LITTLE BENEFITS with another one.... just because when i press to reboot into system... the phone reboots into twrp AND I CAN SEE IT because the screen is ON, whilst with the "latest" twrp i found...... despites the flashing procedure was ALL CORRECT without errors, at the reboot i always entered into twrp...... BUT INTO A BLACK SCREEN MODE, like if the screen was on...touch enabled, but OFF backligt, and the only way to revive it it is to press power 2 or 3 times, to see the home of the twrp.
i've also found that on MOUNT.......... i always see SYSTEM unflagged, ok i flag it, reboot into system, actually reboot into twrp and system is UNflagged, i try the same thing ALSO flagging READ ONLY...... , idem reboot, twrp.
SEEMS THAT i cannot boot to system anymore. but..... if the twrp was fault, why for the first time let me flash the phone? i really entered into the nougat rom! i found all my old apps and files, but of course it was a DIRTY FLASH, i just wanted to make some wipes.....re flashi the rom.... but oddly i missed the possibility to return anymore to the system.
what could i do at the moment?
how to flash a original image? how to see if this recovery is ok? i donkt 'know where to find my answers......
ah last thing, while into the recovery i was always able to transfer files from pc to phone, but from minutes i am NO MORE ABLE to see the internal memory of the phone.
my computer does not see anything!!! so i am fukked i think....... i did not make anything different.
i only made a lot of wipes... a lot of flashing a lot of testin into recovery. i was able to see it from my pc and put new files through pc. now NO.
solved. i flashed with flash tools an old original firmware android 5.0, then i flased latest twrp with flashtool.... and then flashed the zip of a custom rom.
BL
if u have backup then restore ur stock version or reeboot??
I had an issue where my tablet would just reboot over and over. So I tried to reset it using factory reset. This has me now in a recovery reboot loop.
Hardware:
Galaxy Tab S2 (SM-T713) - wifi only
Software:
TWRP 3.1.0.1
Lineage OS 16
What I've tried:
Wiping cache and davalik cache several times
Formatting data
adb reboot fastboot
Wiping cache, davalik cache, and system (which made TWRP report no system of course)
adb sideload of lineage OS 16 - reported success but TWRP still said no system
re-flashing the lineage OS 16 ROM from SD card (this resolved the no system issue)
Reboot to system from TWRP and adb fastboot after the system re-flash
Odin won't respond and says it can't contact the tablet (multiple usb cords tried , etc) so no luck re-flashing OEM ROM
No matter what, it goes into recovery reboot and won't try to start the system. I can't find anything else to try through searches on XDA, google, etc. Any suggestions?
Not exactly the same, but I thought I had hard bricked my T713 about 9 months ago. I was on stock at the time (not even sure what build), and a bunch of wipes and formats later I was in a TWRP loop. I couldn't even power the machine down. Even that would loop me back to TWRP. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power and volume down and spam the home button until I got to the download screen. After that I was able to get back into odin3_v3.12.5 and load the factory image. I am on LineageOS 16 official now, so I have no idea if this is of any help. I'm pretty sure the boot img came after drilling all the way into the XAR-T713XXU2BRB2_T713XAR2BRB2-20180206 file, since that is the one I eventually got to load.
Yes, I forgot to mention that symptom - it won't power down at all. Just goes back to TWRP.
I'll give that a try, thanks.
apollard said:
Yes, I forgot to mention that symptom - it won't power down at all. Just goes back to TWRP.
I'll give that a try, thanks.
Click to expand...
Click to collapse
Flashing the boot.img file did it! I was able to get in to download and use Odin to reflaah the stock ROM. Now to switch to LOS.
apollard said:
Flashing the boot.img file did it! I was able to get in to download and use Odin to reflaah the stock ROM. Now to switch to LOS.
Click to expand...
Click to collapse
I am so glad that worked for you.
As the title suggest, I fail to boot into TWRP.
I have unlocked the phone and flashed TWRP (https://dl.twrp.me/raphael/twrp-3.3.1-0-raphael.img).
I could boot into TWRP using Power + Volume Up , wiped everything (except vendor) and pushed a custom rom to the internal storage.
I restarted the phone for some reason and cannot boot into TWRP anymore. Whatever I do, I end up in fastboot. Tried to flash various versions of TWRP with the same result.
Can you guys help me out?
Edit: I flashed the corresponding Xiaomi fastboot image and repeated the process, same problem.
Edit: Solved by repeating again.
flel said:
As the title suggest, I fail to boot into TWRP.
I have unlocked the phone and flashed TWRP (https://dl.twrp.me/raphael/twrp-3.3.1-0-raphael.img).
I could boot into TWRP using Power + Volume Up , wiped everything (except vendor) and pushed a custom rom to the internal storage.
I restarted the phone for some reason and cannot boot into TWRP anymore. Whatever I do, I end up in fastboot. Tried to flash various versions of TWRP with the same result.
Can you guys help me out?
Edit: I flashed the corresponding Xiaomi fastboot image and repeated the process, same problem.
Edit: Solved by repeating again.
Click to expand...
Click to collapse
In future, don't wipe everything. You should only need to do the factory reset in TWRP, which will automatically wipe data, cache and dakvik. If you are flashing over MIUI then you will also need to format data.
There is almost never any need to wipe anything else in TWRP when doing normal custom ROM flashing.