Database Info

[Q] TWRP cannot read my sdcard (encrypted?)

So, my previous post was a bit too optimistic. I've managed to get TWRP onto my phone, but when I went to actually load a custom ROM into it, I found that it couldn't read anything from my sdcard.
I'm having what appears to be a common problem: when I boot into Recovery, TWRP asks for a password. When I cannot provide it (because I have no idea what it is), TWRP is unable to access the data partition. Apparently, the partition is encrypted and I have no way to de-crypt it.
I've found dozens of other posts by users having this problem and the solution everyone is giving is to fully wipe the data partition and start over. But I *can't* wipe the data partition, because TWRP can't access it and fails almost immediately. I have tried a multitude of options, including:
* Installing old versions of TWRP - same behavior; asks for a password, fails to wipe/format the data partition.
* Installing ClockWork's recovery - same thing; fails to format/wipe the data partition
* Flashing back to stock recovery, using that to format my data partition; this worked fine but as soon as I put TWRP back, the problem came back.
On my last attempt, I used the stock recovery to completely wipe the data partition, and made absolutely sure that it never booted into anything but Download or Recovery modes after that. I was hoping that would prevent the stock software from ever re-encrypting the data, but somehow, when I booted TWRP, it still can't read my partitions. Note that my phone itself is not "encrypted" as far as the Settings application is concerned, but apparently Android is doing something behind the scenes anyway. There doesn't seem to be any option in the stock settings to turn off this encryption.
Is there any hope for getting a custom ROM onto this phone?
Thanks for the help!

Any solution? I'm running into the same issue where TWRP is asking for a password.

SGH-T769 (SGS Blaze 4G) Bricked? Can still access CWM Recovery!

So I believe I've bricked my SGH-T769, at least, whenever I attempt to turn it on, I am greeted with the standard Samsung splash-screen and can never proceed past it. I can still boot into recovery mode and i wanted to know if I could use the "restore from sdcard01" option to fix this. I have a removable SDCard and the ability to add files to it via- cardreader. Can I even get system restore files?
P.S. I cleared EVERYTHING... not JUST the harddrive, dalvik, and caches, i mean... i cleared EVERYTHING which was obviously a mistake because that's when the problems came. I believe I may have actually cleared the system files themselves...
:silly:
Oddly enough, CWM Recovery is still alive and well, but I cannot access DOWNLOAD MODE
(I KNOW HOW TO ACCESS DOWNLOAD MODE BUT IT IS JUST BROKEN WITH THIS PHONE)

Hello,
Yes, if you made a nandroid backup in recovery then restoring that nandroid should fix you.
To better assist you, your thread will be moved to your device forum linked below.
http://forum.xda-developers.com/blaze-4g/general
The experts there may be able to help you with any other questions you have. Good luck.

digfive3 said:
So I believe I've bricked my SGH-T769, at least, whenever I attempt to turn it on, I am greeted with the standard Samsung splash-screen and can never proceed past it. I can still boot into recovery mode and i wanted to know if I could use the "restore from sdcard01" option to fix this. I have a removable SDCard and the ability to add files to it via- cardreader. Can I even get system restore files?
P.S. I cleared EVERYTHING... not JUST the harddrive, dalvik, and caches, i mean... i cleared EVERYTHING which was obviously a mistake because that's when the problems came. I believe I may have actually cleared the system files themselves...
:silly:
Oddly enough, CWM Recovery is still alive and well, but I cannot access DOWNLOAD MODE
(I KNOW HOW TO ACCESS DOWNLOAD MODE BUT IT IS JUST BROKEN WITH THIS PHONE)
Click to expand...
Click to collapse
No, you are not bricked. If you are able to access recovery, think of it as a second chance . Since you have recovery available, have you tried transferring a ROM to it? If that is what you were aiming for, I recommend transferring TWRP onto it, flashing it, reboot to recovery, and proceed to flashing a ROM.

xWolf13 said:
No, you are not bricked. If you are able to access recovery, think of it as a second chance . Since you have recovery available, have you tried transferring a ROM to it? If that is what you were aiming for, I recommend transferring TWRP onto it, flashing it, reboot to recovery, and proceed to flashing a ROM.
Click to expand...
Click to collapse
Can I just use an SD card to do that or will I need to find a way to get into download mode?

