Ok so i want to put CM rom onto this S2 I have but trying to put a safe kernel on first so dont brick it with that wipe bug.
Problem is whenever I flash dream kernel, skfire etc. the device doesnt boot, only boots again when I flash cf-root back.
Its ICS 4.0.3
I am flashing via install frim zip file on CWM as instructions arent given on the kernel threads.
siyah flashed via odin, the logo appears very briefly at boot then black, nothing.
CWM with siyah logo in background works.
Ok I flashed cm9 now anyway.
It was confusing to me but incase anyone else is confused in the same way, cf-root is still safe as long as the stock isnt 4.0.4. I thought its possible cf-root used a 4.0.4 kernel on 4.0.3 and so was heistant.
I got no idea why none of the custom kernels would boot tho so that still has nme curious, CM has booted fine.
Related
so the story goes like that.
few days ago (before ICS officialy came from asus) i've tried just for fun Paul's ICS port. i really dont see myself as a noob, so please treat my question as it is.
at first i've tried to flash it from cwm without wiping and stuff- got stuck at boot.
so i did i full wipe with "Android revolution super wipe".
and flashed ics port again- now with success.
after couple of days decided to go back to HC Revolver. so just went again to CWM and full wiped again, and flashed revolver 3.11.
then i started to get the bad news. it seems nothing can be flashed anymore from the recovery. when i flash a rom it finishing it too fast and when i reboot it just bootlooping on the splash screen. tried everything, including removing the cwm recovery and installing it again.
the one and only thing that worked is nvflashing a prime rom. but it still didnt fix the recovery problem.
i tried to flash also back HC kernel with no luck.
what did go wrong?!
please help me
num1gever said:
so the story goes like that.
few days ago (before ICS officialy came from asus) i've tried just for fun Paul's ICS port. i really dont see myself as a noob, so please treat my question as it is.
at first i've tried to flash it from cwm without wiping and stuff- got stuck at boot.
so i did i full wipe with "Android revolution super wipe".
and flashed ics port again- now with success.
after couple of days decided to go back to HC Revolver. so just went again to CWM and full wiped again, and flashed revolver 3.11.
then i started to get the bad news. it seems nothing can be flashed anymore from the recovery. when i flash a rom it finishing it too fast and when i reboot it just bootlooping on the splash screen. tried everything, including removing the cwm recovery and installing it again.
the one and only thing that worked is nvflashing a prime rom. but it still didnt fix the recovery problem.
i tried to flash also back HC kernel with no luck.
what did go wrong?!
please help me
Click to expand...
Click to collapse
You need to flash the stock kernel again, Paul's ICS kernel is still there, and that won't work. CWM does not flash the kernel when flashing a ROM unless the kernel is included with the ROM (like Paul's). Download Roach2010's kernel and CWM flash it, then reboot and see if that fixes it. Then, if you want to go to stock, use revolver parts to download the stock Asus kernel and return to stock.
Try hereee
http://forum.xda-developers.com/showthread.php?t=1513698
And then here
http://www.tabletroms.com/forums/tra...ing-tools.html
Ok, so I have been running a nice custom ROM of ICS on my phone, I then tried the updated version for a couple of days, but deceided to revert back to my previous back up. Did the back up through CWM manager, but from here, it failed to boot and went to the black "Samsung Galaxy note" screen.
I then went in to recovery, did a full wipe, and then just tried to re install my custom ICS ROM. It only got as far as flashing the modem, and then hangs, I tried this a few times, and with a few different roms. Pre ICS roms, and a stock KK9 rom just failed instantly.
I then put the phone in to download mode, and hooked it up to the PC to do a flash through ODIN.
I selected a stock KK9 rom, but this failed.
I now cant get to recovery, and I dont have the black "samsung galaxy note" screen, it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I then try to do this, but Kies wont connect to the phone.
I am at a loss, please help
I'm really sorry about your trouble..I can't really help with your current issue but I can tell you what probably happened.
You probably tried to restore a gingerbread backup while using the ICS recovery. You just can't do that.
When you want to flash a gingerbread rom or gingerbread backup coming from a ICS rom you must ALWAYS flash a gingerbread kernel first. After that simply reboot recovery in advanced section and then restore gingerbread from there.
That way you know next time..Hope you get it fixed.
Sent from my GT-N7000
dannstarr said:
Ok, so I have been running a nice custom ROM of ICS on my phone, I then tried the updated version for a couple of days, but deceided to revert back to my previous back up. Did the back up through CWM manager, but from here, it failed to boot and went to the black "Samsung Galaxy note" screen.
I then went in to recovery, did a full wipe, and then just tried to re install my custom ICS ROM. It only got as far as flashing the modem, and then hangs, I tried this a few times, and with a few different roms. Pre ICS roms, and a stock KK9 rom just failed instantly.
I then put the phone in to download mode, and hooked it up to the PC to do a flash through ODIN.
I selected a stock KK9 rom, but this failed.
I now cant get to recovery, and I dont have the black "samsung galaxy note" screen, it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I then try to do this, but Kies wont connect to the phone.
I am at a loss, please help
Click to expand...
Click to collapse
I assume the stock KK9 rom is from your region? Same thing happened to me because I stupidly flashed a rom that wasn't from my region (I have an unlocked phone from India). Hopefully that's what happened because it was an easy fix for me. Good luck!
Which custom ics rom did you have and which recovery?
Sent from my GT-N7000 using Tapatalk
When flashing between ICS ROMs I often flash the Abyss kernel first and then flash a new ROM from it's recovery. I think the issue is that your ICS ROM was not fully rooted. Try to flash Abyss kernel and the wipe and flash your next ROM.
csasek said:
When flashing between ICS ROMs I often flash the Abyss kernel first and then flash a new ROM from it's recovery. I think the issue is that your ICS ROM was not fully rooted. Try to flash Abyss kernel and the wipe and flash your next ROM.
Click to expand...
Click to collapse
Yes - this way always works for me. flash the abyss kernel in CW and then select reboot to recovery (do not select reboot the phone). When back in recovery, flash a GB ROM
Sent from my GT-N7000 using Tapatalk
Always use redpil from abyss to install a gb when comming from ics.
Can someone explain why this happens:
1. I flash CM9 nightly or latest release
2. Phone goes into boot loop
3. I power the phone up into the yellow boot loader screen and flash the Semaphore ICS kernel with Heimdall
4. The phone boots and runs OK
Why does the phone go into a boot loop until I flash the Semaphore kernel? How can I stop this behaviour?
Sounds like a big error... don't sound good. You flashing cm9 or cm10? nightly builds are really good. i recommend getting a cm10 nightly build and try that. otherwise, try and find a way of flashing roms and kernels a different way...
Hi there.
I have a Samsung Galaxy S4 GT-I9505 and I’m using TWRP Recovery 6.0.4.4.
I tried to flash a nightly-version of CyanogenMod (cm-10.2-20131101-NIGHTLY-jfltexx.zip). I did a Factory Reset before flashing, TWRP said it had been successful.
When I tried to boot my phone, I can see the "SAMSUNG GALAXY S4 GT-I9505" logo, here it got stuck. I can not see the cyanogen boot animation.
Though MD5 hashes and file sizes are ok, I tried another ROM: SuperNexus http://forum.xda-developers.com/showthread.php?t=2407616
Here it was exactly the same. My device gets stuck even before the boot animation.
I was so desperate, that I tried to format my complete internal storage. Flashing the ROMs was successful again, I could boot both ROMs CM and Supernexus then. But after I turned off my device I can't boot any more. Again I can not see the boot animation.
I have already tried it with PhilZ and CWM. I flashed them using my current recovery.
Any advice?
I am sorry for my English, if you need more detailed explanation, please ask. I tried to describe everything as detailed as I can.
Can you get into download mode? You may have to flash a stock ROM to get it to working again. Was the phone previously rooted?
And are you currently on a stock ROM or coming from a custom ROM?
Yeah, I can get into Download mode.
Well, I am not sure what ROM I'm currently using since I wiped everything. Previously I had FoxHound ROM, samsung-based pre-rooted custom ROM.
Have you tried flashing a custom Kernel?
Sounds like what I had when I tried to flash a TW Kernel for a AOSP ROM.
If you can't get into recovery, go into download mode and flash the latest CWM. Got my phone working.
FoxHound ROM installed a custom Kernel, "Ausdim Kernel" I think.
Now I have CWM 6.0.3.2 from here: http://forum.xda-developers.com/showthread.php?t=2279579
Not sure if this is the latest version ... I can't find an Odin-flashable *.tar
Anyway it doesn't work too. This recovery can't even flash CM, it gets stuck at "opening update package ..."
Sorry its a bit late.
http://forum.xda-developers.com/showpost.php?p=46312260&postcount=149
Use them. This may help as a tutorial to follow loosely but that was for non working WiFi.
http://forum.xda-developers.com/showpost.php?p=47076192&postcount=6
I have a i9000 and i would like to install twrp so i can install a 7.0 rom but i dont know how to install twrp can someone tell me how?
I would also like to know this as well. I've tried CWM through odn but it's a zip so wont flash. I've tried it in stock recovery but obviously get the signature fail msg.
TWRP comes with the kernel and hence the ROM.
It gets automatically installed if you're on older BML/MTD device..
In which case you should have rebooted after acceptign wipe..
Ahh right, so I flash a new kernel to it and that comes with the recovery built in.
Do I flash the kernel from odin or stock recovery. Got the stuff to unbrick the phone if that happens, just wanted to know the right way before flashing stock rom back and starting again.
MrGRiMv2 said:
Ahh right, so I flash a new kernel to it and that comes with the recovery built in.
Do I flash the kernel from odin or stock recovery. Got the stuff to unbrick the phone if that happens, just wanted to know the right way before flashing stock rom back and starting again.
Click to expand...
Click to collapse
The kernel is flashed by the ROM zip... I dont remember if it automatically reboots to recovery or not..
However it does create a file in cache that makes it boot to recovery.. Since the /system is not yet installed.
You should flash the ROM after it boots to new recovery.. then install the zip file again..
All this is described in https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh
I got there in the end.
I flashed CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar with odin, then installed cm-10.2.0-galaxysmtd.zip which also updated my older CWM. It had a spam, so I wiped/factory/dalvik etc from the updated CWM and then reinstalled cm-10.2.0-galaxysmtd.zip - now running the rom just fine.
Will be trying out some more over next few days now I have a nandroid of CM10.
Thanks for pointing me in the right direction.