Database Users

Save internal storage from i9505 software brick/stuck on bootlogo

Hello,
since one week my device, a samsung galaxy s4 i9505, is software bricked and stuck on bootlogo and I've been tryin to save my internal storage, but I'm close to giving up. I hope someone here can help me.
My situation:
1. Updated my TWRP to version 3.0.1-0-jfltexx with odin 3.10.0
2. Flashed new ROM "OMEGA ROM", that worked good.
3. Backup with TWRP, successfull, reboot, galaxy logo appears, flash, again -> bootloop
4. Flashed firmware "i9505XXUHOB8" BL and modem, with odin 3.10.0 in BL and CP
5. No bootloop anymore, but stuck on ROM Logo with normal start and with recovery start blue text "recovery booting..." on galaxy screen but nothing happens.
6. Saw that TWRP 2.8.7.0-i9500 is the recommended TWRP for the i9505, flashed the .img.tar with odin 3.09 in AP (is the .img a problem?) but still same problem, with TWRP 2.8.6.0-i9500.tar too.
6. Tried different firmwares: i9505XXUHOB7, i9505XXUHOF2, i9505XXUHOJ4 -> I thought the problem is the bootloader -> odin error: complete (write) operation failed or NAND write error (->problem was usb port)
7. Tried different odin versions: 1.85, 3.10.6, 3.09
8. Tried different usb cables
9. Flashed cf-auto-root to mount the data partition, but theres no option. Recovery mode is now working, but the samsung recovery, not TWRP.
10. Tried to copy internal storage with ADB, can navigate the directory but can't pull or cd /storage/sdcard0 -> no such file or directory, same with /mnt/sdcard (ADB only works during the ROM logo)
11. Flashed stock samsung firmware "i9505XXUHOJ2_i9505AUTHXXUHOJ1_i9505XXUHOJ2" with odin 3.09 -> now stuck on samsung boot logo. My ROM is now deleted, right?
12. Wipe cache don't help
13. Could wipe data/factory reset or repartition with odin but then I will lost my internal storage.....
I have a backup from the successfull backup with TWRP, but can't open the data.ext4.win001 after rename it (the .win000 is ok)....
Can anyone help me or have an idea how can I save my data and repair the system?
-Mr.Tea

use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.

3mel said:
use TWRP to copy files from internal storage over to external SDcard for stuff you wanna keep.
if you manage to backup the data partition you're supposed to be able to extract apps and data from a nandroid with titanium backup pro (never tried it though).
this data you wanna save, if it wasn't created while running omega rom then it wasn't likely to work with it anyway. that could be the source of your bootloops. if that data came from a previous custom rom then try to go back to it, and if successful backup apps with titanium and files to SDcard. you can't keep your data partition and go into a new rom with it.
if the data came from a stock rom you'll loose it trying to go back so extracting from a nandroid is probably your best bet there or restoring once back to stock.
Click to expand...
Click to collapse
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.

Mr.Tea said:
TWRP is not working anymore -> blue text "Recovery booting..." on galaxy logo
In many forums they mean TWRP backup not includes the internal storage (/sdcard partition)?!
Can extract my "data.ext4.win000" and "data.ext4.win001" but not find the /sdcard location or my userdata.
Click to expand...
Click to collapse
try TWRP 3.0.0 by JDCteam, hundreds of happy users there. if it works first time make sure to try backing up your data partition and then wiping it. you can copy your media storage with the built-in file browser as mentioned.
you've got bigger problems if it's not data causing your problems...

Not possible to do a complete backup under Recovery TWRP

Hello everyone.
I am new owner of an S7 Edge and so I root it is ok!
I have installed a recovery version 3.0.2.4 this is ok too but I have a concern to make a full backup.
1 - When starting recovery I have a screen that says "Installing zips or operations via adb may change the system partition".
2 - When I want to do a backup I have these 03 options that are checked.
Booting
System
Data
But when I drag to make this backup I have error messages
Here are the images to better understand.
I think I have forgotten something, could you orient me please?
Thank you for your help.

encrypted data...... so if you want do a backup try out flashfire......

Working fine with flashfire !!
But there is still the solution of real recovery?
How to decrypt the data?
To make a backup?
Thanx !

1. Reboot to TWRP, Wipe > Format Data > Type 'yes'. This will wipe all the data on your phone including internal storage.
2. Don't reboot, and flash either SuperSU or one of the zips from here (latest version would be preferred). Since you have to wipe your internal storage in the previous step, put the zip in your external sdcard beforehand or flash it through adb sideload if you know how to.
Be careful when flashing stock firmware with odin, as it will automatically encrypt your device again. After you flash stock firmware, reboot directly into download mode again, flash TWRP, reboot to TWRP, and then follow step 2.

Hi !
I will download a stock rom in case of problem and I come back to give the results.
Big thanks !!! :good: :good:

