I just picked up a Barnes & Ignoble SM-T713 "Nook" on FleaBay. I managed to Odin flash stock 2BRB2 and TWRP 3.2.2. The problem is that TWRP can't seem to mount the /data partition, so anything I try to flash that way fails; subsequently I get a "verification error" asking for a password on boot.
I'm assuming that the Nook variant is locked down in some way. I'd like to root this puppy, but this is a road block! Any idea how it's locked down and if a relative newbie like me can fix it.
Thanks in advance!
Edit: I have to learn to read the whole thread. The trick is to FORMAT (not WIPE) data in TWRP.
https://forum.xda-developers.com/showpost.php?p=67187922&postcount=36
Related
Like an idiot, I accepted an OTA (4.4.2) while rooted with a custom recovery (Philz). I got stuck in a boot loop and proceded to run through the instructions here (method 2) to get back to stock. I have tried several iterations of this using different stock images with the same result, I can't mount /cache or /data. In the end my phone tries to boot, but gets past the unlocked bootloader screen and flashes the android laying on its back with error written below. My bootloader is 30.B2. Oh yeah, I even tried to download an experimental Cyanogenmod and install it using the ADB sideload, but it failed because it could not access /data.
Any help would be greatly appreciated.
T-Mobile Moto X with unlocked bootloader.
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?
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!!!
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.