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.
Phone is unloacked and S-OFF
So my phone was ONLY able to boot into recovery/bootloader.
I tried wiping my phone, but TWRP gave "Failed" message
I decided to simply continue and try flashing the ROM anyways
Phone rebooted and was stuck on the HTC logo
After a LONG time of waiting I decided to pull the battery out
Phone will not turn on, but my computer can detect it.
Also, I was unable to turn on USB-Debugging because, well no OS, and TWRP did not give an option to do so.
Edit: Update
Phone is now turning on and I am able to boot into bootloader
I am able to boot into TWRP (v2.8) now. Image of error below:
http://i.imgur.com/EGBpufh.jpg (embedding image only shows the large full size)
Unable to mount "System" partition
What are my options? I am using WinToolKit and it's not working. When I boot into fastmode (manually) my computer gives a message saying it cannot be recognized and that there may be a problem with the device.
Edit: solved my problem, thank you all for your help
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
MotoJunkie01 said:
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
Click to expand...
Click to collapse
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
foxcell said:
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
Click to expand...
Click to collapse
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
MotoJunkie01 said:
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
Click to expand...
Click to collapse
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
foxcell said:
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
Click to expand...
Click to collapse
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Well I got some bad news... phone is stuck in a boot loop now, and no longer loads TWRP. I followed your directions and Oreo installed with no errors or warnings. Since going to Reboot -> System, it boots, says "N/A", then reboots.
I can get out of the boot loop by pressing volume down + power key, and from there I can access Android recovery (says 'bad key' when booting, instead of 'N/A') which gives me various options. It can still read SD cards and even says the proper OS.
I think it can still be saved since I can access Android recovery. I haven't tried the format system or cache options from Android recovery, because that might permanently screw it up.
Anyways... I'm here if you have any advice on what I can do. Maybe I should of bought an E4, lol.
Would you suggest I follow this?
https://forum.xda-developers.com/moto-e5/how-to/firmware-restoring-moto-e5-play-to-t3820053
I have no data on the phone so everything can be wiped no problem.
MotoJunkie01 said:
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Click to expand...
Click to collapse
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
foxcell said:
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
Click to expand...
Click to collapse
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
MotoJunkie01 said:
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
Click to expand...
Click to collapse
I did as followed, and phone is restored!!! Now when starting up it says "bad key" so I assume that means bootloader is still unlocked?
I still want to root and such, but I think I'll wait because rooting instructions I found were vague and trying to follow them got me into the situation I was in, lol.
Thanks for your help!!
foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77283595&postcount=196
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
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not