Im on 38R stock rooted encrypted . today i flashed franco r30 kernel and after the decrypt prompt my phone is not loading anything.
Please tell me how to go back to stock or how to fix my issue.
i fixed the issue by formatting in twrp.
So franco doesnt support encryption ?
i lost data though... Anyway to fix it...
Related
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?
sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do
about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks
and to clarify , it was gapps 4.2.2
Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.
If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app
i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .
You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.
actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.
i figured out twrp. never gave it achance. ill see if that does the trick
tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks
Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
kevinga said:
My OPO is rooted and I have TWRP installed. I think I now may have a file or two that has been corrupted and I would like to reflash the CM11s rom. I ran the CM11 nightlies on my LG G2 and that was always a fix to get the files back where they should be.
Is there any reason why I can't dirty flash this http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH25R-bacon-signed.zip with TWRP?
Click to expand...
Click to collapse
So just to make sure I understand this correctly you just want to know why you cant dirty flash CM11s rom over itself. First off you can dirty flash all you want but the issues you may or may not get are on you. Now may I suggest your wipe system when dirty flashing with TWRP. I check off dalvilk, cache and system whenever I upgrade or dirty flash.
Also this is still android and most if not all of the flashing rules still apply
The problem I have is with wifi. This developed a couple of days ago where I have to toggle airplane mode on/off before wifi will reconnect. I actually did a factory reset last night and it did not fix it. I am now thinking that I will need to do more. I suppose the wifi is monitored by the kernel? baseband? I am not sure that a factory reset would reset those things. I could be wrong.
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
I've been running Cataclysm + Franco Kernel for a little while now, and it's been a pretty pleasant experience. Well, I decided to make the jump and see what all the hype about ElementalX is - this didn't end in my favor.
After making backup of my current ROM/Kernel in TWRP, I flashed the latest version of ElementalX. Upon rebooting, I'm greeted with a never-ending loop between a black screen and the Google/Unlocked Bootloader screen.
I promptly restored from my backup inside of TWRP. Unfortunately, The same thing happens with the regular and express ElementalX packages. Is there something I'm missing? I really want to try out this kernel...
AppleGeek911 said:
I've been running Cataclysm + Franco Kernel for a little while now, and it's been a pretty pleasant experience. Well, I decided to make the jump and see what all the hype about ElementalX is - this didn't end in my favor.
After making backup of my current ROM/Kernel in TWRP, I flashed the latest version of ElementalX. Upon rebooting, I'm greeted with a never-ending loop between a black screen and the Google/Unlocked Bootloader screen.
I promptly restored from my backup inside of TWRP. Unfortunately, The same thing happens with the regular and express ElementalX packages. Is there something I'm missing? I really want to try out this kernel...
Click to expand...
Click to collapse
Did you reflashed your Cataclysm rom before flashing ElementalX? It could be some incompatibility between those kernel. Maybe try to format your boot partition and flash it with the default boot.img present on Cataclysm zip file. Then ElementalX has to work since I'm running Cataclysm + ElementalX. Just in case, did you changed your /data or /cashe filesystem format?
the same situation here.
i did everything that i can do. wiping everything and full clean flashing include.
Use an older version of twrp maybe?
nunojsa said:
Did you reflashed your Cataclysm rom before flashing ElementalX? It could be some incompatibility between those kernel. Maybe try to format your boot partition and flash it with the default boot.img present on Cataclysm zip file. Then ElementalX has to work since I'm running Cataclysm + ElementalX. Just in case, did you changed your /data or /cashe filesystem format?
Click to expand...
Click to collapse
Yes. I've tried flashing the kernel after doing a factory reset, wiping cache/dalvik, and refreshing Cataclysm. I've even tried flashing the kernel over the Nexus 5 stock Android 5.1 ROM, no dice. I'll try flashing the boot.img when I get home.
Update: Flashing the boot.img from the Cataclysm .zip via Fastboot had no effect on anything. Also, I haven't tinkered with the filesystem of my /cache or /data.
AppleGeek911 said:
Yes. I've tried flashing the kernel after doing a factory reset, wiping cache/dalvik, and refreshing Cataclysm. I've even tried flashing the kernel over the Nexus 5 stock Android 5.1 ROM, no dice. I'll try flashing the boot.img when I get home.
Click to expand...
Click to collapse
try flashing the image from googles developer page to end the boot loop
Pranjal53 said:
try flashing the image from googles developer page to end the boot loop
Click to expand...
Click to collapse
I have a backup in TWRP that I can always restore from, so I'm not stuck in a boot loop. Thanks for the suggestion though.
flar2 said:
Use an older version of twrp maybe?
Click to expand...
Click to collapse
I'll try it, thanks so much. Edit: Flashing Cataclysm/ElementalX using TWRP v2.6.3.4 solved the problem. Thanks so much, it's great to see you interacting with the community