[Q] kanged my own rom, having trouble with kernel flashing - Epic 4G Q&A, Help & Troubleshooting

Alright so I was being adventurous and borrowing stuff from all my favorite roms, themes and patches to create my own personal rom. I have pretty much just used 7zip and notepad++ to get this far. I used the updater-binary and updater-script from SRF 1.2. Everything seems to work when I am on SRF or Random rom but when I try to install from stock ec05 I get stuck on the Samsung boot screen. These are the steps I take:
1. Odin to stock EC05 2. Run newest one click 3. Boot into CWM 4. Run RFS2EXT4 script 5. Install Rom.
So I am guessing the issue is my rom isn't flashing the kernel. I am trying to flash the Genocide Kernel v2.0 with the rom. Are there any changes I need to make to the updater-binary or updater-script?

first, get a logcat (adb logcat) and make sure its booting right in the first place. then get back to me.

feefeeboomboom said:
first, get a logcat (adb logcat) and make sure its booting right in the first place. then get back to me.
Click to expand...
Click to collapse
Alright, I am trying to get the logcat with adb. I am in CWM, adb states waiting for device, I hit restart phone in CWM. Nothing changes in adb and the logcat is blank any ideas?
This is the logcat:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Did you edit the scripts to flash the kernel? SRF 1.2 doesn't do that on its own.
Sent from my locked down, rootless temp rooted EVO 3D

Try this, grab the kernel update.zip, after flashing the ROM flash the kernel just to see if it will boot, if it does then you know for sure everything else is ok, but like it has been stated, 1.2 may not have the script to flash the kernel, I cant remeber, but I never built off of 1.2 only 1.0 and under.

Thanks for the tips, ill give them a try in the morning.
Sent from my SPH-D700 using XDA App

As mentioned, SRF 1.2 does not flash a kernel. RandomROM does, check the code towards the end of updater-script for the kernel code, it's clearly labeled. Just make sure your updater-script code matches the code that came with Genocide 2.0, including the folder name that it's flashing from. RandomROM uses "kernel", some roms use "kernel_update."

Alright I got it to work by switching the scripts from the SRF 1.2 to RandomRom. I initially chose SRF because Randrom was based on it. Then I added the kernel flashing script to the updater-script from SRF but i probably messed something up in there. Thanks for the help guys.

Related

[REQUEST] Need a kernel update.zip converted to a boot.img

