Hello
Really bad morning.
Woke up to find my OPO (was running COS 12.1 with TWRP), which I had plugged in to charge overnight, stuck on an android screen which said please enter your password. I entered my Google account password and then the next screen says, decryption unsuccessful. "Your password is correct but your data is corrupted. You need to factory reset your device and once you reboot you will have an opportunity to retrieve data backed up with your Google account".
I tried to reboot, just to make sure, and the same set of screens reappeared.
I tried to boot into recovery. The 'teamwin' screen kept flashing to no avail.
Entered fastboot. Flashed recovery, TWRP-2.8.7.0-bacon.
Tried to factory reset but the prompt flashed an error as follows:
'E: Could not mount /data and unable to find crypto footer' and then a series of others, but " could not mount '/data' " was repeated over and over
I'm still stuck here. How to get out of this situation?
PS: When I try to look at the mount options in recovery, the internal storage is labelled as 0 MB. This is scary.
I'm more screwed than you are. Twrp 2870 does not properly support encryption. Great to know an official release is that broken, right? Flash an older twrp, I believe 2860 or 61 are what you want. Try to reflash your cm zip. You're going to have to resetup your device but your internal sd should be fine, it says 0 mb because it's not decrypted so it can't read it. Then you should be okay... Well, except I've never seen that screen you described in the first paragraph. But that usually related to apps, not your internal sd. Good luck. I've accidentally erased all my system and data so I can't adb flash and can't flash from internal sd. My last hope before reformating everything and losing my pictures is to install via USB OTG. Which you could also do.
Good luck
Sent from my Nexus 5 using Tapatalk
Hey, I just found out that there is a way to flash a system image via fastboot! This is why I buy unlocked developer minded phones! If only OP hadn't dropped the ball on the OP2 (I actually got an invite which I didn't even use).
Anyway, go here: https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/
and scroll down to "The Bad" In ORANGE text: 2. Recovering from no OS installed and no access to TWRP, fastboot does work.
Since TWRP is basically useless for us, I followed the instructions. I flashed everything EXCEPT the userdata img. AND, instead of flashing the extracted recovery, I just reflashed TWRP 2861 which I have on the PC.
Unfortunately! All my pics are gone. Pretty sure removing encryption with TWRP (before reading it was broken) did it. Try installing a good ROM via USB OTG and let me know if that saves your internal sd. I'd love to know for the future.
Related
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
deralaand said:
Here is the history
NS4G
Rooted in early January and flashed an ICS rom (Vgomez)
Then flashed CM9 alpha 20 and made a couple of Nandroid backups over the course of the month.
Briefly flashed the Stock 4.0.4 rom. Didn't like it.
Restored via Nandroid to the CM9 alpha 20
everything was great.
Yesterday I went to make a call and the phone locked. I tried to power down...no luck. So I pulled the battery.
It never came back. (got some type of 'android lost encryption' error)
I power up the phone and it brings me to a brand new user page where I would have to login with my gmail creds.
Then it starts throwing errors like calander stopped working, google settings app stopped working, android.process.acore stopped working. etc...
I can boot to CWM and but it will not allow me to recover to anything other than what I described above.
I can mount the USB partition and it appears to allow me to copy files into that partition. However, if I try to flash a ROM, Kernel, etc. It terminates the operation and says the file is bad.
When I reboot CWM and go to view the USB partition again, those files that I had just moved into the partition are now missing.
It is as though I have not copied the file at all.
Without access to the allow USB debug setting, I cannot adb anything.
I have tried the Samsung yellow boot/restore (odin?) when I click the 'Download files' button it throws a generic error and halts the process.
At this point, I don't care if the phone is put back to stock because I won't lose anything important. I just want to get my phone working again.
edit: I do have access to fastboot. I have wiped everything and tried to boot and it sticks in the bootloader (good?) I assume that when I try to flash one of the ROMs that I do have in the USB partition...it will go back to the way it was. (errors and all)
I suspect that the Kernel is corrupt. How would I fix this without being able to write to the USB partition?
Click to expand...
Click to collapse
If you have access to fastboot and assuming your flash storage isn't damaged, you should be able to flash over /boot with a boot.img and over /system with a system.img... But you might have to search around for them. Sorry i can't be more help.
kernels ; battery ; ROM ; gov/sched
http://www.mediafire.com/?wg9krukqp43nq1i theres a link to the boot.img for the apex bigxie rom (ics 4.0.3), try flashing that through fastboot i think the command is "fastboot flash boot %imglocation%.img" so just put the img in the folder you usually flash stuff with the fastboot bat in it, then try and flash this boot and tell me what happens.
ps, the %imglocation% should be the name of the img wherever you put it, so it will probably be boot.img.
So I had been attempting to encrypt my phone for 2 days and finally today I did something and it started encryption. I had rooted the phone and had TWRP on it.
The encryption finished and it rebooted and now its stuck with the screen on the 1 logo. i can turn it off and go to the bootloader and TWRP but no matter what i do it won't let me flash anything. in TWRP I tried formatting the drive but that didn't do anything either, it keeps giving the error "Unable to mount drive"
I was trying to find an Odin type package for it but no go yet. Even LG had a flashing tool. Any ideas?
You can download the fastboot images from the official cyanogen site:
https://cyngn.com/products/oneplusone/
Transmitted via Bacon
Yes, i did have the fastboot images but it wasn't letting me flash them.
Ok, so I think I wiped out the OS while wiping the phone earlier and that's why it wasn't going anywhere after the 1 logo.
What I now did was pushed down the Pacman ROM zip via TWRP to the local drive and flashed it and its booting now. I should be able to get the rest going.
heres how i handled that exact situation and got encryption working correctly on 11S
https://forums.oneplus.net/threads/fix-fixing-encryption-and-keeping-wireless.133304/
WIFI issue after encrption
Im having issues after encrypting.
I have twrp and rooted my phone. today i encrypted my device. No issues. After password first time device dint do anything i thought its hanged or something.
powered off and started again . second time phone started without issues after decryption password. But to my surprise phone for factory reset.
But my major issue now is. Im not able to turn on wifi. Its is disabled. Can tell me what to do.
Shall i reset in TWRP ?
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
update: it's all gucci, i've managed to figure it out.
Have you tried the patched twrp version? There is a link in google camera port thread. I havent tried but that could work.
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
not a professional but coincidentally this happened to me today while rooting and installing twrp on my s7 sm-g930L 8.0, i installed twrp 1st and was just using a supersu.zip to root it, booted straight into twrp after flashing and had the same problem you have and couldnt install the zip as it wasnt showing up and also saying 0mb, i couldnt even send the zip to it from my computer either until i pressed format in the wipe menu next to advanced wipe button , it was in a bootloop so i hit format cause i was just gonna reinstall stock firmware but i noticed all the correct mb's appeared in system data etc and i could copy/paste n install the zip, flashed it rebooted and it all works, rooted and twrp on official fw 8.0, you might have to reinstall apps and stuff after but hopefully this helps, goodluck
hype. said:
soo... i have a fully functional working samsung s7 rooted with the latest magisk and twrp recovery. after all the installation of apps and the root itself, i hopped into twrp recovery just to see if it was also working - turns out it's not reading any partition; leaving me with 0mb internal storage or unable to mount. i would also try rebooting but as soon as i enter "recovery" on twrp, it would automatically boot itself. i've tried researching for the problem but i don't think my research is good enough. i've looked out for multiple solutions, but i couldn't trust any. just wondering if any professionals on xda are able to fix this flaw. thanks!
tldr? working rooted s7, twrp recovery 0mb, automatically rebooting itself, couldn't find solution.
Click to expand...
Click to collapse
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
ttuleyb said:
INSTRUCTIONS BELOW WILL DESTROY ALL DATA ON PHONE GET BACKUPS IF YOU CAN'T IM NOT RESPONSIBLE
Get rid of encryption if you can then try
If you can't get rid of encryption or it didn't work then
Goto wipe and press format data
Type yes and press the tick at bottom left
Then once you see success or error messages go back to wipe
Swipe it to wipe internal memory
After success or error message shows you are most likely to be able to see and mount to internal storage.
Click to expand...
Click to collapse
This is just temporary the next time you flash you will see 0mb again you will need to format again.
mkl.xda said:
This is just temporary the next time you flash you will see 0mb again you will need to format again.
Click to expand...
Click to collapse
Unless you flash decrypt zip before booting after flashing
ttuleyb said:
Unless you flash decrypt zip before booting after flashing
Click to expand...
Click to collapse
Still the same. Tried it many times.
mkl.xda said:
Still the same. Tried it many times.
Click to expand...
Click to collapse
Try using superman rom and use option called disable encryption that might work,
If you just wanna root then install magisk because it works with encryption
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.
niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk
I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.
I've done a bit of digging but I'm on a time crunch, and frankly I don't want to dig myself in a deeper hole.
I was attempting to make a backup of my OnePlus 7 Pro prior to doing an OTA update while preserving root.
I was getting a "failed to mount" and "0mb storage" so I looked into fixes and found this:
How to Fix TWRP Unable to Mount Storage, Internal Storage 0MB - Appuals.com
Some TWRP users, especially those who install custom ROMs, sometimes run into an issue where TWRP will an error that reads “Unable to mount storage”. The
appuals.com
.
I followed this and got to the point where I attempted to change file system from ext4 to ext2 and back again.
After doing this however I got stuck in a bootloop.
I entered TWRP recovery and tried to mount and boot? to system, and now I'm totally stuck on a fastboot loop -- unable to access TWRP.
I have several tools on my laptop saved from the initial root process such as the Tool All In One and the MSM download tool.
I would just like some clear direction to proceed. I'd rather not have to essentially reset my device, as I'm pretty sure all my data is in the device but I think I'm in the wrong partition. I'm just not savvy enough to know how to get it without causing further issues.
Any help would be great. I'm leaving for a 12 hour shift now, so I can't do any more digging on my own.
Thanks in advance.
Lower TWRP version.. is the fix, but.. i dont known anything about the OnePlus serie