Can't undo encryption? :( - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

CWM can not mount /data, and thus can not format it. Latest version installed. Also, I can boot and and use the phone, but only on the first time after installing a rom. After a reboot it always hangs at the android man when decryption.
On that note, I will NEVER try to encrypt my phone again.

oic0 said:
CWM can not mount /data, and thus can not format it. Latest version installed. Also, I can boot and and use the phone, but only on the first time after installing a rom. After a reboot it always hangs at the android man when decryption.
On that note, I will NEVER try to encrypt my phone again.
Click to expand...
Click to collapse
Bump

Related

I Cant fix it, Please help

Well im somewhat new to rooting etc, so while I was in twrp I accidentally hit the format button assuming it would give me options and I formatted the internal SD, I could not Re partition it, So I formatted everything and installed a new and clockwork mod(some said that would fix it), attempted to reformat it and partition it, i couldn't, it wouldn't even recognize so after trying everything I could, I just made the problem worse and worse, now clockwork mod wont even go back, like I literally cant go back, It just crashes when I try to go back, Whenever I try to flash from Odin to the phone, trying to with clockwork mod, it still seems corrupted, so its been sitting on my desk for a week, I've been trying to fix it for two, so being the stereotypical guy, the last thing I do, I ask for help, So please, Help?
BrandonSnoog said:
Well im somewhat new to rooting etc, so while I was in twrp I accidentally hit the format button assuming it would give me options and I formatted the internal SD, I could not Re partition it, So I formatted everything and installed a new and clockwork mod(some said that would fix it), attempted to reformat it and partition it, i couldn't, it wouldn't even recognize so after trying everything I could, I just made the problem worse and worse, now clockwork mod wont even go back, like I literally cant go back, It just crashes when I try to go back, Whenever I try to flash from Odin to the phone, trying to with clockwork mod, it still seems corrupted, so its been sitting on my desk for a week, I've been trying to fix it for two, so being the stereotypical guy, the last thing I do, I ask for help, So please, Help?
Click to expand...
Click to collapse
Well I fixed it, I updated my cwm through odin, but I still can't mount /sdcard ive tried formatting ive tried reinstalling, any ideas?
BrandonSnoog said:
Well I fixed it, I updated my cwm through odin, but I still can't mount /sdcard ive tried formatting ive tried reinstalling, any ideas?
Click to expand...
Click to collapse
Try flash this Rom which has root access built into it
Also, I recommend you use TWRP recovery (flashable zip) instead since it's UI and features are better than CWM(I think the author had discontinued the project)
LimeliME said:
Try flash this Rom which has root access built into it
Also, I recommend you use TWRP recovery (flashable zip) instead since it's UI and features are better than CWM(I think the author had discontinued the project)
Click to expand...
Click to collapse
Tried it and only goes to the Samsung logo and goes into a reboot cycle. Still no luck.
BrandonSnoog said:
Tried it and only goes to the Samsung logo and goes into a reboot cycle. Still no luck.
Click to expand...
Click to collapse
Did you do a clean flash ? (Factory reset then flash the Rom)
Or try wipe the internal SD Card (backup your data first) then flash the Recovery Zip (first) then the Rom (Second), finally the Gapps (third)
LimeliME said:
Did you do a clean flash ? (Factory reset then flash the Rom)
Or try wipe the internal SD Card (backup your data first) then flash the Recovery Zip (first) then the Rom (Second), finally the Gapps (third)
Click to expand...
Click to collapse
Formatted and wiped both manually and using infamous cache wipe and the infamous super wipe, then using odin flashed an md5 of twrp 2.8.5 then used twrp to flash the rom you sugested and then gapss, still stuck on a reboot loop.
BrandonSnoog said:
Formatted and wiped both manually and using infamous cache wipe and the infamous super wipe, then using odin flashed an md5 of twrp 2.8.5 then used twrp to flash the rom you sugested and then gapss, still stuck on a reboot loop.
Click to expand...
Click to collapse
Did you "flash" the recovery ? If no then try to flash the recovery instead....
If all above didn't work for you, then I suggest you to odin back to the stock Rom

