Hello!
The last couple of days I'm struggling to get any custom kernel running on my phone.
Every custom JB kernel is tried resulted in almost instant instability (while setting up my phone after a full wipe for example).
Even Alex's kernel which is almost stock with only the S2W function build-in is unstable for me.
Real stock kernel is running rock stable, and in the past(ICS) i hadn't any issues when flashing custom kernels.
My phone is on Hboot 1.31 <updated to 1.39> and I have a variant 1 Tegra 3.
I'm using Renovate Final 1.1 (and as far as I read the comments in their thread, nobody is experiencing the instability issues).
I tried the following kernels (repacked for my rom):
* Alex-v s2w
* XM-Kernel
* KozmiKKernel
* NXC V6
I have flashed in the right steps:
* Clear cache/dalvik/system/data (recovery)
* Full wipe
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install rom.zip (recovery)
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img custom kernel (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install modules.zip (recovery)
* Clear cache/dalvik/system/data (recovery)
Normally(ICS) my phone would run fine after the above steps, but now my phone is really unstable after flashing one of these custom kernels.
Is there something wrong with my hardware or are these custom kernels not build for my variant 1 ?
Since stock kernel is really stable without any issues.
Dude you are making things overly complicated.
1. Fastboot flash boot boot.img
2. Fastboot erase cache
3. Go to recovery
4. Select ROM zip
5.full wipe option in aroma installer OR you could have wiped system/data/cache in recovery
6. Flash modules zip
7. Reboot
PS variant affects overclocking and undervolting ability. Also, Alex kernel shouldn't cause problems since its just stock kernel with sweep2wake. And you don't need to perform wipes a billion times, its like trying to tidy an empty room.
Sent from my HTC One X using xda app-developers app
tomascus said:
Dude you are making things overly complicated.
1. Fastboot flash boot boot.img
2. Fastboot erase cache
3. Go to recovery
4. Select ROM zip
5.full wipe option in aroma installer OR you could have wiped system/data/cache in recovery
6. Flash modules zip
7. Reboot
PS variant affects overclocking and undervolting ability. Also, Alex kernel shouldn't cause problems since its just stock kernel with sweep2wake. And you don't need to perform wipes a billion times, its like trying to tidy an empty room.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ye I know I clean too thoroughly, but I did that to remove any obstructions that might cause issues, but neither work.
I upgraded my HBOOT to 1.39 but still stability issues when running a kernel that isn't stock (even Alex).
d33f said:
Ye I know I clean too thoroughly, but I did that to remove any obstructions that might cause issues, but neither work.
I upgraded my HBOOT to 1.39 but still stability issues when running a kernel that isn't stock (even Alex).
Click to expand...
Click to collapse
Are you repacked the KERNEL for your ROM? If don't try to repack with http://forum.xda-developers.com/showthread.php?t=1815607. Most of the Developers recommend to repack the KERNEL to the ROM!!!
Thant said:
Are you repacked the KERNEL for your ROM? If don't try to repack with http://forum.xda-developers.com/showthread.php?t=1815607. Most of the Developers recommend to repack the KERNEL to the ROM!!!
Click to expand...
Click to collapse
The kernels are repacked for my rom(those I tried)
then dont use s2w?
d33f said:
Hello!
The last couple of days I'm struggling to get any custom kernel running on my phone.
Every custom JB kernel is tried resulted in almost instant instability (while setting up my phone after a full wipe for example).
Even Alex's kernel which is almost stock with only the S2W function build-in is unstable for me.
Real stock kernel is running rock stable, and in the past(ICS) i hadn't any issues when flashing custom kernels.
My phone is on Hboot 1.31 and I have a variant 1 Tegra 3.
I'm using Renovate Final 1.1 (and as far as I read the comments in their thread, nobody is experiencing the instability issues).
I tried the following kernels (repacked for my rom):
* Alex-v s2w
* XM-Kernel
* KozmiKKernel
* NXC V6
I have flashed in the right steps:
* Clear cache/dalvik/system/data (recovery)
* Full wipe
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install rom.zip (recovery)
* Fastboot erase cache (fastboot)
* Fastboot flash boot boot.img custom kernel (fastboot)
* Fastboot erase cache (fastboot)
* Clear cache/dalvik/system/data (recovery)
* Install modules.zip (recovery)
* Clear cache/dalvik/system/data (recovery)
Normally(ICS) my phone would run fine after the above steps, but now my phone is really unstable after flashing one of these custom kernels.
Is there something wrong with my hardware or are these custom kernels not build for my variant 1 ?
Since stock kernel is really stable without any issues.
Click to expand...
Click to collapse
d33f said:
Ye I know I clean too thoroughly, but I did that to remove any obstructions that might cause issues, but neither work.
I upgraded my HBOOT to 1.39 but still stability issues when running a kernel that isn't stock (even Alex).
Click to expand...
Click to collapse
The reason why you end up in the bootloop is because you clean up too much , after you flash the rom with the default kernel that comes with it (boot.img) let it boot up in system , after that wait at least 5 mins for it to load everything and seddle then do a full reboot, after that you can flash the kernel , if you don't know how to repack on your own use this link = http://nibble.cc/repack/ , in the *source* box put ROM boot.img and in the *kernel img* put the boot.img from the kernel that you want to flash , wait few mins to repack it , download it, rename it into *boot.img* and done, after that flash exactly as i type:
go to bootloader
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
go to recovery
Wipe cache
Wipe dalvic cache
If on 100% battery wipe battery stats
Install the modules
REBOOT
Enjoy the new kernel
Your bootloops were happening because you were wiping SYSTEM which means you delete the SYSTEM of the ROM = 100% bootloop , when you install modules you're not install whole new system on the phone only the kernel ram disk and few other small things. NEVER wipe anything else then what i wrote above. Anyhow after you boot up in the system let the phone seddle for 5 mins at least and then do FULL REBOOT . after that do whatever you want to doo. Hope it helps.
I didn't had any boot loops, only stability issues.. (rom is booting fine, only my phone reboots as soon as I start Antutu and let it benchmark).
Furthermore I tried to install my rom again with full wipe and I've done these exact same steps after flashing my rom:
go to bootloader
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
go to recovery
Wipe cache
Wipe dalvic cache
If on 100% battery wipe battery stats
Install the modules
REBOOT
Enjoy the new kernel
Still really unstable as soon as I push my phone (freeze and reboot)
The only reason I can think of is that I didn't let the rom settle (flashed the rom and immediately flashed the custom kernel after).
But in the past(ICS) I've done this the same way without any issues
d33f said:
I didn't had any boot loops, only stability issues.. (rom is booting fine, only my phone reboots as soon as I start Antutu and let it benchmark).
Furthermore I tried to install my rom again with full wipe and I've done these exact same steps after flashing my rom:
go to bootloader
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
go to recovery
Wipe cache
Wipe dalvic cache
If on 100% battery wipe battery stats
Install the modules
REBOOT
Enjoy the new kernel
Still really unstable as soon as I push my phone (freeze and reboot)
The only reason I can think of is that I didn't let the rom settle (flashed the rom and immediately flashed the custom kernel after).
But in the past(ICS) I've done this the same way without any issues
Click to expand...
Click to collapse
You should never flash the kernel right after the rom , you should let the Rom with it default kernel and boot img boot up 1st for the 1st time, set it up if you like or not , but let it seddle at least for 5 mins, then do 1 full reboot and after that flash kernel.
Even if this doesn't help then probably your chip isn't strong enough for Oc'ed version of Kernels , if you have variant 0 that could be your issue , or perhaps 1 , but 1 should support this, my cousin has variant 1 and he can flash / use kenrnels without issues. Anyway try after the flash to boot up the phone and do what i wrote above , if that doesn't help report back i'll try to think of something else in the meanwhile lol.
Edit - nevermind about variant forgot you mentioned you have variant 1. Oh well just try with other things i suggested.
Shan89 said:
You should never flash the kernel right after the rom , you should let the Rom with it default kernel and boot img boot up 1st for the 1st time, set it up if you like or not , but let it seddle at least for 5 mins, then do 1 full reboot and after that flash kernel.
Even if this doesn't help then probably your chip isn't strong enough for Oc'ed version of Kernels , if you have variant 0 that could be your issue , or perhaps 1 , but 1 should support this, my cousin has variant 1 and he can flash / use kenrnels without issues. Anyway try after the flash to boot up the phone and do what i wrote above , if that doesn't help report back i'll try to think of something else in the meanwhile lol.
Edit - nevermind about variant forgot you mentioned you have variant 1. Oh well just try with other things i suggested.
Click to expand...
Click to collapse
Thanks for your advice, I'll try it again later today and report back..
My rom has settled for a couple of days now with stock kernel, so I'll see what it does with a custom kernel again.
I tried NCX V13 today, it's stable!
What I've done differently is that I didn't wipe anything in recovery after flashing the modules.
Furthermore I let the phone settle for 5 minutes before running Antutu.
I don't know if this is really the cure for my issue or that this V13 kernel is the first kernel stable enough for my SoC, but it works now!
Did got a few hard reboots today while running Epic Citadel/Antutu with gaming boost enable and phone on charger.. I reflashed the kernel, let the phone cool down and everything is running stable again
Related
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
dntesinfrno said:
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
Click to expand...
Click to collapse
Thanks man, will try your method and report back.
once you flashed your ROM(aokp) you need to reboot and let the phone fully boot into android... after that reboot to recovery and try flashing your Gapp + kernel
don't forget all the wiping and fixing permission for each steps
edit: wow this tab was open for a long time i guess. there was no other answer when i wrote this browsing through my opened tabs.
dingrn said:
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
Click to expand...
Click to collapse
Kevin my phone is exactly having the same problem did you come to a resolution
Especially on aosp roms it might help to flash the rom, let it boot once, then boot into recovery and flash kernel, wipe cache & dalvik, and fix permissions.
Also i've heard that some people will have alot of reboots before the kernel starts running smooth and stable. Or you could just have a bad phone that doesn't like to be tweaked. If i were you i'd take advantage of that warranty and try to get a replacement.
sorry for being a newbie....but what do you mean by fix permissions? =/
ohaai said:
sorry for being a newbie....but what do you mean by fix permissions? =/
Click to expand...
Click to collapse
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
jefferson9 said:
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
Click to expand...
Click to collapse
ive tried so many different methods of flashing kernels and all of them result in huge problems with crashes and random reboots all methods posted earlier are a gigantic fail. Im returning this refurbished phone for another refurbished and will report back
droidfta said:
Kevin my phone is exactly having the same problem did you come to a resolution
Click to expand...
Click to collapse
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
dingrn said:
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
Click to expand...
Click to collapse
hey had the same exact problem. Got a new phone under warranty cpu temps run lower and stable under current kt747 kernel I'll wait a few more days before underclocking but it's defiantly the phone you just got a weak cpu like I did
i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?
i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop
also not running the newest version of that rom, i am running v15a
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,
1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0
Hey guys,
since a few weeks now i have some problems if i flash new kernels on sense based roms.
Always if i flash a new kernel WIFI/Signal/GPS does not work...
On AOSP/CM10/AOKP everything works fine.
I also tested some new radios, currently im on 5.1204.162A.29 and on hboot 1.36 (CID VODAP120)
Does someone know how to fix that?
Greets Gingerbread
/Edit: I also tried to set APN manually but it doesnt work...
Which ROM are you on currently?
If you flash an AOSP kernel on a Sense ROM, it might break something and vice-versa.... hence the problem...
And after flashing the boot.img via fastboot, you also have to flash the modules via recovery and then wipe cache/dalvic!
vin4yak said:
Which ROM are you on currently?
If you flash an AOSP kernel on a Sense ROM, it might break something and vice-versa.... hence the problem...
And after flashing the boot.img via fastboot, you also have to flash the modules via recovery and then wipe cache/dalvic!
Click to expand...
Click to collapse
Im Currently on MIUI v5, and i flashed a sense Kernel.
Here a list what i did:;
1. flashed boot img.
2. erase cache
3. flashed sense Kernel. (After i did a full boot of the rom)
4. wipe dalvik cache
5 setup APN
and it still does not work.
Gingerbread23 said:
Im Currently on MIUI v5, and i flashed a sense Kernel.
Here a list what i did:;
1. flashed boot img.
2. erase cache
3. flashed sense Kernel. (After i did a full boot of the rom)
4. wipe dalvik cache
5 setup APN
and it still does not work.
Click to expand...
Click to collapse
I have absolutely no idea about MIUI.. I only know this much that you have to flash a sense kernel... Does it need repack? No clue! Wait for some other person to reply or ask in the MIUI thread...
However, you shouldn't boot into your ROM after flashing the boot.img
1. fastboot flash boot boot.img
2. fastboot erase cache
3. Go to recovery and wipe cache partition and wipe dalvic
4. Flash modules.zip
5. Reboot
vin4yak said:
I have absolutely no idea about MIUI.. I only know this much that you have to flash a sense kernel... Does it need repack? No clue! Wait for some other person to reply or ask in the MIUI thread...
However, you shouldn't boot into your ROM after flashing the boot.img
1. fastboot flash boot boot.img
2. fastboot erase cache
3. Go to recovery and wipe cache partition and wipe dalvic
4. Flash modules.zip
5. Reboot
Click to expand...
Click to collapse
Oops sry, i mean i flashed boot.img AND kernel after i made a full boot.
And i tried it with repacking and normal boot.img.
Gingerbread23 said:
Oops sry, i mean i flashed boot.img AND kernel after i made a full boot.
And i tried it with repacking and normal boot.img.
Click to expand...
Click to collapse
Hmmm... try wiping cache and dalvic... Reboot...
Ask ROM related issues in the ROM thread m8! there you will get more accurate answers from the other MIUI users and developer!
The problem is its on all sense roms...
Only on AOSP/CM10/AOKP roms everything works fine.
push
I am trying to install Fulmics Rom and then Flash with Xceed but this is my first time so I'm wondering if the steps I took is correct?
What I did:
1. Root using the one click method
2. Boot into recovery with TWRP
3. Wipe data, system, cache, dalvic and then install Fulmics Rom
4. Boot back into recovery and flash using the Xceed Kernel?
When I boot after flashing with the Xceed Kernel, Synapse keeps saying that the Kernel has not been applied or something like that so I was wondering if I was doing something wrong.
You can install the Xceed kernel directly after flashing the ROM, by adding it to the queue in TWRP. There's no need to reboot back into recovery to flash the kernel.
Baegmon said:
I am trying to install Fulmics Rom and then Flash with Xceed but this is my first time so I'm wondering if the steps I took is correct?
What I did:
1. Root using the one click method
2. Boot into recovery with TWRP
3. Wipe data, system, cache, dalvic and then install Fulmics Rom
4. Boot back into recovery and flash using the Xceed Kernel?
When I boot after flashing with the Xceed Kernel, Synapse keeps saying that the Kernel has not been applied or something like that so I was wondering if I was doing something wrong.
Click to expand...
Click to collapse
Like the above, and if synapse say this, its because it detected that the settings that you set were dangerous for the device.
So i rooted my phone sometimes ago, and it worked fine at first but after some reboots it is now stuck at Redmi logo and would boot to fastboot mode after a while. Now i want to share my experience so people can be more careful, i may be a newbie but i do want to help people too.
So here's what my phone is using, CorvusOS 7.0 and SiLonT kernel and no more modifications other than that. Now i have read stuff online that some people have experienced bootloops and some can't boot to the OS they rooted their device with magisk. I have also read that dirty flash may solve the problem. But if you're already facing this problem maybe you can try these methods below:
Method 1: probably the easiest one, wipe the Dalvik and the cache
1. Reboot to your custom recovery
2. Go to advanced wipe (location and UI may differs between custom recoveries)
3. Simply tick Dalvik and cache and untick anything else
4. Reboot
Method 2: uninstalling magisk (this will unroot your device)
1. Download magisk uninstaller.zip (if you didn't downloaded it already from the start. Also make sure the uninstaller is the same version as your magisk version, idk what will happen if you do it with a different version but just in case )
2. Reboot to your custom recovery
3. And simply just flash/install the magisk uninstaller.zip, this will delete all magisk's files
4. Wipe Dalvik and cache (just in case)
5. Reboot
Method 3: dirty flash (for custom ROMs)
1. Uninstall magisk (follow method 2)
2. Get/download your custom ROM you are using (make sure it's the same ROM and version as the ROM you're using rn)
3. Flash it without wiping anything
4. Wipe Dalvik and cache (just in case, again)
5. Reboot
Method 4: reinstall/install your ROM, for custom ROMs users (I'm sorry i am not experienced with XiaomiFlashTool so i can't tell you how to flash stock ROM)
1. Backup all data cause this will erase all your data
2. Reboot to recovery
3. Uninstall magisk (follow method 2)
4. Wipe system, data, cache, Dalvik (the usual stuff you would wipe before installing a custom a ROM)
5. Install your chosen ROM
6. Wipe Dalvik and cache (just in case)
7. Reboot
If those methods above doesn't work you can try searching a tutorial on flashing the stock ROM on the internet, but if you still didn't manage to get your phone boot to the OS again then i am sorry to say that you have to take your phone to the nearest repair center.
So, what's the cause of this problem?
Well, it's simple, every human make mistakes, At least once. So it is normal to make mistakes. The developers are humans too so it is normal for them to make mistakes too, so instead blaming them we should support them and give them advice. But on the other side you may did a mistake too, probably a similar mistake that i did. Like maybe you did something wrong according to the tutorial, or you flashed an incompatible version of magisk, and etc. So from now on always ask if it's compatible, whether it's about magisk versions, ROM compatibility, kernel compatibility, recovery compatibility, and etc. And always double check just in case.
If i did something wrong tell me down below and I'll fix it as soon as possible.
Peace.
One quick little note: i fixed my device by doing a dirty flash (method 3) just to let you know
Edit: Phone won't boot after uninstalling magisk*, that was supposed to be title. Sorry I just realized sometimes ago
This happens to me all the time when flashing Android 11 ROMS. Curiously this doesn't happen when flashing Android 10 ROMs. I also never had this issue with TWRP, only OrangeFox.
But it could be other things too. For example, Xiaomi.eu 12.5 always go into a bootloop here, and trying to go back to any other ROM after flashing it leads to a boot loop. The fix is to flash disabled vbmeta if you're flashing xiaomi.eu 12.5. That might be the fix for A11 roms too but I never tried.
More than once it happened to me too that no matter what I did the phone would be stuck in bootloops with any ROM, any recovery. In that case, flashing stock rom via fastboot fixed the issue.