I am in a bit of a pickle. I'm one of the unfortunate souls who's brand new Evo doesn't take kindly to flashing. I am rooted and running sprintlovers Rom, but would like to try some overclock goodness, not to mention having the framerate unlocked. My thought is that, though I can't flash anything from recovery (when you try to flash anything, it just bootloops right back into recovery when you restart), I may be able to flash an OC'd kernel through fastboot. I looked into how to do this myself, but it still seems a bit over my head. Is there a kind soul out there who would make me a boot.img out of either or both of these???
netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal
netarchy-toastmod-4.2.1-cfs-bfq-havs-less-smartass-universal (Less Aggressive Undervolting)
Thanks a lot for your help!!!!!
Richard
you can't flash anything from recovery?
Put it on your PC, open up the .zip and you may find a little surprise in there...
xHausx said:
you can't flash anything from recovery?
Click to expand...
Click to collapse
Nope. I have S-off, I am running sprintlovers and have root, but when I boot to recovery, flash something, and then reboot.....all I get are bootloops. Yesterday, I opened up logcat just before booting. Here us the one and only log entry:
Code:
C:\A>adb logcat
- waiting for device -
link_image[1995]: failed to link /system/bin/sh
CANNOT LINK EXECUTABLE
Igotsanevo4g said:
Put it on your PC, open up the .zip and you may find a little surprise in there...
Click to expand...
Click to collapse
Lol, I may be new to the evo, but I'm not a total n00b. That was the first thing I checked. There is no flashable boot.img file in the kernel folder. Now, maybe one of the files in that folder just needs to be renamed, I'll admit my ignorance right upfront. I did do research before I made this thread, but when they started talking hex editing (of which I've only done a little) and running prl scripts, I knew I was getting over my head.
EDIT: BTW, I have tried both clockwork and Amon-Ra recoveries. Both have the same basic logcat readout, just a slight variation in syntax.
Afternoon bump
tejasrichard said:
Afternoon bump
Click to expand...
Click to collapse
if its the new evo u cant flash a kernel or any rom that isnt based on the latest OTA's. Its because they have a few different drivers and the kernels dont support them yet so thats why u cant flash anything really. so just sit tight with a rom like sprint lovers or Vaelpak and you should be good for now
Use the Android kitchen in the chef's forums. It will inject that kernel into whatever boot.img you want real fast
May be a dumb reply but did you wipe and clear cache?
You can strip the zimage file out of the .zip and push it to the phone using adb...

[Q] Problem Flashing kernel

Whats up guys,
got a quick question. i just downloaded the fresh 3.5 Rom yesterday and have no problems with it what so ever, very fast and responsive. out of curiousity ive been looking around at kernels, and have realized that i can get my phone even faster. i know that fresh's Rom already comes with a kernel, but like i said, out of curiousity im looking to see if i can get it even faster. i place the folder onto the sd card, and wipe the cach and douch (whatever its called), and go to flash the file under recovery mode only to find myself searching through the files within the kernel folder (kernel, system, and META-INF) instead of actually installing the kernel itself. what am i doing wrong here?
:FYI i am also using a mac if that makes a difference at all
It sounds like you extracted the zip file.
Try downloading the zip using the xda app or tapatalk.
And don't unzip it just put it on the root, if using Amon_RA 1.8 or leave in downloads if using 2.1.1 or Clockwork
Sent from my PC36100 using Tapatalk
Well what i did was download the file straight from the xda forums, and dragged it from the downloads list once it was finished and onto the root. I didnt unzip anything on purpose, but maybe it does it automatically?
And i am using Clockwork, what exactly do u mean leave in the downloads?
Flash the kernel in exactly the same way that you flashed fresh's rom. If you used rom manager to flash the rom then these instructions don't apply. Try downloading the kernel with your phone, and then reboot to clockwork and go to flash zip. From there navigate the folders until you get to your chosen kernel. It will be in "downloads" or "my downloads" or "tapatalk downloads" or something along those lines.
Thanks a bunch man, helped me figure out my problem. I flashed the 4.1.9.1 netarchy-toastmod and it runs very nice. I ended up getting the zip off of xda and downloading it straight to the root, flashing it and rebooting sucessfully. Thanks againA
Excellent glad it worked out for you.
Glad it worked for ya
When flashing the kernel from stock, say HTC #15 to something else (ziggy, net, etc.), and then flashing back to HTC #15, will those other kernels leave anything behind that can cause trouble for the HTC kernel?
I'm thinking settings/temp files/other files that one kernel leaves behind aside from cache/dalvik.
Does that happen?
snovvman said:
When flashing the kernel from stock, say HTC #15 to something else (ziggy, net, etc.), and then flashing back to HTC #15, will those other kernels leave anything behind that can cause trouble for the HTC kernel?
I'm thinking settings/temp files/other files that one kernel leaves behind aside from cache/dalvik.
Does that happen?
Click to expand...
Click to collapse
Modules will more than likely be left behind. Possibly other files such as a vdd folder if the kernel adjusts vdd on the fly. It all depends on what the kernel installs when flashed and what it does when running.
So far I have overclocked htc #15, added all the governors minus userspace, undervolted it on the lowest frequencies (at the kernel), and the only modules it uses are the stock ones for wifi and wimax.

Issue with ASOP roms and Kernels

Hey guys I am trying to figure out what is going on here. I have tried MIUI and CM7 and both have issues with the first boot and a reboot right away. I have figured out the CM7 with the stock kernel works ok but I can't load MIUI with its stock Kernel at all because it boot loops. Why is my phone acting so strange. I have wiped several times and ran both kings and chakins format all trying to get a clean install but its almost like something is stuck? Anybody have any ideas?
Seagrizzly said:
Hey guys I am trying to figure out what is going on here. I have tried MIUI and CM7 and both have issues with the first boot and a reboot right away. I have figured out the CM7 with the stock kernel works ok but I can't load MIUI with its stock Kernel at all because it boot loops. Why is my phone acting so strange. I have wiped several times and ran both kings and chakins format all trying to get a clean install but its almost like something is stuck? Anybody have any ideas?
Click to expand...
Click to collapse
Have you updated your radio recently, and did you use the all in one
(prl , radio, wimax, etx) zip?
There were reports of problems after flashing the all in one deal, or I suggest wiping again and reflashing each individual part.
I have the newest Radio but not sure about the others. I guess I can just try and flash them over the top of what I have. I know I did a PRL update a day ago in sense so that should be fine. I will try and see about flashing that other stuff.
I checked all the stuff in the list, only one that was older was hboot and I bumped that up to the newest version. Didn't help though. I have no clue what is going on and it sucks that I can't even use an ASOP rom because of reboots.
What root method did you use?
I'll give you a hint:
There's no such thing as "ASOP". There's this thing called AOSP (the Android Open-Source Project) which you might be confusing it for.
As for helping, it would be most useful if you could grab a logcat of the booting of CM7 Nightly 28 after wiping /system, /data, /cache, dalvik-cache, and flashing only Nightly 28 and GApps 20110307.
Which version of MIUI were you trying? If you were trying 1.3.5 or 1.3.11, you need to flash 1.3.4 and then the hotfixes. If you tried to flash only the hotfixes, you'll get boot loops.
Well it seems more to do with kernel then rom, even in CM7 I get boot loops if I change up the Kernel from the stock one. This is with Savage or Tiamat.
Seagrizzly said:
Well it seems more to do with kernel then rom, even in CM7 I get boot loops if I change up the Kernel from the stock one. This is with Savage or Tiamat.
Click to expand...
Click to collapse
logcat
logcat
logcat
logcat
logcat
logcat
logcat
logcat
Post it to pastebin.com, and give us the link here.
Um how do I do a logcat, sorry pretty new but if you can send me a link that tells me how to do it that would be awesome and I will get a capture over right away!
Seagrizzly said:
Um how do I do a logcat, sorry pretty new but if you can send me a link that tells me how to do it that would be awesome and I will get a capture over right away!
Click to expand...
Click to collapse
aLogcat can be DL'ed for free from the Market.
You can save a log to a text file to your SD Card. Move that file to your computer. Load it to Pastebin. Note the link and provide it in this thread.
Like the person above me said, or if you're hooked up to a computer, download and install the Android SDK, open your command prompt, navigate to the Android SDK/platform-tools folder, and run the following:
Windows:
Code:
adb logcat > %userprofile%\Desktop\logcat.txt
Linux:
Code:
./adb logcat > ~\logcat.txt
OS X:
Code:
./adb logcat > ~\Desktop\logcat.txt
Those will put the logcat in a text file on your Desktop (or in Linux, your home folder).
Ok so I download and run this then load the kernel and then upload the logs! I will do this asap, Thanks guys.
Ok so here is the logcat from a boot just after installing the kernel and booting to OS, I took a couple pictures thought things were working fine and then it rebooted, now it boots sits at home for a bit then reboots again. I cleared cache and dalvik before loading kernel too.
http://pastebin.com/yZqCLx0B

[Q] Need help with CWM Recovery and other issues!

Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity
Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App
Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.
Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.
onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.

[ACS][Base Rom]Stock Rooted Odex & Deodex[Updated 10/15/11][Closer to Real Stock]

Welcome!
Hello, these roms were made in order for people to have recovery-flashable zips of stock roms (not having to rely on tars and Odin). These roms are compiled from Odex and Deodex system dumps and have no other mods besides root, busybox and recovery.
***Disclaimer***
I am not responsible for any damage, be it mental, physical, mechanical, etc caused by the flashing of this rom. If you flash it, you do so at your own risk. Glad we could get that out of the way
If any developers want to use these as a base rom, there is no need to ask. Just grab em and go. I made these for themers and other rom developers who don't usually work at making the rom itself, but taking what's there and making it better. I hope it helps out!
First the shout outs:
CNZ (RoadRAGEN) - Updater Script, Odex & Deodex Dump
ptfdmedic - Deodex System Dump
bubby323 and chris41g - for use of kernels and general help.
k0nane - noCIQ mod.
thefredelment, phantomfreak53, darren.wsln1 and lballer59 - Help identifying issues.
And of course the Testers:
henbone11(WR47HANZ), COMEDY, lovinlissa1984, geraldweb, lballer59 and banksj174
The Goods:
Okay, the goods:
EG30 Stock Deodex with root, recovery, busybox WITH No CIQ
EG30 Stock Deodex with root, recovery, busybox WITHOUT the No CIQ mod
EG30 Stock Odex with root, recovery and busybox
The Download links:
Download links can be found here at the ACS Forums!
(Download links to prior versions are in post 2 over there)
Changelog and Features
Version 1 and 2 changelogs in the 2nd post
Changelog
Re-added bubby323's kernel so it is a pure stock rom with ONLY clockwork 5 recovery (no additional features) (all 3 roms)
Removed all non-stock apks and replaced all missing stock apks (only required for the deodex roms)
[/LIST]
Features
Android Version 2.3.4
Kernel Build: bubby323's stock with cwm 5
Rooted with SU v3.0 with fully updated binaries(thanks to cnz(RoadRAGEN))
busbox latest version(thanks to cnz(RoadRAGEN)
ClockworkMod Reocvery version v5.x (thanks to bubby323's kernel)
No-CIQ mod (one of the deodex roms only)(thanks to k0nane)
All stock apps/widgets included (I have removed nothing that came stock)
Pick Which SD Card You Want Recovery to Read
For now, the recovery on the kernels in these roms tells CWM to read from the internal memory card. If you want it to read from the external memory card go here and download the "Latest Compiled Version". Flash in Odin and CWM will work with the external sd card. These roms run the link under "Older releases".
Installation Instructions
For those who just wanna use it as their daily drivers, here's the installation instructions:
ALWAYS MAKE A NANDROID BEFORE YOU FLASH ANYTHING!!!!! <-----Words to flash by.
1. Download rom, put it on your phone.
2. Boot into recovery.
3. FULL WIPE IS REQUIRED. Data AND cache AND dalvik.
3.5 Go back and make sure step 3 has been completed
4. Flash rom.
5. reboot and enjoy
**Warning**
The flash process and first boot takes a minute. Be patient, it will work!
Known Issues
Okay, for whatever reason, the deodex w/NoCIQ just will not install the MyFiles.apk. This doesn't sound significant. However, without it, the contacts app will Force Close when you attempt to assign a custom ringtone to a contact. There are two workarounds:
1. Get a different file manager, navigate to the sound and manually assign it to a contact.
2. Find the apk (it's in every flashable rom) and install it onto your phone manually.
I will attempt to fix it once an update comes out and I'm forced to play with these roms again. Until then, the workaround works just as well. (thanks lballer59 for finding the problem).​
Downloads for older versions found In the 2nd post on this thread
Changelog 10/04/11
Version 1's changelog is in the 2nd post.
Deodex WITH No-CIQ changelog:
Restored the following missing apps:
EmailWidget.apk added
LiveWallpapers.apk added
PicoTts.apk added
SamsungWidget_News.apk added
SamsungWidget_WeatherClock.apk added
SecretWallpaper1.apk
SecretWallpaper2.apk
ShareApp.apk
Swype.apk
Tasks.apk
Added k0nane's NO-CIQ mod
Orange Overscroll Glow (result of the NoCIQ mod)
Added Chris41g's kernel found here
Deodex WITHOUT NO-CIQ mod
Restored the following apks:
EmailWidget.apk added
LiveWallpapers.apk added
PicoTts.apk added
SamsungWidget_News.apk added
SamsungWidget_WeatherClock.apk added
SecretWallpaper1.apk
SecretWallpaper2.apk
ShareApp.apk
Swype.apk
Tasks.apk
Added Chris41g's kernel found here
Odex changelog:
Added Chris41g's kernel found here
Changelog 10/1/2011
Roms were compiled from odex and deodex system dumps
Modified cnz's updater script to fit these roms
Inserted Bubby's Stock Kernel zImage w/ ClockworkMod 4.x​
How to flash if I am not rooted stock?
Hi can you provide a just a few more steps for people like me who are still on stock non rooted rom? I know it says save it on and then flash.
Welcome to the party!
Samsung Galaxy S II
Thank you for you hard work And i totaly agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kenel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
spdwiz18 said:
Thank you for you hard work And i totaly agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kenel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
Click to expand...
Click to collapse
+1
Sent from my SPH-D710 using Tapatalk
spdwiz18 said:
Thank you for you hard work And i totally agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kernel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
Click to expand...
Click to collapse
From my understanding the kernel is built from stock source not the sgs2. However, the cwm is built using the sgs2 binaries to save time. I know a new version is being worked on. I have been using Bubby's stock cwm for about a week and it is working great. Using a jig removed the exclamation mark and the i9100 screen so I am happy where I am. But I am looking forward to a new release that is completely stock with hopefully nothing but boot animation support and init.d. I hate having root and busybox built into the kernel. Just a personal issue.
---------- Post added at 10:31 AM ---------- Previous post was at 10:30 AM ----------
Great work absolutezerogi!
CWM first?
Do I need to flash CWM first for this to work? In that case which CWM should I use? I see two versions available.
Thanks.
rukshmani said:
Do I need to flash CWM first for this to work? In that case which CWM should I use? I see two versions available.
Thanks.
Click to expand...
Click to collapse
Yes. I use Bubby's.
Looking for something Stable... Hope I find it here ( ACS are normally stable ) giving it a shot now! Thanks
So far, this seems to be the closest we can get, without actually getting there.
I have tried Zedomax, and had a few LOS', no big deal, but I went back to stock.
If I go back to Zedomax (CWM, SuperUser, Root), can I flash this in CWM and have a completely stock rom with CWM, SuperUser, and Root WITH the stock kernel?
Thanks in advance.
spdwiz18 said:
Thank you for you hard work And i totaly agree with what you said in your OP.
And the only prob i see is you are using buddy'2 kernel + cmw. From what i understand, and PLEASE correct me if im wrong, THat kenel is still a hack of source and initrams from int sg2. The jury still seems 2b out on wether or not there r issuse with that.
Im still currently looking for totaly stock kernel +root+cmw. IF i new how to make, I would.
again correct me if im wrong and thank you.
Click to expand...
Click to collapse
Got your developers backwards lol. Zedomax's first kernel was from source and initramfs from the SGSII international. I pulled the initframfs myself for bubby's kernel, it's stock I promise
Hi can you provide a just a few more steps for people like me who are still on stock non rooted rom? I know it says save it on and then flash.
Click to expand...
Click to collapse
Hi there!
First you must be rooted. If you're not you need to go to one of our root methods and get rooted and get recovery. Then you just flash these in recovery However, I will make the instructions a little more detailed for ya.
Hi guys!
UPDATE: Now includes busybox.
Enjoy!!
Off topic, but do you suppose cm7 will be compiled using this kernel?
Sent from my SPH-D710 using XDA App
asafegous said:
Off topic, but do you suppose cm7 will be compiled using this kernel?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This is stock rom with TouchWiz and Bubby's completely stock rooted kernel. CM is made fro AOSP (Android Open Source Project) source and then ported to a phone. So, CM won't be using this at all lol.
crap!
UPDATE 2 - back in business. needed to flash stock kernel/rom then let it encrypt, then tell it to decrypt, then re-root, re-flash, back to normal again.
I have a problem, I really hope someone can help.
I followed the directions here, and everything worked great.
i was rocking the rom for about a day and then I noticed in settings that I had an option to "encrypt the phone" so stupidly (and obvoiusly not thinking) i did it and was thrown into a boot loop.
I tried rebooting, and nothing.
I tried booting to recovery, and wiping all, and then reflashing this rom. - nothing
I tried doing the volume down and power, then the volume up thing, and then I reapplied the zImage using heimdall and nothing.
Currently - all I can get to is recovery, I can't mount the the phone (nothing shows up on the computer, maybe because it is encrypted?) So I can't even copy something to the phone to try to flash it
Any ideas? - really deperate here, I can't believe I pulled such a newbie move.
Downloading this as soon as I can. Thanks for your hard work!
Sent from my Galaxy S II
realmrealm said:
UPDATE - So I've been able to get the phone to mount to the computer, but I'm stuck in a loop at this Sprint 4G animation. It just keeps playing it over and over again. (5 minutes now) - I'm just going to let it keep going and see what happens.
I have a problem, I really hope someone can help.
I followed the directions here, and everything worked great.
i was rocking the rom for about a day and then I noticed in settings that I had an option to "encrypt the phone" so stupidly (and obvoiusly not thinking) i did it and was thrown into a boot loop.
I tried rebooting, and nothing.
I tried booting to recovery, and wiping all, and then reflashing this rom. - nothing
I tried doing the volume down and power, then the volume up thing, and then I reapplied the zImage using heimdall and nothing.
Currently - all I can get to is recovery, I can't mount the the phone (nothing shows up on the computer, maybe because it is encrypted?) So I can't even copy something to the phone to try to flash it
Any ideas? - really deperate here, I can't believe I pulled such a newbie move.
Click to expand...
Click to collapse
odin zedos v3 to get cwm then flash this to get back where you want, pm me if you need help.
op, great work on this sir.
realmrealm said:
UPDATE - So I've been able to get the phone to mount to the computer, but I'm stuck in a loop at this Sprint 4G animation. It just keeps playing it over and over again. (5 minutes now) - I'm just going to let it keep going and see what happens.
I have a problem, I really hope someone can help.
I followed the directions here, and everything worked great.
i was rocking the rom for about a day and then I noticed in settings that I had an option to "encrypt the phone" so stupidly (and obvoiusly not thinking) i did it and was thrown into a boot loop.
I tried rebooting, and nothing.
I tried booting to recovery, and wiping all, and then reflashing this rom. - nothing
I tried doing the volume down and power, then the volume up thing, and then I reapplied the zImage using heimdall and nothing.
Currently - all I can get to is recovery, I can't mount the the phone (nothing shows up on the computer, maybe because it is encrypted?) So I can't even copy something to the phone to try to flash it
Any ideas? - really deperate here, I can't believe I pulled such a newbie move.
Click to expand...
Click to collapse
I'm also going to PM with these instructions so I can be sure they get to you faster.
Go here: http://forum.xda-developers.com/showthread.php?t=1282420
download the stock tarball made by crawrj
boot into download mode (volume down + power)
Odin that tar. It'll return you to pure stock (unrooted, stock everything). You should be able to boot then. Do a factory reset once you do (to wipe everything), then you should have a functioning phone to re-root and do whatcha want. Let me know if that works.
Thank you so much OP. I flashed to v4 of Zedomax, then I flashed your ROM in CWM, and now I have everything. CWM, SuperUser, and all of my root apps are working on a deodexed ROM!!!
Thanks again.
Sent from my Galaxy S II

Categories

Resources