I was backing up files when switching to a new N6. A temporary boot.img triggered the encryption process. Not thinking it through, I rebooted at about 4% complete. I now only get the "encryption unsuccessful" message advising me to wipe it and start over. I hadn't backed up since Nov and will lose a lot of important files if I can't recover at least something. I made TWRP and TiBu backups but didn't pull them before this happened. I understand the data is likely corrupted, but is there ANY chance a method might allow me to recover anything?
I found this. http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Couldn't get Philz recovery to flash but TWRP has ADB sideload as well. I can get it to recognize the device as adb devices but the adb shell command just says error: closed. Am I wasting my time or might this be possible? Not sure if I could wipe everything but internal storage and flash something that might help. Please help!
For anyone reading, the OP's question is a follow-up to this thread.
OP, You're wasting your time. The guide you linked to covers a situation where the device owner doesn't let a ROM upgrade or install optimize the apps at start due to being impatient. The guide author was able to resolve his problem because when he wrote it, he was on Android 5.0, which doesn't have device encryption.
The only way to resolve this is to do as the "encryption unsuccessful" message advises.
yup. botched encryption = lost data, no way around it.
Related
Yep, probably again a noob that bricked his phone.
As there was no info on my phone that wasn't on google servers or something I was so stupid to start installing the latest official CM12 built on my XT1068 without any decent backups.
- I think the moto/google service for lost devices encrypted my phone without me really noticing it. :crying:
- I was on Lollipop, the latest update I got here from in Benelux/Europe.
- I unlocked my device, worked fine. device also tells in bootloader
"Device is UNLOCKED. Status Code: 3"
- when than having installed TWRP 2.8.0.1, os started but gave problems installing superSU.
(no prob I thought, I go immediately forward with CM12 installation, so don't have to bother with the old ROM) :silly:
- wiping everything for clean install I already saw some messages coming up. on hindsight; Difficulties with opening /data folder etc...
- tried to install CM, and several other more stock roms, but never get through the message. All bad installs.
- maximum I got is CM12 booting up, preparing some apps and than a message describing the encryption problem, asking to reboot.
TRIED:
- install from usb drive (with OTG cable)
- erase and reinstall from TWRP 2.8.0.1 and other recoveries.
- fastboot flash a standard recovery again, to wipe data from there,
(from this standard recovery installers never got through even the verification to install, so tried than installing from other recoveries, same problem.)
Can still try but hesistant:
Unlock my mothers phone (same month, same model, same place, probably same encrypted) to try backup there in TWRP, recover this on my phone, and this way flash standard rom again. From there I could probably get rid of encryption. (as found already in several places)
I would afterward immediately try to lock my mothers phone again, don't know so much of how to get recovery to standard one again though. Can I backup this before. When I try now "adb backup - all" on my phone from my mac, I get "unable to connect for backup" message though. Even when phone is saying "phone connected".
Anyone an idea of how to get out this trouble?
Greetings
Otto
[email protected]: try "fastboot erase userdata"
have the feeling I'm getting there. Gapps still don't work but rom boots. Recovery has to be standard one to make encryption to work. Thats the key.
Hello there, this is my first post here so go easy on me
So I got a new P9 yesterday and I immediately set to work trying to put Lineage OS on it. It took me ages to get a bootloader unlock password but I managed to unlock it in the end. Then I went ahead and installed TWRP. TWRP launched fine, and I proceeded to wipe and attempt to install the Lineage zip from the external SD.
That's when things started to go wrong. At first, during install, it threw an error about not being able to mount the system partition. I've seen this before on my Galaxy S4 and solved it easily by reformatting the partition. So I tried that. It still didn't work, and over the next 4 or 5 hours I tried everything Google and I could think of, and now the phone is completely gone.
I can't factory reset (a bunch of cannot mount errors), format data (same), advanced wipe (same) or change file system (same). The system partition can be formatted but it still says it cannot be mounted. The data partition looks like it's totally gone. In fastboot, when I try things like 'fastboot erase system' or 'fastboot erase data', I get 'FAILED (remote: Command not allowed)'. I can, however, still do 'fastboot flash recovery [twrp.img], and it'll flash the recovery. I used to be able to do that to data and system too but now I can't anymore.
Something I want to try is to flash it manually with fastboot back to the manufacturer recovery and rom, but my Google-fu apparently isn't good enough to find one. A big problem I'm having with this is the fact that this phone came all the way from China and therefore is a Chinese model (EVA-DL00) and I'm searching in English. When I search in Chinese I can see the words EVA-DL00 everywhere but my Chinese is nowhere near good enough to navigate all that.
So I guess what I'm asking is:
1. Does anyone know why I can't mount the data partition? I've considered maybe its encryption or something but I really have no idea.
2. Does anyone know how I can completely return my phone to stock? Where can I find images for EVA-DL00?
3. If I take this in for repairs, is it possible that it's bricked so badly that they won't be able to repair it?
I'd greatly appreciate any help I can get
Thanks!
Infraxion said:
Hello there, this is my first post here so go easy on me
So I got a new P9 yesterday and I immediately set to work trying to put Lineage OS on it. It took me ages to get a bootloader unlock password but I managed to unlock it in the end. Then I went ahead and installed TWRP. TWRP launched fine, and I proceeded to wipe and attempt to install the Lineage zip from the external SD.
That's when things started to go wrong. At first, during install, it threw an error about not being able to mount the system partition. I've seen this before on my Galaxy S4 and solved it easily by reformatting the partition. So I tried that. It still didn't work, and over the next 4 or 5 hours I tried everything Google and I could think of, and now the phone is completely gone.
I can't factory reset (a bunch of cannot mount errors), format data (same), advanced wipe (same) or change file system (same). The system partition can be formatted but it still says it cannot be mounted. The data partition looks like it's totally gone. In fastboot, when I try things like 'fastboot erase system' or 'fastboot erase data', I get 'FAILED (remote: Command not allowed)'. I can, however, still do 'fastboot flash recovery [twrp.img], and it'll flash the recovery. I used to be able to do that to data and system too but now I can't anymore.
Something I want to try is to flash it manually with fastboot back to the manufacturer recovery and rom, but my Google-fu apparently isn't good enough to find one. A big problem I'm having with this is the fact that this phone came all the way from China and therefore is a Chinese model (EVA-DL00) and I'm searching in English. When I search in Chinese I can see the words EVA-DL00 everywhere but my Chinese is nowhere near good enough to navigate all that.
So I guess what I'm asking is:
1. Does anyone know why I can't mount the data partition? I've considered maybe its encryption or something but I really have no idea.
2. Does anyone know how I can completely return my phone to stock? Where can I find images for EVA-DL00?
3. If I take this in for repairs, is it possible that it's bricked so badly that they won't be able to repair it?
I'd greatly appreciate any help I can get
Thanks!
Click to expand...
Click to collapse
are you on nougat already?
Regards
OldDroid said:
are you on nougat already?
Regards
Click to expand...
Click to collapse
Not quite sure what you mean :/
The stock OS was nougat before I decimated it, and I was planning on installing the latest Lineage OS build which is based on nougat.
It doesn't have any OS on it right now though.
I have had issues with my zenwatch 3 being crazy slow on android wear 2.0, and i read some possible solutions..
I also have an issue where whenever i turn my watch on it says "device software cannot be checked for corruption" and it makes it take an additional 10-15 seconds to boot up. This has been on the watch since i got it (i bought used and the bootloader was already unlocked, if thats why its doing that. When going through forums I also saw mention for disabling dm verity and wondered if that would get rid of that annoying screen.
I wanted to see if i could remove the zenfit stuff, cause i saw that some users claimed speed improvements, so i flashed twrp, and when i booted in i accidentally said to allow modifications (even though now i see that people say not too). I didnt make any changes while in here, but thought that might be important to state. In the instructions to remove zenfit i again saw to disable dm verity, so i moved onto that.
I then connected through adb and ran the command fastboot oem disable_dm_verity, but that didnt seem to do anything. I then ran the command "adb reboot "dm-verity enforcing" which i dont think was a good one to run, and i wonder if caused my issue. When i tried to boot back into twrp it would boot to a dead android.
I decided at this point that instead of screwing things up further, i would just flash to AW 1.5 and hope for speed improvement there. I downloaded the files, and through fastboot flashed the stock 1.5 boot, system, and recovery. using this thread https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
i rebooted the device and it went to the android wear screen and loaded for a while, and then to the upgrading android screen. when it got to step 7 it went back to the aw loading animation and then attempted to boot up and gave an error "unfortunately process android.process.acore has stopped" and started all over again trying to upgrade android and then getting to this point and failing. I then downloaded the images for stock 2.0 and flashed and got the same exact error.
I then tried to flash twrp again, and now if i try to flash 1.5 or 2.0 it just goes to a dead android screen. I can boot into twrp still with the boot adb command
I want to try flashing 1.5 or 2.0 through trwp, but my watch will not mount/connect at mtp to my PC while at twrp for some reason...
Any ideas or solutions? how can i flash everything straight back to default. Including whatever i may have done to the dm verity?
Please help
If ADB and Fastboot is working on your watch, try this
csrow said:
If ADB and Fastboot is working on your watch, try this
Click to expand...
Click to collapse
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Coltonbyu said:
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Click to expand...
Click to collapse
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
csrow said:
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
Click to expand...
Click to collapse
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Coltonbyu said:
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Click to expand...
Click to collapse
Glad it worked out.
If you want to stay at 1.5, you know what to do.
Sorry. I wouldn't post here unless I was absolutely desperate.
This started when I was getting an error message when trying to make a data backup with TWRP. So I tried to follow a suggestion online to repair my data partition with the TWRP format tool. However, it stalled so I forcibly rebooted my phone.
Now my phone can't boot into the OS and only gets stuck on the TWRP splash screen. I can use 'adb shell' from my PC when I'm on TWRP but I'm not able to see my data files with the 'ls' command.
I can boot into the fastboot screen on my phone, but I'm not able to connect from my PC. So I'm not sure how I can flash TWRP.
I've tried to use the following guide with no success. I keep getting an error message about "Sahara Communication Failed."
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Thanks for reading.
The guide I linked miraculously worked after I tried again. I just had to delete all traces of the old 3T drivers from my PC and reboot. Sorry for making a thread.
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll