TWRP can't mount /system - Redmi Note Q&A, Help & Troubleshooting

I tried dual boot my redmi note 4g using an chinese software. As I don't know chinese Ijust followed instructions given on source site. I got dual boot on my phone successfully. But after incomplete installation of second rom i wiped cache which cause my phone an bootloop formatting my internal memory.
I tried installing official miui rom through recovery. But TWRP gave me error of unable to mount /system.
After some research I found that
Code:
/dev/block/platform/sdcc.1/by-name/system2
is causing problem.
This file mounts at /system partition. The actual name should be
Code:
/dev/block/platform/sdcc.1/by-name/system
.
I want to rename this file. I tried many ways but it gets renamed back after each reboot. This is also preventing from installing rom through fastboot method. I guess I will have to do changes somewhere else through partition table. I don't know much about this so what exactly I should do to rename
Code:
/dev/block/platform/sdcc.1/by-name/system2
to
Code:
/dev/block/platform/sdcc.1/by-name/system
.
Sorry for bad english.

Related

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.
Anyone have any idea?
Thanks
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?
You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes
I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.
you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)
Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.
Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.
I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?

[Possibly bricked] "Failed to mount /data" & no internal storage

Hello everyone!
I have a P9 lite VNS-L31 running 7.0.1. on EMUI 5.0.2..
However during a factory wipe, it stopped booting correctly and I can't get passed from neither bootloader nor recovery.
I have TWRP Revolution v.260317 (TWRP 3.1.0-0) installed and my main problem is that for some reason the phone says that I have no internal storage whatsoever and if I try to wipe the /data partition it fails to mount it (error: Failed to mount /data (Invalid argument)).
I tried any of the methods in videos titled "how to fix unable to mount /data" (sorry, I cannot post links :/ ) but with no luck.
I can't seem to repair nor resize nor change file system of the /data partition. When trying to repair data using e2fsck it gives out the message:
" /sbin/e2fsck -fp process ended with ERROR: 16"
Any ideas?
I can use recovery and fastboot if necessary.
Regards
flash this twrp ;
https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
give me a thanks if it works
Exiatron00 said:
flash this twrp ;
https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
give me a thanks if it works
Click to expand...
Click to collapse
Well, more or less, but I managed to solve it!
I found out that the reason why it said there was 0mb of internal storage was because the bootloader that was previously unlocked turned itself locked, that's why it couldn't mount the /data partition. I just used SKR Tool to unlock the bootloader and after that yes, I installed that version of TWRP that you linked.
I also found out that the Revolution TWRP installed in the eRecovery partition (/recovery2 ?) instead of the normal recovery partition. What image is supposed to be installed in that partition?
That is the second recovery partition (another recovery) aka huaweis last ditch attempt to fix a broken phone. There's no actually problem if u don't have it-as most of the time (in my experience) its utter garbage, but there's no harm in flashing it if u want.
U can extract it from ur update.app file using huawei update extractor.
Exiatron00 said:
That is the second recovery partition (another recovery) aka huaweis last ditch attempt to fix a broken phone. There's no actually problem if u don't have it-as most of the time (in my experience) its utter garbage, but there's no harm in flashing it if u want.
U can extract it from ur update.app file using huawei update extractor.
Click to expand...
Click to collapse
Yeah, I tried to install the RECOVERY2.img that I extracted from the UPDATE.app and it didn't work so I just didn't bother and installed the TWRP again.
But at least everything is solved!
Thanks

Phone not accessable after trying to install Custom Rom

