I'm sorry if this is something stupid i did wrong. I just got myself the Nexus 7 (2013) and i put cm.11 on it almost as soon as i got it, but i found there was something wrong when i tried to change to any different ROM. If i use any other ROM than cm.11 (I've tried Omnirom, Parandroid, and Dirty Unicorns.) The ROM completely reboots the system any time i try to use an app. I was wondering if anyone else has had this problem or if there are any fixes for the issue.
I use the latest TWRP custom recovery.
There is already a thread about random reboots. Many people have this issue. It seems to be prevalent to the 16gb version of this tablet, while the 32gb doesn't suffer the same fate.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
aarsyl said:
There is already a thread about random reboots. Many people have this issue. It seems to be prevalent to the 16gb version of this tablet, while the 32gb doesn't suffer the same fate.
Click to expand...
Click to collapse
Are you using the correct kernel after changing from CM? Kernels for CM based roms and kernels for AOSP based roms don't play nicely with the other rom type for the most part.
Related
For some odd reason I cannot flahs any custom kernels. Whenever I flash some rom, the included kernel will work just fine. But if I flash another one, like franco or matr1x, I end up in bootloop, or stucks at boot. Anyone else experienceing this behaviour?
You need to make sure you flash a kernel that is built for the version of android you are using.
For example ARHD 2.1.1 is 4.0.2 so you can not use the Matr1x v1.5 kernel because it is built for 4.0.3
Always read the OP before flashing, the info is there
Edit: messed up my version numbers
Sent from a phone that is not running ICS
I have the same problem - no matter what kernel I use or how I try to install it I have yet to find one that will work with a stock version of ICS 4.0.2 on my phone - they always freeze at the boot screen, I don't get any further.
I have indeed checked versions before flashing.
Sent from my Galaxy Nexus using xda premium
[XXLE4]Issue with custom kernel - disturbing reboots
Hi everyone,
I am facing an huge issue that make me unable to flash any custom kernel without rebooting.
I though it was because brand new XXLE4 cannot support 1k+ frequencies or may be another things than I could not have been imagine because of my poor informatic and linux knowledges but it seems that i am just unable to flash custom kernel. only the original CF-ROOT doing his job but others aren't.
May be because of the SetCPU apps but it is less sure that the origin take his effect from that apps. It is a quit anoying because I would have been set my Scary 120 - 1350 to get an impressive battery life with the brand new UC-Kernel but seems to be a mirage for me.
I had got some custom roms but I can't just use them because I want an real free-bugs ROM an official release are the only one option for me and my usual usage.
Thanks in advance for the help provided and I apologies for my bad english.
maybe EXT format?
Chaw Rash said:
maybe EXT format?
Click to expand...
Click to collapse
Could you please rephrase it in others "newbie's words" ? Didn't get what's EXT format.
Forgave my poor knowledge and my english.
crfrank said:
I have the same problem - no matter what kernel I use or how I try to install it I have yet to find one that will work with a stock version of ICS 4.0.2 on my phone - they always freeze at the boot screen, I don't get any further.
Click to expand...
Click to collapse
4.0.2? I believe no custom kernels support 4.0.2 anymore. Updated/latest versions of said custom kernels at least. I think franco has a 4.0.4 version of his though i'm sure very few people are on 4.0.4, 4.0.2 is just a thing of the past.
tristan202 said:
I have indeed checked versions before flashing.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
How are you flashing kernels? What recovery do you have installed?
Drakenlord78 said:
Hi everyone,
I am facing an huge issue that make me unable to flash any custom kernel without rebooting.
I though it was because brand new XXLE4 cannot support 1k+ frequencies or may be another things than I could not have been imagine because of my poor informatic and linux knowledges but it seems that i am just unable to flash custom kernel. only the original CF-ROOT doing his job but others aren't.
May be because of the SetCPU apps but it is less sure that the origin take his effect from that apps. It is a quit anoying because I would have been set my Scary 120 - 1350 to get an impressive battery life with the brand new UC-Kernel but seems to be a mirage for me.
I had got some custom roms but I can't just use them because I want an real free-bugs ROM an official release are the only one option for me and my usual usage.
Thanks in advance for the help provided and I apologies for my bad english.
Click to expand...
Click to collapse
I'm sorry, i dont know any LE4 bb or bl version, nor a CF-ROOT kernel? These are the Gnex forums.
sent from my i9250
Hi,
I've purchased a a Samsung Galaxy 551 (I5510) (Middle east region) about a year ago and i was running android 2.2 fine for a while. When the Gingerbread 2.3 update came out i tried installing a European ROM because the ME ROMs weren't updated, it worked fine but had a weird glitch that if the screen was off (phone still working) for a while it would be very dark when turned on afterwards, it looked like this video:
http://www.youtube.com/watch?v=Kwll8ZfgaD0
P.S. I didn't make the video, just linking it because its the same issue
it would randomly work again after a couple of lock-screen off-unlock cycles, then happen again randomly when it's off
I tried a number of GB ROMs (mostly 2.3.4) but to no avail, then finally the latest EU ROMs (I5510XWKPJ) fixed the problem, nowhere to be seen anymore.
After that i tried installing Cyanogen mod for the phone and the problem came back with different degrees:
1. Cyanogen 7 - normal boot, screen gets dark after being off for a while.
2. Cyanogen 9,10 - show Samsung logo at start, screen gets dark as soon as the cyanogen logo appears and continues to be
Any help on what would be causing that especially on the newer CM builds? and why it doesn't happen at all in (I5510XWKPJ)
Thanks in advance,
use stock gb rom XEO-KPG from here...u find no bug in it....install as one pakage through odin...
http://galaxy551.wordpress.com/2011/12/20/new-stock-rom-xeo-kpg/
I will give it a try, though i have to clarify and say that on the current stock rom that i'm using (I5510XWKPJ) the problem doesn't happen. It only happens after i flash Cyanogenmod (any version) and persists till i reflash the Stock rom then it disappears again.
EDIT: Forgot to add that this isn't a CM specific bug as it happened also when i tried other roms too (Arkas, Miui,...)
You cannot say that this is a bug bcaz no other mamber of galaxy 551 and even me also not have this kind of problem....
So I think its problem of ur phone...
Sent from my GT-I5510 using xda premium
No change after installing (XEO-KPG) stock rom, the rom itself works fine with no problems, same as the (XWKPJ) I've been using. but as soon as i install CM the bug rears it's ugly head.
priyesh103 said:
You cannot say that this is a bug bcaz no other mamber of galaxy 551 and even me also not have this kind of problem....
So I think its problem of ur phone...
Sent from my GT-I5510 using xda premium
Click to expand...
Click to collapse
The reason i think it's a bug because it happens across lots of custom roms (which rules a rom being the cause) and it never happens when using the 2.3.6 stock roms. And on the custom roms it only happens after the screen has been off for a while, if i set the screen to never turn off for instance it never happens, but that butchers battery life.
IMO it might be a display driver issue, but since i have no experience with it i came here to get some help
Bump, any help would be appreciated.
So I've done some searching in the forum (on phone) and wondered if anyone else is having an issue flashing roms other than stock rooted.
I've tried all kinds of other roms cm, miui, liquid smooth, et cetera, and they all get stuck at boot. This is a new thing because I've run all these roms in the past.
I'm on moar 6.1 and it's a great Rom, but I'd like the option to change roms at some point...
You are naming AOSP roms. If you have a newest S3, please try with an updated version. Start with SlimBean build 2( exactly that one) because it's confirmed to work with newest models.
Sent from my SPH-L710
csmasn said:
You are naming AOSP roms. If you have a newest S3, please try with an updated version. Start with SlimBean build 2( exactly that one) because it's confirmed to work with newest models.
Sent from my SPH-L710
Click to expand...
Click to collapse
Dude....it wasn't the ROM's fault at all, nor the phone's....it was the loose nut behind the wheel....me.
I forgot (have been forgetting) to format data. For whatever reason, I was manually formatting just the minimums. DANGIT! Works like a charm now...or rather I'm working like a charm now.
Thanks anyway.
I'm trying to flash the AT&T Google Play Edition HTC One M8 ROM onto my phone. I'm coming from the CyanogenMod nightlies. I really do love CyanogenMod and all its extra features, but with all the bugs included in the nightlies (which is too be expected) and the lack of BoomSound and HTC's Ultrapixel camera, it seems pointless.
The problem is, after doing a factory reset in ClockWorkMod Recovery, I try to flash the ROM, and it says "Status Error 7." Any idea how to fix this?
I can't really answer your question but I have noticed that error 7 when trying to flash a ROM or two. What I found is that changing to a earlier ROM or redownload the ROM helped me. I had issues with Liquidsmooth and MIUI and waited for a new release of those Roms and it worked. Just a thought.
Sent via electrical potential to your device. HTC One M8 - MIUI V5 rom
frankieworld said:
I can't really answer your question but I have noticed that error 7 when trying to flash a ROM or two. What I found is that changing to a earlier ROM or redownload the ROM helped me. I had issues with Liquidsmooth and MIUI and waited for a new release of those Roms and it worked. Just a thought.
Sent via electrical potential to your device. HTC One M8 - MIUI V5 rom
Click to expand...
Click to collapse
Or something as simple as updating CWM
BerndM14 said:
Or something as simple as updating CWM
Click to expand...
Click to collapse
I tried that, in my case, including downgrading and also using TWRP and never worked for my case. That's what made life frustrating as a noob like myself that's learning on XDA...
Sent via electrical potential to your device. HTC One M8 - MIUI V5 rom
frankieworld said:
I tried that, in my case, including downgrading and also using TWRP and never worked for my case. That's what made life frustrating as a noob like myself that's learning on XDA...
Sent via electrical potential to your device. HTC One M8 - MIUI V5 rom
Click to expand...
Click to collapse
That's what makes it fun though... :good:
BerndM14 said:
That's what makes it fun though... :good:
Click to expand...
Click to collapse
That's true.. Spent this whole weekend and the last and the one before that flashing, s-off and other good stuff.. I think I need help, I have a flashing addiction lol
Sent via electrical potential to your device. HTC One M8 - MIUI V5 rom
Get an iPhone no more flashing[emoji12]
I apologize if this is explained elsewhere, did a search but not coming up with much:
I'm somewhat new to Android rooting. I have a Verizon M8 that was on 4.4.4. I installed Sunshine 3.02, got root no problem, TWRP installed with no issues, SU installed fine. I tried to run a few of the Lollipop ROMs but they would not run, I jut got returned to TWRP. (Some, like ViperOneM8 run fine). According to a post in another thread, I also need to update the kernel to get it to work with these newer ROMs.
My question is: what now? There's a section on XDA for Kernels but they all appear to be custom kernels, the ROM I want to use (Android Revolution) says that using the stock kernel is best. How do I find these kernels and how do I figure out which one to use?
Anyone willing to give me the short version of when I would need a new kernel and why?
Thanks for any help!
You need to update to Lollipop firmware.
You should also make sure you stick to ROMs that specifically support the Verizon variant (if you are not doing so already) as its a CDMA variant, which is different hardware from most other (GSM) versions.