I was beak bootloader using fastboot. Everything was ok then i try to use miui and CM kernel.
And i follow this this thread http://forum.xda-developers.com/showthread.php?t=934965 to make Security on. For no reason but now i wanna flash a new kernel but i can't.And can't flash ROM too.
Now i wanna S-off to flash a new kernel. I was try to use fastboot but that said
INFODevices was already unlocked!.
What can i do for S-off to flash a new kernel. Please help me.
You don't need S-off to flash a kernel you just need a custom recovery. Flash Amon Ra or clockwork mod 2.X and then try and flash the kernel through recovery.
I'm using clockmod recovery. i can't flash a new kernel through recovery too. what can i do now? please help me.
thanks so much
Why can't you flash a new kernel? Does it come up with any errors? There shouldn't be anything preventing it unless the download is corrupt, or it isn't for your phone.
My files is not corrupt. If these file corrupt i can't unzip in windows. When i'm flash a new kernel everthing is notice done well and a ROM too. But nothing happened.
I don't know if my phone or is a reason in this case. Actually this is my phone.
So, it seems like it flashes, but it actually doesn't? Or you try to flash it and it errors out?
Thanks all for helping me. I was try over 20 files then i still don't know some file can flash and some can't.
Thanks you all again.
The only way to tell that your flash worked is to check your kernel version in Settings -> About Phone. Otherwise, there isn't much of a difference.
Related
Its a great program and all. I however dont flash roms. All I do is just update my kernel, I use one of existz's kernels. Anyway, I use Quickboot to boot into recovery to flash new kernels, and it seems to work fine. Recovery is Recovery, right? I've read a few things about SGS Kernel flasher, but have also read it can cause some issues.
The only reason I could ever see for ROM manager would be if you lost your copy of CWM.
Sent from my SAMSUNG-SGH-I897 using XDA App
rom manager is only good for getting CWM onto your stock rom
So I should keep it? Just wondering. Trying to get rid of unused crap on my phone.
The only problem I've had with Kernel Flasher is getting in a hurry and forgetting to disable my lagfix (guar anteed bootloop).
I see. Ive never disabled it with CWM through ROM Manager. Am I supposed too?
i dunno what/where he was coming from talking about kernel flasher.
we were talking about rom manager...
if your kernel has CWM built in you do not need Rom Manager and the update.zip file.
CWM is BUILT IN to the kernel.
so if you dont need it get rid of it.
Oh. Ok...ya I dont rename anything to update.zip anymore. Let me read and see if that kernel has CWM
you dont normally rename anything. in rom manager the first button is download CWM. it downloads update.zip to your root SDcard directory and it uses that to "re-install package" from 2e 3e recovery. if you never see 2e/3e recovery anymore your kernel is probably CWM. what kernel are you using?
I use existz Captivate Kernel #8 lol. I don't think it has another name.
ConeyKiller said:
Its a great program and all. I however dont flash roms. All I do is just update my kernel, I use one of existz's kernels. Anyway, I use Quickboot to boot into recovery to flash new kernels, and it seems to work fine. Recovery is Recovery, right? I've read a few things about SGS Kernel flasher, but have also read it can cause some issues.
Click to expand...
Click to collapse
Op said he didn't like kernel flasher. Thought I would throw that out since he said all he wanted to do was flash a new kernel.
I have it. I never use it.
hey guys,, i seem to have stuffed the recovery of my phone,, i stupidly installed cwm on my phone without root, but when i reflashed with odin the stock recovery works but when i install cwm, it doesnt go into recovery
CWM doesn't require root!
Try to reflash a stock rom. Not the one package file but the whole rom.
---------------XDA Premium--------------
Don't be a noob. Be a newbie..!!
Details here.
___________________________________
i have tried, once i flash cwm it doesnt boot into recovery,, ill try redownload and see if that helps
finally got it to work, i found a odin flashable cwm and it now works
ok now that i have cwm semi working on my phone, its now very difficult install roms, the only rom i can get to work on my phone now is stock,,, i now cannot flash cwm from recovery otherwise i get cwm bootloop only flashing by odin works, all custom roms get bootloop no matter how many times i flash and wipe data/cache,, i think my phone is stuffed
You sure you're installing cwm and roms for your device? What model ace do you have? (Not the i model right?)
dxppxd said:
You sure you're installing cwm and roms for your device? What model ace do you have? (Not the i model right?)
Click to expand...
Click to collapse
yeah mate im sure, i know what im doing, but it just doesnt seem to work anymore lol,, i have the T model
Make sure it is Just the "S5830" Any other then your in the wrong thread.
Tbh The order i do it, Flash the latest stable stock rom Via odin, Flash update {Any Kernel} (On phone) Then Reboot into CWM To flash a rom.
JDMBrooksy said:
Make sure it is Just the "S5830" Any other then your in the wrong thread.
Tbh The order i do it, Flash the latest stable stock rom Via odin, Flash update {Any Kernel} (On phone) Then Reboot into CWM To flash a rom.
Click to expand...
Click to collapse
yes it is, im not a noobie,, done that too,, im trying to flash cm9 b10 now but its stuck at samsung, and yes i have done data wipe and cache wipe
Only way i can think of is:
Flash new software with Odin: http://www.4shared.com/rar/FCyxijg8/odin_s5830_package.html
Then flashing "CWMRecovery" {AttacthMent} as an update through stock recovery as an update
Then reboot into CWM Recovery To wipe data Etc Etc, Then flash what ever ROM you want..
please more info man really not helping.
JDMBrooksy said:
Only way i can think of is:
Flash new software with Odin: http://www.4shared.com/rar/FCyxijg8/odin_s5830_package.html
Then flashing "CWMRecovery" {AttacthMent} as an update through stock recovery as an update
Then reboot into CWM Recovery To wipe data Etc Etc, Then flash what ever ROM you want..
please more info man really not helping.
Click to expand...
Click to collapse
ok ill try to remember what i did to stuff the phone,, ,i flashed my phone with s5830xwkt7 the rooted and flashed cwm 5,, i went to flash a custom rom but chose the wrong one and took the battery out,,, booted into cwm and did a full wipe and flashed the custom rom,, tested the rom and went back to stock rom, done root and installed cwm 5 again then went to reboot back to cwm for flash oc kernel and it started to bootloop after the samsung logo,,, its all fixed for now but im sure it will happen again
winxuser said:
ok ill try to remember what i did to stuff the phone,, ,i flashed my phone with s5830xwkt7 the rooted and flashed cwm 5,, i went to flash a custom rom but chose the wrong one and took the battery out,,, booted into cwm and did a full wipe and flashed the custom rom,, tested the rom and went back to stock rom, done root and installed cwm 5 again then went to reboot back to cwm for flash oc kernel and it started to bootloop after the samsung logo,,, its all fixed for now but im sure it will happen again
Click to expand...
Click to collapse
Flash "Root" After Flashing "CWM" See if that helps? if not please try the order i have gave, or try looking for different resources.
The Sources i have given you are working fine for my Ace.
Hey Guys,
Before i start let me explain that i use to cook roms for my magic, so i know what im doing with this stuff.
Anywho i have been having a weird issue where whenever i flash a rom, it will not boot to either the rom or back into the recovery. my only option is to relock the bootloader and flash back to the stock ruu, and reinstall recovery.. right now im stuck on the stock rom and i hate it!
btw the device is s-off and unlocked bootloader, so wth, if anyone has any advice please let me know!
Did you try reflashing the recovery? Or a different recovery ? had a problem once with my pc antivirus blocking certain files and was causing the zip to be corrupted , just some thoughts
shael said:
Hey Guys,
whenever i flash a rom, it will not boot to either the rom or back into the recovery.
Click to expand...
Click to collapse
All you get is the white HTC screen when you reboot?
What about when you boot into HBOOT, then choose recovery manually?
As you mentioned, you're used to this stuff, so this part probably isnt helpful - do you do the 4 wipes when flashing? (data/cache/dalvik/system?)
I wonder if (even though you are S-OFF), the kernel portion of the rom isnt flashing? This can cause your phone not to boot and just sit there... i.e. your phone hasn't experienced a stockish/insecure kernel flash first, so recovery is having trouble flashing the custom recovery that comes with the rom.
See this thread for more info (it helped another user):
http://forum.xda-developers.com/showthread.php?p=30658376#post30658376
Also - to what Bigtjmc is saying - in the link above, I mention the recovery I use (which has not let me down at all!) Maybe you want to try it (if you're not using it already?)
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
Try Wildchild's Recovery (by far MY most favorite)
And if it's not passing verificiation, like the other user said check your anti-virus and check the MD5 Checksum to make sure you have a complete good download, wipe all data cache and blah blah blah then with fastboot "fastboot flash boot <Insert kernel file name here>.img
hmm, well in the past ive always flashed kernel with fastboot... its almost like my chip timed out and wont let me flash the kernel anymore :s
If recovery is crashing you might need to relock the bl and run the stock ics ruu to get you back up and running then try n start over , I used the tool kit just this morning for the same troubles and got back where I wanted to be in just a few minutes .
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
This happened to me as well... can't remember what script it was that was running but there is a script that is associated with a rom (vague I know) that is messing up the cache partition. If I remember correctly I also might be associated to the recovery you are using... but I can't remember. Anyway, If you do a fastboot erase cache command from the bootloader and re-flash the recovery of your choice you should be back to normal.
Awesome, thanks for you help guys, unfortunatley i dont have easy access to a pc, so i gotta wait a bit before i can try this... thanks again though
OMG!!!!! you guys are simply amazing, thank you everyone for your help! wiping the cache from fastboot, then flashing stockish kernel, then flashing cwm recovery, then wiping cache, and factory reset, then flashing my rom worked!!! <3
Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
EDIT: SOLVED!!!
Hi guys! I have a question. I have twrp that I installed with the help of advanced stock kernel. But it doesn't look like a permanent recovery. If I install a custom ROM without a recovery, I will lose my recovery. Can you help me install a permanent recovery on my phone. ?
I have tried flashing using flashtool and it only boots into twrp and not android.....
Thanks !
panzerox123 said:
Hi guys! I have a question. I have twrp that I installed with the help of advanced stock kernel. But it doesn't look like a permanent recovery. If I install a custom ROM without a recovery, I will lose my recovery. Can you help me install a permanent recovery on my phone. ?
I have tried flashing using flashtool and it only boots into twrp and not android.....
Thanks !
Click to expand...
Click to collapse
The reason you lose recovery when installing a new ROM is because TWRP is built in Advanced Stock Kernel,and when you flash for example SLiMM ROM it reflashes its kernel.
That means that every time you install a new ROM you will need to reflash the kernel.
Dinkec27 said:
The reason you lose recovery when installing a new ROM is because TWRP is built in Advanced Stock Kernel,and when you flash for example SLiMM ROM it reflashes its kernel.
That means that every time you install a new ROM you will need to reflash the kernel.
Click to expand...
Click to collapse
Don't worry, Im going to close the thread now . The problem was that i cannot flash the kernel on roms like PA or CM without getting a bootloop, but i managed to find out how to flash a recovery to the recovery partition and then enter it using a key combo, and it works quite well, perfect for my needs!
Thanks anyway!:good: