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
Related
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
xlxcrossing said:
I bought this 3D used but like new and wanted to flash it to Boost so I was doing some preliminary pre-flash things like rooting and loading a custom recovery and rom. I used the HTC unlock method for the bootloader and flashed Eternity and it stuck at Beats screen (boot animation). I downloaded a different rom to see if it was the rom but that one froze at the animation screen as well. I attempted to do an RUU stock reset on my PC from bootloader but it returned an error saying update failed. I'm basically locked out of this phone. I read everything it said about flashing custom kernels and how you are supposed to flash them from bootloader. I know Eternity has a stock kernel don't know about the other one. My last resort is to download a zip of a stock rom and flash that from recovery. If it freezes on me I'm not sure what I'll do next. Any help is appreciated...
Click to expand...
Click to collapse
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
JayDaKissEP said:
Did you follow the root instructions all the way through to install Superuser and the recovery? If so, did you boot into fastboot, connect usb, then do the fastboot boot recovery.img before flashing the rom?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I did not use that method to flash, no. I'm assuming you mean from my PC execute the command. I did follow the instructions to install TWRP which is a custom recovery and I flashed a ZIP from TWRP for Superuser and checked it to be working which it was. (I tested Root Explorer and Terminal Emulator for root)
I was operating off the assumption that custom roms with a STOCK kernel could be flashed by booting into recovery. I went to bootloader then recovery then flashed the rom. Obviously I did something wrong since both roms wouldn't load. I will use your method of PC commands from fastboot into recovery and see where that gets me....pease let me know if this is correct or anything else I need to do....thanks a bunch.
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
xlxcrossing said:
UPDATE : I tried the method of loading recovery from fastboot usb - it worked thank you. The rom loaded. I'm wondering why since it was a custom rom with a stock kernel why I couldn't flash it from recovery.
Click to expand...
Click to collapse
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
ifly4vamerica said:
While the kernel is stock, Virus has a bunch of binaries and such that will be mismatched without flashing the boot.img properly ... So while some of his builds say "stock" not always completely stock.
Click to expand...
Click to collapse
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
xlxcrossing said:
cool cool thanks for the info. So I need to load the recovery.img file from usb fastboot EVERY time I want to flash a rom? Any way to eliminate this hassle....I just assume flash less often if not...thanks
Click to expand...
Click to collapse
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Twolazyg said:
With hboot 1.5, the ONLY way to flash a ROM correctly is with fastboot>recovery.
Click to expand...
Click to collapse
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
JayDaKissEP said:
Not true. You can flash a ROM but if you don't use fastboot it won't touch the kernel. I always change roms with the stock kernel. He must have done something wrong
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
ifly4vamerica said:
If the kernel is pure stock with no added binaries or stuff it will work. Virus puts lots of little tweaks in that require it. Now if you can load a completely stock kernel and ramdisk then load Eternity (of course some eternity builds did have a completely stock kernel) then you may be onto something.
As far as flashing with hboot 1.50 easiest way to do that without the computer is with joeykrm's flash image gui. I don't have 1.50 but I have used his gui to do partial updates on svn builds in tandem with adb sync and it works great. His post with the apk is in development section. just read the instructions and flash away.
Click to expand...
Click to collapse
Yeah I read all about it I'm still stuck on why if I had a stock kernel installed with a stock rom and I do a custom rom flash and as stated it doesn't touch the kernel why the rom wouldn't simply run off the stock kernel - that's what confuses me. I understand the issue of the kernel not being flashed which is obviously what happened with me. I just don't really know where I stand with what kernel to ALWAYS have loaded since if that's the thing with the issue I would want to for purposes of not doing tons of work stay away from flashing kernels and stick to flashing roms when I want to change it up. But if the STOCK kernel won't load with a custom rom which technically it should I guess I'll just have to flash a universal custom kernel and assume any rom I flash will simply use that kernel. Kind of a nightmare compared to my 4G....welcome to the world of the 3D I guess.
I guess going into recovery from hboot with the volume and power buttons wouldn't count - I have to stick with PC commands?
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.
I want to unlock my bl and to flash this kernel LuPuS_smultron_GingerBreadv1-full for stock GB,BUT i don't know what's the next step after flashing it
Do i have to flash gb rom or not,after flashing this kernel can i boot my phone?
I'm on stock GB!
So,i need help or a guide or something which is helpful for my question...
I hope you guys understand what i want?!
arvarobert said:
I want to unlock my bl and to flash this kernel LuPuS_smultron_GingerBreadv1-full for stock GB,BUT i don't know what's the next step after flashing it
Do i have to flash gb rom or not,after flashing this kernel can i boot my phone?
I'm on stock GB!
So,i need help or a guide or something which is helpful for my question...
I hope you guys understand what i want?!
Click to expand...
Click to collapse
@arvarobert
first you Unlock the bootloader after that let your device boot first... once it boots power off it again, once you are done with it..... connect your device to latest flashtool in fastboot mode and flash the kernel you want thats it!!
*make sure that the kernel supports GB
* how to connect in fastboot mode??
Ans: Once your phone is switched off hold the volume Up button and connect the USB cable then the notification LED will glow Bluewhich means you are connected in fastboot mode
DONT forget to click thanks
This kernel is for GB!
So just flash kernel and turn on Your phone. No need to install ROM again.
Here is the original thread
http://forum.xda-developers.com/showthread.php?t=2295108
BTW:is the official way for unlocking bl still working?
arvarobert said:
BTW:is the official way for unlocking bl still working?
Click to expand...
Click to collapse
Yes. http://unlockbootloader.sonymobile.com
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!
Rooting Method for Xperia Z Ultra Lollipop V5.1 .
What You Need :
5.1 .
Root & Recovery Pre-Installed .
Flashtool & PC .
MAKE A BACKUP FIRST​
How To :
As a Start, You Gonna have Lollipop 5.0 with Root & Recovery installed .
Move 5.1 to firmwares folder .
Download This SuperSu Flashable file and move it to SDCard & Internal Storage .
Open Flashtool .
Select The ROM .
Exclude Kernel ONLY .
Flash the ROM .
Boot the Phone and enter Recovery ASAP .
Install the ZIP File, if Flashtool didn't wipe Internal storage yet, then install it from Internal storage, otherwise from SD Card .
Power Off .
Open Flashtool .
Select 5.1 .
Exclude All expect the Kernel .
Un-tick Data / Cache and the third option too .
Flash .
Boot ! .
As a feedback from my friend, he said there was not problem with 5.0 kernel on 5.1 system for first boot ( recovery entering only ) .
Please feedback, and don't forget the backup !
is it 5.1 or 5.1.1?
The quick way to root any ROM, including the newly released 5.1.1 is, if you have an unlocked bootloader:
- Hotboot any custom kernel with a recovery (fastboot)
- Flash SuperSU
- Reboot
If you want CWM/TWRP:
- Flash NUT's Dual Recovery kernel through fastboot
- Reboot
You're now rooted, and you have recovery.
NOTE: If you have no idea how to use fastboot, then you can use QuickIMG. It lets you flash .IMGs very easily without needing to use any commands. Do however read the instructions provided before you use it.
It's also a good idea to learn how to get out of a sticky situation in case something goes wrong. If you want to be on the safe side when testing kernels, hotboot, or boot an IMG/kernel instead of flashing. Once you see that the kernel is indeed working, and you're not experiencing any bootloops or red LED blinking, then you can safely flash it to disk.
Note: Hotbooting means that the device will only boot the kernel once, so it doesn't really flash it to the device. Flashing a kernel writes it to the device, making it permanent until you replace it by flashing a different kernel yourself.
jaime4272 said:
is it 5.1 or 5.1.1?
Click to expand...
Click to collapse
5.1.X
Klaos3000 said:
The quick way to root any ROM, including the newly released 5.1.1 is, if you have an unlocked bootloader:
- Hotboot any custom kernel with a recovery (fastboot)
- Flash SuperSU
- Reboot
If you want CWM/TWRP:
- Flash NUT's Dual Recovery kernel through fastboot
- Reboot
You're now rooted, and you have recovery.
NOTE: If you have no idea how to use fastboot, then you can use QuickIMG. It lets you flash .IMGs very easily without needing to use any commands. Do however read the instructions provided before you use it.
It's also a good idea to learn how to get out of a sticky situation in case something goes wrong. If you want to be on the safe side when testing kernels, hotboot, or boot an IMG/kernel instead of flashing. Once you see that the kernel is indeed working, and you're not experiencing any bootloops or red LED blinking, then you can safely flash it to disk.
Note: Hotbooting means that the device will only boot the kernel once, so it doesn't really flash it to the device. Flashing a kernel writes it to the device, making it permanent until you replace it by flashing a different kernel yourself.
Click to expand...
Click to collapse
The way for locked bootloader not for unlocked .
Anyway, anyone tested it ?
How about using the prf (pre rooted firmware) tool for locked bootloader?
Sent from my C6833 using Tapatalk
ejhayanchorez said:
How about using the prf (pre rooted firmware) tool for locked bootloader?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I Didn't see a pre-rooted firmware, that's why i put this guide, if someone can do it and upload the firmware that's would be awesome .
hi there. I just want to say that after following your guide I could not get in to recovery after flashing the 5.1.1 ftf minus the kernel. when turning the phone on it goes straight to normal boot but it doesn't. it goes in to a boot loop. some how it removes dual recovery and can't flash SuperSU there for loosing root and yes I was rooted with dual recovery. could you explain with more details how to please because I did as you said and didn't work
jaime4272 said:
hi there. I just want to say that after following your guide I could not get in to recovery after flashing the 5.1.1 ftf minus the kernel. when turning the phone on it goes straight to normal boot but it doesn't. it goes in to a boot loop. some how it removes dual recovery and can't flash SuperSU there for loosing root and yes I was rooted with dual recovery. could you explain with more details how to please because I did as you said and didn't work
Click to expand...
Click to collapse
Follow this guide : http://forum.xda-developers.com/xpe...ck-rom-5-1-1-lollipop-xperia-z-ultra-t3206107
This guide isn't working on all devices, don't know why.
thanks i'll give it a try