Alright so here's the deal, my internal SDCARD is corrupted and the /data partition is unusable.
My device is i9003 and it's running on MIUI at the moment. By default MIUI didn't detect my external SD or my internal SD but after editing "vold.fstab" I was able to mount the first partition of my external SDCARD as external memory and everything was good, I could finally use the camera and pretty much do everything else.
But I was still unable to mount the second partition of my external SDCARD as my internal memory which meant none of my messages could be saved and the phone would pretty much go back to factory settings after a reboot, this apparently is because the /data partition (present on the internal memory) stores all the user data such as the time, the theme I'm using, etc and not having a /data partition meant none of these settings were really saved.
Having no internal memory also means I cannot install any apps such as Link2SD.
Moving on, after many hours of googling I found out that it might not be possible to mount the internal memory using "vold.fstab" and the only way to do it could be by mounting the memory manually during init.
So here's what I want again, I want to use the second partition of my external SDCARD as internal memory, this is likely to solve all my problems and make my phone usable again.
Thanks for all the help, appreciate it.
You need to edit /init.rc (or init.vendor.rc). To make the edits here stay, you'll need to create a new boot.img to flash your device with.
Have a look at an extract of mine init.<vendor>.rc:
Code:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
#mount yaffs2 [email protected] /system
#mount yaffs2 [email protected] /system ro remount
# Use below two lines instead of above to run /system from SDcard instead of internal flash
mount ext3 /dev/block/mmcblk0p3 /system
mount ext3 /dev/block/mmcblk0p3 /system ro remount
#mount yaffs2 [email protected] /data nosuid nodev
mount ext3 /dev/block/mmcblk0p4 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
Compare the lines I've commented out with the others. Here both /data and /system resides on the SDcard, you only need to care about /data. Also remember your device nodes may not be named "mmcblk0p3" etc.
But you'll need to make those changes in the initramfs in your flashed boot.img to make them stay.
kuisma said:
You need to edit /init.rc (or init.vendor.rc). To make the edits here stay, you'll need to create a new boot.img to flash your device with.
Have a look at an extract of mine init.<vendor>.rc:
Code:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
#mount yaffs2 [email protected] /system
#mount yaffs2 [email protected] /system ro remount
# Use below two lines instead of above to run /system from SDcard instead of internal flash
mount ext3 /dev/block/mmcblk0p3 /system
mount ext3 /dev/block/mmcblk0p3 /system ro remount
#mount yaffs2 [email protected] /data nosuid nodev
mount ext3 /dev/block/mmcblk0p4 /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
Compare the lines I've commented out with the others. Here both /data and /system resides on the SDcard, you only need to care about /data. Also remember your device nodes may not be named "mmcblk0p3" etc.
But you'll need to make those changes in the initramfs in your flashed boot.img to make them stay.
Click to expand...
Click to collapse
Thanks for the reply man, mind telling me the how I can go about doing this?, I've got the ROM I flashed via CWM here with me, I could send it over to you if that would make things easier for you.
EDIT: would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img? In case it's the latter, I'm going to need help doing it.
PhantomPhreek said:
Thanks for the reply man, mind telling me the how I can go about doing this?, I've got the ROM I flashed via CWM here with me, I could send it over to you if that would make things easier for you.
Click to expand...
Click to collapse
You'll find a good tutorial about how to work with boot images here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
If you already got the ROM in a file, this should be easy! Got ADB and FASTBOOT as well?
kuisma said:
You'll find a good tutorial about how to work with boot images here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
If you already got the ROM in a file, this should be easy! Got ADB and FASTBOOT as well?
Click to expand...
Click to collapse
I'm not sure I've got FASTBOOT but I've definitely got ADB and I've also got the ROM. Would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img?.
PhantomPhreek said:
I'm not sure I've got FASTBOOT but I've definitely got ADB and I've also got the ROM. Would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img?.
Click to expand...
Click to collapse
No. You need to reboot the phone for the init.rc script to execute, and once you reboot the phone, the root file system is overwritten by the flashed image ... Catch 22.
You'll NEED to create a new boot.img with a new initramfs containing your changes.
kuisma said:
No. You need to reboot the phone for the init.rc script to execute, and once you reboot the phone, the root file system is overwritten by the flashed image ... Catch 22.
You'll NEED to create a new boot.img with a new initramfs containing your changes.
Click to expand...
Click to collapse
Shucks, this explains why it didn't work. Alright, so I extract boot.img from the rom, follow the tutorial.What is it that I have to edit again? "/init.rc" or "init.<vendor>.rc"?.
Thanks for the help man, appreciate it.
EDIT: Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?
PhantomPhreek said:
Shucks, this explains why it didn't work. Alright, so I extract boot.img from the rom, follow the tutorial.What is it that I have to edit again? "/init.rc" or "init.<vendor>.rc"?.
Thanks for the help man, appreciate it.
Click to expand...
Click to collapse
Of course, MIUI may have some boot hooks you could use to re-mount /data after boot. I know nothing about that ROM. Also keep in mind that each time you update the ROM, you have to remake this edit.
Also, no idea what MIUI calls its init.rc, you'll just have to see for yourself. If you've got the mount commands in init.rc, fine. Else look elsewhere.
A good first step would to make sure you really are able to flash a new boot.img. Download fastboot and verify your device understands it. Else you have to use some proprietary flash program, and I'm not familiar with Samsungs bootloaders at all. Ask in the Samsung forum if so.
kuisma said:
Of course, MIUI may have some boot hooks you could use to re-mount /data after boot. I know nothing about that ROM. Also keep in mind that each time you update the ROM, you have to remake this edit.
Also, no idea what MIUI calls its init.rc, you'll just have to see for yourself. If you've got the mount commands in init.rc, fine. Else look elsewhere.
A good first step would to make sure you really are able to flash a new boot.img. Download fastboot and verify your device understands it. Else you have to use some proprietary flash program, and I'm not familiar with Samsungs bootloaders at all. Ask in the Samsung forum if so.
Click to expand...
Click to collapse
Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?. ADB and I do see the file init.rc and I also see the mount commands as well. I used adb shell to run the command you sent over with a few edits for second partition and it does mount but as you said, it all goes away after reboot.
PhantomPhreek said:
Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?. ADB and I do see the file init.rc and I also see the mount commands as well. I used adb shell to run the command you sent over with a few edits for second partition and it does mount but as you said, it all goes away after reboot.
Click to expand...
Click to collapse
Hmm... are you even able to create a second ext3 partition on the SDcard using Windos..?
kuisma said:
Hmm... are you even able to create a second ext3 partition on the SDcard using Windos..?
Click to expand...
Click to collapse
haha, I used CWM to create the partitions initially, but then I used a software called MiniTool, works well. Can I get you to to do it?
PhantomPhreek said:
Alright so here's the deal, my internal SDCARD is corrupted and the /data partition is unusable.
Click to expand...
Click to collapse
The ROM you are using requires an ext4 partition as partition #3 of the SDcard. This is mounted as /data. Repartition your SDcard #1 as FAT, #2 whatever, and #3 as ext4, and everything will work as intended. :victory:
I guess you've missed this in the ROM documentation ...
kuisma said:
The ROM you are using requires an ext4 partition as partition #3 of the SDcard. This is mounted as /data. Repartition your SDcard #1 as FAT, #2 whatever, and #3 as ext4, and everything will work as intended. :victory:
I guess you've missed this in the ROM documentation ...
Click to expand...
Click to collapse
Wah~ really?, I'll try that and get back here with the results. Thanks a lot!.
EDIT: Is it FAT or FAT32?
PhantomPhreek said:
Wah~ really?, I'll try that and get back here with the results. Thanks a lot!.
EDIT: Is it FAT or FAT32?
Click to expand...
Click to collapse
FAT32.
kuisma said:
FAT32.
Click to expand...
Click to collapse
Tried but didn't work out. I made three partitions, all primary - #1 FAT32, #2 FAT32, #3 EXT4. Plugged the SDCARD in and the external memory was detected as usual, but not the internal memory.
I tried changing the time, it was reset back after reboot.
After that I left the SDCARD as is and flashed the ROM again and now, neither the internal nor the external memory are detected. This is probably because the "vold.fstab" which was edited by me, was overwritten on re flashing.
I'm at a dead end, any ideas?
PhantomPhreek said:
Tried but didn't work out. I made three partitions, all primary - #1 FAT32, #2 FAT32, #3 EXT4. Plugged the SDCARD in and the external memory was detected as usual, but not the internal memory.
I tried changing the time, it was reset back after reboot.
After that I left the SDCARD as is and flashed the ROM again and now, neither the internal nor the external memory are detected. This is probably because the "vold.fstab" which was edited by me, was overwritten on re flashing.
I'm at a dead end, any ideas?
Click to expand...
Click to collapse
Attach an output of "df", "mount", the file "/init.latona.rc" and "/etc/vold.fstab" here, and I'll have a look at it. Hmm... include the output of "dmesg" as well, to be on the safe side.
kuisma said:
Attach an output of "df", "mount", the file "/init.latona.rc" and "/etc/vold.fstab" here, and I'll have a look at it. Hmm... include the output of "dmesg" as well, to be on the safe side.
Click to expand...
Click to collapse
What bugs me is the fact that the external SD is not detected, from what little knowledge I have, external SD is unrelated to the internal SD which I currently have problems with, meaning it should be detected without a problem.
Also I have to add, CWM doesn't detect my external SD right away, when I go to recovery and go over to "Choose zip from sdcard" it says "E:Can't mount /sdcard/". The solution I've found coincidentally is to go to "mounts & storage", mount "/emmc", pull the SDCARD out plug it in again and then "mount /sdcard" this works perfectly and I'm able to flash roms from the sdcard.
One problem at a time, please. Attach the files I requsted, so we can determine why /data failes to mount. Looking at your ROM:
Code:
$ grep " /data$" init.latona.rc
mount ext4 /dev/block/mmcblk0p3 /data
I want to know why this fails, and I guess the answer is in the dmesg output. And please before I'll get another whiskey.
kuisma said:
One problem at a time, please. Attach the files I requsted, so we can determine why /data failes to mount. Looking at your ROM:
Code:
$ grep " /data$" init.latona.rc
mount ext4 /dev/block/mmcblk0p3 /data
I want to know why this fails, and I guess the answer is in the dmesg output. And please before I'll get another whiskey.
Click to expand...
Click to collapse
I can't seem to find "/init.latona.rc" everything else you requested I've mailed them over already
EDIT: the dmesg output is AFTER I mounted "/sdcard" manually as explained in my previous post.
PhantomPhreek said:
I can't seem to find "/init.latona.rc" everything else you requested I've mailed them over already
EDIT: the dmesg output is AFTER I mounted "/sdcard" manually as explained in my previous post.
Click to expand...
Click to collapse
The files you mailed me does not correspond to the ROM you refereed.
The /etc/fstab show that /data is mounted as an rfs file system, not ext4. So either format partition #3 on the sdcard as rfs (Samsung proprietary), or edit /etc/fstab and change "rfs" to "ext4". I'd prefer the later, assuming your kernel supports ext4. Else use ext3.
Code:
/dev/block/mmcblk0p3 /data rfs rw
But you can't have flashed the ROM you told me you did. It excepted an ext4 file system ...
When I boot on system, there is a message say that:
Security policy restricts use of external sdcard
Click to expand...
Click to collapse
When I tried to mount sdcard in Recovery mode, it can't mount sdcard. They show this error
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
I: failed to mount ext4/vfat/exfat /dev/block/mmcblk1p1 /sdcard (null)
W: failed to mount /dev/block/mmcblk1p1 /sdcard ext4 (No such file or directory)
E: Can't mount /sdcard/
Click to expand...
Click to collapse
Is my card reader chip on my s2 broken?
Go to Settings/Security/
Device Admins and see if there are any possible restrictions else try wiping cache and dalvik cache (just in case) !
oh i just read it again and i saw you posted EXTERNAL sdcard, haha i thought it was internal sdcard
well do what niku~ said. first go in security and see if there's smth and wipe cache/dalvik.
it happened to some people that flashed a theme to the Rom, and after flashing another theme, the bug disappeared...so if u flashed a theme, try it...
if it doesnt work, try reflashing Rom.
if it doesnt work too, i suggest you do a full wipe and flash another Rom.
this is probably a software issue
it happened to some people that flashed a theme to the Rom, and after flashing another theme, the bug disappeared...
Hallo, guys!
Well, I bought myself Mate 10 Lite. Then I asked Huawei for oem unlock key, became a root/admin of my device. I flashed TWRP 3.1.1-0 (coloured version, not the black/grey) wiped all the Huawei mess, killed all unnecessary mem eaters and I am quite happy with stock firmware. BUT!
For some reason, no custom recovery will save my settings! Any time I access it, it always asks me for making the system writeable, my time zone, my display & vibro settings, etc., all is always reset to some default. I tried different TWRPs, I even fully wiped the rooted phone to factory defaults, formated Dalwik, Data, Cache, even internal SD (did not dare to format the other partitions since I dont know what would that do...). Well, I wiped it, rebooted to TWRP, set all things as I want them and powered off the device. Then powered on into TWRP and again, TWRP is in default... W T F...?
So, how to make the custom recovery to save my settings, please?
Gang-star said:
Hallo, guys!
Well, I bought myself Mate 10 Lite. Then I asked Huawei for oem unlock key, became a root/admin of my device. I flashed TWRP 3.1.1-0 (coloured version, not the black/grey) wiped all the Huawei mess, killed all unnecessary mem eaters and I am quite happy with stock firmware. BUT!
For some reason, no custom recovery will save my settings! Any time I access it, it always asks me for making the system writeable, my time zone, my display & vibro settings, etc., all is always reset to some default. I tried different TWRPs, I even fully wiped the rooted phone to factory defaults, formated Dalwik, Data, Cache, even internal SD (did not dare to format the other partitions since I dont know what would that do...). Well, I wiped it, rebooted to TWRP, set all things as I want them and powered off the device. Then powered on into TWRP and again, TWRP is in default... W T F...?
So, how to make the custom recovery to save my settings, please?
Click to expand...
Click to collapse
It's because TWRP saves settings to internal storage by default, and since you're probably encrypted (and your twrp can't decrypt) it won't save settings.
You can fix it by unpacking your twrp image using Android Image Kitchen, go to the ramdisk/etc/ folder and open recovery.fstab in Notepad ++.
Here you have a few choices.
I used to add settingsstorage to /cache but the downside is that it will remove settings when you clear /cache.
You can add it directly to /data instead, as the root of /data is not encrypted.
So basically you'd change
flags=display="data";backup=1
To
flags=display="data";settingsstorage;backup=1
Or you can add it to /product, /odm, /cust.
Wow! Thanks for advice! I Will surely try that! But I dont think I encryped the phone, I ll check that out and let you know. Thank you anyway! See, I am more Windoez BSODed rather than Linux freed... But I know the kichen and Notepad++ is my default text editorSo I am really thankful for any help. Cheeerzz, man!
Hallo again!
Bellow is all the content of my recovery.fstab:
/boot emmc /dev/block/bootdevice/by-name/boot
/cache ext4 /dev/block/bootdevice/by-name/cache
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust";wipeingui;backup=1
/cust_image emmc /dev/block/bootdevice/by-name/cust flags=display="Cust Image";flashimg=1;backup=1
/data f2fs /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/product ext4 /dev/block/bootdevice/by-name/product flags=display="Product";backup=1
/product_image emmc /dev/block/bootdevice/by-name/product flags=display="Product Image";flashimg=1;backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery
/recovery2 emmc /dev/block/bootdevice/by-name/recovery2 flags=display="Recovery2";backup=1;flashimg=1
/system ext4 /dev/block/bootdevice/by-name/system
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=display="Vendor Image";flashimg=1backup=1
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=display="Vendor";backup=1
/version_image emmc /dev/block/bootdevice/by-name/version flags=display="Version Image";flashimg=1;backup=1
/version ext4 /dev/block/bootdevice/by-name/version flags=display="Version";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable
/usbotg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable;backup=0
And there is no flags by /data. Here is what I did! I extended the line:
"/data f2fs /dev/block/bootdevice/by-name/userdata"
to
"/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="data";settingsstorage;backup=1"
without quotes of course, but that did not work and after flashing the modded recovery and couple changes made in settings and restart, it still goes back to default
2 questions here: A) what if I simply mod the default settings to fit within my needs? B) How and where? Little quick guide would be appreciated ;o)))
A btw., I know my phone is not crypted. It seems like it would only allow to encrypt and external microSD card.
Cheers ;o)))
Hallo again!
Bellow is all the content of my recovery.fstab:
/boot emmc /dev/block/bootdevice/by-name/boot
/cache ext4 /dev/block/bootdevice/by-name/cache
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust";wipeingui;backup=1
/cust_image emmc /dev/block/bootdevice/by-name/cust flags=display="Cust Image";flashimg=1;backup=1
/data f2fs /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/product ext4 /dev/block/bootdevice/by-name/product flags=display="Product";backup=1
/product_image emmc /dev/block/bootdevice/by-name/product flags=display="Product Image";flashimg=1;backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery
/recovery2 emmc /dev/block/bootdevice/by-name/recovery2 flags=display="Recovery2";backup=1;flashimg=1
/system ext4 /dev/block/bootdevice/by-name/system
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=display="Vendor Image";flashimg=1backup=1
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=display="Vendor";backup=1
/version_image emmc /dev/block/bootdevice/by-name/version flags=display="Version Image";flashimg=1;backup=1
/version ext4 /dev/block/bootdevice/by-name/version flags=display="Version";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable
/usbotg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable;backup=0
And there is no flags by /data. Here is what I did! I extended the line:
"/data f2fs /dev/block/bootdevice/by-name/userdata"
to
"/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="data";settingsstorage;backup=1"
without quotes of course, but that did not work and after flashing the modded recovery and couple changes made in settings and restart, it still goes back to default
2 questions here: A) what if I simply mod the default settings to fit within my needs? B) How and where? Little quick guide would be appreciated ;o)))
A btw., I know my phone is not crypted. It seems like it would only allow to encrypt and external microSD card.
Cheers ;o)))
Hello!
I googled that command settingsstorage a bit and it seemed to me like i mistyped it. It shall be "settings storage" not "settingsstorage", it should have contain a space between them 2 words. So I rewrote it, repacked, flashed it... but it did not work either. I am still trying to save the settings on DATA partatition. I will try other partition as well. I let you know.
Bye
Hallo!
Well I am very confused... I left the idea of being able to save the settings for any custom recovery within Android 7.0 and moved forward to Android 8 Oreo, thinking the new Andy will perform better that the old one. I have fully unlocked phone (RNE-L21C432). I was able to flash the oreo-dediacated TWRP then I struggled a bit with Huawei Firmware Finder for Windows and flashing it with the hwOTA tool. For some time, during the flashing, I recognized that the TWRP 3.2.1-0 from Catuva21 hold the settings. But after flashing the firmware files and couple of restarts, the recovery again always started in the default condition.
But what is even worse is the fact that the phone is soo damn slow with the Oreo ROM!! I rooted it with Magisk 16 succesfully, removed a lot of bloatware and services that I do not necessarilly need but still, for example the response for fingerprint unlock is soooo damn slow! It takes about 6-8secs. to unlock and lod the home screen fully. It took about 1-2 secs. in Android 7.0/MIUI5.1. DO NOT UPGRADE TO 8.0!!!
And another strange thing is that even that I downloaded the latest RNE-LE21C432CUSTC432 8.0.0.330 firmware from early June 2018 and flashed it successfully, I still only see 8.0.0.046(0BYF) in my device info tab. I cant even move to 8.0.0.304 that is also downloadable. I followed the guide here https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
and I think if I repete the procedure with the latest files for my phone I should be fine and fully up to date, but no.... I wish I never moved to Oreo...ever!!!
Gang-star said:
Hallo again!
Bellow is all the content of my recovery.fstab:
/boot emmc /dev/block/bootdevice/by-name/boot
/cache ext4 /dev/block/bootdevice/by-name/cache
/cust ext4 /dev/block/bootdevice/by-name/cust flags=display="Cust";wipeingui;backup=1
/cust_image emmc /dev/block/bootdevice/by-name/cust flags=display="Cust Image";flashimg=1;backup=1
/data f2fs /dev/block/bootdevice/by-name/userdata
/misc emmc /dev/block/bootdevice/by-name/misc flags=display="Misc";backup=0
/product ext4 /dev/block/bootdevice/by-name/product flags=display="Product";backup=1
/product_image emmc /dev/block/bootdevice/by-name/product flags=display="Product Image";flashimg=1;backup=1
/recovery emmc /dev/block/bootdevice/by-name/recovery
/recovery2 emmc /dev/block/bootdevice/by-name/recovery2 flags=display="Recovery2";backup=1;flashimg=1
/system ext4 /dev/block/bootdevice/by-name/system
/vendor_image emmc /dev/block/bootdevice/by-name/vendor flags=display="Vendor Image";flashimg=1backup=1
/vendor ext4 /dev/block/bootdevice/by-name/vendor flags=display="Vendor";backup=1
/version_image emmc /dev/block/bootdevice/by-name/version flags=display="Version Image";flashimg=1;backup=1
/version ext4 /dev/block/bootdevice/by-name/version flags=display="Version";backup=1
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable
/usbotg auto /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;removable;backup=0
And there is no flags by /data. Here is what I did! I extended the line:
"/data f2fs /dev/block/bootdevice/by-name/userdata"
to
"/data f2fs /dev/block/bootdevice/by-name/userdata flags=display="data";settingsstorage;backup=1"
without quotes of course, but that did not work and after flashing the modded recovery and couple changes made in settings and restart, it still goes back to default
2 questions here: A) what if I simply mod the default settings to fit within my needs? B) How and where? Little quick guide would be appreciated ;o)))
A btw., I know my phone is not crypted. It seems like it would only allow to encrypt and external microSD card.
Cheers ;o)))
Click to expand...
Click to collapse
Gang-star said:
Hallo!
Well I am very confused... I left the idea of being able to save the settings for any custom recovery within Android 7.0 and moved forward to Android 8 Oreo, thinking the new Andy will perform better that the old one. I have fully unlocked phone (RNE-L21C432). I was able to flash the oreo-dediacated TWRP then I struggled a bit with Huawei Firmware Finder for Windows and flashing it with the hwOTA tool. For some time, during the flashing, I recognized that the TWRP 3.2.1-0 from Catuva21 hold the settings. But after flashing the firmware files and couple of restarts, the recovery again always started in the default condition.
But what is even worse is the fact that the phone is soo damn slow with the Oreo ROM!! I rooted it with Magisk 16 succesfully, removed a lot of bloatware and services that I do not necessarilly need but still, for example the response for fingerprint unlock is soooo damn slow! It takes about 6-8secs. to unlock and lod the home screen fully. It took about 1-2 secs. in Android 7.0/MIUI5.1. DO NOT UPGRADE TO 8.0!!!
And another strange thing is that even that I downloaded the latest RNE-LE21C432CUSTC432 8.0.0.330 firmware from early June 2018 and flashed it successfully, I still only see 8.0.0.046(0BYF) in my device info tab. I cant even move to 8.0.0.304 that is also downloadable. I followed the guide here https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
and I think if I repete the procedure with the latest files for my phone I should be fine and fully up to date, but no.... I wish I never moved to Oreo...ever!!!
Click to expand...
Click to collapse
If you had quoted or mentioned me I would've seen this earlier.
Anyway, "settingsstorage" without a space is correct.
Huawei use fileencryption as default for both Nougat and Oreo so unless you removed encryption it will still be there.
To remove it you would have to edit fstab in boot (Nougat) or /vendor/etc (Oreo), then Format Data in TWRP.
I would suggest adding it to /cache instead if it doesn't want to work.
You should be able to downgrade back to Nougat.
ante0 said:
If you had quoted or mentioned me I would've seen this earlier.
Anyway, "settingsstorage" without a space is correct.
Huawei use fileencryption as default for both Nougat and Oreo so unless you removed encryption it will still be there.
To remove it you would have to edit fstab in boot (Nougat) or /vendor/etc (Oreo), then Format Data in TWRP.
I would suggest adding it to /cache instead if it doesn't want to work.
You should be able to downgrade back to Nougat.
Click to expand...
Click to collapse
Hallo!
Thank you for your time and advise. I am now on a family vacation and I am not going to mess with my phone here. I but I am definitely considered to revert back to Nougat. I already read some articles and guides about how to do that. But first I want to bring all the vacation records home and only then format the storage and revert. I let you know, if you wouldn't mind and eventually ask for help if I get stuck. Thanks again!
Regards, Gang-star