I have this persistent problem across different ROMs and kernels. The problem is, when I flash a kernel through fastboot mode, it "sticks" only for the first session after flashing. When I reboot my device, the flashed kernel is gone, and I am left with the old kernel.
I wish to state that I have tried to search for the answer to this before posting. I also state that I have followed all installation instructions for the respective ROMs/kernels exactly. This is a recent problem for me, as I have done a lot of flashing before, and never encountered such a problem.
This happened when I moved from:
1) CM 9.1 (ICS) official stable with its default (FXP) kernel to LegacyXperia (JB) with its default kernel.
I was stuck in a loop here, like I would enter fastboot mode, flash the new kernel, new ROM and gapps, and when I reboot system through recovery, I still get the FXP logo (old kernel and old recovery), and a boot loop follows. Then I repeated the process for a couple of times, and then flashed the official Sony .587 ICS firmware, hoping it would set things right.
2) Stock Sony .587 firmware (ICS) with stock kernel (flashed official FTF) to Suave kernel.
I can see Suave kernel when I boot for the first time following flashing it, but when I reboot, the recovery is gone, and I can see the default Sony kernel again.
I hope I have stated my question clearly. Please help me find a solution to this.
RneoV said:
I have this persistent problem across different ROMs and kernels. The problem is, when I flash a kernel through fastboot mode, it "sticks" only for the first session after flashing. When I reboot my device, the flashed kernel is gone, and I am left with the old kernel.
I wish to state that I have tried to search for the answer to this before posting. I also state that I have followed all installation instructions for the respective ROMs/kernels exactly. This is a recent problem for me, as I have done a lot of flashing before, and never encountered such a problem.
This happened when I moved from:
1) CM 9.1 (ICS) official stable with its default (FXP) kernel to LegacyXperia (JB) with its default kernel.
I was stuck in a loop here, like I would enter fastboot mode, flash the new kernel, new ROM and gapps, and when I reboot system through recovery, I still get the FXP logo (old kernel and old recovery), and a boot loop follows. Then I repeated the process for a couple of times, and then flashed the official Sony .587 ICS firmware, hoping it would set things right.
2) Stock Sony .587 firmware (ICS) with stock kernel (flashed official FTF) to Suave kernel.
I can see Suave kernel when I boot for the first time following flashing it, but when I reboot, the recovery is gone, and I can see the default Sony kernel again.
I hope I have stated my question clearly. Please help me find a solution to this.
Click to expand...
Click to collapse
Are you hotbooting kernel instead of fastbooting?
And what commands are you using to flash kernel?
Sent from my Xperia Neo V using xda app-developers app
I tried doing both hotboot via adb from flashtool and using fastboot from cmd prompt.
I used the command:
fastboot boot <kernel>.img
Sent from my MT11i using xda app-developers app
RneoV said:
I tried doing both hotboot via adb from flashtool and using fastboot from cmd prompt.
I used the command:
fastboot boot <kernel>.img
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
That's the problem... Use command fastboot flash boot kernel.img... And don't hotboot...
Sent from my Xperia Neo V using xda app-developers app
Attitude.SSJ said:
That's the problem... Use command fastboot flash boot kernel.img... And don't hotboot...
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
I am sorry, I messed up the sequence. I tried the ADB hotboot as an alternative after the fastboot command from the cmd prompt did not work.
I tried it again just now, and it worked.
Anyway, that is all I wanted. I appreciate your help!
Related
I flashed the custom kernel, it is successful to boot and works fine
However, whenever I reboot or power off then turn it on, it return back to the default kernel. I re-flashed the kernel so many times. I don't have any ideas about this problem, Please help.
Sorry for my poor English.
How are you flashing the Kernel? with Flashtool? Command line?
I believe there is an option in Flashtool to Hotboot a Kernel... AFAIK this will only boot the kernel once then revert back to the old one on the next reboot... (great for testing different kernels for compatibility or for gaining root access on stock firmware that doesn't have root access available yet.. doesn't always work tho)
Just double check your method for flashing the Kernel (don't use hotboot!)
Kiwi
You are hot booting the kernel
Use this to flash it :
fastboot flash boot boot.img
Qwerty123 \m/ said:
You are hot booting the kernel
Use this to flash it :
fastboot flash boot boot.img
Click to expand...
Click to collapse
Thank you two.
You are very nice.
It works.
I'm so embarrassed for making this kind of mistake
Hello everyone! I have a problem with flashing custom kernels. I have unlocked my bootloader via Test Point method and whenever i want to flash a new kernel i have a problem. When new kernel is flashed (e.g. NeroDroid) the logo of NeroDroid appears on the screen and then phone restarts and logo of the SE apperas instead of the kernel's logo (the kernel isn't working, it returns to stock kernel). I wasn't sure if the device was really bootloader unlocked so i have checked it on the second method of unlocking BL (with IMEI and SE site) and when i wanted to unlock it, the information "your device is unlocked" appears. So what should i do to properly install kernel?
How did you install another kernel?
Sent from my WT19i using xda premium
Via fastboot. "fastboot boot boot.img"
The command is "fastboot flash boot boot.img" or "fastboot -i 0xfce flash boot boot.img" which is necessary on some Xperias.
What you did was simply boot the kernel once, but you didn't flash it.
following these procedures i never had any trouble flashing to any of my devices
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
curently i'm using 3 different devices, all rooted and running on pac 4.3, always latest nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
no sony though but i suppose that the following littel steps to consider are most probably similar with all or most android devices running
ICS or JB :cyclops:
now to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
flashtool
Snowho said:
Hello everyone! I have a problem with flashing custom kernels. I have unlocked my bootloader via Test Point method and whenever i want to flash a new kernel i have a problem. When new kernel is flashed (e.g. NeroDroid) the logo of NeroDroid appears on the screen and then phone restarts and logo of the SE apperas instead of the kernel's logo (the kernel isn't working, it returns to stock kernel). I wasn't sure if the device was really bootloader unlocked so i have checked it on the second method of unlocking BL (with IMEI and SE site) and when i wanted to unlock it, the information "your device is unlocked" appears. So what should i do to properly install kernel?
Click to expand...
Click to collapse
Use flashtool .it must surely solve the problem
press thanks if I had helped you
EaSy
1. Use flashtool and the click on the flash icon.
2. And then click on the flash icon (it looks like lighting).
3. Click on fastboot mode.
4. Then click on select kernel to flash go to the directry where you have placed your .img file
You are done...:good:
---------- Post added at 06:43 PM ---------- Previous post was at 06:40 PM ----------
mustufa_kheroda said:
1. Use flashtool and the click on the flash icon.
2. And then click on the flash icon (it looks like lighting).
3. Click on fastboot mode.
4. Then click on `select kernel to flash` go to the directry where you have placed your .img file
You are done...:good:
Click to expand...
Click to collapse
Hit thanks if i helped
Hello Snowhoe,
Use Flashtool to flash Kernels.
It's the best way of flashing Kernels/ftf.
Hello,
I have unlocked my bootloader using official method on my neo v. It has Stock 2.3.4 GB with 4.0.2.A.0.69 version, So i cant root it. Now what should i do? i want to put pureness rom in my mobile. But i would need to install CWM for that and have to flash the kernel. So my question is if i flash knight elf kernel then would my stock GB boot up after that ? so that i can put CWM and make a backup of stock and then i can also install the Rom by CWM. What do i do?
Best thing you can do is read the sticky topics.......
All your questions are answered there, no need for this thread.
Sent from my MT11i using xda app-developers app
mpiekp said:
Best thing you can do is read the sticky topics.......
All your questions are answered there, no need for this thread.
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I cant seem to find the answers for my questions. Please help.
dar820 said:
I cant seem to find the answers for my questions. Please help.
Click to expand...
Click to collapse
Before i started to mess with my phone, I read pages and pages, for few days. You just searched 1hour(based on time of your posts).
Put a bit effort and inform yourself.
Information is out there, convert it into knowledge.
Maybe its not written in custom kernels thread, since that's general knowledge, but 99.99% of custom kernels already have recovery.
--
sent from my vacation
They most definitely are but as your either too lazy or too stupid to find them I answered below.
All custom kernels include cwm, so you flash a gingerbread kernel to keep your existing rom, make your backup, then flash whatever takes your fancy and the appropriate kernel for whichever rom, there is no universal one.
Sent from my MT11i using xda app-developers app
just install a kernel using flashtool, some kernels already have cwm
dar820 said:
Hello,
I have unlocked my bootloader using official method on my neo v. It has Stock 2.3.4 GB with 4.0.2.A.0.69 version, So i cant root it. Now what should i do? i want to put pureness rom in my mobile. But i would need to install CWM for that and have to flash the kernel. So my question is if i flash knight elf kernel then would my stock GB boot up after that ? so that i can put CWM and make a backup of stock and then i can also install the Rom by CWM. What do i do?
Click to expand...
Click to collapse
Instead of taking the risk of flashing knight elf just hotboot it using fastboot! Type the command fastboot boot boot.img( the kernel name!)
Fastboot reboot
The kernel will be booted just once, so directly open the recovery n flash the rom !
P.s. I am not sure if ice cream Pureness can be flashed from gb! I think u first need to upgrade to stock ics....
Sent from My Xperia NeoV! Don't be a retard! Press the thanks button!
First at all, if you unlock your bootloader you should know what you are doing. Unlocking bootloader is not like rooting, rooting can be easily undone, unlocking the bootloader not.
There is something you should know regarding to phones and computers: If you don't know what you are doing then DON'T DO IT.
There are plenty of topics about rooting and installing custom ROMs just read.
According to the pureness rom thread it even works on locked bootloaders.
My bootloader is unlocked
my bootloader is unlocked what to do to go to bootloader recovery mode
varunangirash said:
my bootloader is unlocked what to do to go to bootloader recovery mode
Click to expand...
Click to collapse
Turn off phone.
Hold menu key
insert usb cable
You should see blue LED on the side of the phone
You now have fastboot access via cmd window in PC
Run this
Code:
fastboot devices
to check your device is connected
gregbradley said:
turn off phone.
Hold menu key
insert usb cable
you should see blue led on the side of the phone
you now have fastbook access via cmd window in pc
run this
Code:
fastboot devices
to check your device is connected
Click to expand...
Click to collapse
no no you got ut wrong bro i dont have pc but i want to open simple recovery mode and i have galaxy y and i can easily open recivery by pressing home nd volume keys but i dont how to open it neo v
varunangirash said:
no no you got ut wrong bro i dont have pc but i want to open simple recovery mode and i have galaxy y and i can easily open recivery by pressing home nd volume keys but i dont how to open it neo v
Click to expand...
Click to collapse
No,
I answered your question correctly,
It appears you asked the wrong question!
If you want to get into recovery mode you keep pressing the back key (Or if that doesnt work the volume down key, or if that doesnt work keep pressing the screen) when you see the sony logo after turning the phone on.
Of course you must have installed a RECOVERY to do this.
Rooting is not the same as unlocking bootloader. You mean recovery mode and you probably mean you have rooted your phone and NOT that you have unlocked the bootloader
gregbradley said:
no,
i answered your question correctly,
it appears you asked the wrong question!
If you want to get into recovery mode you keep pressing the back key (or if that doesnt work the volume down key, or if that doesnt work keep pressing the screen) when you see the sony logo after turning the phone on.
Of course you must have installed a recovery to do this.
rooting is not the same as unlocking bootloader. you mean recovery mode and you probably mean you have rooted your phone and not that you have unlocked the bootloader
Click to expand...
Click to collapse
bro i have rooted my phone and unlocked too i want to ask you which button us to pressed to get factory recovery because i wabt to install your icecream pureness rom but i dont know how to do it
varunangirash said:
bro i have rooted my phone and unlocked too i want to ask you which button us to pressed to get factory recovery because i wabt to install your icecream pureness rom but i dont know how to do it
Click to expand...
Click to collapse
There is no factory recovery, you have to install it yourself.
Goto the sticky threads in the dev section and start to read,
First, download flashtool, found in the first sticky thread in the dev section.
Second, Install recovery via flashtool or by flashing a custom kernel (Which you can do if you have unlocked your bootloader and can get into fastboot mode)
Third, install pureness via recovery.
PS, if you have NEO V you dont need a custom kernel for pureness so you can install recovery via flashtool and then the rom, but if you have NEO then you need the alliance kernel which requires unlocked bootloader, fastboot and a PC
gregbradley said:
There is no factory recovery, you have to install it yourself.
Goto the sticky threads in the dev section and start to read,
First, download flashtool, found in the first sticky thread in the dev section.
Second, Install recovery via flashtool or by flashing a custom kernel (Which you can do if you have unlocked your bootloader and can get into fastboot mode)
Third, install pureness via recovery.
PS, if you have NEO V you dont need a custom kernel for pureness so you can install recovery via flashtool and then the rom, but if you have NEO then you need the alliance kernel which requires unlocked bootloader, fastboot and a PC
Click to expand...
Click to collapse
is overclocking works in iccream pureness
Switch off your phone , press the power button and keep pressing the volume down button when you see Sony Ericsson for the first time until you see CWM(not the logo/boot animation , the SONY ERICSSON screen which appears first) task COMPLETE
varunangirash said:
is overclocking works in iccream pureness
Click to expand...
Click to collapse
Yes, but you need a custom kernel for that, and that means unlocked bootloader and fastboot and PC
ffs, read a sticky thread
I bought the Xperia Mini Pro as second-hand device just days ago (almost new for just ~$40 ) and this small guy really impresses me with its MSM8255 CPU and the ability to run CM10.1 as smoothly as my other devices
However, as I checked in ROM threads, before I flash any ROM, I have to flash the boot.img included MANUALLY VIA FASTBOOT, which renders on-the-go ROM switching impossible (i.e. I'll have to reach for my laptop whenever I'm itching to flash ).
One extra thing I tried is that, for my other devices, this command:
Code:
flash_image boot boot.img
...flashes a boot.img kernel via Terminal Emulator on the phone, enabling me to switch kernel really fast. Plus, these devices can also flash zip packaged kernels via CWM.
But when I executed the same command on XMP, an error pops up that goes, "can't find boot partition, failed with error: -1"...
So here's my question: how to flash kernels (boot.img) on the phone itself? Both command line method and CWM flashing method are welcome.
Thanks for reading this far and thanks in advance for any assistance!
Sent from HTC Incredible S @ PACman v21
It's not possible at the moment and probably will never be. You need access to PC if you want to flash kernel.
Koloses said:
It's not possible at the moment and probably will never be. You need access to PC if you want to flash kernel.
Click to expand...
Click to collapse
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package. Why not for similarly hardware designed XMP (and all MDPIs)? Is there any vital partition differences I missed?
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package.
Click to expand...
Click to collapse
No it doesn't, just because it's in the zip doesn't mean it gets flashed.
AndyYan said:
Reason? I've had my hands on an Arc S before, same 2011 lineup device, and its CWM flashes the kernel that comes with the ROM package. Why not for similarly hardware designed XMP (and all MDPIs)? Is there any vital partition differences I missed?
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
No it won't work like that. One reason should be that kernel+recovery are on one partition. But you need a PC
And no, arc s can't do that, too!
Sent from my Nexus 7 running Android 4.2.2
XperienceD said:
No it doesn't, just because it's in the zip doesn't mean it gets flashed.
Click to expand...
Click to collapse
mihahn said:
No it won't work like that. One reason should be that kernel+recovery are on one partition. But you need a PC
And no, arc s can't do that, too!
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Oh well... I must have forgotten about that Arc S, yeah I remembered I used fastboot to flash a FXP128 kernel to it back in the days... Thanks for helping guys! Too sad that I don't have easy access to my PC though...
Sent from HTC Incredible S @ PACman v21
mihahn said:
One reason should be that kernel+recovery are on one partition.
Click to expand...
Click to collapse
Wait a second! What's that partition's name, if it's not "boot" or "recovery"?? May not help with my problem, but if you know, please tell me!
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Wait a second! What's that partition's name, if it's not "boot" or "recovery"?? May not help with my problem, but if you know, please tell me!
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
I don't know the name and you can flash a kernel/recovery on its own, but if you flash the recovery first and afterwards a kernel, it'll be overwritten. So I guess it's the same partition, but I don't know more, sorry!
Sent from my Nexus 7 running Android 4.2.2
mihahn said:
I don't know the name and you can flash a kernel/recovery on its own, but if you flash the recovery first and afterwards a kernel, it'll be overwritten. So I guess it's the same partition, but I don't know more, sorry!
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
Well then, thx
Sent from HTC Incredible S @ PACman v21
Its not that kernel and recovery are on the same partition, its that we doesnt even have dedicated recovery partition in the first place. In fact, we doesnt even have the so called stock recovery at all.
All the custom recovery like twrp or cwm we got by fusing it in kernel ramdisk, and for locked bootloader by adding it to system partition.
an0nym0us_ said:
Its not that kernel and recovery are on the same partition, its that we doesnt even have dedicated recovery partition in the first place. In fact, we doesnt even have the so called stock recovery at all.
All the custom recovery like twrp or cwm we got by fusing it in kernel ramdisk, and for locked bootloader by adding it to system partition.
Click to expand...
Click to collapse
But here I'm talking about boot, not recovery, and not having a dedicated recovery is no prob for me. (Sorry if this sounds rude)
Recovery is fused into kernel, then is there a dedicated BOOT/KERNEL partition?
Sent from HTC Incredible S @ PACman v21
Of course there is. Every phone got boot partition. If it doesnt have one then where would the kernel be stored.
Consider this
There's a boot and a system partion. But no recovery partition
So the recovery goes along with the kernel to the boot partition. Since changing the kernel would involve changing in boot partition, the recovery would be wiped along with it, so it can't be done from the phone itself.
(Correct me if iam wrong)
Don't forget to hit thanks
I recently purchased a Xperia S LT26i. It does not have a recovery partition and cwm is embedded in the kernel ramdisk. Still, it is possible to flash kernels from recovery. I have no idea how does it work but we can definitely flash kernels via CWM. Secondly, flashing kernels means flashing a new recovery but on XS we have a Fota partition which is being used for storing the recovery(even without using this partition kernels can be flashed via CWM)
So maybe something can be done for our phones too.
Sent from my LT26i using xda app-developers app
mnishamk said:
Consider this
There's a boot and a system partion. But no recovery partition
So the recovery goes along with the kernel to the boot partition. Since changing the kernel would involve changing in boot partition, the recovery would be wiped along with it, so it can't be done from the phone itself.
(Correct me if iam wrong)
Don't forget to hit thanks
Click to expand...
Click to collapse
AFAIK, once CWM recovery is displayed, it's loaded into memory and thus the recovery partition CAN be wiped with recovery itself. Plus with other devices, the command "flash_image recovery recovery.img" works while booted up and in Terminal Emulator.
And we seem to drift away from my original question: is flashing KERNEL from phone possible? Not related to recovery, though recovery is bundled with kernel, with the above theory a kernel still can be flashed. I just don't know what the corresponding partition NAME for XMP's kernel is...
Sent from HTC Incredible S @ PACman v21
AndyYan said:
AFAIK, once CWM recovery is displayed, it's loaded into memory and thus the recovery partition CAN be wiped with recovery itself. Plus with other devices, the command "flash_image recovery recovery.img" works while booted up and in Terminal Emulator.
And we seem to drift away from my original question: is flashing KERNEL from phone possible? Not related to recovery, though recovery is bundled with kernel, with the above theory a kernel still can be flashed. I just don't know what the corresponding partition NAME for XMP's kernel is...
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
Even I think that Cwm is loaded into the ram when it starts. Here is the proof - when I had cwm installed on /system partition, I formatted /system in cwm but cwm still functioned properly until I rebooted. This proves that Cwm is loaded into Ram memory which is volatile.
Sent from my LT26i using xda app-developers app
To the OP AndyYan,
You can flash your boot.img file to xmp from your arc s and to arc s from xmp. Just find and download fastboot binary for arm devices. I flashed a kernel to my friend's Neo V from my XMP by this method. You have to connect the devices via a usb otg cable.
RavinduSha said:
To the OP AndyYan,
You can flash your boot.img file to xmp from your arc s and to arc s from xmp. Just find and download fastboot binary for arm devices. I flashed a kernel to my friend's Neo V from my XMP by this method. You have to connect the devices via a usb otg cable.
Click to expand...
Click to collapse
You mean I can run fastboot on another phone and flash the kernel? Well, not exactly what I expected, but still, will you give a link? And will the fastboot binary work for 1) non-Sony device and 2) device that doesn't support OTG?
EDIT: I got the fastboot binaries, and I do have a non-Sony device (the Vido tablet in my sig) which supports OTG. See if this works and I'll report back later
Sent from HTC Incredible S @ PACman v21
AndyYan said:
You mean I can run fastboot on another phone and flash the kernel? Well, not exactly what I expected, but still, will you give a link? And will the fastboot binary work for 1) non-Sony device and 2) device that doesn't support OTG?
EDIT: I got the fastboot binaries, and I do have a non-Sony device (the Vido tablet in my sig) which supports OTG. See if this works and I'll report back later
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
fastboot works on other devices too. you can check whether it works or not by typing any fastboot command in the terminal.
RavinduSha said:
fastboot works on other devices too. you can check whether it works or not by typing any fastboot command in the terminal.
Click to expand...
Click to collapse
Thanks, will try tonight!
(However, having to flash kernel in this way really suppresses my enthusiasm of flashing ROMs on XMP... )
Sent from HTC Incredible S @ PACman v21
Hello, thank you taking your time.
I Have flashed rooted modified many sony and samsung devices including 2 XUs before but this one does not get rooted in ICS.
I got a XU of a colleague running GB and I updated it to ICS .B.100 firmware. and for root, as usual method flashed .10 kernel and flashtool also stated boot loader status as rooted. but I cant get SU binary or superuser or supersu into the system using flashtool root or Doom-Lords batch file. all stops with 6..1.B.100 not supported even I have already flashed .10 kernel. So I checked build number on settings and it also stating .100 even flash tool successively flashed .10 . Then I tried manually push SU binary via adb and it soft bricked the phone. I cant understand what else I can do here. all adb drivers, s1 fast boot drivers, adb commands, fastboot commands all working perfectly. can somebody help me with whats going on here?
thank you again.
Note: Boot loader unlocked.
Fastboot a custom gb kernel?
Sent my Carbonised Xperia P
AndroidNoob69 said:
Fastboot a custom gb kernel?
Sent my Carbonised Xperia P
Click to expand...
Click to collapse
No I haven't tried that. but is it possible to use GB kernel with ICS firmware?
can you please give me little steps to include su binary after flashing it? thanks.
Update
I tried with different computer to flash .10 kernel but still flashtool says its successfully flashed but build number is still .100 and not getting root by DoomLord tool or flashtool.
suspect008 said:
I tried with different computer to flash .10 kernel but still flashtool says its successfully flashed but build number is still .100 and not getting root by DoomLord tool or flashtool.
Click to expand...
Click to collapse
So you are on ICS lol.... Then fastboot flash a ics custom kernel almost all custom kernels come pre-rooted.
P.S. Please use THE XDA Thanks button
Sent my Carbonised Xperia P