kykint said:
1. Reboot to TWRP, Wipe > Format Data > Type 'yes'. This will wipe all the data on your phone including internal storage.
2. Don't reboot, and flash either SuperSU or one of the zips from here (latest version would be preferred). Since you have to wipe your internal storage in the previous step, put the zip in your external sdcard beforehand or flash it through adb sideload if you know how to.
Be careful when flashing stock firmware with odin, as it will automatically encrypt your device again. After you flash stock firmware, reboot directly into download mode again, flash TWRP, reboot to TWRP, and then follow step 2.
Click to expand...
Click to collapse
Work perfectely very very good !
Thanks for answers !!

Instructions

Hey there great people out there!
Can somebody provide me the correct instructions for installing any Oreo ROM? It's not that I am lazy to search, believe me I have tried But problems came like Internal storage is not showing up on twrp(encrypted).Thanks a lot!BTW I'm on marshmallow right now,so please provide on how to update from marshmallow ?

Tech x 125 said:
Hey there great people out there!
Can somebody provide me the correct instructions for installing any Oreo ROM? It's not that I am lazy to search, believe me I have tried But problems came like Internal storage is not showing up on twrp(encrypted).Thanks a lot!BTW I'm on marshmallow right now,so please provide on how to update from marshmallow ?
Click to expand...
Click to collapse
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that case.

Lol I will not brick my device.I can get back to marshmallow anytime!The only problem I was having before was the device wouldn't show anything(0mb) on internal storage on booting in the ROM.Is this normal.Maybe the ROM is encrypted.On nougat this is not happening on any ROM.Currently Iam on nougat(stock).It shows internal storage only after formatting data but reinstalling the ROM and booting again in recovery it shows 0mb on internal storage.

Tech x 125 said:
sk.vyshak said:
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that caseencryptedThanks Man!
Lol I will not brick my device.I can get back to marshmallow anytime!The only problem I was having before was the device wouldn't show anything(0mb) on internal storage on booting in the ROM.Is this normal.Maybe the ROM is encrypted.On nougat this is not happening on any ROM.Currently Iam on nougat(stock).It shows internal storage only after formatting data but reinstalling the ROM and booting again in recovery it shows 0mb on internal storage.
Click to expand...
Click to collapse
Reinstalling the rom means it is again getting encrypted. By default encryption is on in stock rom. So you have to format data to break encryption. Otherwise you cant access internal storage. You need latest firmware (nov security patch) for oreo roms.
Click to expand...
Click to collapse

thanks
sk.vyshak said:
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that case.
Click to expand...
Click to collapse
thanks

Decrypt stock Moto ROMs ?

Can Moto Stock 8.1 ROM be decrypted ? I have tried no-verity-opt-encrypt-6.1.zip and formating the data partition using TWRP. AFter the phone reboots, the phone reports its still encrypted. Thanks,

Nivead said:
Can Moto Stock 8.1 ROM be decrypted ? I have tried no-verity-opt-encrypt-6.1.zip and formating the data partition using TWRP. AFter the phone reboots, the phone reports its still encrypted. Thanks,
Click to expand...
Click to collapse
It absolutely can and you seem to have done the right things, maybe in the wrong order.
Check this post:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
And more information:
https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption
Normally the way should be:
Boot into TWRP
Format (not just wipe) data
Flash magisk (see "and more information" above)
Flash Disable_Dm-Verity_ForceEncrypt.zip
I had flashes where I had to repeat the steps but actually I'm rooted and decrypted on stock 8.1
Sent from my Moto G5 Plus using XDA Labs

Procedure I used;
Boot into recovery mode
In TWRP goto WIPE then FORMAT DATA, yes, then Back, then back navigation arrow, then back navigation arrow, then INSTALL, select storage, select micro SD card, ok, tap Magisk.zip, then tap Add More Zips, tap no-verity...zip, then Swipe to confirm flash, (no errors on installs), then REBOOT SYSTEM.
Phone reboots, set up google stuff, then to SETINGS, SECURITY & LOCATION, ENCRYPTION & CREDENTIALS, and phone shows its encrpyted.
I have tried different combos, followed the guides posted, maybe I missed something ?
Thanks for your help.

Nivead said:
Procedure I used;
Boot into recovery mode
In TWRP goto WIPE then FORMAT DATA, yes, then Back, then back navigation arrow, then back navigation arrow, then INSTALL, select storage, select micro SD card, ok, tap Magisk.zip, then tap Add More Zips, tap no-verity...zip, then Swipe to confirm flash, (no errors on installs), then REBOOT SYSTEM.
Phone reboots, set up google stuff, then to SETINGS, SECURITY & LOCATION, ENCRYPTION & CREDENTIALS, and phone shows its encrpyted.
I have tried different combos, followed the guides posted, maybe I missed something ?
Thanks for your help.
Click to expand...
Click to collapse
I'm not sure but it sounds as if you flash magisk and no-verity in one task. If so I wouldn't do that, maybe a reboot between the both files could be helpful.
You could also try the following (see also https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption ):
Run the following command in your recovery's terminal before installing magisk.zip:
Code:
echo KEEPFORCEENCRYPT=false>>/cache/.magisk
Magisk should set the force encryption flag to false then.
I don't know which disable....zip you're using, I had always success with this one: Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
And as I wrote above I (and other users too) had to repeat the whole process from formatting data on to get it stick.
Sent from my Moto G5 Plus using XDA Labs

