bmwdroid
Senior Member
- Mar 8, 2014
- 2,195
- 1
- 927
Gotta flash it in TWRP.
As always, if not already included in the ROM.
Gotta flash it in TWRP.
leaving me with no access to my storage.unable to mount storage
failed to mount '/data' (Invalid argument)
Hi
I have a SM-T820, I flashed the latest tweaked rom (twrp 3.2.1-1_ashyx) but to achieve a leaner OS i decided to flash the lineageOS 17.1, unfortunately I missed the full wipe and went for a facory reset --> boot loop on restart
but now when I go back to twrp and try to do the full wipe i get:
leaving me with no access to my storage.
Does anyone know what I should do next please?
Thanks
[EDIT] SOLVED, I could sort it out following these instructions.
@BenG7 already thought of starting from scratch by flashing stock?
Thanks @bmwdroid, I will try it but first, could you please confirm these are the steps I should go thru given the idea is I want to run a rooted LineageOS 17.1 (no GApps whatsoever) and a working TWRP as opposed to what I currently have (see final lines at the end); as you will see, this is a compilation of steps that can be found across the TWRP, LineageOS threads but I must be getting it wrong somewhere... well, first I didn't do it from a stock rom - that is noted!):
In my previous attempts, I noticed at the end of the lineageOS flash, the process tells me it couldn't find the magisk addon so I assumed it was not rooted and I flashed magisk again
- put my t820 in DOWNLOAD mode
- flash latest stock (T820XXU3CTD5 for me) with odin
- reboot to latest stock
- Go into system and click seven times on build to get to show the Developpers options
- in the developper options allow OEM unlock & USB debugging
- put my t820 device in DOWNLOAD mode again.
- uncheck Auto reboot in Odin's Options tab
- Load the latest twrp available twrp_3.2.1-1_T820_28518.tar into the AP slot in the Log tab
- hit start
- after ODIN reports PASS, press POWER + HOME + VOL DOWN to reboot to recovery - as soon as the screen goes blank, change to VOL UP whilst still holding POWER + HOME --> this will get me into TWRP recovery
Up to here I agree although I'm not sure about getting into stock recovery as on all my samsungs I access first screen with three button combo and carry on only with Vol + without holding the others further on.
- < to disable forced encryption, mount internal storage (DATA) and disable dm-verity I will then flash (thru Install in TWRP) the Forced encryption patch: Tabs3_oreo_forced encryption_disabler (previously copied from laptop to internal storage in TWRP) Wasn't needed for me (see below)
- once this is done, without rebooting (please confirm), Yes I shall format DATA using the *FORMAT DATA button* / "yes" under the wipe options (this will WIPE ALL INTERNAL STORAGE!)
- once this is done, without rebooting (please confirm) Yes, I shall then flash (thru Install in TWRP) Magisk 20.4 (also previously copied from laptop to internal storage Better use a SD-card to store all neccessary files onto or an USB stick as OTG should work in TWRP)
- reboot and check DATA is mountable (Please confirm this is a reboot to System or to Recovery) I didn't do any of this except formating data and flashing Magisk but see bottom.
- backup all partitions (at least efs) and store somewhere (in order not to lose IMEI)
After flashing recovery I recommend to save EFS, if possible, before doing anything else.- full wipe all = factory reset + format data thru dedicated button + "yes" under the wipe options in TWRP
- flash (thru Install in TWRP) LineageOS 17.1 (also previously copied from laptop to internal storage in TWRP)
- reboot to system which should now be a rooted LineageOS
- go into system and click seven times on build to get to show the Developpers options, allow USB debugging.
+ when I rebooted into recovery:
- I still need to allow modifications
- my twrp settings (time zone + vibration) are not saved
- data is not mounted
Thanks a lot in advance for your help.
In my previous attempts, I noticed at the end of the lineageOS flash, the process tells me it couldn't find the magisk addon so I assumed it was not rooted and I flashed magisk again
- put my t820 in DOWNLOAD mode
- flash latest stock (T820XXU3CTD5 for me) with odin
- reboot to latest stock
- Go into system and click seven times on build to get to show the Developpers options
- in the developper options allow OEM unlock & USB debugging
- put my t820 device in DOWNLOAD mode again.
- uncheck Auto reboot in Odin's Options tab
- Load the latest twrp available twrp_3.2.1-1_T820_28518.tar into the AP slot in the Log tab
- hit start
- after ODIN reports PASS, press POWER + HOME + VOL DOWN to reboot to recovery - as soon as the screen goes blank, change to VOL UP whilst still holding POWER + HOME --> this will get me into TWRP recovery
Up to here I agree although I'm not sure about getting into stock recovery as on all my samsungs I access first screen with three button combo and carry on only with Vol + without holding the others further on. Confused here: as I described I just flashed TWRP, I get into TWRP recovery, not stock recovery, I take it this is a mistake?- < to disable forced encryption, mount internal storage (DATA) and disable dm-verity I will then flash (thru Install in TWRP) the Forced encryption patch: Tabs3_oreo_forced encryption_disabler (previously copied from laptop to internal storage in TWRP) Wasn't needed for me (see below) I take it you mean it wasn't necessary for you to copy the disabler from laptop to internal storage as you use an sd card NOT it wasn't necessary for you to flash the disabler ?
- once this is done, without rebooting (please confirm), Yes I shall format DATA using the *FORMAT DATA button* / "yes" under the wipe options (this will WIPE ALL INTERNAL STORAGE!)
- once this is done, without rebooting (please confirm) Yes, I shall then flash (thru Install in TWRP) Magisk 20.4 (also previously copied from laptop to internal storage Better use a SD-card to store all neccessary files onto or an USB stick as OTG should work in TWRP); I will use an SD card (I wanted to save myself the hassle of putting the card in)
- reboot and check DATA is mountable (Please confirm this is a reboot to System or to Recovery) I didn't do any of this except formating data and flashing Magisk but see bottom. OK
- backup all partitions (at least efs) and store somewhere (in order not to lose IMEI)
After flashing recovery I recommend to save EFS, if possible, before doing anything else. OK- full wipe all = factory reset + format data thru dedicated button + "yes" under the wipe options in TWRP
- flash (thru Install in TWRP) LineageOS 17.1 (also previously copied from laptop to internal storage in TWRP)
- reboot to system which should now be a rooted LineageOS
- go into system and click seven times on build to get to show the Developpers options, allow USB debugging.
+ when I rebooted into recovery:
- I still need to allow modifications
- my twrp settings (time zone + vibration) are not saved
- data is not mounted
Thanks a lot in advance for your help.
Expand the quote as I edited your post.
Gotta admit I'm using rorys tweaked ROM which is debloated and I deleted even bloats more before flashing. I came from rorys tweaked ROM which is still too bloated in my opinion (and that's why I decided to move on to LineageOS 17 even though I had further debloated Rory's rom with Titanium Backup)
I replaced the mentioned TWRP with twrp_3.2.1-1_T825_ashyx_Valera1978_repack.img. Arf, I take it you have an SM-T825 as twrp_3.2.1-1_T825_ashyx_Valera1978_repack.img is for T825 given its name (where did you get it? I couldn't find it); I have the SM-T820 model; and i suspect the issue is with twrp_3.2.1-1_T820_28518.tar not being able to mount /data properly…
Exchange Magisk to the newer one. I am already using Magisk 20.4.
Might be possible, that OEM setting will not be displayed directly after turning on dev options because some time most pass after dev option is set. I noticed the OEM unlock does not show anymore in the Developer options now, it only showed the first time I rooted the tablet prior to the installation of Rory's rom
To bypass this try to set time manually one month back before connecting to the internet.
That worked for mine several times.
On all my devices I've flashed Magisk either directliy after the custom ROM or after a first reboot but never before flashing the ROM.
On my devices I do the following:
Unlocking if necessary or flashing ch-autoroot.
TWRP flash in AP with Odin (auto reboot unchecked)
rebooting to new TWRP recovery
Backing up everything wanted or needed
Wiping all partitions and additionally formating data.
Custom ROM (with or without Gapps) flashed
either reboot to flash Magisk while on some devices it works to flash directly.
Except for this latest buy of the SM-T820 at a now reasonable price, it's been a while since I dealt with samsung devices (I switched to LG phones following samsung taking on apple style price policy for their own devices…), but this is indeed what I used to do and at the time there was no encryption / partition A& B business…
Never had problems with not mounting Data or encryption so I don't now much about this
Thanks again, it's probably me getting all mixed up to be honest!@BenG7 to not enlarge the post to much I start newly here.
Yes, mine is T825.
TWRP I got from here and I assumed @Valera1978 made it for both models as he didn't quote differenty, but you may be right that it's only for mine. Did you try 3.1.0-1 as well?
I do have some devices on which TWRP doesn't save Time settings either.
I got confused with accessing TWRP after Odin flash as well as I only boot with button combo and it starts TWRP without any further buttons need to be pressed. Just a blue note appears on top saying "recovery booting" then you can release the buttons.
Magisk 21.1 from here.
I wonder why you bother about encryption problems at all as (acc. to what the dev wrote it's only relevant for Oreo) and you were either flashing debloated Pie or LOS17 =Q, or do I misunderstand something?
Hope I didn't miss a point.
OK, from reading the whole thread, I'm going to give it another try after I re-flashed the latest stock (pie); instructions on how to root the SM-T82x under Pie are not provided in the OP so I'm providing them here for reference:
@ashyx / @rorymc928 / @LedgendaryEpics: please correct me if I'm wrong (will do this tomorrow as it is pretty late now here)
Flash with ODIN using the AP slot.
1. Put your device in DOWNLOAD mode,
2. Uncheck Auto reboot,
3. Load the adequate twrp_3.2.1-1_T820_28518 / twrp_3.2.1-1_T825_29518 into the AP slot and hit start,
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME --> You should now be in TWRP recovery.
5. Install the RMM V3 bypass
6. Install the Dmverity and encryption patch
7. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
8. Install Magisk
8. Reboot and check DATA is mountable --> Done.
Looks like the kernel source is fubarred. It's not the first time Sammy source code has been unbootable and it always Qualcomm source code.Ok, just tried the AQB9 Bootloader with your first and second permissive boot.img, but didn't worked. Stucked at first boot logo with the yellow writing in the upper left corner like before. Do you maybe have a AQBB, AQC1 or AQD6 permissive boot.img?
Edit:
Just to be sure that the error lies in your kernel source, I downgraded the firmware to AQB9. Ended up with the same errors for both permissive boot images like before.
Try reading the OP instead of posting pointless questions. Ciao.
The issue, as I suspected, the kernel version was mismatched to the base firmware on the device.Data mount works!!! I think we(you) have a winner! Camera works, rotate works,an supersu works,and flashes in twrp as it should. Great job, curious as to what the issue was.