I have Samsung Galaxy S III GT-I9300 with 4.3 stock ROM, rooted with CF-AutoRoot/SuperSU and Recovery replaced by ClockWork Recovery Mod. I used face unlock password together with unlock pattern backup. Now I wanted to encrypt my device. I go trough every step, setting password, charging battery over 80% and plugging in charger. When I finally click Encrypt device, the green Android mascot flashes for second, then screen goes black for minute or two, then phone boots up but no encryption process is performed and the phone is unencrypted.
I tried:
1. Disabling SuperSU
2. Disabling Orbot startup
3. Disabling SIM card PIN request
4. Doing encryption in both portrait and landscape mode
5. Unplugging charger right before clicking Encrypt
I have installed: Flashed Stock ROM with Odin, did a factory reset from stock Recovery, set up my phone, then rooted phone using CF-AutoRoot, Installed SA Manager 2.0, then Xposed Framework and Phone ID changer plugin, then flashed ClockWork Mod Recovery with Odin. At one point I wiped Cache partition from ClockWorkMod Recovery and when exiting choose Repair Root. Then I installed Orbot, Orweb, SecureChat and four other applications to manipulate NFC cards.
What is causing my phone to not encrypt upon reboot? I don't want to reset and reflash everything because my phone already have lot of information that I don't want to lose.
Edit: After trying various methods, I found that disabling SuperSU from paalications menu allowed me to encrypt the phone. This thread delivered http://forum.xda-developers.com/showthread.php?t=2485126&page=4 Tomorrow I will repeat the process again and will tell if Safe Mode is really required for success or only disabling SuperSU
Also the fools saying that Encryption is irreversible process are fools. They are copying each other's wrong blog posts. I clearly see a Decrypt device button and I will try to use it tomorrow!
It all comes down to this: If phone does not encrypt (reboots and then boots few minutes later, but no encryption) then do the following:
To successfully encrypt:
1. Disable SuperSU from applications menu
2. Restart phone in Safe Mode (tap Application key repeatedly while phone restarts)
3. Follow encryption procedure as normal (setting screen lock password, charger, etc.)
4. When encryption is complete, enable SuperSU in Applications menu.
To successfully decrypt:
1. Disable SuperSU
2. Reboot (Safe Mode not required)
3. Decrypt as usual
4. Enable SuperSU again afterwards
This information probably need to be included in some FAQ. This could save other people a lot of time and frustration trying to figure out what is wrong.
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
My stock Nexus 5 hardlocked today while attempting to connect to a wifi network. Upon restart, the boot-up animation took longer than usual, then displayed the 'Optimizing Apps' screen (which is not typical). It completed optimization on 5 apps, claimed to be starting Android, and then reset back to the boot-up animation, continuing the same cycle.
Unsuccessfully tried to boot into safe mode, although I can access Recovery Mode. Wiping system cache did not help. Installed ADB/Fastboot and sideloaded the original OTA without any improvement.
At this point, I'm hoping for either another path to get the device to boot or a way to extract some critical data (SMS, docs, etc.) off the device before doing a factory reset.
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
audit13 said:
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
Click to expand...
Click to collapse
Sadly no, fully stock phone.
Gave up and pulled the trigger on factory reset. We'll see if it helps.
On the plus side, this incident has motivated me to unlock and root my phone, hopefully expanding my options for the next time this happens.
Yup, an unlocked bootloader is definitely a plus in these situations.
I always unlock the bootloader unless it voids the warranty on the phone. Once the warranty is over, I unlock it if possible.
Factory reset seemed to work. Now unlocked and rooted!
Hi, I rooted my phone with magisk, now everytime I restart the phone all my personalisation and folders disappear and I need to log in to every app.
Pretty sure I have done something stupid but thought I would check with you guys.
Would twrp factory reset get rid of my root? Would flashing a from help?
Thanks
Alright, I ran the restore factory settings from the phones' official settings, it rebooted in TWRP asking me if I want to keep the system modifiable to what I checked yes and rebooted the phone. Then the phone booted and there was a message saying that the phone cannot be set up due to the data being encrypted (something along those lines), then I checked to keep the system read-only cause TWRP prompted me again but the same message popped up. Then the same "data encrypted window appeared" and I, who knows why, decided to wipe internal storage in TWRP and the phone is now stuck on the blue "Honor" splash forever and boots again if I shut it down manually. I can shut it down via TWRP.
Don't really know what to say other than I really don't know what I'm doing and I was just hoping to format my internal storage quickly so that I can swap my phone with a family member. I'm really disgusted with how I approached this whole scenario and I need help to fix my phone if possible. I can access the internal storage thanks to TWRP and the only folder there is TWRP.
Facts:
1. Did factory reset over official settings.
2. Did very stupid things, then wiped internal storage for the finale.
3. Phone is stuck forever blue splash screen and keeps restarting if I turn it off.
4. I have accesss to TWRP and can mount internal storage.
5. I should have no business owning a rooted phone.
6. The firmware on was(is?) BLN-L21.
Please help.
I was able to unbrick it. Please delete/lock this thread.