digfive3 said:
Can I just use an SD card to do that or will I need to find a way to get into download mode?
Click to expand...
Click to collapse
That works also.

digfive3 said:
Can I just use an SD card to do that or will I need to find a way to get into download mode?
Click to expand...
Click to collapse
Yes, download your ROM and Gapps package, place the zips on your external sdcard, boot to recovery, flash the ROM zip then flash the Gapps zip, do the wipes(factory reset, wipe cache, wipe dalvik cache), reboot.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
Yes, download your ROM and Gapps package, place the zips on your external sdcard, boot to recovery, flash the ROM zip then flash the Gapps zip, do the wipes(factory reset, wipe cache, wipe dalvik cache), reboot.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Could you link me to a rom for my device? I'm having a hard time finding an actual ZIP file, just a bunch of .IMG files.

digfive3 said:
Could you link me to a rom for my device? I'm having a hard time finding an actual ZIP file, just a bunch of .IMG files.
Click to expand...
Click to collapse
Do a Google search for "custom ROMs for SGH-T769" that should give some results if anything exists.
Sent from my SCH-I535 using Tapatalk

digfive3 said:
So I believe I've bricked my SGH-T769, at least, whenever I attempt to turn it on, I am greeted with the standard Samsung splash-screen and can never proceed past it. I can still boot into recovery mode and i wanted to know if I could use the "restore from sdcard01" option to fix this. I have a removable SDCard and the ability to add files to it via- cardreader. Can I even get system restore files?
P.S. I cleared EVERYTHING... not JUST the harddrive, dalvik, and caches, i mean... i cleared EVERYTHING which was obviously a mistake because that's when the problems came. I believe I may have actually cleared the system files themselves...
:silly:
Oddly enough, CWM Recovery is still alive and well, but I cannot access DOWNLOAD MODE
(I KNOW HOW TO ACCESS DOWNLOAD MODE BUT IT IS JUST BROKEN WITH THIS PHONE)
Click to expand...
Click to collapse
By the way, there is a device called a USB jig that is used to force a device into download mode, you can get one for $4-5 on eBay or you can make your own by cutting the end off of an old micro USB cord and using a 300k resistor(or any combination of resistors that equal but do not exceed 300k), there are videos on YouTube that show how to do that. That should boot you to download mode so you can restore the device to stock.
Sent from my SCH-I535 using Tapatalk

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.

[Q] Stuck on boot loop and cannot flash other ROM

Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance

Try to delete everything in data manually through twrp file manager (Advanced->File Manager)

john99ap said:
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
Click to expand...
Click to collapse
Im using CWM recovery T.T

iqbaladeee said:
Im using CWM recovery T.T
Click to expand...
Click to collapse
Then, install the latest common twrp by Andi from here: http://andi34.github.io/recoveries_tab2.html
and try it (first try also to wipe data with twrp)

iqbaladeee said:
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Click to expand...
Click to collapse
I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a rebootFormating the storage doesn’t work (after reboot the old rom and apps are back)You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.
source: http://andi34.github.io/faq.html

Unsuccessful decryption

Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?

Factory reset but your data will be gone.

Random Pinenut Joy said:
Okay, I'm not sure if this entirely the right place. Have updated to Viper 2.1.0. Rebooted my phone, as I do each morning. It came up with needing to to enter a decryption key, ie; my password. Did said & it failed saying that data is corrupt. TWRP can no longer read the data portion either. Therefore can't wipe it in TWRP.
Is there a way to format or wipe the data partition through either fastboot or adb?
Click to expand...
Click to collapse
Try this, Venom helped with it a while ago and it worked, you will just have to re activate smart lock in google setting.
TWRP-Advanced-File Browser.
Navigate to /data/system and delete the locksettings.db.

I got my phone back from HTC after repair my phone screen and they wiped my custom rom and recovery but still have unlocked bootloader and restore oreo 8.0.
I managed to re-install twrp and tried to install a customed rom and experienced the same "decryption unsuccessful". But there is no lockingsettiings.db in the folder.
I will later try this method and report.... been a frustrating day....
=https://forum.xda-developers.com/showpost.php?p=59685278&postcount=3