I did a research regarding Flashing Kernels and Roms and currently i have installed Cyanogen 9.1 for my device.
1.Will I be able to update my phone and bring back to old ICS firmware via SUS once i brick my phone(I have already unlocked the bootloader via fastboot method)?
2.Evrytime when i flash the Rom(say CM9) i used to flash kernal(boot.img) for the respective rom.Is this necessary all the time? Will i able to flash a GB rom on ICS kernal(I am afraid to give it a test)?
3.Regarding CM9.1 which i have installed ryt now,I am satisfied with the performance,but i want a stable ROM wud make me happy with a better battery life unlike CM9.1. Any GB/ICS ROM which wud have a stable performance with descent battery life.
4.After using GB for a long time,i was very much addicted with the Phone pad kinda keyboard,but when ICS came into picture everything vanished,Smartkeyboard Pro is no gud,Touchpal is conjusted,i want the exact GB keyboard in ICS.
Phone: Xperia Ray
ROM: GB Stock Rom
So I've been looking into flashing custom kernels, and I can't seem to find an answer to this question. Basically, I'm wondering if the kernel remains after installing a new nightly, or do I have to reflash the kernel every time the ROM updates?
When I got my phone at the end of last year I rooted it using a Chain-Fire kernel - v 4.2, I think. After flashing, it worked perfectly, since when I have flashed the old bootloader to get my USB Jig working to remove the yellow triangle and flashed a patch again to allow the USB Jig to reset the binary counter.
I have very much wanted to install and get the new Sky Go application working.
What I had to do was flash the Stock kernel for my Stock Rom - I have never messed with my Rom - it is Gingerbread 2.3.4 in a CPW phone here in the UK.
Doing the flash and installing Voodoo OTA (to temporarily hide my root) has been enormously successful
Now then to my query....
The original Chain-Fire mod v 4.2 installed CWM.
After of course cancelling the "hide root" function to show my phone as rooted once more, I went to do a backup, using CWM but it refuses to work. It says my kernel needs v 5.0. Obviously the Stock Rom I flashed to get Sky Go working has thrown CWM some what.
I have downloaded Rom Manager from the Market but this seems not to work either - it starts to work (reboots) but then halts with the following messages: -
E : failed to verify whole-file signature
E : signature verification failed Installation aborted
What I would like is some way of installing a backup previously made before flashing the Stock kernal and also to make a fresh backup now.
I have an xperia X8 with some naa kernel and xperiadroidx 6.1.The thing is that with this custom kernel and ROM when i put a SIM from another network carrier, the question asking for the SIM-unlock code input is not showing up. (this appeared before when phone was in stock state).Is it possible to do it without re-flashing to stock?
...or i have to put back the phone to stock? What is the easiest/safest/best way to do this? using the restore option in "PC companion" SE app? Is it only needed to put the stock kernel and ROM, or Do i also need to re-lock the bootloader?
I don't need the whole explanation, just a little guidance, just a few tips to know what to do, then i can google/search myself for the specifics on how to actually do it.
I have samsung galaxy pocket duos gt s5302..I have rooted it and flashed CWM recovery then I tried to flash custom compact kernel made by Deadly. After I flashed through CWM my phone got hard bricked It wont turn on What should I do?
I recently rooted my Evo using UnRevoked 3.2 and flashed Fresh 3.3 on it. I'm generally happy with the results, the upgrade seemed to fix some problems with random reboots and screen locks I was having on stock (I'm thinking that moving a lot of apps to SD may have helped, as I seemed to be always low on memory).
In any case, I do think the phone is a bit "laggy" after the update. I downloaded FPS2D and checked my FPS, seem to average right around 50fps with std dev of 9. It seems like many people are getting much better screen performance using the custom netarchy 4.1.9 kernel. I'd like to give that a try but I have a couple of basic questions...
1. I will do a nandroid backup and Titanium before I flash, but I noticed that restoring apps last time was a drag...I use FolderOrganizer and it's a pain to get them all set up the way I had them. Does flashing the kernel wipe your phone clean? How much app/Sense restoring would I have to do assuming all goes well? I'm assuming that flashing the kernel has little to no effect on installed apps or Sense screen layouts...he cried hopefully...
2. I'm assuming here that Fresh 3.3 is compatible with netarchy 4.1.9, correct? Also, I saw an indication that netarchy 5.0 may be around the corner...is it better to wait? Or is reflashing a kernel that easy so there's no reason to wait?
3. It looks like an overclocking app is included in the netarchy kernel? Is it necessary to tweak the profiles, and if so what are the recommended tweaks for best performance? I have some experience with this coming from an overclocked Palm Pre, but I care a lot more about my Evo...I don't want to hurt it!
4. Battery performance is less of a concern than screen performance for me...I have chargers everywhere. Still, I'd like to get the best battery performance I can. I believe there may be "rogue" services on my phone that are eating up the battery (for example, I use Exchange ActiveSync and I turned it off recently because sync problems were causing it to stay on in the background). What's a good way (or app) to identify rogue apps/services and kill them?
I have a rooted Droid Incredible, running stock 2.2 and Hydra's 1.15 ghz kernel. I found a ROM called "Light Speed," and I'm wondering if I should try it out. Here's the link: [ROM] Light Speed - Droid Forum - Verizon Droid & the Motorola Droid Forum I'm thinking of the sense version. Do you think it will work? Also, it says it features KingxKernel #6. Is this a stable kernel? How many ghz will it go to? Any other tips before I flash? (Ex. wipe, backup)
So I was under the impression that you could use ROM manager or ClockWork mod to install a custom kernel that I had downloaded to my SDcard. I downloaded a low-volt, overclock kernel and I have discovered that I don't quite know to flash it to my phone.
I decided to split this off to a new thread, and hope some coders will join in and start compiling a kernel. We could then merge this with the galaxy asop effort.
Here's a bit more technical information.
The galaxy flash files are just yaffs images and a zimage (and of course AMSS) all tarred up. The tar format needs to be oldgnu for odin to accept it. There's no protection at all. Thats because the glaxy is released completly security unlocked (simlocks are different, not the same thing). You can flash any image you like.
AMSS - arm ELF binary for baseband kernel - zimage system - standard yaffs image recovery - standard recovery format tar - oldgnu style standard tar file
The Galaxy also has a mtd device driver which means you can read/write its partitions with dd.
The behold has the same image format, yaffs, zimage and AMSS. See below for specific differences per image:
AMSS - arm ELF binary for baseband
The behold 2 also contains a partitions file. This is most likely for the AMSS, and allows the layout of the baseband to change. I'm not sure if the galaxy supports the same, but probably does.
Its safe to say you should NOT try to flash an AMSS from galaxy to the behold or vice versa.
Since the radios have the same functionality, and we don't know how to recompile and AMSS, you should never flash any new AMSS with a custom rom. Only flash AMSS with official updates.
> kernel - zimage
Just like the Galaxy this is a standard zimage. There's nothing special about it and you can modify it however you want. BUT in order for it to flash the tar file needs a special header (see tar below)
Since we can change the kernel, upgrades to newer OS versions is now possible.
> System - standard yaffs image
It appears the system image format on the behold2 is DIFFERENT to that on the galaxy. If you flash a galaxy system file onto the behold 2 you will most likely end up with a brick.
I suspect the behold 2 file has the flash address embedded inside it. Flashing the galaxy system file writes to a bad address killing the bootloader. When i say BRICK i really mean BRICK. No life in the phone at all, it wont even charge. so DONT DO IT!
In order to write a custom system to the behold 2, we will need to untar or unyaffs the modified system from the sdcard on first boot. This can easily be accomodated in the init.rc of you're modified zimage.
> Recovery - standard recovery format (protected?)
The recovery image format seems to be the same - standard android format with a ramdisk, kernel etc. However flashing it using odin doesnt work. There is some sort of protection which is preventing the image being flashed. I havnt looked thoroughly at this and someone really should. I suspect either it is signed (unlikely since the other images dont seem to be protected), or there is a write address embedded in the file, like the system file.
It would be nice to be able to flash a custom recovery, or even boot from a ramdisk, but I think this wont be simple.
> tar - oldgnu style standard tar file (with header)
Both the galaxy and behold2 have a header at the top of tar. The galaxy will flash regardless of if this header is intact or not. The behold 2 however MUST have this header intact for it to flash anything.
It seems this header contains the size, and write address of the zimage. Its possible the addresses of other images like the recovery are embedded in this too. We should look more closely at this header, especially between firmware versions to see what changes. In the mean time to replace the zimage, just hexedit your new image over the existing 'kernel' file in the tar. Remember you need to keep the size the same, so pad with zero's or just leave the remainder of the old kernel in the extra space.
The sources that samsung provided are missing patches. This means you can't compile the behold kernel simply.
Also because the partitions are different, and the memory layout is different (compare msm/board-init files) a standard galaxy kernel will not boot.
Making the changes to get it to boot are not that dificult. It would be nice if someone who actually has a behold 2 and linux knowledge could have a look at this. It takes far to long for me to do this remotly, and frankly I just dont have that much time.
All you need to do is:
- compile the galaxy kernel (test your environment) - replace board-init in the galaxy source with that from behold2 sources - turn on linux console
Now boot and check if the galaxy kernel is able to see device's for each partition on the behold. If not you'll need to copy the disk/flash driver from the behold 2 sources.
Once you are able to get that far, you can merge the changes into the i7500 asop project and add a kernel switch for the behold 2. Now all galaxy 2.x progress will be directly transferable to the behold2.
You will need to make a change to the init.rc to mount the drives and unyaffs the modified system.img the first time it boots. Again a simple change.
Forgot to mention HOW to flash a kernel.
1) Take the stock behold 2 PDA tar file. 2) Use jzip (must be jzip on windows, winzip etc wont work) to remove ALL files except the kernel. 3) Extract the kernel file for reference (leave it in the tar too) 3) Download HexWorkshop or similar Hex utility. 4) Use Hex Workshop compare function to compare 'kernel' and the tar. It will highlight the kernel in the tar file 5) Open new kernel in Hexworkshop. Select all and Copy 6) Highlight the same number of bytes in the tar file and paste over the original kernel 7) Flash with Odin (JUST this tar) as PDA, and of course selecting the behold ops file.
I was getting to the installation of the rom that Gava97 and Maclaw are developing for the Xperia U (I installed for testing), now it wont let me downgrade to any ROM getting error 7 and 6 when flashing others, looked up the respective fixes for each error and still nothing.
im new in android and a couple hours ago i try to instal beanstalk - legacy kitkat 4.4 and they suggest to download kernel from dark raven "dark kernel cm11.0" 11DarkUrushi20131130 after that im flash the kernel and something happen....
my phone dont boot up and the logo dont appear
im try to connect to flash tool but still dont get it...
I own a Sony Xperia ZL and running firmware C6503_10.4.1.B.0.101 (I hope this is the right one, I'am still a newbie about this), unrooted and bootloader locked. A few days ago, I got a bootloop on my device, and after searching the solutions they told me to flashing it. Then I just flashing it, and to be honest this is my first time flashing and I don't know any effect of this.
After successfully flashing, I lost all my internal data
But luckily , I don't know why but my device auto download all of my apps and also recover my contact automatically. I also got my WA messages because still have my back up on micro SD.
But not about the SMS, not even a single SMS appear. I already try Dr.Fone for Android software and use deep scan, but the software found nothing. How to recover my SMS.
I have been reading up alot recently about rooting and flashing my phone (Sony Ericsson Xperia Ray) as currently my carrier (O2) is not releasing ICS for updates as they have not "tested" it sufficiently on my particular device (this was there explanation to me via email).
I have looked on the official sony ericsson website trying to find a way to update my phone and found that the method there required my phone to have "S-Off" but unfortunatly my phone is "S-On" (im assuming due to it being locked to O2 although it is a pay as you go model).
I have read conflicting opinions on whether you can root and flash your phone in my situation and was just wondering (before i tried anything at all) need to clarify if it would be possible to update my phone to ICS.
i recently flashed custom roms in my arc s and returned to stock because of the features, when i installed ics 4.0.4 the battery meter is stuck in 100% and the mobile would switch of all of a sudden saying battery is emply i tried deleting battery stats, formatted everything except sd card still no use it is still stuck.. i flashed gingerbread and the battery meter worked fine i was showing the correct percentage, once after i flashed gingerbread charged the battery to 60% and flashed gingerbread it was showing the right percentage... i know the sensor is fine coz its working in gb.. i tried battery calibration and different battery status apps all show 100%. ics once the batterys drained it doesnt charge properly..
I flashed + rooted (strangely in that order, which means I must have rooted my phone ages ago.. and then locked my bootloader after flashing..?)...
I do have Rom manager installed... but I don't quite recall how I ended up flashing the stock rom onto the phone.. Anyways, as I did seem to reset my phone, I upgraded all the apk packs and I'm pretty happy with the speed upgrade + ext2 internal space expansion.
As I now want to create a nandroid backup, so I can always come back to my current status, when I want a clean reinstall..!
My main question is that as I seem to have skipped creating a CWM recovery... if I do so now, will I loose all my data and go back to the basic stock rom?
The problem I'm facing right now is that I'm unable to boot into the recovery mode using either "adb reboot recovery" or the power on + vol buttons / menu button. (which means that I don't have the recovery mode installed.....)
So.... will I loose my current upgrades + phone settings (reset into factory mode), if I flash the recovery mode?
Everyone probably has the exact same Build Number, but than again, maybe a couple don't. So after a search, I was not able to find a thread like this, so here it is. I just received my X10 yesterday and per Sony Support, my X10 has the current OS. So here is my info:
I have vanilla linux kernel version 2.6.27. I want to apply android specific patches and convert it to android linux kernel 2.6.27. Where can a user find the patches to convert a normal vanilla kernel into android kernel?
1. I updated to stock 2.1 using the sprint update tool. 2. I followed the video tutorial to root the phone 3. then i used joey's page (http://www.joeyconway.com/sdx/custom/index.php) to install the his kernel (joeykrim-SDX-kernel v2.0.4 (includes root)).
I have done nothing else to the phone but this and removing a couple of bloatware apps (i checked the list of permitted deletions before i removed anything.) I have not installed a new recovery..at least i dont think that I did as part of one of the other operations I performed (as an aside, i am not really sure what the custom recovery is or what it is used for, so i didnt install it...i guess i need to read up more...)
So that is where I am..but i have a couple of questions.
1) i am now having issues with my wifi connection - the signal reception is very spotty in areas where i should have atleast 2 bars of reception, and the wifi often cuts out completely....Is there any know corellation between joey's kernel and this wifi issue? I have searched the forums and have found nothing that answers this.
2) Is there an easy way to get back to the stock kernel? I have read that i can get back to stock everything by using the sprint download center where I did my original 2.1 update. But is there a way to get back to just the stock kernel without wiping the phone?