CM13 Not Starting - Accidentally Wiped TWRP

I've gone and screwed up again. I managed to root and install TWRP from Lollilop. Before flashing with CM13, I wiped everything except the external SD and I believe I wiped TWRP and SuperSU in the process. So then I was like, no biggie, let's root and get TWRP back on. I rooted via ADB but now when I power the phone up, it's stuck in an endless CM boot screen.
How can I resolve this. Go back to stock and start over? I really want to avoid any further screw ups hence why I am posting here.
Thanks!
Can anyone offer some pointers? I'm truly at loss and I don't want to brick the phone.
dmg14 said:
I've gone and screwed up again. I managed to root and install TWRP from Lollilop. Before flashing with CM13, I wiped everything except the external SD and I believe I wiped TWRP and SuperSU in the process. So then I was like, no biggie, let's root and get TWRP back on. I rooted via ADB but now when I power the phone up, it's stuck in an endless CM boot screen.
How can I resolve this. Go back to stock and start over? I really want to avoid any further screw ups hence why I am posting here.
Thanks!
Click to expand...
Click to collapse
dmg14 said:
Can anyone offer some pointers? I'm truly at loss and I don't want to brick the phone.
Click to expand...
Click to collapse
Yeah, sure.
So how about telling me first how you managed to wipe TWRP? I'm pretty sure there is no option under "wipe" to wipe the recovery partition?
And CM13 is rooted, all you need to do is enable it in settings, you can install SuperSU optionally if you wish to manage superuser access with it.
So like, confirm that you actually wiped recovery (still don't get it how? you used dd command?), try to enter TWRP with hardware key combination. If successful get a new CM13 zip and reflash.
NatusVincere said:
Yeah, sure.
So how about telling me first how you managed to wipe TWRP? I'm pretty sure there is no option under "wipe" to wipe the recovery partition?
And CM13 is rooted, all you need to do is enable it in settings, you can install SuperSU optionally if you wish to manage superuser access with it.
So like, confirm that you actually wiped recovery (still don't get it how? you used dd command?), try to enter TWRP with hardware key combination. If successful get a new CM13 zip and reflash.
Click to expand...
Click to collapse
Under the wipe settings of TWRP, I checked all the boxes except external SD. Then after installing CM13, the phone didn't power on unless I pulled the battery before turning it on. Also, recovery mode doesn't boot into TWRP is simply says Factory Reset? Which is the stock recovery I believe.
This is the first time that TWRP doesn't work after wiping the phone and installing CM.
No.. It is not stock. If you installed cm then you had twrp. Just click yes when asked to wipe and you will go to twrp.
Sent from my LG-D855 using Tapatalk
NatusVincere said:
No.. It is not stock. If you installed cm then you had twrp. Just click yes when asked to wipe and you will go to twrp.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
That worked. Thank you! I re-flashed CM13 and all is good.

Unbrick the device please? Problems with encryption and OOS 4.0 N update.

Guys, a bit of help.
I clean flashed the new OOS 4.0, coming from the 30dez RR-N Unoff by Eliminator.
That worked, but encrypted my system. I couldn't access the recovery, was asking for a pass.
So I formatted everything, and now trying to go back to RR 5.7.4 M. I tried Eliminators and Takers builds. Both are stuck at the RR logo.
I flashed 3.2.8 firmware, followed by
ROM
Nano 6.0 Open Gapps
Ex Kernel 0.39(CM)
SuperSU 2.79
Xposed v87
TB
Followed this for both the Official and Unofficial build.
Both stuck at the RR logo.
Do I need the modified .28 TWRP?
I wanted xposed, so I wanted to downgrade back to M
Tried something
Flashed the modified TWRP, and tried flashing OOS 3.2.8 and SuperSU 2.79
Getting this error now
Code:
Encryption Unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
Here, there is a button to reset the phone, but pressing that does nothing. Pressing the power button gives me the options of powering off the device, rebooting, and taking a screenshot.
I went into fastboot then and did a fastboot erase userdata.
Then I booted into TWRP and did a format all, typed yes(that keeps changing the data partition to F2FS, so I changed it to exFat)
I flashed OOS 3.2.8 again, followed by SU again.
Got the same Encryption Unsuccessful message again, with the same option to reset the phone, which is not working.
Tried the 3.2.4 firmware, and then I flashed OOS 3.2.8 along with SU 2.79 again, in the hopes that if it boots properly, I will clean flash BJRR 5.7.4.
First I got error 7.
Formatted everything again and flashed again
Still getting the Encryption Unsuccessful message.
What to do?
I'll try flashing BJRR M directly this time.
I think the issue was after installing the new OOS 4.0 update, it encrypted my phone, and I flashed stuff before unencrypting it, I thought format option in TWRP would remove encryption.
Help please.
Its been 15 mins, BJRR 5.7.4 still stuck at the RR logo.
gro0vr said:
Guys, a bit of help.
Help please.
Its been 15 mins, BJRR 5.7.4 still stuck at the RR logo.
Click to expand...
Click to collapse
Flash 4.0 full rom, reboot
flash modified twrp, change /data to ext4
wipe /data, cache, dalvik
reboot
you are now 100% stock with working twrp and /data partition
BTW with encrypted issue.
Wipe Userdata with Fastboot
Go back to Twrp flash rom and directly flash SuperSU
You should be decrypted currently we can't encrypt because of TWRP.
atulclassic said:
Flash 4.0 full rom, reboot
flash modified twrp, change /data to ext4
wipe /data, cache, dalvik
reboot
you are now 100% stock with working twrp and /data partition
Click to expand...
Click to collapse
Thanks for getting back.
I already flashed the modified TWRP through fastboot. Will I need to flash that again after installing 4.0 ROM?
I will try this and get back to you.
Puddi_Puddin said:
BTW with encrypted issue.
Wipe Userdata with Fastboot
Go back to Twrp flash rom and directly flash SuperSU
You should be decrypted currently we can't encrypt because of TWRP.
Click to expand...
Click to collapse
I tried fastboot erase userdata.
the command completed successfully, but on OOS 3.2.8, it still showed the Encryption Interrupted error.
I will try flashing OOS 4.0 and get back.
If I want to downgrade from OOS 4.0, how will that work? Do I just wipe everything after flashing the OOS 4.0, then flash RR 5.7.4 or OOS 3.2.8?
atulclassic said:
Flash 4.0 full rom, reboot
flash modified twrp, change /data to ext4
wipe /data, cache, dalvik
reboot
you are now 100% stock with working twrp and /data partition
Click to expand...
Click to collapse
Flashed 4.0 after formatting everything.
Rebooted.
Changed /data to extfat by mistake.
Wiped /data, cache, dalvik
Rebooted in OOS 4.0
Got the Encryption Interrupted message again, but this time pressing the reset phone button worked, and took me to TWRP.
Booting to sysyem again took me to TWRP again.
Noticed everything had been deleted.
Formatted everything again
Installed 4.0
Reboot
Installed the modified twrp again via fastboot(already flashed it, so I skipped it during the first time I flashed 4.0)
Changed /data to ext4 correctly this time.
Wiped /data, cache, dalvik
Rebooted.
Again came back to twrp
Now, when I install 4.0, and change /data to ext4, it deletes everything, and I am reboot back to twrp even if I select reboot to system in TWRP.
Since I can't have 4.0 with /data on ext4, I tried to install RR 5.7.4.
Same result, keeps sending me back to recovery.
gro0vr said:
Flashed 4.0 after formatting everything.
Rebooted.
Changed /data to extfat by mistake.
Wiped /data, cache, dalvik
Rebooted in OOS 4.0
Got the Encryption Interrupted message again, but this time pressing the reset phone button worked, and took me to TWRP.
Booting to sysyem again took me to TWRP again.
Noticed everything had been deleted.
Formatted everything again
Installed 4.0
Reboot
Installed the modified twrp again via fastboot(already flashed it, so I skipped it during the first time I flashed 4.0)
Changed /data to ext4 correctly this time.
Wiped /data, cache, dalvik
Rebooted.
Again came back to twrp
Now, when I install 4.0, and change /data to ext4, it deletes everything, and I am reboot back to twrp even if I select reboot to system in TWRP.
Since I can't have 4.0 with /data on ext4, I tried to install RR 5.7.4.
Same result, keeps sending me back to recovery.
Click to expand...
Click to collapse
Yes.. Flash stock recovery if it boots flash TWRP back. Its a mess it really is..
Puddi_Puddin said:
Yes.. Flash stock recovery if it boots flash TWRP back. Its a mess it really is..
Click to expand...
Click to collapse
I'll try flashing the stock recovery.
Could you tell me what are the stock formats of /system partition? ExFat or Ext4?.
/Data keeps changing to F2FS, what should I change that to? exfat or Ext4?
Also, what should I change cache to? Its currently at exfat.
gro0vr said:
I'll try flashing the stock recovery.
Could you tell me what are the stock formats of /system partition? ExFat or Ext4?.
/Data keeps changing to F2FS, what should I change that to? exfat or Ext4?
Also, what should I change cache to? Its currently at exfat.
Click to expand...
Click to collapse
Ext4 is default. Don't change cache.. Only Data.
IT BOOTED!!!
Puddi_Puddin said:
Ext4 is default. Don't change cache.. Only Data.
Click to expand...
Click to collapse
Thanks. Just booted.
Atulclassic told me /data was ext4, was wondering about /system.
It just booted.
I followed both your advice, flashed stock recovery, then relocked the bootloader.
Then tried pushing ota via adb. That didn't work
Said loading failed.
So I unlocked the bootloader again, flashed modified TWRP
Flashed OOS 3.2.8
Just that, didn't flash SuperSU or anything else.
Just booted into the setup page.
Thanks a ton for helping me out.

TWRP acts weird, crashes and breaks ROMs when reloaded.

Hey guys, could one of you please tell me how to do a complete wipe?
I'm having so many problems with TWRP at the moment, and so I want to nuke the partitions in hope that it'll fix it. I've tried using the fastboot format commands for system, data & cache. I've also tried to wipe the recovery, but it gives me the error "Formatting is not supported for filesystem with type ' ' ". So for that I just use format erase and flash the recovery again.
The only other partitions I know of are the boot and bootloader, but I don't want to touch them if at all possible.
The problem I'm having and why I want to wipe sotrage is that if I install sultan's LinageOS (haven't tested with other ROMs yet), TWRP ****s the bed and will make the device undetectable from ADB, (while TWRP is still running though), and if I then try to go into TWRP again, it'll hang, crash, and somehow make the ROM think its just been freshly installed again (data partition corruption?), and it'll do that every time I reboot from then on. The only way to fix this is to wipe the phone as I mentioned earlier, but it will always get stuck again when I re-flash the ROM.
Also, another unusual thing is that when I boot the phone, it has the old boot splash from my previous ROM when loading recovery or for the first few seconds when loading a ROM. So that might be having an effect on the problems I'm having, and what makes me believe that wiping will help.
Any help would be greatly appreciated. (Sorry if it's a bit incoherent)
TL;DR: Flash TWRP, load TWRP, flash ROM, flash Gapps, load ROM, restart, load TWRP, TWRP hangs, crashes, and breaks ROM. ROM will keep being broken until full wipe. Also weird thing where I have old boot splash from old ROM.
Edit: Ended up bricking my phone, and using the unbrick tool to fix that. It seems that it was what I was looking for, where it wiped the phone completely. I'll have to see if that actually fixes my problem.
TWRP 3.1.xx is having this problem, believe the fix is to use the blue_spark 3.1.xx version or the nethunter 3.0.4-1 version, both found here on the forums somewhere

I accidentally wiped vendor in twrp while flashing RR rom is that a problem?

Hi!! I flashed twrp as soon as I got the device and as a redmi note 3 user I don't know anything about vendor so I wiped it and even flashed 3 OTA updates of RR will I face any problems in future?if yes are there any solution?
Ps- now the device is running fine no probs at all
**Thanks for tuning in this question is answered**
Yep. Now you can't mount data, vendor and probably can't flash any other roms.
Happens to my other devices.
beeduq said:
Yep. Now you can't mount data, vendor and probably can't flash any other roms.
Happens to my other devices.
Click to expand...
Click to collapse
False. Please don't spread misinformation.
RR overwrites the vendor partition anyway, so @sreek995 will have no problems. If you eventually want to flash GSIs just flash this first.
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
JoseRebelo said:
False. Please don't spread misinformation.
RR overwrites the vendor partition anyway, so @sreek995 will have no problems. If you eventually want to flash GSIs just flash this first.
Click to expand...
Click to collapse
thank you sir!!
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
This is actually my first phone with a vendor partition, but that is weird. Bad TWRPs are probably doing something terribly wrong, that shouldn't happen. But you should still be able to flash the vendor partition.
Sorry if my message came out a bit too harsh.
JoseRebelo said:
This is actually my first phone with a vendor partition, but that is weird. Bad TWRPs are probably doing something terribly wrong, that shouldn't happen. But you should still be able to flash the vendor partition.
Sorry if my message came out a bit too harsh.
Click to expand...
Click to collapse
Me and vendors were not in good terms, I guess. ?
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
I think after formating data ,you might mount it again.
Dush4711 said:
I think after formating data ,you might mount it again.
Click to expand...
Click to collapse
Nope, it's gone and never mounted again. Even format, repair or change the storage type cannot re-mount the vendor.
The only way, I can get it to work is by flashing original recovery using computer and let it format it. After that, using computer flash twrp.
But I never unlocked bootloader in this device (note5), so I don't know about it's recovery. Xiaomi's can be very tricky or very easy. My wifes phone (Mi 5X) came with unoriginal rom, and I brick it when trying to install twrp, but by open the device and doing something inside of it, I manage to restore it to original and flash twrp.
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
it happened on my samsung j6 plus (SM_J610F) and i can not even flash it with original rom (in download mode it said sw rev check failed fused 4 binary 1) and t can not do any thing. twrp said /vendor has no data in it (0MB) and vendor img has (477MB). do you have any idea i can resurect my phone from dead.
tumo07 said:
it happened on my samsung j6 plus (SM_J610F) and i can not even flash it with original rom (in download mode it said sw rev check failed fused 4 binary 1) and t can not do any thing. twrp said /vendor has no data in it (0MB) and vendor img has (477MB). do you have any idea i can resurect my phone from dead.
Click to expand...
Click to collapse
Use PIT file for your model (don't use other or you'll brick the phone) in Odin.
Good luck.
Sent from my SM-A300FU using XDA Labs
;-;
you dont wipe vendor partition and reboot. If you wipe vendor, wipe system partition too reinstall the rom and everything runs fine. If you wipe vendor and dont flash rom, sure you'll get into trouble(Not that trouble actually,just cant boot into your rom).
Prathamesh 27 said:
you dont wipe vendor partition and reboot. If you wipe vendor, wipe system partition too reinstall the rom and everything runs fine. If you wipe vendor and dont flash rom, sure you'll get into trouble(Not that trouble actually,just cant boot into your rom).
Click to expand...
Click to collapse
yep, vendor is essential to runs the system

Categories

Resources