Related
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
BuglessPete said:
I was hoping some of the kernel devs can help me with a quick question. I am familiar with unpacking and repacking boot.imgs for the Droid but not for the Evo, I usually use the method found here. Is there an alternate method or even some perl scripts that will make the job as easy as it is for the Droid? Note: I am not trying to compile a boot.img, I just want to be able to edit the ramdisk of existing ones. Thanks in advance!
Click to expand...
Click to collapse
reading through the tutorial you linked to, i see perl scripts and directions. is there a certain part of that tutorial you've used on the EVO and have had trouble or its resulted in some kind of error? guess i didn't catch what isn't working for you?
edit: reviewing the tutorial again, i have been wondering which partitions are which on our phone? boot mtd2/3 ? recovery mtd2/3? i know system is mtd4 and data is mtd5 ...
once i know which partition for sure is boot, it might be worth while for me to grab the kernel and post up the stock ramdisk as a starting point for all those looking to do simple kernel mod'n ...
Not sure why this got moved out of development section, as it is related to developing a boot.img although it was a question.
I used the unpack perl script and it threw an error. I will also try the split script when I get off work.
Sorry to resurrect a dead topic, but I'm looking into this as well, and I haven't been able to modify a ramdisk successfully (I'm basically looking to set ro.secure=0 in default.prop). I typically use the same procedure as Pete outlined in the link, but using that for the EVO results in a hang at the bootscreen. (the white HTC EVO 4G screen seen on boot) Any help would be appreciated.
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
kmartburrito said:
Resurrecting this topic once again.
ADB functionality is broken in Sense FroYo roms, maybe all froyo roms. I can communicate appropriately through fastboot and through ADB in Recovery, but not when running.
The /sbin/adbd process isn't running like it is on other ROMS, such as eclair and gingerbread.
Following this link:
http://code.google.com/p/android/issues/detail?id=9437
I found that some nexus one devs had the same issue, and had to replace the adbd process on the ramdisk with one from another build that worked in froyo.
Following this guide that everyone links to:
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
I was not able to use the included unpack/repack perl scripts without modifying them. It appears that the Evo has another file at the end and that script wasn't meant to handle that. Others commented out that line that kills it, I did so, but apparently that script doesn't grab the header appropriately, and the repack doesn't work appropriately for another. I get the white boot screen and it stays indefinitely.
I took the Boot.img and went through a hex editor to do it manually, and wasn't able to get the ramdisk to unzip correctly.
I'm at the end of my rope, and need someone else who's much smarter than I am to assist in what steps to take next.
I am developing a new app, and desperately need to have ADB working inside FroYo. I would run CM7, but it doesn't work right all the time, and has bad battery life for me. I use my phone for business too, so it all has to be stable.
Any ideas? I have lots of this stuff available as I've been working on it for the past couple days, so I can post links and the like to help bring anyone up to speed with what I've done. Thanks a crap-ton in advance. If you can help me get this working, I will send you a donation!
Also, this will fix ADB in all Froyo roms too, so you'd be doing the community a great favor as well.
-Nathan
Click to expand...
Click to collapse
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
lovethyEVO said:
Adb does work in sense froyo roms. It works on mine and I nandroid between my daily sense rom and my dev sense rom when I need to. I prefer to use adb through recovery but I have successfully adb pulled and pushed com.htc.resources from the framework while my device was running just last night. I have also not changed the adb file in the ramdisk (even though I could if I wanted to) so I doubt adb not working in sense roms is the issue unless the rom maker did in fact mess with the ramdisk and inadvertently messed something up.
Click to expand...
Click to collapse
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
kmartburrito said:
It's not working for me on Fresh 3.5, Evio 1.8, or Mik's Z rom that was just released. I can go back to my PC36IMG.zip (eclair) or CM7, and it works just fine.
I've tried stock and custom kernels, to no avail. I'm absolutely NOT the only person with this issue. As you can see in the post above, Nexus one users are having the same problem, as are tablet owners with Tegra 2 chipsets, etc.
So, let me ask you, what ROM are you using? Is that the only ROM you've used since upgrading from Eclair?
I am at a loss for why this isn't working. As I said before, the /sbin/adbd process is NOT running, and I get a segmentation fault when attempting to launch it. It works fine on CM7 and Eclair, but NOT froyo. Not brand new, unaltered ROM installs, nothing. Whatever it is, the only thing in common is Sense and FroYo.
Thanks for responding, I think at this point I just need people to provide other things to look at that I haven't thought of. I'd still like to learn how to unpack and repack though, it could be a last resort.
Click to expand...
Click to collapse
For my daily I use a rom based on miks eng base that I rooted and edited myself. For my dev rom I use joeykrims odexed rom that I deodexed. I also use a barebones 3.70 taken directly from the ruu, rooted and edited myself as well as deodexed it.
My two dev roms provide me with at least some sort of variables since joeykrim adds some extras to his rom.
In all three roms, the only thing I changed in the ramdisk is the kernel I compile and use (htc15 compiled to have sbc, havs, undervolt, etc.).
It could be (possible though unlikely since others do have success with adb on the roms you mention) that the ramdisk may have been edited in a way that prevents adb from starting in the init files.
Again just last night, both on my replacement evo and my wifes evo (she runs what I put on her evo which is usually a more polished version of mine) I used adb while the devices were running to pull some system apps and do some editing and then pushed them back. These are both sense based 3.70 roms using the same kernel.
Your situation is puzzling me at the moment since you said it works fine on cm7 and eclair but not on any sense based froyo roms. I would have drawn the same conclusion but since I personally can use adb on a sense based froyo rom I have to think the problem lies somewhere else and not solely on froyo. I'll try to duplicate this situation though I don't think I can without seeing what your device looks like.
As of now is there any way to return to stock? I think I'm going to exchange my phone and hope for the best. I got LOS like 10 times today, and it's getting tiresome.
Just the stock kernel that is posted.
The Evo3D Killer!!!
Like musclehead mentioned, the only method currently available is to reflash with the stock kernel available here.
IMPORTANT: If you rooted with a zedo kernel, you'll want to manually delete Superuser and associated files before flashing the stock kernel. It's very easy, see these instructions.
Edited to mention: I had los when using zedo's kernel but haven't had it since I reflashed stock (not sure if it was kernel-related or just coincidental). If you have some time before your 14 day return period ends, might be worth seeing how your phone behaves on the stock kernel before returning.
So when diving into the world of modifying a smart phone, there is a lot of learning one must do reading threads and watching videos prior to getting started. Otherwise instead of rooting your phone, you may end up bricking it.
So lets talk about some of these things.
First off, if you are looking to open your phone up to unlimited modification, the quintessential step is rooting it, which is to say, unlocking root access so everything can be changed from fonts and colors to CPU overclocking.
If I understand this correctly, Rooting is done by flashing a modified kernel onto the phone. I wont try to pretend I know that with any confidence, these are the terms I'd like better explanations for. so... A release comes from the manufacturer and contains everything from the operating system to the firmware and the modem. A ROM is a pre-customized variation of a release, dunno exactly what a TAR, MD5, or a kernel is. A modem is a part of a release, but just the software part that deals with how your phone uses its radios. NANDroid is a way to completely backup your phone as a NAND. Clockworkmod is a utility set that can load and manage ROMS, NAND's, themes, and all kinds of other stuff. Recovery is actually usually used as a term for a built in function for restoring your phone back to a pre-loaded state (if it's not bricked, which means something went wrong and the phone won't turn on, which is different from soft-brick which means the phone is in a startup-boot-loop) I don't know what a bootlogger is. ODIN is a program 'leaked' by samsung used for flashing updates onto phones. Download Mode or Odin mode is used for updating and what you boot into by turning off your phone, then turning it on while holding the volume down button. a OneClick is a pre-made ODIN update that that automatically updates your phone. Stock means the release is unmodified from the manufacturers original. A Tweak is a modification that can be flashed onto a ROM? A Theme I assume is an aesthetic style that can be applied to even a non-rooted phone. But I think it requires the phone to be Deodexed, which is something that can be done to a release... otherwise the release is odexed?
GA10, Fk23, FL16, etc etc. You're probably wondering what that is. It's a coding system for the date of the release. Because android released in 2007, the coding system starts at 2007. That first letter represents the year, the second letter the month, and the number represents the day of the month. So a release from january 1, 2007 would have been AA01. febuary 15th 2007 would have been AB15, which is why a release on december 16 2012 got FL16.
This may not be the end, but to wrap up the small bit that I've learned in 17 hours of reading FAQ's and stickies, cutting edge threads and archives. The last 4 things we need to talk about are the flash count, or odin counter, which tracks how many times your phone has been flashed by an external source. Then there is the yellow triangle which is an indicator thrown during startup by a phone which has detected that it is not running a stock ROM. these 2 indicators can be reset on our e4gt by using a USB Jig, a small piece of hardware which can be bought online specific to our phone, which when plugged into the microusb port, resets the odincount and gets rid of the yellow triangle. And finally, there are some special procedures that must be observed when flashing around from release to release. Flashing to the same release is relatively safe, it sounds, but flashing down or up should be done without preserving data. (restore vs nodata).
Honestly, I've spent a lot of time on learning just this, and I still feel like I'm writing words that don't add up. In fact, I know I am. So I'd honestly appreciate it if someone could take what I've tried to do here, edit it for readability, proper word usage, accuracy, add any or all missing information, and post a new sticky. One that explains these things. Because there are a lot of stickies that provide instructions for how to do things, but very few are written in a way a beginner can understand. I've bolded words that are regularly used but dont make complete sense to non-developers and novice power-user hopefuls.
Hey, I might add some of the terms and what they mean to the FAQ thread. :good:
Am I getting it? or am I wasting my time.? I feel like some of this is for advanced root users only, (like maybe flashing just a modem while using older releases ROMS) and some of this is for beginners only, like one-clicks. I'd love if somebody made just 3 very simple, very useful beginner wikis/stickies. ONE is a 'terminology' post, like the one I've haphazardly attempted to put together above. TWO is an "everybody knows you're supposed to blah blah blah" post, for things like mobile odin and modems, making a backup, how to stick to the basics if you're new, not flashing backwards with ROMs, and knowing how to recover back to warranty eligible stock (odin counter and everything), finally THIRD would be the thread that explains how to do each of the different kinds of flashes, but not just instructions, but what it means to do them.
I've combed through these threads for a day straight and I've got more questions than I started with.
So, if someone doesn't want to put these together, Questions I'd love to know definitive answers to, so this thread can continue to be helpful to others....
A) If I flash anything, or everything, a hundred times, ROMs, modems, kernels, recoveries, roots, can I find a stock release of whatever-is-current-OTA to flash and then use TriangleAway to reset everything back to warrenty elligible? if not, what about the USB jig? Is this even possible.... If so...
B) Since my phone is not rooted now (first timer), Am I able to make a complete backup of my phone un-rooted so I can flash back to it if I ever need to become warrenty elligible again. If so, do I use nandroid, or titanium backup? don't both of these require root? Can I flash back to undetectable stock?
C) obviously, disclaimers everywhere show that it is never safe to flash anything, everything is at your own risk, but is there a general rule of thumb for whether a stock release is more reliable than a customized ROM. or do ROMs tend to be more stable with problems fixed.
D) Does a phone need to be already rooted, (or already flashed up to a release number or with a release modem) in order to flash a ROM onto it, or does it just require Odin and the TAR. Is a ROM a TAR? is a ROM a Kernel? or does a phone need to be rooted to some version first, then using CWM to load a same-version ROM?
I would say stock is more stable, on average. Think about what your goal is, why you would want root, and why you would use a custom rom. Rom choice, for me anyway, is based on customization availability, and tweaks. If you are simply driven by curiosity, and that is a good thing, read, and read some more. Patience and knowledge will keep you from trashing your phone, but most importantly attention to detail when performing any of these activities. Good luck, we all started somewhere.
.: :: Sent from USC-GS2~PACman via Tapatalk 2 :: :.
Triangle away will reset the counter now even in jellybean. Just not gingerbread. For going back to stock for warranty, dont worry about that. You can use a tar file or a one click. If you want a stock backup for yourself to rely on, I need to know what version number you want so I know what to do. Yes titanium backup as well as m.o. require root. For anything below ga10 touchwuz roms, use exynos abuse.apk you can root your phone no computer needed.
sent from MY BAD A$$ ET4G
I don't understand how a recovery is different from a backup. but somehow is independent of a ROM, and build, but is included in a kernel? Apparently I need a CWM recovery kernel to flash Kobridges GA10 ROM. I see that there are repositories of all kernels, and modems, and roms. So a build is a TAR which contains a kernel, which contains a recovery, but also is the original ROM, after which other ROMs are built?
My phone, purchased October 2011, (only updated OTA to this point) is running FI27 ICS 4.0.4.
I've been trying to understand what I need to know, and need to have, to get started. I think I need FI27 to flash back to if I ever want to go back to un-rooted stock. Or do I want to flash back to something safer, (perhaps a 1click?) and then do OTA updates if desired. I think I'm reading that the CWM EL26 Recovery Kernel is the gold standard for pre-flashing before flashing any ROMs. But I don't know how that exactly works considering clockworkmod uses root, and I don't have root yet. I'm simultaniously trying to confirm what I'm trying to understand, but also find out what I don't yet have or understand, without asking somebody to just lay it all out for me (unless in the form of a wiki/sticky which could benefit anyone else like me who comes along after).
A)
So I have an e4gt.
I have backed up all essential files from internal storage to my PC, but if I understand correctly, I cannot create a nandroid.
I have SPH-D710_FI27_CL1127689_UNROOTED_NoData.exe to go back if I need stock.
Now if I want to just put TeamSextapes GA10 release on, that's pretty simple, I just flash the tar with odin. Everything is done. no root. No Rom
I can use a USB Jig to make it run as if I got the update from sprint even. But I shouldn't use the factory reset?
Going back from that, I'd use my one-click FI27 unrooted nodata.exe right, and then the USB Jig?
B) Am I right so far, from A) to B)?
All of this assumes I don't want roms or root.
When we're talking about ROMs, I'm still confused, because of how to get from where I am, to there, I gather it requires root, nandroid, clockworkmod, and CWM EL26 recovery kernel, and the process seems to double back a lot. flashing a root rom seems to require root. the process seems rather more opaque. I understand how to do a 1 click root, and older versions of root kinda make sense too, but how can someone flash kobridges GA10 ROM when it requires root, but no rooted stock GA10 is available?
Maybe I need to stay away from GA10, but my whole goal for learning all of this is to know how to get the best performance, with the least bugs, out of my phone, and signs point to GA10 for that. I had expected JB to roll out with the GSIII months ago, and all news of it has gone silent except here.
Thanks for continuing to support my inquiry. If I can come to understand how it all works, I will post a supplement to the "how to not brick your e4gt". Because as absolutely fantastic as that thread is... it still is way too deep water for a complete beginner. Regarding aspects of all this, I feel like I've learned more than I need to about some, and only enough to be dangerous about others. But still, Thanks!
I'll try to help with with what I understand. Clockworkmod or any recovery in general is packed up with the kernel. So if you want to make a backup just Odin a kernal with a recovery and it would be fine (I.e Kuban kernel). The thing is when you use Odin to flash kernel's it will cause the Samsung binary counter to increase and you will get a yellow triangle on boot. This is an easy fix but you need root access to run an app called triangle away which can be found in these forums or you can buy it off the play store if you want to support the dev. I would suggest getting the Directboot el29 kernel as it boots up directly into recovery. El29 or el26 are gingerbread kernels so if your running stock your phone won't boot up unless you are on gingerbread but you can always access recovery. I would suggest also getting an app called mobile odin (same deal as triangle away on how to get it)you can flash anything you can with regular Odin except it won't cause the counter to increase. Now for root.. I can be stock and have custom recovery just from using a custom kernel through Odin. Now 1 clicks are amazing let's say I have to take my phone in for repairs or warranty reasons. All I have to so is use the triangle away app (if I have the yellow triangle on boot) then boot my phone into download mode and use the FI27 stock no root data wipe. You can run a 1 click from your phone in any ROM ect... And bam you can take your phone to sprint for repairs or warranty. When you get your phone back just flash a 1 click for root access or a custom kernel for the recovery and then restore a nandroid and return to how your phone was. Now this is why I bought mobile Odin to support the dev.. Like in your case you want ga10. What I would do is just drag the download to my phone run mobile Odin and flash the ROM through mobile Odin.. Why? Because it can inject root to stock as it flashes. Just be careful and remember to back up your data because most jellybean leaks wipe internal data like pictures etc.. This doesn't happen when you flash a ROM and they ask you to wipe data. Now for modems stock jellybean modems don't work on ICS. You need a jellybean modem (if you do use the mobile Odin route you will have to flash a jellybean modem using regular Odin because mobile Odin doesn't seem to flash modems for our phones). When you Odin modems it will not increase the binary count and trigger the yellow triangle. Gingerbread modems and ICS modems interchange with each other so I wouldn't fear odining them.. Just see which works best. Hope this helps... I'm pretty sure you will read this cause you took the time to write a very long post lol.
Sent from my SPH-D710 using XDA
Thanks! That answers a number of my questions, now that the 1click for ga10 is out, i think ive finally got enough figured out to mess with it a bit with relative confidence.
Sent from my SPH-D710 using xda app-developers app
jt323bd said:
My phone, purchased October 2011, (only updated OTA to this point) is running FI27 ICS 4.0.4.
I've been trying to understand what I need to know, and need to have, to get started. I think I need FI27 to flash back to if I ever want to go back to un-rooted stock. Or do I want to flash back to something safer, (perhaps a 1click?) and then do OTA updates if desired. I think I'm reading that the CWM EL26 Recovery Kernel is the gold standard for pre-flashing before flashing any ROMs. But I don't know how that exactly works considering clockworkmod uses root, and I don't have root yet. I'm simultaniously trying to confirm what I'm trying to understand, but also find out what I don't yet have or understand, without asking somebody to just lay it all out for me (unless in the form of a wiki/sticky which could benefit anyone else like me who comes along after).
A)
So I have an e4gt.
I have backed up all essential files from internal storage to my PC, but if I understand correctly, I cannot create a nandroid.
I have SPH-D710_FI27_CL1127689_UNROOTED_NoData.exe to go back if I need stock.
Now if I want to just put TeamSextapes GA10 release on, that's pretty simple, I just flash the tar with odin. Everything is done. no root. No Rom
I can use a USB Jig to make it run as if I got the update from sprint even. But I shouldn't use the factory reset?
Going back from that, I'd use my one-click FI27 unrooted nodata.exe right, and then the USB Jig?
B) Am I right so far, from A) to B)?
All of this assumes I don't want roms or root.
When we're talking about ROMs, I'm still confused, because of how to get from where I am, to there, I gather it requires root, nandroid, clockworkmod, and CWM EL26 recovery kernel, and the process seems to double back a lot. flashing a root rom seems to require root. the process seems rather more opaque. I understand how to do a 1 click root, and older versions of root kinda make sense too, but how can someone flash kobridges GA10 ROM when it requires root, but no rooted stock GA10 is available?
Maybe I need to stay away from GA10, but my whole goal for learning all of this is to know how to get the best performance, with the least bugs, out of my phone, and signs point to GA10 for that. I had expected JB to roll out with the GSIII months ago, and all news of it has gone silent except here.
Thanks for continuing to support my inquiry. If I can come to understand how it all works, I will post a supplement to the "how to not brick your e4gt". Because as absolutely fantastic as that thread is... it still is way too deep water for a complete beginner. Regarding aspects of all this, I feel like I've learned more than I need to about some, and only enough to be dangerous about others. But still, Thanks!
Click to expand...
Click to collapse
You can still flash a kernel with a custom recovery using desktop odin if you are not rooted. You can they boot into custom recovery and make a nandroid of your unrooted stock rom.
Your flash counter only increases if you flash unofficial stock files using desktop odin. So if you flash a modem.bin in the phone slot in desktop odin, your flash counter will increase. If you flash a kernel.tar file in desktop odin, your flash counter will increase. Thats why you go to rwilco12's repo in dev forums and use the one-click.exe files. Oneclick.exe files do not increase flash counter. You only need jib to reset flash counter or boot to download mode if you can't normally boot to download mode.
You could flash EL26 CWM kernel in desktop odin and boot to CWM recovery to flash any rom zip file you want even if you are not rooted. Don't jump to jelly bean roms from ics without first flash a stock jellybean oneclick.
Hi I might want to flash another kernel but gather it would be best to know more first. Firstly I get that it is the bridge between software and hardware.
If I flash another one that didn't come with the rom (I am using cyanogenmod 10.1) is it likely to cause problems? Also if it did would restoring a backup from rom manager return it to the former kernel or is the kernel on a lower layer which would remain unaffected?
I read that it is responsible also for managing processes/performance so if I flashed the stocked kernel would that then mean that the battery drain etc would be as if I were running stock android?
Search the forum or try it out. I guarantee you'll find the answers to your questions.
If you don't like it restore your backup and try again
Let me start by saying I've never flashed a custom kernel separately, one which did not come with a rom. But let me say this: since a nandroid takes a backup of the boot.img, which i believe is the kernel, i would think the backup would restore the previous kernel. As far as problems, I'd say you'd find that only by reading through the kernel threads, but it would seem that kernels would be optimized to work with many roms, undergoing updates as needed and having particular problems here and there. I say try it and report back. While I support reading and searching, and am aghast at how many posts repeat the same questions, i also think there are learning opportunities here, and sometimes repetitions teaches others, and digs out threads and topics we would not have otherwise accessed.
Body is mostly right. A nandroid restore will restore your kernel if you want it to. A kernel won't necessarily work the same on different ROMs though. Try 2 or three and see if you find one you like. I always end up back on the stock kernel myself, though I've previously had good luck with Trinity.
Well yes it did flash back to the original kernel because I had to restore a backup and luckily its OK.
After flashing the stock kernel it wouldn't boot up properly. Kept doing continuous force close errors on the lock screen after ages trying to boot that I couldnt get past coz they continuously popped up.
Sent from my Galaxy Nexus using xda app-developers app
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
yamus08 said:
What's up everyone? I am having a strange problem when trying to flash just about any kernel on my N7. While I'm not a developer or anything, I'm not new to flashing ROMs or Kernels by far. In fact, my love affair with smartphones began when I got an HTC Apache with Windows Mobile 5. Anyway, every time I try to flash a kernel, it will show successful, and then the phone will boot into a fuzzy/pixelated light blue screen. Eventually, this screen will go away and my device will be pretty much locked up. All the images will have turned blue and orange, and the only way for me to get back into recovery will be to hold volume down + power, until the phone shuts off. The only kernel I have had any success with is Glitch, and I have even had this happen with it a couple times.
I always make sure to read through the instructions, and have done lots of searching here, and via Google. After I flash a rom, I will make sure the N7 boots up, and works properly, then reboot into recovery, do a full wipe, and flash the zip from TWRP. My most recent attempt was with Buttered AOKP w/Aroma installer. It walks you through the steps in a manner that should make this easy for anyone. It give you the option to wipe cache and kernel, which I always do, but no go. The only way I can get Glitch to run on it, is to complete the whole process twice.
Sorry if the answer is right under my nose, but I couldn't take it anymore and had to ask. I've never once bricked a device, nor have I had issues flashing kernels on any device before. Somebody please restore my sanity!!! I didn't have much to begin with.
Click to expand...
Click to collapse
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
xfrancis14 said:
Flashing a CAF kernel on an aosp Rom or a aosp kernel on a CAF Rom. What Rom are you on? (cynanogen based roms are CAF)
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Currently on: [ROM] Buttered Flo AOKP 4.3.1 [+Aroma] [2013-10-12]
It has all the kernels built into the aroma installer, so I would assume they are all compatible. Some more than others.
I got 3.4.1 Glitch-Flo to run on it, but had to return phone to stock, and flash twice, to get it to work. The aroma installer also has the option to use Faux Kernel in one of three flavors. I tried the "Ultra CCCCCCOMBO" first, and then the "Enhanced Stock", but no go.
When I go to the thread for both kernels, it says they are CAF kernels, but it's kind of strange they they would be included as an option in the rom. I have tried a few other roms, with various kernels too, and not had any luck. I want to get a log to post, but I'm not sure if I will be able to pull it via ADB, when the device is pretty much unresponsive.
Thanks for your response, and let me know if what you think about the CAF kernels being inlcuded with the AOKP rom.
Thanks,
Yam
Sooooo..... Isn't aokp based of the cm kernel? If that's the case, any of the kernels I am trying should work. I would post this in the ROM thread, but its happened with just about every ROM kernel combination in have tried. What's the dealio
Any update on this? I am having the exact same problem with my Nexus 4 running ProBAM 2.0 ROM. I have tried flashing every kernel and every version possible and it either freezes before boot (Google logo) or I get the blue screen... help anyone? I really want to flash a kernel with FauxSound, that's really all I want. Thanks so much!