[Q] Sprint S4 Reboots After Encryption Unlock - Galaxy S 4 Q&A, Help & Troubleshooting

Hey guys! Long day.. My phone (Sprint Samsung Galaxy S4 sph-L720) has been **** since I sync'd Exchange and it required me to encrypt my phone. It requires me to enter a 4 digit pin before the device fully boots in to the OS.
I installed SuperS4 via the below link after installing CWM. It now boots showing the new boot splash page (I think it's called), then goes to the encryption unlock. As soon as I enter the 4 digits, it reboots. It says "Kernel is not Senadroid enforcing" up top but I read that's normal.
How do I delete all the encrypted data and start over with a new image? No encryption or anything. Hopefully this thread is in the right place.. Thanks!
galaxys4rootDOTCOM/sprint-galaxy-s4-roms/supers4-rom-for-sprint-galaxy-s4-android-4-4-2nae/
Edit: Yes, I wiped cache and factory reset via CWM. Still encrypted.

I rooted it with a different package, mounted /sdcard/ and installed from there instead of sdcard1 (external) and it worked. FYI.

Related

[Q] A500 bricked after failed device encryption

Hi All,
Need your help. I tried setting up a corporate Exchange Account on my Iconia (rooted, running Honeyvillain 1.05). After set up of the account, I was asked to encrypt the table (policy from the corporate server). I followed the prompts to start the encryption process, entered a password, and then the device rebooted. It then was stuck on the screen with "Android" on it. I waited 30 minutes, and nothing. I forced a restart and then was presented with a green android (with a belt?) and prompting me for my password. After entering the password and hitting "OK" it would then immediately reboot and stop, again, at the screen with the white "Android". I tried wiping and restarting but nothing. I then tried installing a different ROM, but again was prompted for my password. This time (virtuous galaxy rom) it didn't actually restart, but just froze on the screen with the green android robot with the belt looking thing. I've tried running the unbricking process using the update.zip method, but still cannot get past the screen prompting me for my password. Would love your help with this! Am I out of luck?
Thanks,
-T
I use encryption with my tablet, and switched from various stock roms without problems, but I even didn't try with the custom roms, surely it will fail and loose all my data. The only thing I can think for you repair your tablet is to try to flash a stock rom and see if it boots, if not, then you have to erase everything from the tablet. There is a post saying to boot holding the power+vol up keys and then move the lock switch several times on and off, so it deletes everything on the tablet like a hard reset.
After you do that I will recommend stick with the stock rom (rooted if you want, it doesn't disturb the encryption) and encrypt the tablet again, it took quite a time to do it, specially if you have many data in the internal memory.
Hope it helps you.
Hi There,
Thanks for the reply. In the meantime, I actually found some instructions on how to do a factory reset (volume+ and power, then release power, then toggle screen lock twice) and I managed to revive it! I had previously tried installing the update.zip mentioned here: http://androidforums.com/acer-iconia-tab-a500/345419-un-brick-acer-iconia-tab-a500.html, and after a factory reset, the tab booted into this stock EMEA ROM.

[Q] S4 won't turn on after encryption

Hi guys,
The [email protected] app asked me to encrypt the device in order to use company e-mail and VPN. I hit "Encrypt my device" and a different than the usual Android logo appeared but the device turned off. I started it again and tried once more time but now using "Fas encryption" option. Device displays the same logo and turned off.
I just thought encryption didn't work but then I tried to boot up again and now it asks for the password, I type it, it shows that Android logo and turns off again.
Do somebody know what to do in this case?
It's ok to lose the data since I have nothing special stored.
Thank you in advance!
Update: after a few attempts I managed to wipe the entire device from Recovery.
viva_zidane said:
Hi guys,
The [email protected] app asked me to encrypt the device in order to use company e-mail and VPN. I hit "Encrypt my device" and a different than the usual Android logo appeared but the device turned off. I started it again and tried once more time but now using "Fas encryption" option. Device displays the same logo and turned off.
I just thought encryption didn't work but then I tried to boot up again and now it asks for the password, I type it, it shows that Android logo and turns off again.
Do somebody know what to do in this case?
It's ok to lose the data since I have nothing special stored.
Thank you in advance!
Update: after a few attempts I managed to wipe the entire device from Recovery.
Click to expand...
Click to collapse
I get the same now, anyone have a fix?
Have you tried flashing a stock ROM via Odin and performing a factory wipe before booting the newly-installed ROM for the first time?
audit13 said:
Have you tried flashing a stock ROM via Odin and performing a factory wipe before booting the newly-installed ROM for the first time?
Click to expand...
Click to collapse
the phone was rooted and everything worked so i dont think that is the issue

[solved] Note 3 bricked for good? No ADB interface to reflash manually.

Hi everybody.
TL;DR
Recovery hangs upon booting and fastboot mode doesn't show up ADB interface on my PC. How to flash the phone?
Long version:
I wonder if you can help me. My old faithful Note 3 is badly misbehaving. Yesterday I filled almost all its internal memory with some movies before heading out on a trip, but some time later when I reset the phone after unusually long boot all user settings were lost. Well, something went wrong, couple of hours later there was reset after reset so I wanted to restore previous backup... but couldn't. TWRP was showing error messages (TAR something something, 255) very shortly into restoring process. It couldn't restore backup but also couldn't make new one as well (similar error with TAR and code 255 when trying to backup user data).
Something was very wrong, so I thought maybe I will flash newer TWRP 3.0 and give it a try but suddenly after next reset I couldn't even get into recovery anymore - TWRP gives me black screen after several seconds into booting it. No icons, no reaction to key presses, nothing. Even holding power button does nothing.
Ooooookay, it's time to enter fastboot mode then and flash new recovery manually. So I enter it, connect phone to my laptop and... nothing! No ADB interface. Some kind of samsung driver is installing, but the most important one, for ADB, just doesn't show up. It's really weird. Reinstalling drivers doesn't help, only the same one device that shows up gets different names, but that's it - no ADB interface, and, effectively, I can't flash anything because fastbot and ADB can't see any device. Odin can't see the phone too.
What's going on? Is the internal flash dying or what? But if so what does it have to do with ADB not showing up? Do you have any ideas that I can try out in this situation? I checked my laptop with a tablet that I have on hand and it shows up its ADB interface without problem in fastboot mode even though it's the first time I connect it to this laptop, so laptop and it's system are fine.
If nothing helps then, well, One+ 3, here I come.
EDIT: Problem solved. Turns out f2fs on data partition crashed and therefore TWRP couldn't start at all. I managed to flash Philz CWM via Odin somehow (after messing with drivers for some more time) which told me there is something wrong with /data because it couldn't mount it at all. It couldn't format it either. Fortunately SlimLP managed to start and after throwing up some errors I managed to do factory reset which formatted the internal memory back to ext4. Then flashing TWRP, formatting data back to f2fs, restoring backup and voila! It works again. Good, I'll wait until Note 8 if there ever will be one.

OEM locked and stuck in Android safe mode "Decryption unsuccessful"

I recently successfully restored my Axon 7 (A2017U) to B20 and tried to OEM lock it again. After running "fastboot oem lock", the phone rebooted, but came up with something that said "To start Android, enter your password." I didn't have a password before, so I tried something I found online called default_password to see if it would unlock (which it didn't) & then other passwords to get the phone to wipe itself and essentially perform a factory reset. However, now it is stuck in Safe Mode and says "Decryption unsuccessful: The password you entered is correct but unfortunately your data is corrupt." When I try to wipe the phone, it says it is factory resetting, but then it restarts and goes to a blank screen. (Which I suspect is because TWRP is still installed as a recovery, not stock). In addition, power+volume up no longer works since the phone is oem locked, but power+volume down takes the phone into Factory Test Mode. My computer still recognizes the phone when it shows up in Safe Mode, but I cannot see it in ADB.
Where can I go from here to factory reset the phone? Is it possible to send this to ZTE to fix since it is OEM locked at the moment?
I followed razorblader's advice and successfully got the phone into EDL mode and ran tenfar's tool. However, that made it worse and now the phone just shows ZTE for the second & the screen goes blank.
EDIT: Nevermind, I was running that program without recovery.img/boot.img in the same directory, D'OH! Luckily, I still had comms with the phone after that mistake & I re-ran the program successfully. I can now get into TWRP recovery. However, booting into system still shows the corrupt data message. I'm going to try a factory reset from TWRP and see if that fixes the issue.
OK good news, got my Axon 7 working again, stock + locked & am currently posting this from it. One reason I wanted to relock it however was to get OTAs and right now B27 is showing up. Now before I almost brick my axon again, do I need to flash stock B20 recovery before I'm able to install this update? Also, I'd like to get to B29 eventually, but I'm guessing I need to update to B27 first. (correct me if I'm wrong though)

