Sorry for the noob question.
I have upgraded my 5X to 7.0 and flashed a custom recovery and kernel. Everything went fine but I would like to try other kernels. A lot of the custom kernels say they should only be flashed on the original stock kernel. Where can I download the stock kernel and is it as straight forward as flashing the custom builds?
TIA
purpse said:
Sorry for the noob question.
I have upgraded my 5X to 7.0 and flashed a custom recovery and kernel. Everything went fine but I would like to try other kernels. A lot of the custom kernels say they should only be flashed on the original stock kernel. Where can I download the stock kernel and is it as straight forward as flashing the custom builds?
TIA
Click to expand...
Click to collapse
In TWRP, backup only boot.img and name it appropriately. Now flash your custom kernel. Each time you want to switch custom kernels while on the stock rom, reflash that boot.img.
To switch custom kernels while on custom roms, dirty flash your rom then flash the custom kernel. Dirty flashing (no wipe) restores the boot.img that ships with the custom rom.
Sent from my Nexus 5X using Tapatalk
Thanks. Do I flash kernel followed boot.img or other way round ir or does it not matter?
Sorry I read your post wrong. I didn't backup boot while on stock so I will need to go back to stock everything first
purpse said:
Sorry I read your post wrong. I didn't backup boot while on stock so I will need to go back to stock everything first
Click to expand...
Click to collapse
Or download the factory image from Google and pull the boot.img from the zip.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Or download the factory image from Google and pull the boot.img from the zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hmm, I just did this as well.
With ElementalX I was stuck on the android loading screen (bouncing bubbles)
Now after flashing boot.img from google, I"m stuck on the black "Google"
derrickl1990 said:
Hmm, I just did this as well.
With ElementalX I was stuck on the android loading screen (bouncing bubbles)
Now after flashing boot.img from google, I"m stuck on the black "Google"
Click to expand...
Click to collapse
Try flashing the boot and system image.
Sent from my Nexus 5X using Tapatalk
Related
Guys i need some advice with rooting my friend's Arc s. Here s what i did
Phone was on official ICS. I unlocked the bootloader using the official method.
Then i rooted it using some one click root method
Then installed recovery using recoverx software
Booted to recovery, wipe data, format system
Then tried to install a rom called racing bean. But i got and status 7 error. I tried some other JB rom.
But got the same error
Then i switched off and tried get to recovey. but could not
So i relocked the bootloader and installed official ICS again to boot the phone. The phone is fine now.
so can anybody help me to properly do this?? I just want to install CM on this phone
Racing bean or any other jb rom needs a JB Kernel too!.the ics kernel and jb rom mismatch might give that error.First flash a jb kernel and then it should work fine. This one's what i use http://forum.xda-developers.com/showthread.php?t=1885559.
First, you forgot kernel. Second make a backup with cwm before any wipe.
Sent from my LT15i using xda premium
I recommed TWRP recovery over cwm, it gave me problems starting out.
Sent from my EVO using xda app-developers app
Lordemort said:
Racing bean or any other jb rom needs a JB Kernel too!.the ics kernel and jb rom mismatch might give that error.First flash a jb kernel and then it should work fine. This one's what i use http://forum.xda-developers.com/showthread.php?t=1885559.
Click to expand...
Click to collapse
I flashed lupus kernel but after that i could not get into recovey. How can i do that?? I had the same problem with Arc fusion kernel
Well,there shouldnt be any problem,vol down or up button while the device lights up(led glows) does the job.But maybe u can try flashing it agn..if still having an issue..use an app like rom toolbox or boot manager to reboot into recovery..btw srry for the late reply
I gave up the effort. I tried about 6 Roms and kernels. Even ICS kernels with ICS roms. But After flashing the rom the phone does not go pass the kernel boot screen. I had to relock the bootloader and flash the stock Rom again. I have flashed hundreds of roms on so many devices. But never faced this kind of situation
pasanjay said:
Guys i need some advice with rooting my friend's Arc s. Here s what i did
Phone was on official ICS. I unlocked the bootloader using the official method.
Then i rooted it using some one click root method
Then installed recovery using recoverx software
Booted to recovery, wipe data, format system
Then tried to install a rom called racing bean. But i got and status 7 error. I tried some other JB rom.
But got the same error
Then i switched off and tried get to recovey. but could not
So i relocked the bootloader and installed official ICS again to boot the phone. The phone is fine now.
so can anybody help me to properly do this?? I just want to install CM on this phone
Click to expand...
Click to collapse
Not sure why you would have installed RecoverX if you have an unlocked bootloader as all you need to do is flash a kernel that includes CWM.
XperienceD said:
Not sure why you would have installed RecoverX if you have an unlocked bootloader as all you need to do is flash a kernel that includes CWM.
Click to expand...
Click to collapse
I have never played with a xperia device before. But i did flash kernels with cwm and flashed roms. But when i rebooted it never went pass the kernel boot screen
pasanjay said:
But i did flash kernels with cwm and flashed roms.
Click to expand...
Click to collapse
I think you should flash kernels via fastboot.
panda0 said:
I think you should flash kernels via fastboot.
Click to expand...
Click to collapse
Ya right i did flash the kernel via fastboot. Then booted into CWM and flashed the rom. But when i reboot it gets stuck at kernel screen
This happened to me and all I did was leave the phone like 10 mins booting, then it magically worked. I'm using Arc fusion 4.3 with racing bean, no problems. Try this, flash lupus kernel, wipe everything, go on fastboot and flash fusion, try to go on cwm and if it works, try to install racingbean again. At least that's one of the things I did.
AW: Need Help
Always give the recovery log...
& exact error code ^^
Than search google.
Than xda.
Than post ^^
flash newest sony ics stock rom-->fastboot kernel in the cm zip-->wipe all cm need-->use cwm flash rom-->use cwm flash gapp (goo.im/gapps) (ex: cm10 should be gapps-jb-20121011-signed.zip)-->enjoy!!
NOTE: If you are facing problems such as "Status Error 7" while installing, try THIS
Click to expand...
Click to collapse
pasanjay said:
Ya right i did flash the kernel via fastboot. Then booted into CWM and flashed the rom. But when i reboot it gets stuck at kernel screen
Click to expand...
Click to collapse
So you didn't see the boot animation after kernel screen?
How do you flash the kernel? Did you see it finished successful on screen?
croudra said:
So you didn't see the boot animation after kernel screen?
How do you flash the kernel? Did you see it finished successful on screen?
Click to expand...
Click to collapse
No i did not see the boot animation. And yes the kernels were flashed successfully.
croudra said:
So you didn't see the boot animation after kernel screen?
How do you flash the kernel? Did you see it finished successful on screen?
Click to expand...
Click to collapse
Sent froma see e$s my SCH-I535 using xda app-developers app
I started off by install unlocking bootlodaer, install CWM and then finally CM10.
But, when I was install CM10 via update.zip, I got some symlink error and phone just didn't boot & it always got hunged up at "SONY" logo screen. Clicking on Lolo of Sony more than 3 times was not helping either to get to CWM.
The way I solved this issue was by starting mobile in fastboot state and using recovery-nozomi file to flash it. May I know what this file did, because after that, I was able to enter CWM directly without doing any taps on Sony logo.
Someone please guess as to what might have happened? It's just a start & I've to do a lot of things from here on.
General is not for Questions. Post question on Q&A section.
And answering your question, I think you didn't flash CM10 Kernel. Isn't it? Stock kernel not work with CM10. You have to flash CM10 kernel in the package. Go HERE if you want more info about flashing kernel.
pharix said:
General is not for Questions. Post question on Q&A section.
And answering your question, I think you didn't flash CM10 Kernel. Isn't it? Stock kernel not work with CM10. You have to flash CM10 kernel in the package. Go HERE if you want more info about flashing kernel.
Click to expand...
Click to collapse
That was the thing, flashing the boot.img from CM10's zip fixed some random freezes that I was having. Why don't we flash those boot.imgs from the zip+CWM method itself? Is it like, it's not possible?
I think it is not possible to flash boot.img from cwm.
Sent from my LT28h using xda app-developers app
shadyabhi said:
That was the thing, flashing the boot.img from CM10's zip fixed some random freezes that I was having. Why don't we flash those boot.imgs from the zip+CWM method itself? Is it like, it's not possible?
Click to expand...
Click to collapse
Its not possible to flash boot.img from rom via cwm over stock kernel. Once you have a custom kernel, the recovery will automatically flash the kernel from zip the next you flash a different rom .
Sent from my Xperia S using xda premium
Just wondering if there are any flash able kernels yet since twrp is up and running?
There are three kernels that could be flashed without TWRP. Have you not checked the http://forum.xda-developers.com/pixel-xl/development subforum?
I'm currently using ElementalX and it's fantastic.
xocomaox said:
There are three kernels that could be flashed without TWRP. Have you not checked the http://forum.xda-developers.com/pixel-xl/development subforum?
I'm currently using ElementalX and it's fantastic.
Click to expand...
Click to collapse
Hence why I asked with twrp. I am through using fastboot/adb commands to flash kernels.
kirschdog1 said:
Hence why I asked with twrp. I am through using fastboot/adb commands to flash kernels.
Click to expand...
Click to collapse
Either using TWRP or fastboot the kernel gets installed the same way. What issues are you having with fastboot?
kirschdog1 said:
Hence why I asked with twrp. I am through using fastboot/adb commands to flash kernels.
Click to expand...
Click to collapse
You should always flash kernels through fastboot. It is the safest way.
nrage23 said:
You should always flash kernels through fastboot. It is the safest way.
Click to expand...
Click to collapse
Damn, I guess I have been living dangerously all these years. But yes, with fastboot you know what you are doing. With a toolkit, not necessarily so.
Does anybody have a link to stock kernel .img files by any chance?
airmaxx23 said:
Either using TWRP or fastboot the kernel gets installed the same way. What issues are you having with fastboot?
Click to expand...
Click to collapse
Fastboot after flashing stock boot.img to both boot a and boot b. Thrn installing twrp. then flashing su again and Then finally flashing the kernel and su again always gets me stuck in a boot loop. I have not ever since owning this phone been able to flash a kernel without getting stuck in twrp or blinking Google dots hangup. Any idea what I'm doing wrong?
TWRP can flash IMG files if you select the option in the install page of TWRP.
I don't think it'll do zimages though.
CZ Eddie said:
TWRP can flash IMG files if you select the option in the install page of TWRP.
I don't think it'll do zimages though.
Click to expand...
Click to collapse
It will not and dam sure do not try renaming the zimage to IMG. Bootloops will happen
Are all of these able to be installed on the Verizon Pixels?
themadmech said:
Are all of these able to be installed on the Verizon Pixels?
Click to expand...
Click to collapse
Yes
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
kirschdog1 said:
Fastboot after flashing stock boot.img to both boot a and boot b. Thrn installing twrp. then flashing su again and Then finally flashing the kernel and su again always gets me stuck in a boot loop. I have not ever since owning this phone been able to flash a kernel without getting stuck in twrp or blinking Google dots hangup. Any idea what I'm doing wrong?
Click to expand...
Click to collapse
Make sure you're flashing SR4 for root. SR3 and below do not play nice with TWRP
CZ Eddie said:
TWRP can flash IMG files if you select the option in the install page of TWRP.
I don't think it'll do zimages though.
Click to expand...
Click to collapse
So, if we did flash kernel with twrp, would the entire process be-- in twrp flash kernel IMG, then reflash superSU4 then reboot?
ya elementalx v1.0
Sent from my marlin using XDA Labs
@flar2 just updated EX to v1.00 and is flashable via TWRP.
Could someone post minfree values please? Thanks!
Juzman said:
@flar2 just updated EX to v1.00 and is flashable via TWRP.
Click to expand...
Click to collapse
Did u flash elemetal through zimage through twrp. Then flash su 4?
kirschdog1 said:
Did u flash elemetal through zimage through twrp. Then flash su 4?
Click to expand...
Click to collapse
No, downloaded zip and flashed via TWRP like a normal kernel.
^this. It works.
Sent from my Pixel XL using XDA Labs
Ok every time I flash rom it boots to boolaoder.
Instructions
Wipe dalvik cache,cache,data.
Flash rom then install then reboot then setup finish then reboot.flash kernel optional then magisk.
Can't get pass bootloader . Ease help thx and happy new yr to all
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
Ok every time I flash rom it boots to boolaoder.
Instructions
Wipe dalvik cache,cache,data.
Flash rom then install then reboot then setup finish then reboot.flash kernel optional then magisk.
Can't get pass bootloader . Ease help thx and happy new yr to all
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
What rom are you flashing? And what is reboot.flash? Try flashing the rom and then twrp if you want to keep that, I'd recommend you do. Then boot into system to see if it's working ok. Then if it is go back and flash the kernel and magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What rom are you flashing? And what is reboot.flash? Try flashing the rom and then twrp if you want to keep that, I'd recommend you do. Then boot into system to see if it's working ok. Then if it is go back and flash the kernel and magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm trying to flash bootlegger rom. Instructions say factory reset then flash rom then.setup device. Then reboot to twrp flash kernel then magisk. I tried with other rooms same thing stuck in bootloader. @jd1639 what rom are you on? And also how do you flash rom?
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
I'm trying to flash bootlegger rom. Instructions say factory reset then flash rom then.setup device. Then reboot to twrp flash kernel then magisk. I tried with other rooms same thing stuck in bootloader. @jd1639 what rom are you on? And also how do you flash rom?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm currently on stock rom with Kirisakura Kernel, but I have used bootlegger and it works for me.
After you flash the rom and boot into system does it just boot to the bootloader? If it does then I would start over by flashing the factory image with the flash-all batch file with the -w removed. Then make sure it boots into the system. Then I'd boot twrp, wipe the device, install the rom, then install twrp and boot to system. If it boots then boot back into recovery, twrp, and flash magisk. I don't know what kernel you are trying to flash but I believe bootlegger includes the Kirisakura Kernel. I'm very impressed with this kernel so I would not try to flash another one. If you are flashing a different kernel which one is it? It's possible that the kernel is not compatible with the bootlegger rom and that is what is causing your device to only boot to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm currently on stock rom with Kirisakura Kernel, but I have used bootlegger and it works for me.
After you flash the rom and boot into system does it just boot to the bootloader? If it does then I would start over by flashing the factory image with the flash-all batch file with the -w removed. Then make sure it boots into the system. Then I'd boot twrp, wipe the device, install the rom, then install twrp and boot to system. If it boots then boot back into recovery, twrp, and flash magisk. I don't know what kernel you are trying to flash but I believe bootlegger includes the Kirisakura Kernel. I'm very impressed with this kernel so I would not try to flash another one. If you are flashing a different kernel which one is it? It's possible that the kernel is not compatible with the bootlegger rom and that is what is causing your device to only boot to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok yea the furthest I get is after I flash bootlegger rom then twrp then I reboot to system that's when it goes straight to bootloader. I usually flash kernel and magisk after setup
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
Ok yea the furthest I get is after I flash bootlegger rom then twrp then I reboot to system that's when it goes straight to bootloader. I usually flash kernel and magisk after setup
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Start over by flashing the factory image, or at least the boot image to both slots. Boot is probably messed up right now. I'd flash the whole image as I suggested as some times system and other partitions get messed up too.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Start over by flashing the factory image, or at least the boot image to both slots. Boot is probably messed up right now. I'd flash the whole image as I suggested as some times system and other partitions get messed up too.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You think I should wipe the data?
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
You think I should wipe the data?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
No need to wipe data. When you to flash the rom I'd use the default wipe in twrp. Make a backup of the data partition in twrp before you wipe the device and store it off the device. You restore that after flashing the rom.
Sent from my [device_name] using XDA-Developers Legacy app
Hello,
I am trying to root my Google Pixel 2 XL running stock Android 11 with ElementalX Kernel.
However every time I try to root the phone, it gets stuck at boot.
I tried both flashing the magisk zip and patching the boot image with the magisk app.
Any idea why this is happening ?
Thanks !
The kernel could be the issue because the Magisk repo says to use stock kernel and/or stock boot.img. Try with stock everything and try again. Hope it helps.
muhammad42620 said:
The kernel could be the issue because the Magisk repo says to use stock kernel and/or stock boot.img. Try with stock everything and try again. Hope it helps.
Click to expand...
Click to collapse
I tried using the default Kernel and stock boot.img. At the time I was not using a custom kernel.
Thanks for the answer !