so firstly, let me make this clear, i had Android 6 stock rom working initially, i installed TWRP and rooted the phone with SU
All was working fine until i decided to try and wip the phone to test either a lineage os build or the new EMUI 5
However after performing factory reset, the /data partition is now broken.
I know i'm not the only one that has encountered this issue, but i would at least like a straight forward answer in order to resolve the problem.
Stock recovery now doesn't seem to be an option as when i send it to the phone, i reboot and TWRP still exists.
i have tried via fastboot and from within TWRP, i still get the /data partition error if trying in TWRP to flash recovery.
surely there is a proper solution for this, as this is a software issue not a hardware issue.
i would appreciate your assistance and can provide whatever required information necessary.
i did not pay $500 for this phone for it to be a useless brick
I noticed something here about modaco-rc3 recovery, which i am downloading to try, if it flashes properly, as i suspect this /data partition issue is preventing much of anything from being modified now.
i look forward to your responses and will reply to this with an update after trying to flash modaco recovery if successful
The data partition of the EMUI roms are different than what for example lineageos needs (I think because of encryption).
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
christopherpfister said:
You need to flash the stock recovery via fastboot, then wipe and format data from there, then TWRP should be able to mount the partition again. In TWRP you can format the partition again to the format according to what is necessary for the rom you want to install.
Click to expand...
Click to collapse
I am just downloading 4.1 stock rom i found finally on Huawei website after much buggering around last night, clearly it was a long day.
Will get this flashed with the stock recovery that I was able to put back on thanks to SRKTool
Will update again shortly, thank you for the reply.
failed to mount system for rom install
now this is just getting silly...
so i was able to restore stock rom with the dload folder procedure and EMUI recovery restored with SRKTool
successfully then unlocked bootloader, put on twrp-3.0.2-0-eva-modaco-rc3, did the data wipes and tried to install lineage os zip.
(the original problem of going back to stock rom is solved, but this is still ongoing as to now why a custom rom will not load)
now i get the infamous ERROR: 7
after
could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4
mount: failed to mount /dev/block/bootdevice/by-name/system at system: no such file or directory
....this is all seeming far too difficult to install any custom rom on this unit, what is happening?
same issue
I'm having a similar issue, any updates?
Related
My Nexus 6 was running TWRP 2.8.X.X and on CM13. I decided to flash a different ROM but first, I updated TWRP to 3.0.2.0.
When I did the "Wipe" before flashing the new ROM, TWRP apparently wiped my entire system. Now TRWP is telling me that there is no OS installed???.
I'm going to "Sideload" a ROM so that I may re-flash my phone but my question is that TWRP is telling me that my system is "Read Only". Should I first let TWRP change my system to "Read/Write" or will I be able to flash my ROM and restore my phone if I leave it "Read Only"??
I'm a little confused because TWRP never asked me before about modifying my system. It wasnt until I updated that TWRP asked me this?.
It's not bricked. I wipe my os all the time. You will need to use an otg to flash a rom and you'll be fine. Or you need to use add pull/push to get a rom into the internal storage then flash.
Changing your system to read/write should be no problem. I'm no expert but, I would imagine writing to your system partition requires writing permissions to be enabled.
I "adb sideloaded" a ROM and restored my Nexus 6 but everytime I reboot from recovery, TWRP tell me that there is no "OS installed"???. I'm not going to worry about it since everything is working. Must be a bug that happened when I updated TWRP??
you'll find your answers in the TWRP thread...
Hi all,
What happens if you take a stock 3T, upgrade it all the way to Nougat the normal way, then proceed to unlock the bootloader, flash TWRP and supersu?
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard? Is that even a problem in the sense of waiting until a fixed version of TWRP is released? The point is to just flash supersu for the moment. No other need to access that partition from recovery, is there? Or does it directly impact my ability to upgrade TWRP in the future?
And another question: would decrypting the phone after the stock to Nougat update, and only then flashing TWRP&root be of any use? Is this even possible at the moment? I can hold on without encryption until there's a proper version of TWRP, kernel sources are released etc.
I don't seem to find any info on these scenarios. Has anyone tried any of this?
Thank you!
Good questions.
Does the TWRP 3.0.3.0 build have an issue with decrypting and mouting the sdcard?
Click to expand...
Click to collapse
I can confirm 3.0.3.0 has problems with decrypting and mounting sdcard. A new version of TWRP should fix this.
No other need to access that partition from recovery, is there?
Click to expand...
Click to collapse
Well, the need to access partition from recovery depends. You won't be able to flash anything from TWRP. I could sideload different recoveries without decrypting but had to decrypt (with the format userdata command from cmd prompt) to revert to 3.5.4 from TWRP. In the end I mostly downgraded due to bluetooth issues.
I am having the same decryption issue... TWRP shows 0MB as the storage
What should be done now..?
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Amar97 said:
you can get past encryption by formating data in twrp, though that deletes all your data, back ups and everything, but with that you have the phone completely rooted and then you can download or transfer data via mtp to storage, flash super su and verity.
Click to expand...
Click to collapse
Did that already but did not work.. Even tried the setting up of pattern method.. that too did not work...
Also force decrypted with Toolkit but still the same
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Amar97 said:
just to make sure. flash twrp via fastboot( I flashed the 3.0.2.0 version) then when booting to twrp you get get the screen where it asks you for a password, skip that , just swipe to continue then go to wipe, then format data, type "yes" to confirm, the at the next booting it shouldn't ask you for the password anymore. That did it for me. Maybe you should try adb sideload to flash verity.img and supersu
Click to expand...
Click to collapse
why not use 3.0.3.0?
Solnir said:
why not use 3.0.3.0?
Click to expand...
Click to collapse
Don't really know, probably tried solving the problem by trying with the older version and then didn't feel like upgrading to the newer 3.0 after fixing the problem.
Hello,
I have always been on root but somehow something changed.
Since I tried to flash the newest stable stock (5.0.1), nothing works anymore.
No matter if I flash dm-verity disabler, supersu or magisk, dm-verity gets triggered everytime and my phone just says "decryption unsuccessfull" and won't boot.
I've tried everything to fix this, including: different versions of supersu/magisk, reflashing TWRP recovery, even going completely back to stock, locking the bootloader and everything.
Also I read somewhere that you can flash dm-verity disabler and wipe data to completely remove the encryption, but TWRP showed an error message, something like "failed to wipe, cannot mount /data".
In the end I got stuck with no ROM and I couldn't even access stock recovery anymore because it had the weird password bug, so I had to use the unbrick tool to get it working again.
Can someone tell me what I'm doing wrong?
I have always been on root since the early Nexus 5 days, but now I feel really stupid because I must be missing something obvious, so thank you in advance for any help.
Cheers
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
If by chance you are trying to flash OpenBeta 21, I have yet to avoid my data getting encrpyted when trying to flash. And personally, I must have been doing something incorrect ever since I got the phone, because almost every time I've flashed a stock OxygenOS ROM I have triggered encrpytion. In my situation it never seemed to matter if I flashed Magisk, SuperSU, a custom kernel, or even just a modified boot.img along with the disable encryption file... I don't know the steps you're taking, but what I do is this: once I get the "Encryption Unsuccessful" message when trying to boot, I just reboot to fastboot and type "fastboot format userdata". And since flashing stock OxygenOS usually overwrites TWRP with the stock recovery despite my best efforts to avoid it, I tend to go ahead and flash TWRP while I'm booted into fastboot. After, I boot into TWRP; at which point encryption has been removed, yet the total amount of storage available to me is less than 30GB (I have the 128GB model.) You have to go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data. That restores my device back to 111GB free of 113GB. I then transfer over and flash Magisk and whatever other mods I wanted. After that my device is no longer encrypted and works just how I want it to. Hope that helps with your issue.
What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
Click to expand...
Click to collapse
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data.
Click to expand...
Click to collapse
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
kaeptn1 said:
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're not using Blu Spark 8.61 TWRP, then I suggest you install it and try again.
If all else fails, do as @lordcheeto03 suggested and format userdata in fastboot - but note that this will completely wipe your data, including internal storage. Then install TWRP, then flash 5.0.1 and anything else you want.
Sent from my OnePlus3T using XDA Labs
kaeptn1 said:
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're getting the encryption unsuccessful error, I don't think you format data in that manner, you gotta use fastboot and fastboot format userdata to remove encryption THEN boot into TWRP to do that.
Hi all,
I'm having trouble flashing a custom ROM on my Mi 9 Lite. After formatting, TWRP is unable to mount storage, probably due to encryption/decryption issues! Here's what I've done so far:
- unlock boot loader (with Mi Unlock after wait time)
- flash TWRP recovery with fastboot (mauronofrio)
- boot to TWRP worked fine
- followed the OP by gringo80 to install LineageOS 16.0 - as was said there, to do FORMAT once after flashing TWRP
Now TWRP can't mount/find internal storage, says "failed to mount data (no such device)" - can't format or wipe data anymore. All I found so far is that this will be an encryption/decryption issue due to the formatting, but no clue on how to undo this!
Any ideas? Flashing new system or restoring backup always results in bootloop, probably because the ROM can't write on internal storage either?!
Please help :crying:
.M.D. said:
Hi all,
I'm having trouble flashing a custom ROM on my Mi 9 Lite. After formatting, TWRP is unable to mount storage, probably due to encryption/decryption issues! Here's what I've done so far:
- unlock boot loader (with Mi Unlock after wait time)
- flash TWRP recovery with fastboot (mauronofrio)
- boot to TWRP worked fine
- followed the OP by gringo80 to install LineageOS 16.0 - as was said there, to do FORMAT once after flashing TWRP
Now TWRP can't mount/find internal storage, says "failed to mount data (no such device)" - can't format or wipe data anymore. All I found so far is that this will be an encryption/decryption issue due to the formatting, but no clue on how to undo this!
Any ideas? Flashing new system or restoring backup always results in bootloop, probably because the ROM can't write on internal storage either?!
Please help :crying:
Click to expand...
Click to collapse
The current twrp has issues with data try to change filesystem to f2fs and after that change back to ext4 (it forces a full data partition wipe). i've done this always on my mi9 lite AND watch out for the right firmware for lineage os that causes issues too
Layer_DE said:
The current twrp has issues with data try to change filesystem to f2fs and after that change back to ext4 (it forces a full data partition wipe). i've done this always on my mi9 lite AND watch out for the right firmware for lineage os that causes issues too
Click to expand...
Click to collapse
Changing file system to ext4 and back to f2fs did the trick - thank you so much!
Was able to install LOS 17.1 going forward. Thanks again! :good::fingers-crossed:
Need help again :crying:
I flashed the original firmware as instructed, but now all I get is fastboot - NO RECOVERY!
If I flash a recovery with fastboot, all I can to is boot to fastboot again... what can I do now? :crying::crying::crying:
.M.D. said:
Need help again :crying:
I flashed the original firmware as instructed, but now all I get is fastboot - NO RECOVERY!
If I flash a recovery with fastboot, all I can to is boot to fastboot again... what can I do now? :crying::crying::crying:
Click to expand...
Click to collapse
You may have bricked your phone. Did you tick the 'clean all and lock' option in miflash rather than 'clean all'? If so your phone is bricked and needs EDL flashing by an authorized technician to fix it.
Lucky enough, not bricked - I flashed a firmware update in the middle of all of it, one which, of course, replaced almost everything I had done so far. Forgot to flash custom vbmeta when trying to re-flash TWRP, doing so solved the issues I've had. Close call though, as the firmware update could have re-locked bootloader in a worst case scneario, so really lucky to be using my phone with MiuiMiX now, all working perfectly!
Thanks for the help though!!!
So this happened, first time unlocking my phone, installed TWRP and everything good, now I wiped all of the phone and I can't flash any ROMs since TWRP can't decrypt the phone either I can't find a way to revert recovery and system to the original state.
Tried Flashing various versions of TWRP, none seem to work.
Tried the vbmeta-patcher
Formated the whole device.
Tried both MiToolUnlock and Tool All in One
Also, after flashing any version of TWRP and booting, it always goes back to the previous version (unofficial 3.3.1-25 by Mauronofrio)
I don't know what else to do. Any help?
fverdeja said:
So this happened, first time unlocking my phone, installed TWRP and everything good, now I wiped all of the phone and I can't flash any ROMs since TWRP can't decrypt the phone either I can't find a way to revert recovery and system to the original state.
Tried Flashing various versions of TWRP, none seem to work.
Tried the vbmeta-patcher
Formated the whole device.
Tried both MiToolUnlock and Tool All in One
Also, after flashing any version of TWRP and booting, it always goes back to the previous version (unofficial 3.3.1-25 by Mauronofrio)
I don't know what else to do. Any help?
Click to expand...
Click to collapse
Try flashing the correct fastboot ROM for your phone, using the Mi Flash Tool.
Then don't wipe everything in future. Stick with wiping just cache, dalvik and data. It's very rare you will need to wipe anything else.
Try this tool to erase and decrypt your internal storage
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Than install rom using usb otg.