Related
What's up guys? I been flashing roms for a while now, and I have yet to flash a kernel. I wanna flash this one http://forum.xda-developers.com/showthread.php?t=1421704
I'm not sure what steps I have to do to successfully flash a kernel, Can I flash it just like I would a rom in rom manager? Or do I need to flash it in fast boot???
Any help would be appreciated! Thanks.
Flash a kernel by going into CWM recovery, wipe dalvik cache and regular cache , install, done or I think you can do it from rom manager, been awhile, but I believe you can install while wiping dalvik
Edit: oops said rom instead of kernel XD
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
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha
anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks
Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.
Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help
Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.
Hi,
When i tried flashing a custom rom and a custom kernel it just gives me black screen after starting up again maybe you guys have got the same problem before and what did you do to solve this issue? I tried these custom rom/custom kernel combinations :
FreedomOS-op3-nevax-1.7-CE-signed / blu_spark_r114-OOS-6.0.1 thulium
FreedomOS-op3-nevax-1.7-CE-signed / ElementalX-OP3-0.23
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / blu_spark_r114-OOS-6.0.1_thulium_e476ded
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / ElementalX-OP3-0.23
My TWRP version is 3.2.1 official
These are one of the many methods i tried:
Method 1
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Wipe cache, Dalvik/art cache.
4. Flash Custom Kernel.
5. Reboot.
Method 2
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
4. Wipe cache, Dalvik/art cache.
Method 3
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
These are some of the combinations i tried and even some of the methods i tried are nonsens but i am just trying to get it to work. If you need any more information just tell me . Help is very much appreciated .
3.5.2 base dont work with custom kernel yet. The twrp Version is a non known at my End. I think you better read this forum. From A to Z. Since all your awnsers can be found easy.
Saqrez said:
Hi,
When i tried flashing a custom rom and a custom kernel it just gives me black screen after starting up again maybe you guys have got the same problem before and what did you do to solve this issue? I tried these custom rom/custom kernel combinations :
FreedomOS-op3-nevax-1.7-CE-signed / blu_spark_r114-OOS-6.0.1 thulium
FreedomOS-op3-nevax-1.7-CE-signed / ElementalX-OP3-0.23
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / blu_spark_r114-OOS-6.0.1_thulium_e476ded
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / ElementalX-OP3-0.23
My TWRP version is 3.2.1 official
These are one of the many methods i tried:
Method 1
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Wipe cache, Dalvik/art cache.
4. Flash Custom Kernel.
5. Reboot.
Method 2
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
4. Wipe cache, Dalvik/art cache.
Method 3
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
These are some of the combinations i tried and even some of the methods i tried are nonsens but i am just trying to get it to work. If you need any more information just tell me . Help is very much appreciated .
Click to expand...
Click to collapse
try to flash supersu after the rom, reboot to system. Reboot back to recovery and flash kernel
otonieru said:
try to flash supersu after the rom, reboot to system. Reboot back to recovery and flash kernel
Click to expand...
Click to collapse
I didn't flash SuperSU as it is pre installed..
Darkje said:
3.5.2 base dont work with custom kernel yet. The twrp Version is a non known at my End. I think you better read this forum. From A to Z. Since all your awnsers can be found easy.
Click to expand...
Click to collapse
3.5.2 base? Can you please explain it a little bit more detailed thank you and i already read alot and can't find it thats why i made a thread.
Please read the freedom os topic. It address well why you cannot Flash a custom kernel. It is simply that kernel sources for Version 1.7 (aka 3.5.2 base) are not releases.
Darkje said:
Please read the freedom os topic. It address well why you cannot Flash a custom kernel. It is simply that kernel sources for Version 1.7 (aka 3.5.2 base) are not releases.
Click to expand...
Click to collapse
Oh i see any other idea for doing this with a different freedom os or something
Saqrez said:
Oh i see any other idea for doing this with a different freedom os or something
Click to expand...
Click to collapse
As suggested earlier try reading some ROM threads, going around flashing ROMs and kernels with no purpose is going to get you a soft brick very quickly.
My suggestion decide what you need out of a ROM, that is missing from stock, read a few rom threads to identify one that fills your needs. Then when you've got a ROM in mind go back and read the thread THOROUGHLY before flashing, had you done this with FreedomOS you wouldn't be here now.
Hello,
I don't know why my lg g3 phone doesn't want boot on custom rom.
I have the LG G3 d855 model, 16gb memory and here are my procedure to install every custom rom :
1. Flash Stock ROM using LGUP (the version of the firmware is not important but the possibility to root is)
2. Install KingRoot and get root
3. Install AutoREC and enter to the recovery
8. Flash Recovery TWRP 3.1.0-2
9. Reboot to the new recovery
10. ADVANCED WIPE (wipe cache, dalvik cache, data and SYSTEM)
11. Flash baseband 21C
12. Flash CUSTOM rom
13. Wipe cache and dalvik cache
14. Flash Gapp
15. Wipe cache and dalvik cache
16. Reboot
I think I did nothing bad...
but the phone does not start and it stays at the initial logo screen (not the LG logo, but the custom rom logo). I waited over 10 minutes to boot but nothing. Even though I install the identical rom again or install an anoter rom, each time the same issue.
This happens with all custom rom (xenonhd, resurrection remix, and now lineageOS)
I can use and boot on stock rom but each time I want to install a custom rom, my phone doesn't want to boot. The phone display stays at the initial rom logo screen.
It seems that I am alone to have this problem.
I don't know why and I search everywhere to find out the solution...
PS : My phone never restart by itself. I never have bootloop with my phone when I using stock rom and same with custom rom..
The problem is the boot with a custom rom. The phone don't want to boot and stay on logo loading...
Any suggestion may be help.
Thank you.
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Jornwitt said:
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Click to expand...
Click to collapse
Hello,
1. I think that but with specific rom, some people tell us to flash stock rom before flashing a custom rom. eMMC bug related ?
2. Deleting the system changes nothing because the system is wiped when I flash the rom, right ?
3. if the rom boot first then I will install Gapps. Else, I don’t install because the rom doesn’t want to boot.
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
I have the same problem
Jornwitt said:
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
Click to expand...
Click to collapse
Hello,
I have a question.
Can you give me a gapp 100% compatible with all custom rom with android 7.1.2, because i think opengapp are not reliable. Maybe the gapp will cause my issue and the rom won't boot.
Can i use this one https://forum.xda-developers.com/on...isited-slim-gapps-6-0-7-0-unofficial-t3462088 ?
I always use PICO version of gapp
Thank