Hello guys
After running cm13 without nog problemen for over a month I got an update today and installed it as usual (using cwm). However I also run ElementalX custom kernel. When you install a new version of Cyanogenmod it flashes it's own kernel over the custom kernel. Normally I would flash the cm update, wait for it to finish, reboot into recovery again and then flash ElementalX. However today I tried to flash ElementalX directly after installing the cm update. It reboots like normally and all the hardware works but my screen is not responding. I have tried installing a backup, wipe user data , dalvik cache etc but nothing is working. Can one of you help me?
Nexus 5
Cyanogenmod 13
ElementalX
ClockWorkMod
Related
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?
Hello everyone,
I tried installing a custom ROM on the Nexus 5 for the first time last night. (Note: I've installed ROM's for years on different phones.)
It seems as though there is a problem with the official CWM recovery 6.0.4.4.
I found that wiping data/factory reset and formatting system did not actually get the phone ready for a custom ROM.
After doing this and installing the custom ROM, all my APPS and settings were still installed. Android went through the process of "Upgrading Apps" instead of walking we through a new install.
Thanks!
Greg
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Spartiata said:
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Click to expand...
Click to collapse
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Lethargy said:
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Click to expand...
Click to collapse
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Spartiata said:
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Click to expand...
Click to collapse
Not sure what to tell you except try another ROM first.
Lethargy said:
Not sure what to tell you except try another ROM first.
Click to expand...
Click to collapse
i'll try with paranoid and let you know
Paranoids works fine, seems like a CM problem .-.
Spartiata said:
Paranoids works fine, seems like a CM problem .-.
Click to expand...
Click to collapse
CyanogenMod will always be CyanogenMod
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
visclo49 said:
Hi mates.
So, I was running CM12 nightlies on my phone but it began to get slow and buggy.
I decided to go back to stock 4.4.4, ans then flash CM11 on dit
I did full wipe (data, system, cache, dalvik), installed stock 4.4.4 (latest official build)
Then i downloaded CM installer but couldn't get it to work.
So I used Nexus foot toolkit on PC, but the flashing process went wrong somehow, just when it reboots the phone to recovery, nothing happened, no flashing process whatsoever.
From this moment, my problem had appeared
So I rebooted normally, downloaded CM11 and I was unable to flash it. Signature check failed.
I've tried OTA 5.0.1, not working either, same error.
So I am currently running latest 4.4.4 without any problem, but even after an other full wipe I'm not able to flash anything, custom or stock. My recovery is the latest TWRP from the Google play app.
Could you please help me ? I don't mind wiping my phone, and I'd prefer a "no PC" solution but I still can use a PC if needed.
Thanks
Click to expand...
Click to collapse
stop using toolkits, learn something for a change
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try using the base rom as v5.6.11 and try using the old twrp v2.8.7
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Try provide with a logcat, might be more useful in helping you.
No other custom rom is working on my mi4i
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..?
sabujkvkm said:
Hi,
Phone not responding after some minutes . only black screen no "wake up" on anyway. need to forcefully restart.
Currently i am using SlimBit [6.0.1_r12][AOSP][LAYERS][11-Feb]
also tried Resurrection Remix v5.6.3 Marshmellow
Installed using TWRP v3.0 Recovery by clean slate (Wipe Data/System,cache,dalvic including internal storage data)
also installed from MIUI v6.6.10 base version also.
Same problem rises again and again in all CM,ASOP version i installed.
Only without "GAPPS " i can use my device for few Days.
Is that any correct installation method, other than described in each rom thread.???
I need Big help....
Thanks
Sabu John
:crying::crying::crying:
Click to expand...
Click to collapse
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
astro49 said:
I have same issue. Nandroid backup of CM12, Mowkee, Resurection does not successfully load anymore. While the MIUI 7 v7.1.1.0 nandroids still load with no problem. I used to load my other custom rom nandroid with no problem. I did also install the new ver3 TWRP but tried reverting back to Magdag Mi4i TWRP but still same issue.
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you restore your nandroid backup like CM12, Mowkee, Resurection if you from new MIUI ROM.
If you want to restore MIUI7 nandroid backup from CM12 you need to flash MIUI7 patch ROM first.
RIYAN X55TU said:
After clearing the system data cache . . I installed cm13 using twrp by maddag...after successfully installed the rom and gapps when it finishes boot and the welcome screen appears then its stuck in the welcome screen for 5secs then reboots them after booting up again on welcome screen again restarts..it is happening every time.. So I installed cm12 and after finishing boot...again same problem so I reverted back to miui by installing the rom via fast boot by mi pc suite and it booted successfully without any problems.. And in miui rom my mob laggs too much and the benchmark in antutu is 29000...I think I need to replace the mobile phone..still 2 months warranty remaining..
Click to expand...
Click to collapse
Don't forget to flash MIUI V.6.6.6 (or V.6.6.6 patch ROM) first before you flash to CM13, if not you'll get bootloop. If you use default init.qcom.post_boot.sh and your phone heat up it will lags, so use edited init.qcom.post_boot.sh.
Confirmed
Glembozt said:
Try use old TWRP, if you got hard error flash MIUI V6.6.6 first.
Click to expand...
Click to collapse
I can confirm that this DID magically works!
No need to use the old TWRP, just flash MIUI V6.6.6(I used the fastboot package[1], not sure if recovery package works) then flash TWRP then flash other custom OSes.
[1] bigota.d.miui.com/V6.6.6.0.LXIMICF/ferrari_global_images_V6.6.6.0.LXIMICF_20150521.0000.3_5.0_global_46b5474265.tgz