Hi,
so i've tried to root my phone and then to install a custom rom. the root went without any problem. After the root, i tried to install lineage OS 16.0 and followed this guide:
https://forum.xda-developers.com/redmi-note-7/development/rom-lineageos-16-0-t3923203
i downloaded the rom and gapps, put them on my root directory of my phone and then i wiped System,Cache ,Data, Internal Storage and Format Data. After wiping, the roms were gone, so i rebooted and transfered them again into the root directory. Then, i went onto installing (just like i did with magisk) but an error occurred saying:
E: String resource 'zip_compatible_err' not found. Using default value.
Zip Treble compatibility error!
Invalid zip file format!
Error installing zip file '....'
Updating partition details...
...done
Ok. So then, i tried to install another Custom Rom so i went for Oxygen OS, it actually did install but then i couldn't boot into it because it was telling me there was an 'Android System Error'. Ok, back in TWRP, i wiped everything and then i tried to install the Original ROM but i got the same error as above.
For now i tried to download the miFlasher tool but it only wants to download some driver and it literally takes forever.
Hope you can help me...
Download Fastboot ROM for your device and do this Fastboot Method
marcopast said:
Hi,
so i've tried to root my phone and then to install a custom rom. the root went without any problem. After the root, i tried to install lineage OS 16.0 and followed this guide:
https://forum.xda-developers.com/redmi-note-7/development/rom-lineageos-16-0-t3923203
i downloaded the rom and gapps, put them on my root directory of my phone and then i wiped System,Cache ,Data, Internal Storage and Format Data. After wiping, the roms were gone, so i rebooted and transfered them again into the root directory. Then, i went onto installing (just like i did with magisk) but an error occurred saying:
E: String resource 'zip_compatible_err' not found. Using default value.
Zip Treble compatibility error!
Invalid zip file format!
Error installing zip file '....'
Updating partition details...
...done
Ok. So then, i tried to install another Custom Rom so i went for Oxygen OS, it actually did install but then i couldn't boot into it because it was telling me there was an 'Android System Error'. Ok, back in TWRP, i wiped everything and then i tried to install the Original ROM but i got the same error as above.
For now i tried to download the miFlasher tool but it only wants to download some driver and it literally takes forever.
Hope you can help me...
Click to expand...
Click to collapse
Those recoveries are old.. Use orange fox recovery 10.0-2 it will work and format data then install rom.
title?
@BlackGarnett
Thanks, that help me on a quick one!
@loseyourself
Also thank you for this advice, i'm new to rooting smartphones and install cfw since i was using iPhone for the past few years.
But now i got another new question: if i use orange fox recovery and i run a backup with it (i think there will be an option to do a backup), then i format all data and internal storage, can i still recover from the backup or will it be deleted?
thanks again!
marcopast said:
@BlackGarnett
Thanks, that help me on a quick one!
@loseyourself
Also thank you for this advice, i'm new to rooting smartphones and install cfw since i was using iPhone for the past few years.
But now i got another new question: if i use orange fox recovery and i run a backup with it (i think there will be an option to do a backup), then i format all data and internal storage, can i still recover from the backup or will it be deleted?
thanks again!
Click to expand...
Click to collapse
When u make a backup to internal all is lost after format it. Orangefox put files on the internal sd. After format reboot recovery in the option section and flash again Orangefox.
Help me ,i need efs backup for unbrick my decices please

Lenovo tb-8504x help!

