Develop Bugs

[Q] Help! Installed AOKP over Encrypted CM11!!!

Hi All -
First time posting! I am very new to this and I'm in dire need of help! I will write as many details of my situation as I can!
So, I have been running a recent nightly of Cyanogenmod 11 on my d2att/i747 Samsung Galaxy S3 for the past few weeks. I decided to try out the encryption feature (first mistake). I noticed that things weren't running smoothly as they were before and decided to try flashing a new ROM (latest AOKP nightly). NOW, I am in trouble.
First, before installing AOKP, I loaded the ROM and gapps to my external SD. I then did these steps: wipe data/factory reset, then
format /data, then format /system, finally Wipe Dalvik Cache. I then installed AOKP and gapps from the external SD. Halfway through the install I noticed on the screen "E: Can't mount SDCard". However, the install appeared to go through well so I thought it might have been in error.
I then rebooted as per normal, at which point I was shocked to still see the cyanogenmod encryption unlock screen! I plugged in the password, and then watched the AOKP boot screen perpetually load. It never did fully load.
Would any of you be able to help me resurrect my phone? Thank you so much in advance!!!

What version of the AT&T ROM were you running before installing CM11?

audit13 said:
What version of the AT&T ROM were you running before installing CM11?
Click to expand...
Click to collapse
That was ages ago. MAYBE 4.1.1.
I Think I may have to try to do a stock recovery...

As long as you were not on 4.3, flashing via Odin should restore the phone to complete stock everything (ROM, Radio, bootloader).

audit13 said:
As long as you were not on 4.3, flashing via Odin should restore the phone to complete stock everything (ROM, Radio, bootloader).
Click to expand...
Click to collapse
It doesn't seem to be working when I try to flash through ODIN. It says "succeed 0/failed 0". Could that be because of running CM11 (android 4.2.2)? Or the encryption?

Possibly. You're flashing a stock AT&T rom from samfirmware?

audit13 said:
Possibly. You're flashing a stock AT&T rom from samfirmware?
Click to expand...
Click to collapse
not samfirmware. i'll try downloading one from them.

Samfirmware has the official ROM releases.
Link here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware

ARGH. So, in theory ODIN worked. However, after booting up again, I'm getting the same request to enter a code to get past encryption. Even better, that code is no longer working!!!
Any ideas?

doorstop25 said:
ARGH. So, in theory ODIN worked. However, after booting up again, I'm getting the same request to enter a code to get past encryption. Even better, that code is no longer working!!!
Any ideas?
Click to expand...
Click to collapse
I take it back!!! I did another factory wipe and everything turned on!!! WHOOO!!! Thanks for the help!

KitKat flashes fine, won't survive a soft reboot

I wiped the dust off my old S2 in hopes to get it running again. The last ROM I had on it was Jedi Mind Trick JB 4. I flashed sultanxda's CM11 ROM and it booted up fine(logged into google, installed some apps). I did a soft reboot and the phone never wanted to boot back up. It flashed the Samsung logo and then just sat at a black screen. I flashed CM11 again just to make sure it didn't get corrupted the first time, but it still did not want to come up after a reboot. Then I thought maybe it's the ROM/ZIP so I flashed ParanoidAndroid 4.6-beta5. Same issue, it boots up fine after the flash, but will not start up after a reboot.
I'm on CWM Recovery 6.0.2.7, and I wipe/format the usual before the flash. Also on radio UVMC6. Any ideas?

I'm having the same problem, did you find a fix ?

Rushaan™ said:
I'm having the same problem, did you find a fix ?
Click to expand...
Click to collapse
same issue, different roms .

You. Guys are using an out of date recovery. Get the newest version of twrp and you should. Be fine.

CWM: http://www.teamchopsticks.org/p/cm110-release-notes.html
TWRP: http://forum.xda-developers.com/showthread.php?t=1768742

CM 12 + gapps flashed but no google service and now can't flash anything.

Using Odin/towelroot/twrp I was able to flash CM12 on my tab pro 8.4 but after flashing gapps none of the google apps actually work - they all say that google play service is required. I tried flashing different gapps packages and also directly installing just the google play services APK.
I done a full wipe then attempted to reflash CM12 but the flash would just hang on "skipping md5 verification" or whatever it says and nothing is ever shown on the progress bar. Only way of getting out is to hold the power button and turn the tablet off which of course breaks it. Luckily I can use odin to flash the stock firmware and have my tablet working again. However I was very impressed with the new android and would really like to run it. Is there a way to flash CM12 with odin?
Thanks.

No help? Is it possible to use goomanager on these tablets?

Leedy818 said:
Using Odin/towelroot/twrp I was able to flash CM12 on my tab pro 8.4 but after flashing gapps none of the google apps actually work - they all say that google play service is required. I tried flashing different gapps packages and also directly installing just the google play services APK.
I done a full wipe then attempted to reflash CM12 but the flash would just hang on "skipping md5 verification" or whatever it says and nothing is ever shown on the progress bar. Only way of getting out is to hold the power button and turn the tablet off which of course breaks it. Luckily I can use odin to flash the stock firmware and have my tablet working again. However I was very impressed with the new android and would really like to run it. Is there a way to flash CM12 with odin?
Thanks.
Click to expand...
Click to collapse
Make sure you use LP gapps and not kitkat gapps.
Wipe system and factory reset / wipe data, install cm, install gapps, reboot. That is all that is needed.

crpalmer said:
Make sure you use LP gapps and not kitkat gapps.
Wipe system and factory reset / wipe data, install cm, install gapps, reboot. That is all that is needed.
Click to expand...
Click to collapse
I was using lp gapps. The problem is now I cant install anything from any recovery. Tried twrp and cwm with the same result, it says no md5 fou d skipping validation then just hangs there and never makes progress on the bar even after setting for some time.
The only reason my tab didnt get bricked is thankfully it was able to go into download mode and flash a stock rom with odin.

Got it flashed and this time gapps worked first try! After enable mtp it worked first try. Loving cm12 so far this is how this tablet should perform out of the box.

Could you explain how you manage to fix that ?
I'm currently having the same issue with my 8.4 tab pro wifi cm12-20150108-nightly.

I'm having the same issue here. What GAPPS APK are you guys using as well? I was on 6.5.99 (-036) and it wasn't working. I'm going to try 6.5.99 (-436) next.
Edit: flashing (-436) didn't fix it.

Won't boot after updating / flashing new rom

For some reason, my phone doesn't boot after updating my current rom or wiping and installing a new one.
After the install, the boot animation is displayed for about 1-2 seconds. It then reboots and gets stuck during the boot animation. I've let it sit for an hour, so I know I'm not just being impatient.
Funny thing is that I'm able to restore my nandroid without issue. I'm currently running CM 12.1. I've tried dirty flashing a newer version of 12.1, clean installing a newer version of 12.1 and also clean installing various other roms. The latest I tried was the newest android revolution HD. I'm running the latest TWRP (2.8.7.0).
Can anyone think of why this might be happening? Any troubleshooting tips are welcome.
Thanks.

Got it working with Viper One.

MaxGame said:
Got it working with Viper One.
Click to expand...
Click to collapse
I was gonna suggest.

After updating from cm13 to cm14 cant access TWRP recovery mode

Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help

If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.

luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.

nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you

Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.

DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"

This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:

DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/

luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?

DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk

luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?

DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.

luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far