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
Related
Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!
Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.
Cmon guys! I don't want to JTAG it yet.
HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.
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.
Hey all,
I'm not a total noob, but I do this so infrequently that I can't commit it to memory. Would really appreciate some help here.
I followed the official LineageOS Guide for Herolte, over here.
I had done this previously on my Nexus 7 so I was fairly confident.
Everything worked well, I got TWRP installed using Heimdall from Linux, and successfully pushed the latest LineageOS and open_Gapps images to the phone.
Rebooted into TWRP, and followed the recommendation to wipe System, Cache and data partitions. This failed with red text stating that ti was unable to mount data.
I googled some, and found a suggestion to reformat the partitions, first to a different file system and then back to their original file systems again. I tried formatting /data to exFat, and it took forever, eventually erroring out with an error message. After this I can't get into TWRP anymore. When I try the phone boots to the TWRP startup screen, and just freezes there.
I have tried reflashing TWRP using Heimdall and this does nothing. Flash succeeds, nut still freezes at TWRP splash screen.
I googled some more and found a suggestion to flash stock Samsung firmware, and then try again, this time formatting data system and cache without trying to first wipe them. Problem is I can't successfully flash stock firmware.
I tried using this method in Heimdall, but it complains "Local and device PIT files don't match and repartition wasn't specified!" and fails.
I've also tried booting into Windows and using Odin, but it never works. The screen turns grey, and no progress indicators ever start. I assumed this was because I had the incorrect drivers for the phone, and tried using zadiag.exe to replace them, but the driver install fails.
I'd greatly appreciate any help. I can't seem to force the phone to shut off, it just keeps rebooting and getting stuck on either the TWRP spash screen or on the download mode screen. I know this is solveable, but unless I figure it out fast, I'm worried I am going to burn in the screen.
Any suggestions appreciated!
Never mind. I must just have had a bad stock image.
I downloaded a different one, and retried heimdall and it flashed properly.
I am now able to re-flash and boot into TWRP again.
Hopefully I won't have the same problem again when I try to wipe the partitions...
Alright,
So I solved this issue by (once I reflashed stock, and then reflashed TWRP again) formatting the data partition twice, first to ext3, and then back to ext4. This looks to have cleared the encryption issues that were causing thsi problem ,and allowed everything to continue working as expected.
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
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.