Database Users

[Q] Soft bricked phone, encryption key required even after full format

I wanted to update from Cyanogenmod 10.1 to Google Edition 4.3, so I booted into recovery. I had enabled device encryption prior to this, and decided it isn't worth the hassle to me. So I decided to format the phone (I had backups of everything, but no NANDroid!). The formatting went well, there was no ROM to boot into anymore.
I had to use ADB to push the ROM onto the device, which I then flashed successfully. When I booted up, I was asked for my encryption password. The old key didn't work anymore. I was locked out of the ROM.
I looked into using ODIN to flash stock to remove encryption, but ODIN never connected to the device and I don't like this route because I'd have to root and get a recovery again. I tried Heimdall, but even when I installed C++ 2013 redist it wouldn't run, and again I don't like this idea but would do it if I had to.
How can I remove device encryption through ADB and recovery? I won't be able to boot up until I remove whatever files indicate that the device is "encrypted" and re-flash a ROM. My recovery is TWRP 2.600.

Dadasas said:
I wanted to update from Cyanogenmod 10.1 to Google Edition 4.3, so I booted into recovery. I had enabled device encryption prior to this, and decided it isn't worth the hassle to me. So I decided to format the phone (I had backups of everything, but no NANDroid!). The formatting went well, there was no ROM to boot into anymore.
I had to use ADB to push the ROM onto the device, which I then flashed successfully. When I booted up, I was asked for my encryption password. The old key didn't work anymore. I was locked out of the ROM.
I looked into using ODIN to flash stock to remove encryption, but ODIN never connected to the device and I don't like this route because I'd have to root and get a recovery again. I tried Heimdall, but even when I installed C++ 2013 redist it wouldn't run, and again I don't like this idea but would do it if I had to.
How can I remove device encryption through ADB and recovery? I won't be able to boot up until I remove whatever files indicate that the device is "encrypted" and re-flash a ROM. My recovery is TWRP 2.600.
Click to expand...
Click to collapse
Did you ever find an answer to this? I am in the same boat right now.

stpark6985 said:
Did you ever find an answer to this? I am in the same boat right now.
Click to expand...
Click to collapse
Have either of you found a solution, i have the same problem right now. i even tried flashing stock with odin but it is still asking for the DevicePolicyManager password.

Not sure if it's still a relevant question, but here's an answer for you:
I had an issue like this, only I didn't enable encryption by choice, it just turned on automatically (I think I had a bad app). Anyway, on reboot, it said Encryption failed, try a factory reset in recovery and go again. No avail, so I ended up having to re-flash to stock. I grabbed my old MG1 install, flashed though Odin, and ended up working. That night, I flashed a bad modem and effed myself over again, so I re-downloaded and re-flashed (using my mac and Heimdall) to get it back to stock that way. Heimdall command-line is the way to go, if you ask me. You can flash each and every partition manually until you find the one that is broken, and away you go.
The information I used was in THIS THREAD. Just use your TAR file and flash away.

[Q] Stuck at boot screen after TWRP asking if I want to install SuperSU

I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?

You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999

I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.

OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.

Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..

Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...

After mf9 install avd stock recovery did you factory reset

Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.

Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192

Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!

From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app

Sorry for necro, but did anyone figure out a solution to this? This just happened to me.

Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back

This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.

I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.

Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.

Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance

[Q] How do I restore device after failed OTA 5.0.1 update on rooted N4?

Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...

May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.

Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?

Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).

AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.

Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?

SM-N910G stuck in reboot screen/recovery is not seandroid

Hey guys,
So I've read everywhere and tried multiple ways to fix this but can not make any progress, so any help would be appreciated.
Okay my phones model number, SM-N910G and ive recently flashed/rooted my phone to solve a restart loop issue. Then about a week later my phone was stuck in the boot screen showing the message "kernel warranty" etc. So I went to re-root my phone and then I got the "seandroid enforcing" message. So I decided to reinstall stock firmware and start from scratch, which resulted in my phone going into recovery mode and just looping.
Now I'm stuck in this continuous loop of everything I do ends with either "seandroid enforcing" or recovery loop.
Iv'e used a rom from Sammobile and one from here. I've rooted with a CF root and now ive tried to install firmware using Samsung kies.
My very limited knowledge about phones is dried up and I really need some help on this!
Please any suggestions or links to more appropriate firmwares/options is welcome.

Flash latest official stock firmware via Odin with option Nand Erase All. Upon start up, remove and put back battery then go to Recovery via 3-button combo. Wipe data/factory reset & wipe cache then reboot. Wait for a few minutes as it takes time during the first boot up.
If you have important files in your internal sd card, back up it first as it will be all erased.
Also best to remove external sd card when flashing new Rom via Odin. For some reason, I've experienced twice already my ext'l sdcard getting corrupted when flashing new Rom.

Hi GrippingSphere,
I tried what you said and unfortunately I still end up with my phone unable to make it past the recovery booting screen and just restart looping from there? Any ideas? I'm going crazy as this is my only phone and I'm unable to use it. The only thing I can do is enter download mode.
Do you have a link to stock firmware you would recommend?
Thanks

NATHANJBC1991 said:
Hi GrippingSphere,
I tried what you said and unfortunately I still end up with my phone unable to make it past the recovery booting screen and just restart looping from there? Any ideas? I'm going crazy as this is my only phone and I'm unable to use it. The only thing I can do is enter download mode.
Do you have a link to stock firmware you would recommend?
Thanks
Click to expand...
Click to collapse
Have you tried flashing the stock rom with a pit file? if nothing works try to follow this thread
https://forum.xda-developers.com/showthread.php?t=3488114
Sent from my SM-N910G using Tapatalk

[Zenfone 3 ZE552KL] Won't boot to system

Hi,
After doing some unlocking, installing recovery then rooting. I was able to complete root process but i had an issue where my sim cards were not detected. Foolish me, i tried to do a factory reset in the settings and it turns out that my system was not recovered back. Now, it is looping on TWRP and can't boot back to system. Not sure what to do next...
Done fixing: i flash back the original recovery. Stock recovery automatically proceed with "erasing" then it autoreboots. Hope this help others encountering the same problem. To prevent this, just don't do factory reset via system setting when having custom recovery.

jhonny173 said:
Hi,
After doing some unlocking, installing recovery then rooting. I was able to complete root process but i had an issue where my sim cards were not detected. Foolish me, i tried to do a factory reset in the settings and it turns out that my system was not recovered back. Now, it is looping on TWRP and can't boot back to system. Not sure what to do next...
Done fixing: i flash back the original recovery. Stock recovery automatically proceed with "erasing" then it autoreboots. Hope this help others encountering the same problem. To prevent this, just don't do factory reset via system setting when having custom recovery.
Click to expand...
Click to collapse
hello, the same thing happen to my phone and i want to ask where can i get the original recovery file?