Accidentally encrypted phone now cant access it

Somehow my phone got encrypted and now every time I restart I'm presented with a password to turn it on. I don't remember ever encrypting my phone so I don't know the password and also TWRP won't let me do anything as well because it's encrypted. I have no idea how to fix this issue. Please help me.b
You'll have to wipe it. You should be able to bypass the password in TWRP enough to go into Wipe and then Format Data. This happens when you unlock the bootloader.
Sent from my Axon 7
My phone it's self is encrypted and I can't access my internal SD card in TWRP or mount system because of encryption
When I turn my phone on it asks for a pin but my keyboard or jumped won't pop up to enter anything and then when I boot into TWRP it asks for a password. I can get passed that but I can't do anything . Not even restore a backup.
Wipe > Format...
Sent from my Axon 7
Trying it now. Why or how did this happen?
So strange my bootloader has been unlocked for six months an this just randomly happened on reboot.
Some sort of discrepancy between f2fs and ext4 I think, though I'll admit it's somewhat a mystery to me as well
Sent from my Axon 7
I'm still having the same issue man. When I restart my phone it presents me with a black screen that says to start Android enter pin. Can't do anything. No keyboard no nothing.
Was able to restore from backup though and properly access TWRP.
What if I boot into EDL and flash all the way back to stock mifavor?

Categories

Resources