Hi all!, 'cause I'm "new" in this forum I can't post in the development section of this rom but my problem is that when I try to install it in CWM and the aroma installler it installs but afterwars I get a Boot loop in my Nexus 4, any one with the same problem?
Cheers!
try doing full wipe...
Try doing full wipe first if u have not done so.
It boots just fine with me.
zbz999 said:
Try doing full wipe first if u have not done so.
It boots just fine with me.
Click to expand...
Click to collapse
Already done it, same result, even format SD/System same problem!
Any other idea?
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
lackyking said:
I got the logcat here: http://paste.ubuntu.com/6076817/
The device platform is APQ8064.
PLEASE HELP ME!
Click to expand...
Click to collapse
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
simms22 said:
grab the last good nightly and flash it. push it to your device via your recovery and adb sideload.
Click to expand...
Click to collapse
I tried, but also stopped on the first screen of manufacture logo.
lackyking said:
I tried, but also stopped on the first screen of manufacture logo.
Click to expand...
Click to collapse
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
simms22 said:
well, you can always flash the factory img, if nothing else works. did you wipe data when flashing a known good nightly?
Click to expand...
Click to collapse
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
lackyking said:
Yes, I can also flash the stock rom.
but I want to solve the problem for my built rom.
and I had wiped the data & cache.
Click to expand...
Click to collapse
youre not the only one that the latest cm code isnt booting up on.. http://forum.xda-developers.com/showthread.php?t=2435980
ROM: Cloudy G3 2.0 (already posted in his thread)
Recovery: Team Win recovery v2.7.0.0
Whenever I attempt to Full Phone Encrypt it will reboot and stay at 0%. I've tried it a few times now.
It will let me reboot back to the OS so it's not even doing anything.
Due to Recovery/rom? I'd like full encryption...
Thanks for help.
@Unoid I think its the rom, but I am not sure about recovery. Also remember that if encryption fails during encrypting then bad things happen to your data. And also if you are flashing much roms then I suggest to not to encrypt, just use an password.
What stable rom will work with encryption?
I'm in the same boat -- encrypting stays at 0% and rebooting starts up normally like nothing happened. Any luck finding a stable ROM where encryption works?
Unoid said:
What stable rom will work with encryption?
Click to expand...
Click to collapse
boffo123 said:
I'm in the same boat -- encrypting stays at 0% and rebooting starts up normally like nothing happened. Any luck finding a stable ROM where encryption works?
Click to expand...
Click to collapse
Did you guys ever find a ROM that will work with encryption?
bamachevrolet said:
Did you guys ever find a ROM that will work with encryption?
Click to expand...
Click to collapse
I went back to the stock KitKat ROM. I'd still be interested in hearing if anyone gets encryption working on a custom ROM though.
I would be very interested to know a custom AOSP ROM with Encryption as well. I know it works for other phones. Is it specific to the kernal?
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Shinuki said:
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Click to expand...
Click to collapse
Nobody reporting that's kind of issue .I am using RR and Tesla and no problem.
Do clean flash and use pico gaaps.If problem exists then post on the specific ROM thread with ramoops and kmsg file ,so experts can help with reboot isuue.
Had the same problem while on AOSP EXTENDED, the rom is god damn smooth, just the freezes and the random reboots make it clear that Boi, u need to change the rom, NOW!😂😂😂
Shinuki said:
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Click to expand...
Click to collapse
I had faced random reboots with most of N roms. Try changing the kernel.
adithbalan said:
I had faced random reboots with most of N roms. Try changing the kernel.
Click to expand...
Click to collapse
I've tried this, but the LateAutumn project kernel always causes bootloops.
i-AM-BoReD said:
Nobody reporting that's kind of issue .I am using RR and Tesla and no problem.
Do clean flash and use pico gaaps.If problem exists then post on the specific ROM thread with ramoops and kmsg file ,so experts can help with reboot isuue.
Click to expand...
Click to collapse
To be honest, I've seen a few people reporting the same issue. Already flashed with pico gapps, same problem. It happens with literally all Android 7+ ROMs I've seen here, including RR and Tesla. I'll just try to get the logs, thanks.
Ronnie.mac94 said:
Had the same problem while on AOSP EXTENDED, the rom is god damn smooth, just the freezes and the random reboots make it clear that Boi, u need to change the rom, NOW!😂😂😂
Click to expand...
Click to collapse
I had that problem in AOSP-OMS, Extended, RR, Tesla, CM 14.1... nothing seems to work now. But thanks anyway
@Shinuki get the logs and post to LA thread in detail. You're bootloader may be the root of the problem, which if is the reason, then is not upgraded to LP bootloader. Post dmesg and ramoops there.
iamsubhranil said:
@Shinuki get the logs and post to LA thread in detail. You're bootloader may be the root of the problem, which if is the reason, then is not upgraded to LP bootloader. Post dmesg and ramoops there.
Click to expand...
Click to collapse
Got it, but if that's the case, how can I upgrade bootloader? I flashed the MIUI 5.1 ROM recently and still got same issues
iamsubhranil said:
@Shinuki get the logs and post to LA thread in detail. You're bootloader may be the root of the problem, which if is the reason, then is not upgraded to LP bootloader. Post dmesg and ramoops there.
Click to expand...
Click to collapse
I have the same issues and I can't report becouse I never did a dmesg and a ramoops, I can't find how to do it on google, nobody told me, I know the ramoops command, but where I type it? twrp? or in the PC? becouse it keeps bootlooping and restarting
---------- Post added at 17:56 ---------- Previous post was at 17:56 ----------
Shinuki said:
Got it, but if that's the case, how can I upgrade bootloader? I flashed the MIUI 5.1 ROM recently and still got same issues
Click to expand...
Click to collapse
Is your device model 2014819?
TecnoTailsPlays said:
I have the same issues and I can't report becouse I never did a dmesg and a ramoops, I can't find how to do it on google, nobody told me, I know the ramoops command, but where I type it? twrp? or in the PC? becouse it keeps bootlooping and restarting
---------- Post added at 17:56 ---------- Previous post was at 17:56 ----------
Is your device model 2014819?
Click to expand...
Click to collapse
Yeah, it is. From Brazil, to be specific.
Shinuki said:
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Click to expand...
Click to collapse
Signal Strength is good? In Android 7 signal issue is there , reboots occur when there is low or less signals
adithbalan said:
I had faced random reboots with most of N roms. Try changing the kernel.
Click to expand...
Click to collapse
Try to super clean flash. Wipe system > data > cache and dalvik. Reboot recovery and flash the roms.
ntoetsoekarno said:
Try to super clean flash. Wipe system > data > cache and dalvik. Reboot recovery and flash the roms.
Click to expand...
Click to collapse
I always clean flash, still same issue
Shinuki said:
I always clean flash, still same issue
Click to expand...
Click to collapse
Clean flash is only wipe data, cache and dalvik. Try to wipe system too, DON'T FORGET TO REBOOT RECOVERY FIRST before flash roms.
Try flashing pico or nano gapps...:good:
ntoetsoekarno said:
Clean flash is only wipe data, cache and dalvik. Try to wipe system too, DON'T FORGET TO REBOOT RECOVERY FIRST before flash roms.
Click to expand...
Click to collapse
Sorry. I always super clean flash and reboot to recovery.
udayjindal said:
Try flashing pico or nano gapps...:good:
Click to expand...
Click to collapse
I already tried both, no luck.
I honestly don't know what the issue is. A CM 14.1 ROM from October wasn't giving me this issue; same for 6.0 ROMs.
I was on project Alice rom when suddenly after deleting an app, things were crashing so a restarted my phone. It wouldn't boot up. I went into recovery and tried flashing the rom again and it just says could not mount /system. I tried everything, full wipe, format data, still nothing.
I'm on SM-G935F
Please help,
Bump. Please I really need help. If anyone knows what to do, or knows anyone that might know, please tell me, I need my phone functioning ASAP.
.Monkey said:
Bump. Please I really need help. If anyone knows what to do, or knows anyone that might know, please tell me, I need my phone functioning ASAP.
Click to expand...
Click to collapse
Try mount system from twrp
mashardpro said:
Try mount system from twrp
Click to expand...
Click to collapse
I've tried that but no luck. I have tried so many things. I flashed a new ROM and it seemed to work though, even though the ROM I was using was working perfectly for about a week before that happened. Looks like it just decided to not work on my phone anymore :/
.Monkey said:
I've tried that but no luck. I have tried so many things. I flashed a new ROM and it seemed to work though, even though the ROM I was using was working perfectly for about a week before that happened. Looks like it just decided to not work on my phone anymore :/
Click to expand...
Click to collapse
Flash the official firmware, but you will lose twrp and root (you can install later)
.Monkey said:
I've tried that but no luck. I have tried so many things. I flashed a new ROM and it seemed to work though, even though the ROM I was using was working perfectly for about a week before that happened. Looks like it just decided to not work on my phone anymore :/
Click to expand...
Click to collapse
Try to mount it in another format.
Had the same problem. mounted it in another format and changed back to EXT4 after it in TWRP.
Worked without problems.
Pet1981 said:
Try to mount it in another format.
Had the same problem. mounted it in another format and changed back to EXT4 after it in TWRP.
Worked without problems.
Click to expand...
Click to collapse
I tried that, still didn't work. Other ROMs work, it's just that one for some reason could not mount system. No one else is reportedly having the issue with that ROM.