So, I wanted to install a custom ROM, but somewhere along the way something went wrong and I got stuck in a bootloop, I've been reading up on some threads and I followed some steps that were supposed to fix it, but I feel like I'm in even more trouble now (Well, my phone is still alive so I still have hope but yeah..)
Anyways, I'm using Philz custom recovery now, I tried to do a wipe to install a new or stock ROM, at first it said the wipe was succesful, so I tried installing the ROM, but during the install I kept getting:
E: Error mounting /data
It did say the installation was succesful, but after I rebooted it kept trying to wipe eventhough I did not ask for this.
Got another mount error and said Wipe Failed.
Now when I try to sideload stock ROM I get errors like:
Formatting Cache
Formatting /sd-exxt
E: Uknown volume for path /sd-ex
(I also don't know why it's doing that since this phone has no SD card) I got the Falcon edition with the internal storage. Also when my computer recognizes my phone and I want to open the phone folder, there is no longer an Internal Storage folder.
Anyways after those errors it says Data Wipe Complete, Wiping System, Now flash new ROM
But nothing flashes properly it seems due to the mounting error. I've looked for solution, but I can only seem to find threads that involve Samsung
and when I find a solution video it has something to do with either taking your battery out of your phone (which you can't do with this phone) or something
with your SD card (which this phone doesn't have).
So yeah, I'm running out of ideas here and any help would be greatly appreciated!
Cheers.
runittwiice said:
So, I wanted to install a custom ROM, but somewhere along the way something went wrong and I got stuck in a bootloop, I've been reading up on some threads and I followed some steps that were supposed to fix it, but I feel like I'm in even more trouble now (Well, my phone is still alive so I still have hope but yeah..)
Anyways, I'm using Philz custom recovery now, I tried to do a wipe to install a new or stock ROM, at first it said the wipe was succesful, so I tried installing the ROM, but during the install I kept getting:
E: Error mounting /data
It did say the installation was succesful, but after I rebooted it kept trying to wipe eventhough I did not ask for this.
Got another mount error and said Wipe Failed.
Now when I try to sideload stock ROM I get errors like:
Formatting Cache
Formatting /sd-exxt
E: Uknown volume for path /sd-ex
(I also don't know why it's doing that since this phone has no SD card) I got the Falcon edition with the internal storage. Also when my computer recognizes my phone and I want to open the phone folder, there is no longer an Internal Storage folder.
Anyways after those errors it says Data Wipe Complete, Wiping System, Now flash new ROM
But nothing flashes properly it seems due to the mounting error. I've looked for solution, but I can only seem to find threads that involve Samsung
and when I find a solution video it has something to do with either taking your battery out of your phone (which you can't do with this phone) or something
with your SD card (which this phone doesn't have).
So yeah, I'm running out of ideas here and any help would be greatly appreciated!
Cheers.
Click to expand...
Click to collapse
The phone has a virtual SD card.
I had a similar issue. Try flashing TWRP recovery and go to wipe > format data (THIS WILL DELETE ALL DATA) then reboot recovery. Worth a shot if you're not able to use your phone. You can copy over SD card contents to a computer first via TWRP by mounting MTP, or use USB OTG..
Hello
First of all, I'd like to excuse myself because of my lack of knowledge in all that android stuff and also in english. I got my phone rooted just by following tutorials on internet.
I have a Huawei Ascend Mate 7 MT7-L09. Probalby half a year ago, I have unlocked bootloader and installed CWM-based Recovery v6.0.5.1 and got it rooted.
Not long ago, Huawei released a new version of the EMUI, wich I guess is the Android 6.0 marshmallow thing (logically, I was using the previous version). After downloading, I tried to install it but it would reboot to the CWM everytime I was trying. And then, after booting, the phone would tell me the update failed. It's normal, I know. I needed to install it manualy and etc
BUT instead, by pure ''I don't give a crap what may happend'', I did some big crap.
First of all, in the phone's settings, I did a factory reset. I made a backup of all my files and data before (not in the CWM, but in the phone's tools). After the reset, the phone booted in an old-fashioned android version.There wasn't any keys to go home/back on the bottom of the screen. Because of this, the phone was almost unusable because I had to reboot the phone to leave an app and select another.
I raged and booted to the CWM by pressing the + button and the lock phone button.
I went to Mounts and Storage Menu and did all of this
format /boot
format /system
format /cache
format /data
format /storage/sdcard1
format /data and/data/media (/sdcard)
I did the wipe data/factory reset
I also went to Backup and Restore
I made the
delete from /sdcard
delete from /storage/sdcard1
free unused backup data
choose default backup format
I went in Advenced Menu aswell
I chose
wipe dalvik cache
I think that's it. No wonder why it doesn't work well now LOL...
Later on, I thought I may try to fix it. After reading some stuff, I downloaded a package from the official Huawei website, I think it was with the 5.5.3 EMUI or some sort of. After mounting USB storage to my pc, I put the zip file, wich was not really a zip file because it had a .tar format, it would show me by going to the install zip: Impossible to read format lol. Then I found a package of a rom wich was zip. After putting on the phones storage this zip it would start to install and show installing update and then show me: Installation aborted. Then i gave up and decided to ask some help from pros.
So..... What should I do?
I know my explications are weird, but this is the only way I can describe my problem.
Thank you for reading this long story, and even a bigger one if you help me.
hi,
i don't know cwm recovery.
I suggest you install TWRP recovery , then flash the rom image found here.
(i have installed B571 by this way)
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
regards
tar is another compression format like rar and zip.
If you have the software installed to use terminal commands (ADB) to connect to your phone when it is in so called 'recovery'or 'fastboot' mode you should flash the TWRP recovery image for Mate 7 posted somewhere on the forum for better compatibility. It is basically similar as CWM (clockworkmod) but newer.
In another post here there is a summary of firmwares and in that list is also the 'Twrp Backup' of a fresh installation. That should be downloaded, unpacked and placed in the folder where other/previous backups are stored. To find out where that it is you can create a backup yourself in recovery but only select the 'boot' so the backup is done immediately (and useless) and you can browse your phone to see where to put the downloaded recovery backup.
Next is restoring that backup within recovery.
Personally I would also do a factory reset after that but you should be ready to go after that.
I have a phone that was rooted with the original rom (CyanogenOS but not cyanogenmod I think?) and had TWRP 2.8.5.1 installed. I initiated the encryption process and let it run. I returned to it after a couple of hours and found it displaying the cyanogen logo. I waited another 30 minutes before deciding it was stuck. I tried restarting the phone but it would get stuck on the cyanogen logo.
I then booted to recovery and was prompted for the decryption code, but the correct code was rejected. After researching here I concluded that the TWRP version was part of the problem so I flashed version 3.2.1-0
I was then able to boot to TWRP and decrypt the data partition and browse files. Unfortunately it still gets stuck at the cyanogen logo.
I also tried wiping the cache, and wiping and replacing the persist.img.
I'm not very experienced or skilled with these issues. I'm looking for a way to restore the phone to how it was before my encryption attempt; for now I'm abandoning the idea of encrypting the phone.
If it isn't in bad taste or obnoxious to ask this here, I'm willing to pay for help.
edit-0:
I was thinking of using TWRP to backup the decrypted data partition, wiping the encrypted version, then restoring the decrypted version.
It seems like this should restore the pre-encryption state, but am I missing something? Any downside to trying this?
edit-1: a follow-up
I was able to restore the phone by the method proposed above in edit-0
I made a backup with TWRP using a method similar to what's discussed in these threads:
https://forum.xda-developers.com/general/general/twrp-backup-including-internal-storage-t3660479
https://forum.xda-developers.com/android/general/tutorial-create-internal-storage-backup-t3389172
I followed roughly these steps:
1) temporarily rename the "media" folder to "mediabak" from the TWRP file manager
2) confirm size of the "data" partition has increased to expected value after renaming
3) plug in USB drive and mount
4) backup data partition to USB drive
5) make a backup copy of the USB drive to PC
5) wipe the data partition
6) restore the data partition using the backup on the usb drive
7) reboot to TWRP recovery (not a necessary step as far as I can tell)
8) note that at this point apparently TWRP automatically re-creates the "media" directory
9) delete the TWRP-generated "media" directory and rename the "mediabak" to "media"
10) reboot to TWRP recovery and browse restored files to see if things look right
11) reboot phone
Rebooting phone took longer than normal, as I think one would expect.
After lingering for a while the "cyanogen" logo animation disappeared and the message about android updating apps appeared
Phone seems to be working normally.
In retrospect my only exposure to actual data loss the database of Signal app messages. It seems like everything else I could have extracted from file based backups and also directly from the phone after I upgraded to TWRP 3.2.1-0
"Cannot restore System -- mounted read only." even if my storage is read-write
I am trying to restore from a previous backup that I made with TWRP recovery, but every time i do it, it fails saying:
"Cannot restore System -- mounted read only"
I have tried multiple storage devices, and even tried internal storage for a while until eventually that started to yield the same error. I decided to use a pendrive connected to an OTG cable, which I verified was not read only through Command Prompt, and my phone would still refuse to restore from backup, reporting the same problem as previously mentioned.
As to why I had to restore from a previous backup in the first place, I was trying to install ResurrectionRemix for my phone and one of the instructions mentioned to perform a full wipe. I took this the wrong way and wiped EVERYTHING in my phone, which includes data, internal storage, and system (although the next step is to wipe system so that doesn't really matter.) I proceeded with the other instructions and I realized shortly that something didn't really work out, so I decided to restore from a backup I made previously, which brings us to this point in time.
I should add that I was able to flash the custom ROM through the very same SD that I tried to use for recovering from the backup that I created.
My phone is a Samsung J5(SM-J500F) which had the latest Android Marshmallow 6.0.1 prior to wiping everything in my phone.
Thank you for taking the time to help me with my problem!
PS: I am using TWRP 3.0.2-0 recovery, which is not the latest build.
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying