"Decryption failed" after installing AICP + Nano Gapps + Frankenclark Kernel
When I first attempted to install the Frankenclark Kernel, I attempted to install it after already having AICP being installed for nearly a month. After doing so (remembering to wipe Dalvik/cache) the device booted up with the message "Enter your password to start Android." After trying some random characters, it came up with "The password you entered is correct, but your data is corrupt." I wasn't worried about losing my data because it was already backed up, so I tried the option to wipe my data. It followed through with the data wipe and when the system booted back up, it responded with the same message about the decryption failing. So I decided to try yet again with a prior full system/data/cache/Dalvik wipe and full system reinstall. This failed as well and resulted in the same message.
Someone please help or explain why I can't do this
Minor details
Model number: XT1575
Settings for Frankenclark Kernel
300hz Tick Rate
A53 Cores: 1536 Mhz Max
A57 Cores: 2016 Mhz Max
Start-up Scripts
-ghostpepper
-rehpyc_misc
-vibrator
Probably because you flashed frankenclark on a ROM it's not built for. It is only for stock, not cm or aosp. I guess your lucky it even booted up.
dustin_b said:
Probably because you flashed frankenclark on a ROM it's not built for. It is only for stock, not cm or aosp. I guess your lucky it even booted up.
Click to expand...
Click to collapse
Oh, duh
Sorry about that, but thank you so much for the explanation.
Lesson learned!
Related
I am trying to get Ktoonsez kernel running on MDOB ROM so i can create a perfect sRGB profile and FULLY eliminate screen flicker/color shift, running into some problems.
I am rooted with TWRP recovery and debloated via Motochopper CASUAL R527b
I also have Nottach Xposed mod installed.
I attempted to flash version 1.7 of the TouchWiz version of MDOB
Here is where i have a problem; i have a FULL backup of AT&T ROM with the above all installed and running PERFECTLY (which im running on again). I reboot into TWRP recovery, have the aforementioned full backup, i swipe to factory reset, davlik/system/data/cache wipe, then flash the ROM
I did NOT perform a full system/data wipe the first 2 times, and the ROM worked but not on second reboot (had to reboot system via recovery but it worked afterwords. I also got Ktoonsez TouchWiz kernel working, but it would not fully boot unless i booted from TWRP).
I cannot get past the Custom/padlock screen when i hit reboot system, so i cannot flash the kernel and then clear davlik and cache (which i am supposed to do in that order, correct?)
If someone could give me a complete step by step i would appreciate it. i have been waiting to fix the damn screen flicker and create the first perfect sRGB settings for this phone; i cant get this figured out or working, and i dont want to screw something up.
I have linked to EVERY bit of root/hack/ROM/kernel software i have downloaded, only difference is the ROM i have is version 1.7 instead of version 1.8. I believe perhaps something to do with the previous mods ive done may be inhibiting my ability to boot properly. i DID have it running, both MDOB, and later MDOB with Ktoonsez kernel, but i had to reboot from TWRP every time, which i knew was not right, so i flashed the backup AT&T ROM with all system/user/apps/data, the Motochopper Casual R527b Root/debloat mod, and Nottach Xposed mod which are part of my only backup (works flawlessly, im happy with it but i want to perfect an sRGB profile for these phones, its in my area of work and i would love to be able to show stuff that is absolutely correct to clients).
Everything should be annotated correctly, and i flashed everything correctly as per the directions found in appropriate threads, ie reset, davlik/data/system/cache wipe, flash ROM, reboot (worked twice, second reboot i installed Ktoonsez kernel, wiped davlik/cache, rebooted, got in, enjoyed it, rebooted, and it hung at custom/padlock screen). Now after i flash the same MDOB file, it will NOT boot, just hangs at custom/lock screen. i DID fully wipe the device to try to reset everything (via TWRP), and flash the new ROM.
Thanks!
anyone? this is really frustrating; same issue trying to flash v1.8 of MDOB
I'm looking for a definite procedure for switching roms and a kernel. Im currently running pure nexus w elementalx kernel. Everything's working great but part of my reason for buying 6p was all the rom and kernel options. So I wanted to try Chroma w elemental x....Here's what I did:
1. TWRP factory reset THEN I went back and wiped /system
2. Flash Chroma, gapps, supersu 2.65
3. wipe dalvik & cache (not sure if it's necessary but I did)
4. reboot
This seemed fine. Chroma booted up, no app crashes. Now I wanted to flash elementalx. Heres where I was working off mixed knowledge but decided to do it this way.
1. wipe dalvik cache
2. flash chroma, gapps, elementalx
3. wipe dalvik cache (yes. Once more to be sure)
***Im not sure the above is the textbook method BUT it worked. I booted into chroma, elementalx was present and working like it did with pure nexus. For about an hour or so I used the phone, making no changes at all in elementalx. It was getting late. I plugged in my phone and fell asleep. When I woke up 7 hours later it had rebooted and was stuck in bootloop. I tried forcing a reboot. It looked like it was going to work (reaching the "optimizing apps" part) but then just continued to loop. Flashed my pure nexus backup and Im up & running again.
I know the exact cause is nearly impossible to diagnose without a log and I don't have one. Im just looking for some guidance from users with more experience. If you were running pure nexus and elementalx, and you want to try a new rom like Chroma plus elementalx, how exactly would you proceed? Thanks
KLit75 said:
I'm looking for a definite procedure for switching roms and a kernel. Im currently running pure nexus w elementalx kernel. Everything's working great but part of my reason for buying 6p was all the rom and kernel options. So I wanted to try Chroma w elemental x....Here's what I did:
1. TWRP factory reset THEN I went back and wiped /system
2. Flash Chroma, gapps, supersu 2.65
3. wipe dalvik & cache (not sure if it's necessary but I did)
4. reboot
This seemed fine. Chroma booted up, no app crashes. Now I wanted to flash elementalx. Heres where I was working off mixed knowledge but decided to do it this way.
1. wipe dalvik cache
2. flash chroma, gapps, elementalx
3. wipe dalvik cache (yes. Once more to be sure)
***Im not sure the above is the textbook method BUT it worked. I booted into chroma, elementalx was present and working like it did with pure nexus. For about an hour or so I used the phone, making no changes at all in elementalx. It was getting late. I plugged in my phone and fell asleep. When I woke up 7 hours later it had rebooted and was stuck in bootloop. I tried forcing a reboot. It looked like it was going to work (reaching the "optimizing apps" part) but then just continued to loop. Flashed my pure nexus backup and Im up & running again.
I know the exact cause is nearly impossible to diagnose without a log and I don't have one. Im just looking for some guidance from users with more experience. If you were running pure nexus and elementalx, and you want to try a new rom like Chroma plus elementalx, how exactly would you proceed? Thanks
Click to expand...
Click to collapse
Ok. Like I said it was late. I just remembered I did install an xposed mod and it could've (probably) caused the bootloop. Though if it did it was done through a random reboot. I usually get out of that predicament by going to twrp and deleting the modules list.
But if ANYONE sees a mistake in the above flashing procedure(s) please alert me. While we’re here Id also like verification Im using the correct xposed version. I have v83sdk23 arm64. And Im not the most experienced guy when it comes to flashing kernels so if you have any tips Im eager to learn. Thanks again.
Hello Guys
So i was trying to update my rooted Decrypted Nexus 6P from 7.0 to Developer preview 7.1 .
I followed the instructions to flash the OTA zip and then root it with SuperSu (http://forum.xda-developers.com/nexus-6p/general/available-android-7-1-developer-preview-t3483739).
I then flashed Franco's latest kernel as I usually end up doing that. The phone booted fine, but of course the camera had some problems as reported here (http://forum.xda-developers.com/showpost.php?p=69226309&postcount=373) which meant that the Franco kernel was at 7.0 and I needed 7.1 kernel.
So stupidly enough I just extracted the boot.img from the 7.1. OTA zip and flashed it through flashify app to revert to stock kernel for 7.1 and just re-started my phone.
But since that boot img was not patched it forced encryption on the phone which I did not realize until I found the phone was sitting at the boot animation for a long time and I just force re-started it.
Wrong decision . Now I have a phone that boots up to a screen which says Encryption Unsuccessful and has a button which asks me to wipe all the data.
Booting into TWRP asks me password for decrypting the data partition which I assume would be my PIN and supply it, but it sits on message saying 'Decrypting data' and just sits there endlessly. I have tried this as well (http://forum.xda-developers.com/showpost.php?p=66163153&postcount=826) i.e. trying the 3.0.0.1 twrp but that one does not like the PIN that I supply.
I followed this (http://forum.xda-developers.com/verizon-htc-one-m8/help/decryption-unsuccessful-currently-t3074855) to extract the whole data partition from my phone and essentially I have this 58 GB file which i tried to mount in Linux but unfortunately there is nothing that i see in that partition.
Is there anyone who has encountered this and has successfully retrieved their data??? I know it was stupid of me that I didn't take a backup of my internal storage plus the nandroid backup I had is on the phone .
Any help is much appreciated.
Thanks
Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.
Try flashing the safetynet fix in trwp.
triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)
I've decided to unlock bootloader, get a custom recovery and root my new LG G6 H870, so I've downloaded Melina TWRP v321 and Magisk v16.
Unlocking went well, then I downloaded drivers, unlocked debugging, "adb reboot bootloader" -> "fastboot flash recovery twrp.img" -> unplug usb -> boot into twrp by pressing volume down + power (with a tap) -> some weird screen about encryption popped up, but I clicked through -> and then I proceeded to install Magisk straight away, cause this guide said it'd not let TWRP stick if I didn't. After that I tried to boot into system and start the real fun. But it booted me back into TWRP. Again and again.
From there, I've tried Wipe -> Factory Reset, Wipe -> Advanced Wipe -> Repair File System for Data and System, Wipe -> Format Data, Advanced -> Fix Contents, but it all ends with twrp boot... I'm completly lost at this point. I've flashed/rooted a few phones before, but this one... it's a real nightmare.
I've also tried flashing a stock kdz (the filename is "H87011i_00_EEO_GB_OP_0108.kdz" for anyone wondering) through LGUP and redoing this stuff, but I end up with the same result. Please advise how to get it working.
Did you use uppercut when you flashed the kdz file? This is needed to successfully flash back to stock.
Seems it didn't work correctly.
basicreece said:
Did you use uppercut when you flashed the kdz file? This is needed to successfully flash back to stock.
Seems it didn't work correctly.
Click to expand...
Click to collapse
Yes, I did flash through Uppercut (v1).
Since this thread started I flashed it once again, but this time I tried installing official TWRP v321. There was no weird encryption screen, but there were a lot of msgs (when installing magisk or doing a backup, for example) about being unable to unmount /system because it was being used. I did manage to install Magisk though and boot up the phone, but then when I tried installing Xposed, the phone went into another weird loop... but this time, it would get stuck on LG screen and it'd start heating up very fast. It stops heating when I restart using volume down + power into recovery. But I'm once again stuck... this is incredibly annoying, are aall LG phones like that?
How you installing xposed?
Install it via magisk module.
I had no issue.
Unlocked BL
Flashed Zefie TWRP (most stable and backups work)
Flashed fulmics
Flashed Magisk
Wiped cache and dalvik.
Reboot.
Works fine and flashed this over 15 times now no issues ever.
basicreece said:
How you installing xposed?
Install it via magisk module.
I had no issue.
Unlocked BL
Flashed Zefie TWRP (most stable and backups work)
Flashed fulmics
Flashed Magisk
Wiped cache and dalvik.
Reboot.
Works fine and flashed this over 15 times now no issues ever.
Click to expand...
Click to collapse
Did you also have that weird encryption message when flashing Zefie TWRP? Could you be more specific about your way? As in, you wiped cache/dalvik only once or after every flash? Did you wipe anything else? And yeah, I've just downloaded Fulmics and I'm at the installation screen, but I clicked System Information and it says my Storage Size is 5417MB with 104MB free... it reads SDCard Size correctly though. Should I be worried?
Starting from fresh, out the box.
Unlocked bootloader.
Installed Zefie TWRP.
Then added fulmics zip to sdcard.
Flashed zip, followed on screen instructions.
Wiped dalvik and cache.
Rebooted.
Takes a few minutes.
Boots up and done.
Magisk was packed into fulmics when installed.
I do NOT touch xposed. Too many issues plus I need safetynet for Google pay.
Yeah, I pretty much flashed stock firmware back and then followed basicreece instructions, along with flashing Fulmics, but I've got the 'official' Twp (v321). And everything's working so far, but I didn't touch Xposed so far though since Fulmics had pretty much all I wanted from Xposed. Word of advice for future readers though: don't bother staying on stock, too many problems. Fulmics is basically stock, but with some really neat options, and a ton of bugs and problems less.