I got tasked with fixing someones evo lte. He flashed a kernel. cm wont boot or when it does it says some error. now everything bootloops. i tried flashing back to a sense rom and it would hang on the installing kernel part of the installation. finally it finished but just bootlooped.
when it was able to have cm or aokp, can't remember which, to be installed and boot, it would still show that new kernel as the kernel running on the phone.
Ideas?
flash a new rom and then a new kernel?
ive never had the issue of not being able to get back to whatever kernel is packed with the rom.
and really, i've only been able to boot it once since it was brought to me.
right now its pretty much a boot loop all the time.
and yes, wipe, factory reset, wipe cache dalvik all that has been done multiple multiple times
im a One X user, so im familiar with this stuff but all the roms and kernels are different and so im also kinda lost here
thanks
Boot to bootloader and fastboot install kernel for the rom, make sure the base matches 2.13 kernel and ROM, sense with Sense, AOSP with AOSP etc. Meanrom and a few others have built in kernel installers but if for some reason it doesn't boot, extract boot.img from the rom zip.
Related
Hey guys.
I'm on LA4 and i want to flash a custom ROM onto my SGS2.
I treid CM7 (flashed is twice) and som other ROMS but everytime i flash it, i get in a boot loop.
I hope i'm doing it the right way?
I copy the .zip file to my sdcard and press "install zip" in the recovery mode.
Did you wipe data/cache/dalvik before installing the rom? It's pretty much important, especially if you're going from LA4 to CM7
yea,sure!
before and after the flashing i wiped all
Edit: Also try format /system after you wipe the 3 said above.
Try going back to your stock image and flash a stock KERNEL afterwards, boot CWM, flash a stock image, when done, flash a stock kernel and newest radio.
I'd say it might be a kernel issue. I had it when I flashed MIUI, and in reverse when I flashed back to others..
Sent from my Galaxy Nexus using xda premium
Try avoiding wiping it afterwards. Just wipe everything out, flash it and immediately reboot.
I also hope you did a nandroid backup as well. If you did that and it still boot loops, try restoring it and going back to it and having another go.
oh my gosh i figured it out!
CuraeL, you're right.. its a kernel problem
i have to flash the kernel again after the rom update.. weird but only that way it's working!
thanks
No worries. I have had to do it on a lot of the roms I installed myself, on my SGS II, back in the days. Wonderful phone, a bit weird the way the whole kernel thing is made. But I suppose that's cause the kernels are written for 2 different "builts" of the system.
Keep it in mind, as you might need to do it again some day, lol.
Have fun. ^^
hello all,
After upgrate cm-10.1.0-galaxysmtd.zip to cm-10.1.2-galaxysmtd.zip i dont have recovery mode, playstore and rom manager...
how to repair all ?
thanks in advance.
after some manipulation i have just a mode download....:crying:
problems with flashing roms and/or booting in to recovery
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.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not 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
A couple months ago I was having problems with my recovery. It kept crashing every time I tried to flash anything. Found out I needed to format my internal storage, once I did that I was able to flash CM but when I tried to flash a TW rom I get stuck in a bootloop. I re-downloaded the same rom 3 times thinking it was a bad download no dice. Tried other TW roms still no dice. But, when I flash a ASOP rom it works just fine. What could of caused this issue?
Anybody Know how to solve this? Been trying to figure this issue out for a whole month!
just a guess but for Note 2/3/4 users with locked bootloaders you cannot flash a kernel. Using safestrap or another vitual rom required it to be TW-based. If you're running true AOSP and was able to flash CM are you sure you're running the stock kernel?
Reilly1812 said:
just a guess but for Note 2/3/4 users with locked bootloaders you cannot flash a kernel. Using safestrap or another vitual rom required it to be TW-based. If you're running true AOSP and was able to flash CM are you sure you're running the stock kernel?
Click to expand...
Click to collapse
My bootloader is unlocked. I was able to flash any rom running AOSP (Liquid smooth CM only 2 I have tried)
DCVR 614 said:
A couple months ago I was having problems with my recovery. It kept crashing every time I tried to flash anything. Found out I needed to format my internal storage, once I did that I was able to flash CM but when I tried to flash a TW rom I get stuck in a bootloop. I re-downloaded the same rom 3 times thinking it was a bad download no dice. Tried other TW roms still no dice. But, when I flash a ASOP rom it works just fine. What could of caused this issue?
Click to expand...
Click to collapse
It's possible that you could have something partially corrupted in your data/cache partitions.
If you don't want to have to ODIN back to 4.1.2... and then start all over again with CASUAL, etc.... then you might check out this thread : http://forum.xda-developers.com/showthread.php?p=53624921
Wiping cache and doing factory reset in the Stock Recovery might correct things... it apparently does a more thorough wipe than the ones done through custom Recoveries like TWRP/Philz... etc... You can just Odin back your preferred custom recovery after completing the wipes in the Stock recovery.
mattnmag said:
It's possible that you could have something partially corrupted in your data/cache partitions.
If you don't want to have to ODIN back to 4.1.2... and then start all over again with CASUAL, etc.... then you might check out this thread : http://forum.xda-developers.com/showthread.php?p=53624921
Wiping cache and doing factory reset in the Stock Recovery might correct things... it apparently does a more thorough wipe than the ones done through custom Recoveries like TWRP/Philz... etc... You can just Odin back your preferred custom recovery after completing the wipes in the Stock recovery.
Click to expand...
Click to collapse
I will try this today and report back!
DCVR 614 said:
I will try this today and report back!
Click to expand...
Click to collapse
This sounds like the same problem I am having in this post: http://forum.xda-developers.com/note-2-verizon/help/assistance-odin-soft-hard-brick-t3093391
Except I can't flash anything. I will also try flashing this stock recovery because it sounds like the only thing I haven't tried doing.
Thanks so much for this thread I hope it can save my phone.
Clarifying here, it's a simple question.
I saw several people in the blu_spark custom kernel thread saying that you don't need to do a full wipe and flash stock OOS to flash the kernel. If I'm coming from stock rooted with TWRP, am I able to just flash the kernel itself without wiping anything? New to flashing custom things in general.
Dont know for sure, but what I'd suggest is to Flash the Kernel & Wipe Dalvik before reboot, thats what i do, no problems so far, same for updates too.
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Im using despair kernel
Scherzengel said:
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Click to expand...
Click to collapse
How would I be able to check this?
Ask the Dev of the Kernel you want to install. But first read the description of the Kernel and the Devs advice for Installation.
Most kernels do not require a whole system wipe like that. As long as the kernel is compatible with the ROM you should have no problems in just plain flashing it. You can find out if it is compatible by looking on the Original Posting by the developer. Another thing to note: if a kernel developer does not specify a ROM compatibility and yet a kernel installs and the ROM even boots up that does not mean you are completely bug free. An example of this would be using blu_spark's OOS kernel on CM 13. It will flash, boot, but your phone will lag, randomly reboot, apps will force close, etc.
He actually has a beta kernel for CM 13 so that you can use his customization and without above issues.
HD1910 model, I had a working rom and tried various custom kernels to help battery life but decided to change to a rom that I can update via the phone rather than manual fastboot flash.
Chose Carbon rom, went back to latest stock with MSMtool, unlocked bootloader and seemed ok, but got a bootloop.
Thought something was wrong so used MSMtool again and tried various small differences i.e running fastboot -w before I flashed rom, before and after and either got a constant bootloop or a strange occurance where after it bootlooped a few times it went back to a factory reset stock rom.
I attempted to do a slower wipe i.e erase system, boot etc one by one but it said error (I used bootloader fastboot which I can't remember is different) I tried TWRP 3.4.0.2 and 3.4.01
I get FDE error, system_mount and vendor so what is the issue?
I even tried Lineage and same issue, just constant boot logo loops.
I would prefer a custom rom not stock
Is having a custom kernel affecting the install?
"went back to latest stock with MSMtool, unlocked bootloader and seemed ok, but got a bootloop."
This is the only thing that matters, as MSMTool completely resets the phone, if a problem happens after it's not related on what you did before.
My guess, maybe wrong MSMtool?
Or maybe you flashed the room incorrectly?
And what error you did get when you ran fastboot -w?
Pretty much sorted now, I wiped with fastbootd, then installed via a payloaddumper rather than in TWRP, I worked out what was causing bootloop was opengapps, once I used a older version (of the same android 10, pico arm64 etc) it installed and booted.
Only issue now is ctsprofile is false, but at least phone all works.