Hello!
I got this tablet (lenovo tab 4 8 (tb-8504x)) from friend of a friend, who already was trying to install custom rom and recovery to this tablet. So I'm at the situation where I have no idea how bad this tablet has been messed up. At the moment I can open fastboot and twrp recovery. I tried to find stock image to this tablet, but for some reason I can't find any (or can't search good enough). I tried recovery with Lenovo Rescue and Smart Assistant, but recovery always fails for some reason. I also tried to install Lineage OS from this thread, but as a result I'm looking at never ending boot sequence of Lineage OS. I have done exactly as thread said:
- I flashed twrp from this thread and it's working
- I wiped cache, data and system from twrp
- I installed Lineage OS from first thread with adb sideload
- I also tried install Lineage OS with gapps nano
Result is that the Lineage OS wont boot and I has no recovery / stock images to this tablet.
Any help or ideas would be more than welcome!
Here is logs from adb Sideload after installing Lineage OS
--------------
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Starting ADB sideload feature...
Installing ZIP file '/sideload/package.zip'
Warning: No file_contexts
Target: Lenovo/TB-8504X/TB-8504X:8.1.0/OPM1.171019.019/8504X_S001031_191204_ROW:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
script succeeded: result was [1.000000]
Formatting Cache using make_ext4fs...
Wiping Dalvik Cache directories...
-- Dalvik Cache Directories wipe complete!
---------------
From adb at PC, result code was: Total xfer: 1.01x
Ajeem Ahmad said:
I have stock rom (Nougat) in my google drive.
i can share link if you still haven't fixed the tab.
Click to expand...
Click to collapse
I have device that's modified with LOS but I want to restore the stock rom, could you post th link here or give the download to me?
Is it te same as this one: https://androidfilehost.com/?fid=10763459528675561263
Ajeem Ahmad said:
Which version do you need, i have only "x" (tb-8504x) version of rom ?
Click to expand...
Click to collapse
I need tb-8504f rom.

[Q] [HELP] Odin/TWRP Flash successful, BUT not changing anything after reboot

TLDR : I Cannot MODIFY ANYTHING IN SYSTEM or USERDATA(i.e. internal storage) partitions. Files Deleted via twrp in System/internal storage comeback after reboot and new files added from computer vanish after reboot. Also NOW, different flashes are successful through both methods via -
1. twrp recovery-(Boot/recovery/CustomROMs flashes) and
2. ODIN-(boot/recovery/Stock ROM flashes)
but again dont change anything after reboot (previously both methods worked, so no issue with twrp or odin according to me). So, Whole storage (System+Internal Storage) is intact after Reboot as it is. Now I feel it has something to do with magisk. I can see exact file names both in internal storage and /system and do delete, move, rename i.e. any operations in twrp so i guess storage is not encrypted. I can boot into system for hardly 10-15 seconds after that it bootloops again, so i cannot do anything there. Only options to me is twrp recovery or odin, both are not helping for now.
--------------------------------- DETAILED EXPLANATION : ------------------------------------
[PROBLEM 1] DELETION:
Anything deleted via TWRP recovery in system partition or "EVEN in sdcard, i.e. internal storage" deletes successfully in twrp, without any error but comes back in the same state after the reboot. When i delete error causing file or folder via TWRP file manager, it gets deleted, and if you check again it's not there wherever it was present, but just after reboot every file and folder comes back to previous state like if nothing was done. This is true for any file present in any of the partitions. Newly inserted file in internal storage vanishes after reboot, and deleted file comes back after reboot - true for any partition. Status quo maintained !!
[PROBLEM 2] FLASHING:
To solve above problem, i thought it might be an issue with Magisk or the new twrp recovery, so i tried flashing Magisk Uninstaller zip in twrp, which again flashes successfully, SECONDLY- tried zackptg-(dmverity,forceencrypt Disabler) zip file, that also flashes successfully(i thought might be an issue of dmverity or encryption), and THIRD thing i tried flashing older twrp version recovery, that also flashes successfully but after reboot same currently installed twrp boots, not the newly "successfully flashed" older version. So i cannot change twrp-(tried both recovery.img flash in (1) twrp itself and (2) also through ODIN) - both returns flash successful and pass(in Green). FOURTH, tried dirty flash both (1) other ROM and (2) SAME ROM on top of current ROM- everything returns successful but after reboot boots the current erroneous ROM that i want to change. FIFTH, tried Clean Flashing i.e. wiped everything (selected 1. dalvik cache, 2. data, 3. cache, 4. system, 5. Internal Storage in wipe section) and also tried Factory RESET and FORMAT DATA option and after all this flashed Custom ROM zip file only (no gapps or magisk flash), but every wipe operation returns successful and ROM flash also successful, but when reboot into system again that bootlooping erroneous ROM that was present before all of these "successfully done" operations.
[PROBLEM 3] ODIN FLASH:
As all above failed, i thought flashing STOCK ROM through ODIN is my last resort. I did (1) Stock recovery flash through Odin- it was green pass (successful), but when booted returned that same twrp recovery not stock recovery. Tried (2) flashing Stock BOOT.img flash through ODIN, again it was successful but actual boot resulted the same Magisk Patched Boot.img. Third (3) tried flashing whole STOCK FIRMWARE - Official latest Stock firmware that was extracted from Samsung Smart Switch, with default options turned on in Odin, flash was again green-pass(successful) but auto reboot after successful flash through ODIN resulted same old erroneous ROM booting up like a VAMPIRE (I'm not dead, I'm Alive!!)... Fourth (4) tried flashing Stock Firmwave of step 3 with NAND ERASE and RE-PARTITION options turned on by inserting pit file to do BANG BANG, nuking my phone with these options that many people on internet advise not to use, screenshot attached below( it took 42 minutes to complete ), again using these options nand erase and re-partition also resulted successful(green-pass) and resulting that same untouched state as it was before.. Boots into twrp recovery not the stock rom or stock recovery with that same old erroneous ROM present in system with data partition intact. (Tried using different ODIN versions, different USB ports on my laptop, different non-official firmwares(but these non-official firmwares of SM-G530H resulted in some errors in ODIN, i.e. it was not green pass like that of official firmware, but resulted RED FAIL.))
[PROBLEM 4] SYSTEM_ROOT Created:
This i saw for the first time i guess, in my phone, and maybe the cause of this whole problem. Now my root directory in twrp '/ ' contains /system_root along with /system, /data, /cache. One more thing /system_root contains system folder ,i.e. /system_root/system results same things as /system . When checked in twrp>wipe section> Repair system> There System Mount Point is shown as : /system_root instead of previously used to be "/system" normal directory when /system_root was not present at all.
Another thing /system_root contains files like default.prop , init files, sepolicy which are also present in root directory ' / ' . This whole /system_root should not have existed at all when /system exists. Maybe /system_root or the init files or other thing present inside /system_root are preventing all the changes - deletion , flashing changes etc. described in this post and maybe this folder was created by step(3) flashing procedure below , i.e. due to magisk. Also formatting system in twrp>wipe>system returns successful msg but nothing is deleted when checked in twrp file manager or twrp>Backup (system partition backup size shows 1456 mb even after formating)
[OTHER THINGS I TRIED] to solve this -
- Deleting twrp folder to make it to default state, again it's successfull deleted but doesn't loads default configuration after reboot due to PROBLEM 1 above as deletion reverts back after reboot
- Fixing contexts in twrp
- reboot disemmcwp
- mount -o remount,rw /system commands in twrp terminal (again to mention every command that is possible to enter runs without any error, hence successful but problem persists even after that )
- flashing stock boot.img and recovery.img (both successful no changes observed after reboot, but after stock boot or recovery.img flash, if you flash magisk uninstaller zip it still says "magisk patched image detected", and next thing written after it is " ! (Exclamation mark) Boot image backup unavailable" , then "Restoring ramdisk with internal backup" again magisk uninstaller also returns successful. after reboot again runing uninstaller detects magisk again. and boots twrp only instead of stock recovery
- repair, resize system partition in twrp>wipe section results Twrp error 1 (might be due to that /system_root folder that contains now /system which is also present in ' / ' root
- Changing "system partition" file-system with all 6 options returns successful but filesystem stays ext4 only when checked again.
WHAT IS WORKING-
Odin is working. - i once flashed my first twrp recovery on this device through the same version
TWRP is working - Although this is new twrp version 3.6.1_9-0 that i flashed just few time before all this catastrophe happened (maybe it might be the cause or it may be magisk)
Current Configuration:
Device: Samsung Galaxy Grand Prime
Model: SM-G530H (fortuna3g)
ROM: [STABLE][10] LineageOS 17.1 GO by DarkDroidDev from xda
GApps: Customised OpenGapps package (this caused erroneous bootlooping ROM) - i can boot into ROM but it is very lagging, and reboots again after some time, ranging from 10-20 seconds to max 3 minutes. Launcher is not working. And Keyboard is crashing. I can go into settings to change something but change doesn't persists after reboot
Magisk: Magisk 23.0
What was my FLASH PROCEDURES before this happened-
- Cleaned dalvikcache, data, cache, system
- After this, Data and Cache showed 0mb in Backup option in twrp, system showed 2mb containing only usr folder, boot showed 13mb
- (1) Cleaned Flashed above ROM
- (2) Customized OpenGapps flash
- (3) Magisk Patched Boot.img flash - - (not magisk.zip installer, its magisk-patched-boot.img flash through twrp only)
- (4) Dalvik Cache Wipe
- Booted into System.
I was actually testing the customised OpenGapps package,
Before this flashed customised package 10-20 times. i was editing, flashing, seeing the changes... > then again editing, flashing. So this was not the first time.
If any error occured, like launcher not working, i again booted into twrp wiped system data or deleted particular launcher file in twrp, all worked, changes were successful then i again continued my testing.. editing packages > flashing > seeing the changes by booting into actual rom.
But this whole case happened during the iteration of my testing when i introduced Gboard apk, downloaded from Play Store from fortuna3g(this device), into the Custom Gapps Package.
So, the cause of all this according to my knowledge where i doubt maybe one of the following-
(1) - That Keyboard apk installation as system app (most probably permissions problem, as apk was fine as tested before on this device and resulted in keyboard related folders created in that /system/usr folder which always contained only one folder, but only this time contained this keyboard related stuff there)
(2) - That magisk-patched-boot.img flashing procedure, step(3) above, just after openGapps flash "without booting into system first" - this was done first time in my testing iterations, so might be incorrect procedure
(3) - Due to step (3), issue might be related to magisk related stuff - dm-verity, Force encryption
(4) - Creation of /system_root folder in root directory '/ ' maybe due to step (3), there used to be only /system there before
(5) - Hardware Problem, maybe that's why all those successful twrp and ODIN flashes not doing anything
Please suggest something that i have not tried and could solve this PROBLEM of NOT BEING ABLE TO CHANGE ANYTHING ON SYSTEM or USERDATA partition.
I know people here know a lot more than me, and can help me with their valuable suggestions and solutions, if any.
Thanks.
I found one xda thread almost with same issue as mine titled -
[Q] Weirdest problem - flashing anythin thru ODIN does not change anything in my S4​But no working solution there also
LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
Hi mate, My phone is Snapdragon powered..
My problem is almost similar.. But not exactly.. After almost 2 months I am not able to find a solution.. But after this period of researching and googling about things related to my problem.. I feel now, either any one of the following is the cause of problem:
1. Emmc is stuck or locked in read-only mode (Can move files from pc , delete already present files anywhere in any directory, but all changes vanish after reboot... all file and directory structure remain intact- moved files from pc gets deleted.. and deleted files which were already present come back after reboot )
2. Corrupted /data and /cache partition, as e2fsck in twrp terminal results shows "filesystem still has errors" and "e2fsck: unable to set superblock flags on /dev/block/mmcblk0p** ) in both these file system (I think they are preventing flashing procedures- Odin stock firmware flashes and twrp custom ROM flashes both are successful, but after reboot no changes can be seen... - Even Recovery.img and boot.img flashes don't seem to work even both are shown successfully flashed in twrp) After reboot current version twrp boots again instead of newly flashed different version recovery.img ... same with boot.img even after running magisk uninstaller zip files.. running uninstall.zip 2nd or 3rd time also shows magisk patched image detected in log which should be removed in 1st iteration itself..
3. Might be magisk is preventing these changes to be made.. or It might be the /System_root creation as mountpoint for system partition which used to be previously /system normally. This might be the superblock creation which not used to be there. You can see my attachments in my thread to see my directory structure of system_root and my download mode picture
My Samsung's twrp and Download Mode seems to be working but no changes made by them even after successful operations by both.
Can you suggest anything @LinhBT ?

Categories

Resources