Hey, guys
so i tried to flash the minco rom.
which worked fine but when i flashed the bricked kernel
it was stuck on the google logo for ages.
Is there anything wrong with my download?
or is the kernel not compatible?
I thought one of the main features of MinCo is Franco kernel and you are saying that you flash another kernel... Why not using another rom then?
To your question, how about flashing a reset kernel first then the bricked one?
Sent from my Nexus 4 using xda premium
lazinase said:
I thought one of the main features of MinCo is Franco kernel and you are saying that you flash another kernel... Why not using another rom then?
To your question, how about flashing a reset kernel first then the bricked one?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
it is i guess, i just wanted to try out the sweep2wake feature.
just got the phone today, so not too sure about which rom to choose.
any suggestions?
cool ill try a reset kernel
Restore your latest nandroid backup
if you want you can use rasbean jelly. its like minco v6 but optimized for trinity kernel. im using minco though. flash a reset kernel first then flash your own kernel of choice since franco kernel uses a different ramdisk then the other kernels i believe
Hey guys I just rooted and installed a few custom ROMs on my n4. When I install a custom 4.3 kernel on any 4.3 ROM I get ridiculous flickering issues. It never happened on stock and only happens on custom ROMs when flashing another kernel. Am I missing something obvious? I have searched for an answer but have come up empty. Any help would be appreciated cuz I really would like to run Franco or faux ( my two favs from my Gnex days). Thanks a lot guys
Edit: sorry I meant to put this in q and a mods feel free to move
Sent from my Nexus 4 using xda app-developers app
Flash the proper kernel for you ROM hint there are two different builds for 4.3
Sent from my Nexus 4 using xda premium
I did flash the correct kernel. At least I think I'm running cm 4.3 (jss15j) and I tried flashing faux's latest 4.3 kernel. If that is for some reason incorrect which faux or Franco would u recommend?
Edit. Ahh I see what u mean by two different builds. Thanks I thought there was only one build on 4.3
Sent from my Nexus 4 using xda app-developers app
I'm a noob to tables but have done many flashes to my phones. My main question is, I'm rooted and ready to flash a ROM to my Nexus 7 but I'm confused about a few things. I'm running firmware 4.3 so do I need to flash a ROM that's made for 4.3? I'm interested in the Carbon ROM but it doesn't state that it for 4.3.
I'm interested in a stable ROM that has a lot of customizing options. Any suggestions?
Thanx in advance for helping out a Noob!
Sent from my Nexus 7 using Tapatalk 2
ROM = Firmware
Flashing ROM = Flashing different Firmware
If you flash a 4.2.2 ROM over a 4.3 STOCK ROM, then you will have 4.2.2, and nothing about your device will be 4.3
just to verify, you have the old Nexus 7 right?
Yes, old Nexus 7. Thanx! Now I feel comfortable trying some Roms.
Sent from my Nexus 7 using Tapatalk 2
What about the bootloader?
Sent from my Nexus 4 using xda app-developers app
ZombieUsr said:
What about the bootloader?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
There could be partition issues when you have the wrong one.Like there was with the 4.2 update.If you flash a 4.2 rom onto a 4.1 bootloader your whole data will get moved into another /0 folder
Sent from my Nexus 7 using xda app-developers app
filipathtc said:
There could be partition issues when you have the wrong one.Like there was with the 4.2 update.If you flash a 4.2 rom onto a 4.1 bootloader your whole data will get moved into another /0 folder
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
There isn't.
Sent from my Galaxy Nexus
filipathtc said:
There could be partition issues when you have the wrong one.Like there was with the 4.2 update.If you flash a 4.2 rom onto a 4.1 bootloader your whole data will get moved into another /0 folder
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The nested 0 folders was a recovery issue, not a bootloader one. Neither CWM nor TWRP could initially deal with the new multi-user directory structure. Koush and Team Win promptly updated their recoveries to resolve it.
Sent from my Nexus 7 using Tapatalk 4
Southrn Dawg said:
I'm interested in a stable ROM that has a lot of customizing options. Any suggestions?
Click to expand...
Click to collapse
I've been very happy with RasBeanJelly. It has a good cross between features, speed, and light-weight. It tends to be quite stable. I ran it for about 7 months, until I decided that l decided I needed more excitement in my life and jumped to a bleeding edge ROM. Depending on how the new ROM does/does-not develop, I may go back.
Before you go changing ROMs, make sure you are ready. Then make sure you are really ready. After a couple of times you may actually be ready. Look around, and you will find some guides. Here's a good place to start: Flashing Guide. The biggest issue I have had is making sure I have a good BACKUP and RESTORE strategy that works.
Good Luck,
-John
Slimbean 4.3 beta 3 is pretty feature-rich and is a beta in name only...it's been rock solid for me. Get it at www.slimroms.net
Thanx for the ROM suggestions! I been running CyanogenMod Ver 10.2 Unofficial and I like it but now I'm ready to try some more Roms. I've got the hang of flashing stuff again so now I feel comfortable trying some new stuff.
Sent from my Nexus 7 using Tapatalk HD
Hello,
I am running CM 10.2 (latest nightly). I flashed the franco kernel r191 for the first time and it bricked the phone. The boot animation won't come up. It gets stuck after the Google logo. I would appreciate if you could help me out. Fortunately, I had a full nandroid backup and was able to recover my phone.
I use the TWRP recovery.
Thanks.
You need to learn what the definition of bricked means.
a bricked phone is worthless and unrecoverable, it makes a great paperweight/door stop. flashing a kernel that wont boot is not bricking a phone, and not close, and there are many ways to recover from a non booting kernel, nandroid restore being one way. you can also just flash a good kernel or your rom to recover.
Thank you for clarifying the definition of brick. I did not know that. Please feel free to chime in regarding my original question. Thank you.
devadam1 said:
Thank you for clarifying the definition of brick. I did not know that. Please feel free to chime in regarding my original question. Thank you.
Click to expand...
Click to collapse
What IS your question? From what I've read, you were able to restore your nandroid, right? Just don't flash that kernel if it messes things up.
Sent from my LG-LS970 using xda app-developers app
try a different franco kernel. are you sure that you pucjed the right kernel? 4.2.2 kernels dont boot on 4.3, and 4.3 kernels dont boot on 4.2.2.
simms22 said:
try a different franco kernel. are you sure that you pucjed the right kernel? 4.2.2 kernels dont boot on 4.3, and 4.3 kernels dont boot on 4.2.2.
Click to expand...
Click to collapse
According to the author, I am supposed to flash the one that has a JSS tag in the file name. http://franciscofranco.minooch.com/Nexus4/4.3/zips/
I am sure I downloaded the correct file and flashed the right version. Since I am new here, I am not allowed to post in the original thread, which is here:
http://forum.xda-developers.com/showthread.php?t=2002782
iamterence said:
What IS your question? From what I've read, you were able to restore your nandroid, right? Just don't flash that kernel if it messes things up.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I would like to know whether there is a way to flash the franco kernel on CM 10.2. It seems to be buggy. I wanted to post my question here: http://forum.xda-developers.com/showthread.php?t=2002782
But I need at least 10 posts to ask my question there.
devadam1 said:
I would like to know whether there is a way to flash the franco kernel on CM 10.2. It seems to be buggy. I wanted to post my question here: http://forum.xda-developers.com/showthread.php?t=2002782
But I need at least 10 posts to ask my question there.
Click to expand...
Click to collapse
no. custom kernels no longer work on cm properly, if at all.thats probably is the reason why franco kernel wont boot. cm changed their base code from aosp to qualcomm a few weeks ago, and that broke the ability to use custom kernels on cm. custom kernels are based on aosp, and qualcomms code breaks stuff because of it.
Thank you so much! Now I understand why.
Sent from my Nexus 4 using xda app-developers app
when did this start? currently running cm10.2 and Franco190, now I'm scared to update cm as I need Franco for the battery life
Sent from my Nexus 4 using xda app-developers app
Started a couple of days ago. Not sure if the r191 is the cause or the cm 10.2 nightly.
Sent from my Nexus 4 using xda app-developers app
As said previously CM is the cause, Franco still remains AOSP based, you can try hellscore kernel, Google it, it as a nice reputation for amazing battery life and has a CM version of it.
Sent from my Nexus 4 using Tapatalk
devadam1 said:
Started a couple of days ago. Not sure if the r191 is the cause or the cm 10.2 nightly.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
it started with a nightly about 2 weeks ago
Thank you! I'll definitely give it a try.
Sent from my Nexus 4 using xda app-developers app
simms22 said:
it started with a nightly about 2 weeks ago
Click to expand...
Click to collapse
You're right. I just installed the nightly later on.
mine is Sept build good thing I didn't update
Sent from my Nexus 4 using xda app-developers app
albundy2010 said:
You need to learn what the definition of bricked means.
Click to expand...
Click to collapse
simms22 said:
a bricked phone is worthless and unrecoverable, it makes a great paperweight/door stop. flashing a kernel that wont boot is not bricking a phone, and not close, and there are many ways to recover from a non booting kernel, nandroid restore being one way. you can also just flash a good kernel or your rom to recover.
Click to expand...
Click to collapse
Aka: soft brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Endoroid said:
Aka: soft brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't even like the way that term is used to be honest. To me a soft brick is more or less something that requires a JTAG.
A bootloop or a failed boot just isn't any type of brick at all really as far as I'm concerned.
You really should change the title of the thread. Franco does great work and really does not need to be slandered. After all cm is preventing your device from booting not Franco's kernel. If you want to rant maybe you could change the title to cm bricked my phone
Sent from my Nexus 4 using XDA Premium 4 mobile app
I want to try paranoid android. I am currently running CyanogenMod 11, do I need to flash stock or what?
Thanks for all the helpers
You need to wipe to install a new Rom, then flash rom, gapps, and you are good to go.. you do not need to go back to stock rom first
Sent from my LG-D802 using XDA Premium 4 mobile app