Hello, i am quite panicked about this problem so i will cut to the chase.:crying: I will write down stuff i did in numerical orders.
1. Using TWRP 2.8.6.1, I was curious to try to go to Wipe>Advanced>full wipe (wiping everything). After i did and tried to reboot, it said there is no OS. So i tried flashing my flashable stock rom 4.4.4 in zip form but it didn't boot.
2. So i flashed to stock in fastboot. (For flashing to stock, i used this instructions http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/). After finish flashing, i went to stock recovery and wiped dalvik cache and data.
3. After that, i rebooted and... that when it didn't seem right. Nexus 5 COULD connect to my PC but it only showed "Internal Storage" and nothing else. If i tried to move something to the storage, it would immediately say i can't move it there.
4. So i thought this was because the full wipe i did before and that the system partition got totally wiped. So i used TWRP again but to restore my old nandroid backup.
5. After i flashed my nandroid backup, twrp said this one line that goes in red "unable to mount /firmware. I ignored and rebooted. It still had the problem where i couldn't move anything to my storage by MTP but also adb push. It even couldn't save screenshots and download anything from internet like apk or some sort. When i went into the app called "Zipper", it said 'no sdcard'.
6. I searched through the internet to fix this but i kept failing to solve it. I tried going to TWRP and doing chmod, chmod 755, using these instructions (http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
TL;DR : I did a full wipe in TWRP and lost all permissions to read or write. Nandroid backup didn't help. Whatever i flash in twrp, it says "unable to mount /firmware" at the end.
metallikoh said:
Hello, i am quite panicked about this problem so i will cut to the chase.:crying: I will write down stuff i did in numerical orders.
1. Using TWRP 2.8.6.1, I was curious to try to go to Wipe>Advanced>full wipe (wiping everything). After i did and tried to reboot, it said there is no OS. So i tried flashing my flashable stock rom 4.4.4 in zip form but it didn't boot.
2. So i flashed to stock in fastboot. (For flashing to stock, i used this instructions http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/). After finish flashing, i went to stock recovery and wiped dalvik cache and data.
3. After that, i rebooted and... that when it didn't seem right. Nexus 5 COULD connect to my PC but it only showed "Internal Storage" and nothing else. If i tried to move something to the storage, it would immediately say i can't move it there.
4. So i thought this was because the full wipe i did before and that the system partition got totally wiped. So i used TWRP again but to restore my old nandroid backup.
5. After i flashed my nandroid backup, twrp said this one line that goes in red "unable to mount /firmware. I ignored and rebooted. It still had the problem where i couldn't move anything to my storage by MTP but also adb push. It even couldn't save screenshots and download anything from internet like apk or some sort. When i went into the app called "Zipper", it said 'no sdcard'.
6. I searched through the internet to fix this but i kept failing to solve it. I tried going to TWRP and doing chmod, chmod 755, using these instructions (http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
TL;DR : I did a full wipe in TWRP and lost all permissions to read or write. Nandroid backup didn't help. Whatever i flash in twrp, it says "unable to mount /firmware" at the end.
Click to expand...
Click to collapse
EDIT: alright i did a mess up. When i flashed the stock, i didn't rename the radio from radio-hammerhead-m8974a-2.0.50.1.16 to radio.img.
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.
"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
Hi All,
I'd urgently need confirmation and/or tipp from seasoned "brick recovery artists" ;-)
Key questions:
(a) In the scenario presented below, can I recovery from soft brick without loosing data (incl. encrypted external sdcard)?
(b) If no - is there a way to recover directly from a TWRP backup (to pre-encryption status)?
Thanks a million!
-----the issue------
To dirty flash to my S9+ rooted and encrypted device, I tried to perform a dirty flash. See CustomROM thread here.
How the issue unfolded:
1. downloaded the latest v7.4
2. moved v7.4 install file to external sd
3. booted into twrp and performed system partition backup (system image, system, recovery, boot)
4. initiated via twrp a dirty flash
4.1 received error messager after 1 second: damaged zip file
5. rebooted into sysem - WORKED
5.1 realized my SDcard was not mounted and the system tried to "encrypting sdcard 10%/11%/..."
5.2 shut down system immediately
6. repeated step 5 with same results
7. booted into twrp and tried to restore from backup (system image, system, recovery, boot)
7.1 received error message "extracttarfork() process ended with error=255"
8. rebooted into system and rebooted into twrp
9. performed full restore only "system image"
10. booted into system - same as before, in step 5; immediately shut down
11. tried to boot into twrp without success; bootloader 1 error message: "could not do normal boot. INVALID KERNEL LENGTH"
I am a bit screwed here, i think?
the funny thing is that
(a) a OS boot still required me to enter my encryption pin
(b) the OS itself had no sdcard access/mounting issues apparently, same for TWRP partially. HOWEVER, the TWRP system backup was stored on my external SD card - How was TWRP even able to perform a restore from it, if it could not read /data and the sdcard in the first place?
solved. Please close