Hi, it's the first time I use TWRP to make a backup of the rom before changing it, the backup was done correctly but I get red errors in the log file.
TWRP 3.3.1 unofficial Zenfone 5 ZE620KL
I start the system backup, selecting everything except the section: "Data (archive excluded) 0MB" (fails if selected), the backup proceeds correctly to the end, but during the backup many words "Unable to mount '/ are printed in the log" given 'invalid argument', even though you have not selected that empty partition. Is this error normal to occur, and above all there is a risk that the backup is not restorable for this error?
I don't know if it's safe to try to format that partition even if it's empty.
Thanks for the tips.
0 MB usually indicates userdata partition is not mounted, therefore one can't create backup. common reason is encryption.
but without recovery.log it's all guesswork, share your logs to get help
IMO the backup cannot have been successful, otherwise you would not have received the numerous error messages.
Questi sono i miei file di registro, con e senza la cartella Data selezionata.
Aggiungo anche che ho i permessi di root, e ho disabilitato qualsiasi tipo di sblocco schermo e pin, esclusa la SIM ma non credo che possa creare problemi alla SIM.
MOD Edit:
These are my log files, with and without the Data folder selected. I also add that I have root permissions, and I have disabled any type of screen and pin unlock, excluding the SIM but I do not think it can create problems for the SIM.
boromyr said:
I have disabled any type of screen and pin unlock
Click to expand...
Click to collapse
this could be the culprit. usually TWRP will ask for pattern to decrypt Data.
maybe set screen lock and try this?
https://blog.alxu.ca/unlocking-large-pattern-encryption-in-twrp.html
But is this partition the internal partition accessible to the user, where photos, music downloads, etc. are located
I'm interested to know if this partition is needed for ROM recovery, because for apps I have backups with Migrate and Titanium Backup, and photos I have in my pc, so if it's not needed for ROM recovery I could also format it to make it accessible, it seems to be the only 100% working way according to the community.
However, in the meantime I switched to OrangeFox as recovery, which supports my device officially and is more up to date.
userdata partition is the only* writeable partition at all, everything else is read-only. that's why it is called ROM (read-only memory)
if you don't care about factory reset, of course you can just format it to remove encryption.
*let's ignore cache misc fota etc for internal use only
So the data partition is not needed to restore Android OS?
Obviously, before formatting it, I will copy my photos and documents to the external memory.
not needed
Thank you.
Related
Hi guys, this is my first post. English is not my native language, so sorry for any mistakes
One week ago i bought a TF300T in UK and now is with me in Spain. The first thing i did was unlocking the device and testing the CM9 rom. I restored the system and with the stock rom the device is not stable (random freezes and reboots).
Triying to get back to factory settings (to stop the reboots), i deleted the whole sd-card (internal memory) and the '/system' folder (don't know why i did it >_<).
Now, the tablet don't start. The screen show the Asus logo and the "Device is unlocked" message. I can access to the recovery (and i can change it) and to the "fastboot" mode, but the recovery can't mount the sd-card via USB, so i can't flash a new room.
I've tried to load a "system.img" via fastboot, but is useless, /system folder is still empty. To do this i've used the "mkyaffs2image" to create a system.img from an old clockworkmod backup.
In conclussion, i have this:
- Deleted /system partition
- Empty sd-card partition
- Full-functional recovery (clockworkmod and team win recovery project).
- Full-functional fastboot mode
- No access to internal memory (can't copy a new rom to internal memory)
I've been trying to create a valid system.img, but i don't how to (i've been reading about a linux tool called "mkfs.yaffs2" but the tutorial that i found seems to be useless, the tablet i still "bricked").
Can anybody help me?
Thank you
Removed see below post to push the files onto SD card
Another thing you can try is the bottom of my post:
http://forum.xda-developers.com/showthread.php?t=1680570
do you have an SD card reader or a smartphone with SDCARD slot?
with that you can send the files to the sdcard and then try to flash the ROM in recovery.
btw por que borras /SYSTEM
yo aun no agarro valor para hacer el Unlock
gierso said:
do you have an SD card reader or a smartphone with SDCARD slot?
with that you can send the files to the sdcard and then try to flash the ROM in recovery.
btw por que borras /SYSTEM
yo aun no agarro valor para hacer el Unlock
Click to expand...
Click to collapse
My thread above should work as it will allow him to push a new stock rom or CM9 onto the device to flash again.
Northern-Loop said:
Another thing you can try is the bottom of my post:
http://forum.xda-developers.com/showthread.php?t=1680570
Click to expand...
Click to collapse
I LOVE YOU.
I thought that the adb was only "usable" with the OS. I've copied the original 9.4.3.29 firmware and the green little droid is smiling me now :')
Thank you very much ^^
gierso said:
do you have an SD card reader or a smartphone with SDCARD slot?
with that you can send the files to the sdcard and then try to flash the ROM in recovery.
btw por que borras /SYSTEM
yo aun no agarro valor para hacer el Unlock
Click to expand...
Click to collapse
The problem is that the TF300 recovery can't access to the external SD card reader. The sdcard partition is the internal memory.
Lo de borrar system es para pegarme con un calcetín sucio, lo sé
KPY said:
I LOVE YOU.
I thought that the adb was only "usable" with the OS. I've copied the original 9.4.3.29 firmware and the green little droid is smiling me now :')
Thank you very much ^^
Click to expand...
Click to collapse
No problem, glad I found a solution for it.
If you have put the stock ROM on there you will loose Recovery and ROOT but its easy enough to put them back.
I'm trying different rom options, this thing reboots itself too frecuently
KPY said:
I'm trying different rom options, this thing reboots itself too frecuently
Click to expand...
Click to collapse
The Custom ROMs are still very early so if you are new to flashing I'd stick with the Stock one until the custom ones get a bit easier to restore.
The problem is that i have the reboots with the stock rom, that's why i'm testing everything
KPY said:
The problem is that i have the reboots with the stock rom, that's why i'm testing everything
Click to expand...
Click to collapse
It shouldn't reboot on stock ROM. I would say you have a faulty unit, though if you have unlocked it you might not be able to get it swapped out.
Flash the Stock ROM and DON'T Root it or flash recovery, if it still reboots its faulty.
If it doesnt reboot when its unrooted and only reboots when its rooted you have a dodgy app on there causing it
Hello ; in TWRP 3.1.0.0 when I make a backup, everything can be saved except the data which after 35% stops with error 255. So there is something that blocks. How can I know what to remove and / or replace and / or repair this item .
I have a Mate 9 AL29-C636-B188
thanks for the help
CouCouFR34 said:
Hello ; in TWRP 3.1.0.0 when I make a backup, everything can be saved except the data which after 35% stops with error 255. So there is something that blocks. How can I know what to remove and / or replace and / or repair this item .
I have a Mate 9 AL29-C636-B188
thanks for the help
Click to expand...
Click to collapse
Check if you're encrypted, use TWRPs file manager and go to internal SD card and see if it looks OK.
If it has weird folders, you are encrypted and backup will be impossible. To decrypt you would have to Format Data in TWRP (will remove everything in /data including internal SD card), then use a modified boot image which removed encryption (SuperSU 2.82SR3+ And Magisk before 14 does this automatically, or modify it manually).
Then download hw data and public data for C636B188 from http://pro-teammt.ru/firmware-database/ and flash in TWRP (public first) . After that you can backup.
Hi Ante0
I'm not encrypted
On the SD card, everything looks OK, no weird folder visible on the finder or even by Total Commander.
If I format everything & delete the recovery images, how do I restore?
I have an offline fimware C636B181 with UPDATE.APP and UPDATE_MHA_L29_HW_SPCSEAS.APP but is not it just updates?
Otherwise, is it possible to replace this data backup with that of another identical device (same OEM, same system ...) ?
CouCouFR34 said:
Hi Ante0
I'm not encrypted
On the SD card, everything looks OK, no weird folder visible on the finder or even by Total Commander.
If I format everything & delete the recovery images, how do I restore?
I have an offline fimware C636B181 with UPDATE.APP and UPDATE_MHA_L29_HW_SPCSEAS.APP but is not it just updates?
Otherwise, is it possible to replace this data backup with that of another identical device (same OEM, same system ...) ?
Click to expand...
Click to collapse
You need to check if you're encrypted when you're in TWRP. If you already booted you'll be decrypted as it decrypts when you input pin.
To check in TWRP, use Advanced - File manager, then browse to /sdcard and see what it says. Alternatively you can check /data/app/, it should produce the same result.
Indeed, I think you're right :good: and I'm encrypted : / data / data only contains type files with names like 5uE + 5Le6p, Zs54sDTy0DB ... and the same ones in / sdcard ...
With Magisk, can we blow up this encryption without reformatting ?
Why was this data encrypted, nothing was asked of me ?
CouCouFR34 said:
Indeed, I think you're right :good: and I'm encrypted : / data / data only contains type files with names like 5uE + 5Le6p, Zs54sDTy0DB ... and the same ones in / sdcard ...
With Magisk, can we blow up this encryption without reformatting ?
Why was this data encrypted, nothing was asked of me ?
Click to expand...
Click to collapse
No, you have to Format Data. And as of Magisk 14.3 it doesn't remove encryption by default when you install Magisk. You'll have to either pull Magisk's github and build it but with "fileencryptioninline" added again, or unpack your boot image using Android Image Kitchen and change fileencryptioninline to encryptable in hi3660.fstab.
Encryption is turned on by default by Huawei.
Here is the commit: https://github.com/topjohnwu/Magisk/commit/ffa005e4abf71a0c1a14a8cfe8355a18d1f16616
Hello Ante0
Thank you for all this info but I did not understand everything (I just went from iPhone to Android, I'm not disappointed ... ) :
- in TWRP format his phone in full, internal memory and SD card = no problem
- werre can i find a modified boot image without encryption ? Create it through Magisk ?
- then by TWRP reinstall version C188 for C636: update.zip, update_data_full_public.zip then update_full_MHA-L29_hw_spcseas.zip
Hi
Found the solution, to make a backup of datas without error 255, following the information of Ante0 :good: : during the installation or re-installation or update by TWRP : just after the update, before rebooting, make the backup ( we are before the encryption of datas) ; I am trying to find the solution to make this backup later, thanks to Magisk
How I unbricked "Decryption unsuccessful" The password is correct but... (Apps2SD)
Hello, I don't usually post in tech forums, I usually the guy that only reads,
but this is the time when i could not find the straight answer to my problem and had to google the solution out of similar posts, so I decided to glue everything together and write my solution to this particular situation,
so I might save a lot of time to someone who got in exact or similar situation.
Sorry for my crappy English, but here we go.
What this post trying to solve:
You stuck at boot loop: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
and how to make it work Apps2SD with Huawei P9 SD card with enabled password protection.
Basically my Huawei P9 (EVA L-19) with Android 7.0 Nougat got running out of internal space, and i am really a heavy user on apps. Kirin 955 handles just fine as long as it has at least 10Gb of internal free space.
I have SD card 64Gb, but huawei stopped support, native move apps to SD, long time ago. My device is rooted, so I was searching for a solution. There is few apps that can transfer your internal memory apps to SD by using root, but the one that actually worked for me is Apps2SD. The thing is, my SD card is password protected (Huawei native function) I want to keep this function in case of device getting stolen.
Problem is, many third party apps that move your apps to SD, does not know anything about Huaweis SD card password feature. In fact (as far as i tested) only Huawei phone allows you to enter password and show contents of SD card, no PC, or for example Samsung phone will recognize this SD card.
So i was messing with Apps2SD, partitioned my SD card in to 2 primary partitions, 1- exfat, 2- Ext3. It works kinda fine, but after reboot, there is delay, Huawei unlocks SD card after main boot part, and Apps2SD does not understand this and show that it failed to mount second partition.
In this case, Apps2SD starts giving you solutions, one of them is this ADVANCED mounting option. It does not tells u about any dangers, nothing really.
I chose that option to see if it will be able to see second partition contents faster, rebooted - boom bricked.
You see the message: "Decryption unsuccessful" and asks you for decryption password. It might be SD card password, not sure, it does not matter, because you can type ANYTHING and it always say:
"The password that you entered is correct but unfortunately your data is corrupt". And gives you only option: fully data factory reset. Now hold your horses, dont press that. I just knew that this is bull**** and no way
my personal data is corrupted, its just some hadshake issue. (I was right i fully recovered everything up n running)
Assuming you got in this mess, your device must be rooted and you probably have TWRP recovery, cause Apps2SD work only with rooted devices.
To recover from "Decryption unsuccessful" boot message and restore all data and settings:
Got to TWRP recovery by holding power button and volume UP (after phone vibrates, hold both buttons 2sec more and then release power button, and then after 2sec more release volume up, cause if
you do this too fast, u will end up in wifi recovery by Huawei, and it wont work anyway cause your device rooted).
Then go to advanced and file manager, locate sdcard folder (this will be internal memory, not external), you should be able to see all of your personal files! Copy them to flash drive by connecting with OTG.
What we gonna do now is: do a full nandroid backup: TWRP, backup, check: BOOT, SYSTEM, DATA. and do a backup to flash drive connected with OTG or hard drive if it works for u.
After backup is done, go to WIPE, select format data, select DATA partition and see what original file system it uses. Now format in any other system, then reformat again to your original file system.
DATA partition somehow lost its encryption handshake key and this caused the problem, reformatting fixes it.
Now do a full wipe as if you would install new rom, wipe: system, data, storage, cache, dalvic cache.
Restore your previous nandroid backup, reboot to system,now your phone should boot with all the apps and settings just as you left.
You might be missing some pictures and other media in main storage, just connect your P9 with usb cable to pc, and restore previously backed up media from flash drive manually in pc interface (copy paste, replace all),
some small minority files might wont copy, don't worry about it, Im not sure but they are mostly indexing files, all ur media will be back in place.
Now, how to make Apps2SD work with this configuration?
Don't use that advanced method to find SD cards second partition, use any of first 3, the 3rd one worked for me just fine, cause its SU library based one.
Don't move your apps fully to SD, or they will "disappear", move everything except APK, ODEX, DEX (Lib is optional, you usually can move this one just fine). SO basically app core will stay in main storage but cache and app data will be on second SD card. This way, after you reboot your phone, you will have to wait like 3mins and App2SD will link your files to apps itself just fine. It might will show some errors right after reboot, but after Huawei unlocks its card, files will be linked, and apps wont be "gone" cause app core still stays in main storage.
This way i managed to save a lot of space and move most of app storage to SD card, P9 became very responsive, even in 2018 this is a really fast smartphone.
Sorry for a messy post, I'm not a writer, but I hope this helps to someone!
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
So glad this helped someone
dalektehgreat said:
Thanks a lot, you saved my phone-config! ) This step "...and see what original file system it uses. Now format in any other system, then reformat again to your original file system." was unclear to me, as TWRP didn't give me the option to choose a file system, but in the end it worked out fine without just as well.
Click to expand...
Click to collapse
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
zgfg said:
How did you run into this issue?
If it was due to updating Magisk to v19.x (on Huawei with Nougat / EMUI 5)?
In that case, there is an easier solution, just flash back Boot img with Magisk v18 1 and everything will continue to work as it did (without any need to reformat, factory reset, etc), see
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post79493919
Click to expand...
Click to collapse
I'm not entirely sure what caused it, but I suspect Apps2SD just like in the original post (I installed/tried to use it shortly before the problem occured).
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.
twrp recovery showing 0 files in internal storage and showing some random file names I am unable to do anything please help how to fix it
KARTHIKMC007 said:
twrp recovery showing 0 files in internal storage and showing some random file names I am unable to do anything please help how to fix it
Click to expand...
Click to collapse
If you're using a relatively new phone (shipped with android 9.0 or later versions), you most likely have an encrypted data partition. This kind of encryption is relatively new and is called FBE (File Based Encryption), where every file and folder are encrypted separately. (those random file names!)
To access your data partition through twrp, you need to input your lock screen (or boot-up pin) credentials when prompted at the beginning, if you don't receive such a warning at twrp startup, then your custom recovery image may simply not support decrypting storage. In that case use another one .
Slim K said:
If you're using a relatively new phone (shipped with android 9.0 or later versions), you most likely have an encrypted data partition. This kind of encryption is relatively new and is called FBE (File Based Encryption), where every file and folder are encrypted separately. (those random file names!)
To access your data partition through twrp, you need to input your lock screen (or boot-up pin) credentials when prompted at the beginning, if you don't receive such a warning at twrp startup, then your custom recovery image may simply not support decrypting storage. In that case use another one .
Click to expand...
Click to collapse
thank you
but I have flashed orange fox recovery and twrp latest in both it is showing the same random file names