Bingo. This what finally worked:
""Run the following command in your recovery's terminal before installing magisk.zip:""
""
Code:
echo KEEPFORCEENCRYPT=false>>/cache/.magisk
Magisk should set the force encryption flag to false then.""
reboot
""I don't know which disable....zip you're using, I had always success with this one: Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw""
-used yours-
reboot
then format data under TWRP wipe
reboot - and then settings - and under encryption - phone ask if I want to encrypt it, instead of being encrypted by default.
I learned a couple of things tonight. I found if you set "secure start up" on the google start/setup, TWRP was asking for PIN and it did not work to the PIN I had entered - the errors were "unable to Mount Storage and Failed to Decrypt Data".
Thank you very much !! I appreciate your patience - I am 64 years old, was a Linux administrator 35 years back for a few years and then was promoted up, and did not have time to keep the skills up to par. I know enough to be dangerous. I forgot that android was forked from Linux and when I realized it...here I am playing with the phone !!

Nivead said:
Bingo. This what finally worked:
""Run the following command in your recovery's terminal before installing magisk.zip:""
""
Magisk should set the force encryption flag to false then.""
reboot
""I don't know which disable....zip you're using, I had always success with this one: Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw""
-used yours-
reboot
then format data under TWRP wipe
reboot - and then settings - and under encryption - phone ask if I want to encrypt it, instead of being encrypted by default.
I learned a couple of things tonight. I found if you set "secure start up" on the google start/setup, TWRP was asking for PIN and it did not work to the PIN I had entered - the errors were "unable to Mount Storage and Failed to Decrypt Data".
Thank you very much !! I appreciate your patience - I am 64 years old, was a Linux administrator 35 years back for a few years and then was promoted up, and did not have time to keep the skills up to par. I know enough to be dangerous. I forgot that android was forked from Linux and when I realized it...here I am playing with the phone !!
Click to expand...
Click to collapse
You're welcome. Glad that I could help you to make everything work as you want. We oldies have stick together.
Sent from my Moto G5 Plus using XDA Labs

I found a procedure that works everytime. Fastbooted the potter 8.1/op28.85-17-6-2 flashes so the phone would be clean. Reboot then set up google/phone.
Then Fastboot Flash mode and pushed in TWRP to recovery. Then switched to recovery, then in TWRP went to wipe then format data. Then to install and installed magisk. Then reboot system.
Then setup google/phone and confirmed magisk is on the phone.
Then reboot to recovery mode. In TWRP goto wipe, then format data. Then to install, install Disable_Dm-Verity_ForceEncrypt_02.04.2018.zip Reboot system
Then setup google/phone. Noted No Encryption, and Magisk gone. Reboot to recovery and in TWRP install Magisk. Reboot and all is well.
(did the whole procedure three times to make sure all results were repeatable)(and did not need the TWRP terminal commands) (sure is a pain in the rear setting up the phone everytime its reset).

32g SM-T510 showing 16gb of usable space after patching AP with Magisk

I recently reflashed my sm-t510 with the latest stock rom (1/2021 BTU release) and followed the Magisk instructions to root it (patch AP and reflash with Odin). Upon rebooting into Magisk, the tablet shows 16gb of storage instead of the 32gb installed. I have tried this process twice and reached the same result.
Could I fix this in TWRP while keeping my root status or could I use something like parted or gdisk to manually fix it over adb?

I did something similar and I'm sitting at 1.8 GB of total hard drive space down from 32 GB.

Ah, I saw your thread but wasn't sure if our issues were similar so I created a new thread.
I am going to attempt to flash Magendanz's TWRP recovery to my tablet today. I think that will remove my Magisk-rooted system, so I may have to do some more fiddling.

So flashing TWRP to AP with Odin will repair the partition size.
Under the "Wipe" > "Advanced Wipe" option select "Data" and and tap "Resize." Worked without a hitch on my tablet; rebooted and settings showed the full 32gb.
It did remove the Magisk root (because TWRP replaced the Magisk-patched recovery) but it turned out that was easy to flash from TWRP:
- Boot to TWRP
- Format data
- Install Multidisabler
- Format data again just to be safe
- Reboot tablet, go back into TWRP
- Flash Magisk.zip
- Profit