I can't seem to find this kernel on XDA or google.
Im on my SGH I747M 4.1.1
with kernel 3.0.31-538866 [email protected]#1
Where can I get this kernel to flash?
Reason why I'm asking is i'm trying to flash new kernels and want this as a back up to have it stored so i can restore it.
Unless....TWRP recovery images can recover the kernel when you restore that image?
Thanks!
mikoal said:
I can't seem to find this kernel on XDA or google.
Im on my SGH I747M 4.1.1
with kernel 3.0.31-538866 [email protected]#1
Where can I get this kernel to flash?
Reason why I'm asking is i'm trying to flash new kernels and want this as a back up to have it stored so i can restore it.
Unless....TWRP recovery images can recover the kernel when you restore that image?
Thanks!
Click to expand...
Click to collapse
When you restore your backup, it will restore the kernel as well.
and where to get the last kernel for my SGH-I747M.... ( shows this kernel 3.0.31-274808 [email protected] # 1 ) this kernel came with a rom called Hiperdrive RSL11...
but I need to reinstall the kernel to fix something wrong, for that reason I ask for the last or the better kernel for my Samsung galaxy S3 ???
thanks for your help
boni7010 said:
and where to get the last kernel for my SGH-I747M.... ( shows this kernel 3.0.31-274808 [email protected] # 1 ) this kernel came with a rom called Hiperdrive RSL11...
but I need to reinstall the kernel to fix something wrong, for that reason I ask for the last or the better kernel for my Samsung galaxy S3 ???
thanks for your help
Click to expand...
Click to collapse
It's in your ROM zip. Named zimage. Extract that file and you can flash it using Odin.
You can also dirty flash the ROM (without wiping) and it will reflash it.
Btw, reinstalling the kernel doesn't do anything if it's already on your phone. It won't fix anything. If you flashed another kernel though, that's another story.
May we know what you're trying to fix?
BWolf56 said:
It's in your ROM zip. Named zimage. Extract that file and you can flash it using Odin.
You can also dirty flash the ROM (without wiping) and it will reflash it.
Btw, reinstalling the kernel doesn't do anything if it's already on your phone. It won't fix anything. If you flashed another kernel though, that's another story.
May we know what you're trying to fix?
Click to expand...
Click to collapse
look what this member write in the Hiperdrive RSL11 rom :
Venom0642 said:
I would reflash the rom again clean make sure in aroma you chose full wipe system/data and make sure you don't select S Note and flash again once you do that don't reboot from aroma take check mark off aroma so you don't reboot then in recovery flash your kernel which ever your going to flash after that wipe cache davik then reboot do not set up Google account let it sit for 5 to 10 mins after that reboot one more time then let it sit 5 more min after that then start setting up your google account you should not get that popup or any other issues.
Click to expand...
Click to collapse
how to do and flash via odin, if I cant leave the installing rom, because that say Venom in his post ???
this its the post:
http://forum.xda-developers.com/showthread.php?t=2176793&page=113
Related
I'm using the stock Gingerbread "Leak" rom version 4.12.651.1 that was leaked recently and I played around with it at first. Took several pictures and videos and enjoyed getting back to having Sense on my phone.
I used Kernel Manager Lite to download and install the Netarchy Toastmod-cfs-havs-more-sbc kernel and at now everytime I open up the camera it shows a white screen and I can't take a picture or video anymore.
Is there a why to uninstall or undo this kernel without having to reflash my Evo? I'd like to go back to just the stock kernel i guess. I even tried to use the Kernal Manager Lite to download and install a different Netarchy Toastmod kernel but it wouldn't install it over a previous kernel and when I clicked on the kernel I already have installed it won't give me an option to uninstall it...
Thanks for any help you guys can give me.
Find the stock kernel for that ROM and flash in recovery after wiping cache and dalvik cache.I will try to find stock kernel for that ROM.
Yeah there's no way to undo once u flash a kernel.....may I make a suggestions for ya foe the future.....Ive been doing this for a while......flash the ROM and make a backup once yur all setup...this way u can tinker with the rom and kernels and themes and what not.......and if those tweaks don't work for ya......u got a backup of a fully stock rom......
Sent from my PC36100 using XDA Premium App
Thanks guys for the awesome advice!
Reverepats, it's funny you said that because that's the first thing that I thought about after this happened and I'm still kicking myself for not backing it up before flashing the kernel LOL It'll be a lesson learned I guess
Ianmb, that would be AWESOME if someone had this. I'll keep looking for this too but if I have to I guess my only recourse would be to wipe it all and reflash all over again... /sigh
There is a post for a working kernel for that ROM on the second page if the ROM is the stock 4.xxx. Stock kernel 15 I think, can't upload file from my phone?
ianmb, thanks for looking but I can't find any stock kernel #15 out there. not even google can help me =/
So it's possible to reflash a kernel over an already installed kernel? If i find the stock kernel how do I go about installing it? Via recovery?
Forgive me if I'm wrong...but if you just reflashed the rom without wiping, I believe it would install the stock kernel that came with the rom
Sent from my nightly EVO
TwhiT said:
ianmb, thanks for looking but I can't find any stock kernel #15 out there. not even google can help me =/
So it's possible to reflash a kernel over an already installed kernel? If i find the stock kernel how do I go about installing it? Via recovery?
Click to expand...
Click to collapse
Yes you can flash a new kernel over an installed kernel...just wipe cache and dalvik prior to flashing
Sent from my nightly EVO
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Robert00001 said:
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Click to expand...
Click to collapse
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
simms22 said:
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
Click to expand...
Click to collapse
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
simms22 said:
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
Click to expand...
Click to collapse
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Robert00001 said:
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Click to expand...
Click to collapse
It gets you whatever kernel was originally in the ROM.
063_XOBX said:
It gets you whatever kernel was originally in the ROM.
Click to expand...
Click to collapse
Okay thanks for the replies.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
Even the .IMG files are easy enough to handle, OK so perhaps it might cost you a little money but within the Franco app (I don't know about others as not tried them) but you can simply just choose to restore a .IMG kernel file be it stock (which I have a copy of if you wanted it?) So you can swap and change as you wanted and the plus side of flashing this way is that you avoid the long reboot time dues to catch building again due to ram disk changes. I really think this is the best way of flashing kernels and certainly the easiest way if you wanted to carry on back to the OTA update route from Google.
For instance, I'm running stock takju rom 4.2.1 rom with Franco kernel and I have the stock boot loader and baseband and recovery and to install an OTA I just need to delete just one file and restore back to stock kernel that OTA update will install without troubles
Sent from my Galaxy Nexus
sorry if this have been ask before.i tried to do a search on the topic but return empty.
question is if i'm using a custom kernel (redpil kernel) and i like to tried out others kernel .the correct way to do it is to flash over it as how i flash over the stock kernel in the first place? do i need to do any wipe.thanks
arsira said:
sorry if this have been ask before.i tried to do a search on the topic but return empty.
question is if i'm using a custom kernel (redpil kernel) and i like to tried out others kernel .the correct way to do it is to flash over it as how i flash over the stock kernel in the first place? do i need to do any wipe.thanks
Click to expand...
Click to collapse
Flash using your recovery as you did. After flashing do a wipe cache/dalvik and you are good to go.
For kernel, need not wipe anything. Just flash over according to the dev's instructions ie. cwm/odin(pc/mobile) and ensure you don't have any (previous) kernel tweaks ie. in the init.d. Recommended to wipe cache & dalvik if you change rom to refresh the vm dexopt...:good:
and to reset the tweaks to default setting before flashing new kernel right?
Doesn't matter.
Sent from my GT-N7100
mobile odin works wonders:good:
hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
angeltouch 4g said:
hy everybody , i have been trying to install hyperdrive rom rl10 on mt at&t galaxy s3 i have follow every step ,fix, i even flash kt747 kernel and nothing i'm still stuck on boot it won't pass the first boot animation , i also flash xone kernel and still the same it will get stuck on first animation boot even after 7 minutes it wont do anything.:crying:
Click to expand...
Click to collapse
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
xBeerdroiDx said:
What model do you have? Carrier? What option did you first choose for a kernel?
You're like the 50th user in here this week with this issue on hyperdrive. It would appear the device type in the build.prop is being is being edited and there is a conflict during the boot process causing this soft brick. Anyone with more knowledge than this please chime in.
If you can still get back into recovery, your options are probably to restore a backup or flash another rom. In download mode you could flash stock stock rooted via odin. If your s3 is not recognized on your pc, there is a flashable stock firmware zip in the link in my signature. In post #2 at the bottom
Click to expand...
Click to collapse
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
angeltouch 4g said:
hi beerdroid i have at&t sgh-i747
i choose the ziggy kernel in aroma thats the only option for at&t , i did try with the verizon with the zeus kernel,deviant kernel, and stock kernel all with no luck , yea i seen a lots of users with the same problem , yes i can still pull out the battery and do the process again with a different kernel , i have try kt747 kernel ,xone kernel and devil's reject kernel all with no luck , phone will boot but it will get stock on first animation boot , and i have no clue when you say build.prop
Click to expand...
Click to collapse
i'm trying to do is installing the rls 9 and then update see if this help
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
xBeerdroiDx said:
So the very first time you flashed hyperdrive, you selected at&t and the ziggy kernel and it didn't work? I'm assuming you gave it plenty of time on the first boot up. Someone correct me if I'm wrong but hyperdrive is a verizon base, yes? If so, this might be the source of your problem, even though it is a "multi-carrier" rom. You can try wiping data, cache and dalvik in recovery then rebooting. Like i said, though, you will probably have to another route (restore backup or flash new rom). When you successfully boot up next, I would imagine your model is different in about phone
Click to expand...
Click to collapse
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
angeltouch 4g said:
i'm trying to do whay tou are saying but this aroma installer keeps freezing is driving me nuts
Click to expand...
Click to collapse
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
xBeerdroiDx said:
Are you using twrp or cwm for recovery? Twrp is recommended for aroma
Click to expand...
Click to collapse
cwm
angeltouch 4g said:
cwm
Click to expand...
Click to collapse
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
xBeerdroiDx said:
If you're really wanting to get this particular rom going, changing to twrp might help. In my signature there is a link. Near the bottom of post #2 flashable recovery zips are mentioned. Download the twrp one and throw it on your phone. Boot into recovery and flash it. Reboot recovery. Wipe data, cache and try flashing the rom again.
Click to expand...
Click to collapse
ok i'll do that to see if helps thanks
hrsema and
angeltouch 4g said:
ok i'll do that to see if helps thanks
Click to expand...
Click to collapse
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
angeltouch 4g said:
now i got the boot animation hyperdrive sbreen94 how much you think i have to wait it looks like is stock?
Click to expand...
Click to collapse
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
xBeerdroiDx said:
It could take 10 or so minutes for the initial boot. If it takes a lot longer, you can try booting back onto recovery to wipe data and cache again. If this does not work, I would go another route
Click to expand...
Click to collapse
ok , if not i'll try to flash some other kernels to see if it boots up , i f not i'll just give up on this rom and go back to synergy
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
xBeerdroiDx said:
When you're back up and running on a rom, go into settings > about phone and tell me what your device is listed as. You may have small issues down the road if your phone has been designated as an SCH-I535 or anything other than SGH-I747. That's an easy build.prop fix, though. Good luck
Click to expand...
Click to collapse
ok i'll do that and let you know
model number samsung-sgh-i747
baseband number i747ucdlk3
angeltouch 4g said:
model number samsung-sgh-i747
baseband number i747ucdlk3
Click to expand...
Click to collapse
Good. Congrats. What rom did you end up on?
synergy thats were i was before trying to flash hyperdrive
The upside: now you can post in development threads
ok
Hi all sifu. Need to know something before going back to stock from Eclipse V7. Great rom, nothing wrong with the rom (thanks to AholicCert !), just want to go back. Updated to AGNi kernel latest version PSN_AGNi_pureSTOCK-v4.5.1-N7100_4.4.x_AROMA. I already went through many website and guide. Just want to made sure nothing goes wrong.
1. Need to revert back to stock recovery via odin first, or flash stock rom first?
2. with the new AGNi kernel, just flash straight away or need to do anything else before this?
akuma238 said:
Hi all sifu. Need to know something before going back to stock from Eclipse V7. Great rom, nothing wrong with the rom (thanks to AholicCert !), just want to go back. Updated to AGNi kernel latest version PSN_AGNi_pureSTOCK-v4.5.1-N7100_4.4.x_AROMA. I already went through many website and guide. Just want to made sure nothing goes wrong.
1. Need to revert back to stock recovery via odin first, or flash stock rom first?
2. with the new AGNi kernel, just flash straight away or need to do anything else before this?
Click to expand...
Click to collapse
Download official stock rom and flash via odin. Make clean install . Wipe system cache n dalvik before flashing stock rom otherwise u may get into bootloop.
Sent from my GT-N7100 using Tapatalk
1life2love4 said:
Download official stock rom and flash via odin. Make clean install . Wipe system cache n dalvik before flashing stock rom otherwise u may get into bootloop.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
thank you mate... will try after downloaded the stock rom.. Kind of hard cos mostly not supported by download app and my internet is slow...