I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
NATO556 said:
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
This is not that it can't be done, but it the case of ics for the 4.0, it's a bug in the kernel that force us to flash a kernel from heimdall. If this bug was not here, the rom would be simply flashed with cwm. So the answer is it's not because dev don't want to do it like this, it's because they can't.
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
NATO556 said:
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
ti-pich said:
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
Click to expand...
Click to collapse
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
ti-pich said:
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
Click to expand...
Click to collapse
Well, that's part of it too. I think on the 4.0, the problem may be more complicated than that, due to it's storage layout, (I have the 5.0) but rest assured the devs are working on it.
Please let me know when they fix this bug what I need to do from there.
Sent from my YP-G1 using xda app-developers app
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
There's this but mostly because we change the partition (we completely ditch the j4fs support). Also the bootloaders expect to run BML/STL partitions so the bootmode isn't cleared. The thing that teamhackung made is that they created a partition named reservoir that would handle all the bad blocks. This partition is used to flash the boot partition which is the kernel one. This is still an undergoing experimentation for me but I'll try to compile a CM9 with this new type of flashing. An example of the partition layout is here:
https://github.com/CyanogenMod/andr...ung-3.0-ics/drivers/mtd/onenand/samsung_gsm.h
I may miss some things too but this is the things simplified.
Also NATO I do know how you feel about it and I'm trying to do my best (with han and oisis gone) to solve everything as soon as I can. (Don't forget that I have school too )
Sent from my Nexus 7 using Tapatalk HD
Actually most of the GB ROMs for the 4.0 are CWM flashable zips,
http://forum.xda-developers.com/showthread.php?t=1834375
http://forum.xda-developers.com/showthread.php?t=1718339 (older versions)
http://forum.xda-developers.com/showthread.php?t=1821860
http://forum.xda-developers.com/showthread.php?t=1895629
http://forum.xda-developers.com/showthread.php?t=1884557
http://forum.xda-developers.com/showthread.php?t=1719685
http://forum.xda-developers.com/showthread.php?t=1759949 (several ROMs)
http://forum.xda-developers.com/showthread.php?t=1825281
there are 2 or 3 more ROMs that are CWM zips but there based on the OLD CM7 port and with no deep sleep there not worth the time IMO (not the Porting DEVs fault, it was a known issue of the CM7 base).
NOT ENOUGH FOR YOU?
The ones that aren't are because of data corruption issues.
As for ICS, well thats been covered.
Thank you guys for all you do. I really am thankfull to have a website like this one to turn to for help.
Sent from my YP-G1 using xda app-developers app
As soon as the glitch is fixed please let me know. Another question, will there ever be an official CWM release on the player? And will Tardis_Balor update the Terra Silent Kernel once the glitch is corrected?
Sent from my YP-G1 using xda app-developers app
Also, why is hanthesolo's ethereal tomorrow not on this list?
Sent from my YP-G1 using xda app-developers app
rom*
Sent from my YP-G1 using xda app-developers app
BTW, the link for v2.0 of Icy Fusion is dead.
Sent from my YP-G1 using xda app-developers app
Related
There seems to be a bit of confusion on what recovery we should be using. Most threads indicate CWM 3.x
This post is often referenced as the most current recovery for our needs:
http://forum.xda-developers.com/showpost.php?p=13128524&postcount=1
It can be seen being referenced here:
http://forum.xda-developers.com/showpost.php?p=14892705&postcount=1
Then there is this:
http://forum.xda-developers.com/showpost.php?p=14940474&postcount=202
I have not seen many references to CWM 4.x recovery. Is this for gingerbread roms?
Please understand I am not trying to "shake the bees nest" or anything. I just want to make sure we are doing things correctly. I have been doing some research since the above post was made and have come up with conflicting resulsts, looking for clarification. Thanks.
I sent ti a pm asking about this myself - still waiting to hear back.
Another Fascinating post by my XDA app...
Hmmm 74 views, either no one knows or no one is talking! The mystery grows....
Sent from my SCH-I500 using XDA Premium App
I have been unsuccessful at finding a v4 recovery for anything but CM/AOSP for our phones.
Of course, I have not dedicated much time to the search as my current one seems to be fine.
PhoenixPath said:
I have been unsuccessful at finding a v4 recovery for anything but CM/AOSP for our phones.
Of course, I have not dedicated much time to the search as my current one seems to be fine.
Click to expand...
Click to collapse
I thought my current DINOSAUR recovery was fine too. . .someone out there must know.
Perhaps he was just kidding? or wrong and now does not want to talk about it?
(putting on beekeeper suit)
Just use 4.x
https://github.com/imnuts/android_bootable_recovery
nunyazz said:
Just use 4.x
https://github.com/imnuts/android_bootable_recovery
Click to expand...
Click to collapse
when I downloaded this, it was recovery-clockwork-3.0.0.8-fascinate, so what is 4.x about it? My recovery is the yellow 3.2.0.0 - any available upgrade?
i dunno, it said "CWM Voodoo Lagfix Recovery v4.0.0.1 " in the description. Mine is yellow also, works for all the roms I've tried.
nunyazz said:
i dunno, it said "CWM Voodoo Lagfix Recovery v4.0.0.1 " in the description. Mine is yellow also, works for all the roms I've tried.
Click to expand...
Click to collapse
So I guess we can assume that 4.x is fully backwards compatible with older roms?
I just don't understand how we could be snipped at for not using CMR 4.x when it is not even on his own recovery page (or widely referenced anywhere else).
Don't half tell us something then not back up your claims. It seems this stupid GB leak did nothing but make people crabby! (from day one)
I'm on CM7 with CWM4. I would think CWM3 is fine with TW roms if it still flashes everything and last I know it did. If CWM4 was something you should have there would probably be posts for it in the dev section.
Keithn said:
I'm on CM7 with CWM4. I would think CWM3 is fine with TW roms if it still flashes everything and last I know it did. If CWM4 was something you should have there would probably be posts for it in the dev section.
Click to expand...
Click to collapse
Ummm... that's my point. Did you follow the links in the OP? especially the last one. That is where the confusion came from.
Sent from my SCH-I500 using XDA Premium App
I guess I'd have to look into it but I didn't know of any major differences such as those between CWM2 and 3. So I don't know why it would be a huge deal to use CWM3 if I figure anything out I'll post.
CWM 3.0 may be responsible (but probably isn't) for the sd cards being borked by some of those who've flashed the EC09 GB leak or the early ROMs based on it. That might be why times_infinity made his dinosaur post. That said, it's more likely that the SD card issue is strictly an EC09 issue having nothing to do with which recovery you use. I suggest going on IRC to find your answers (I think either #samsungfascinate or #teamsbrissenmod or maybe #tsm).
Another Fascinating post by my XDA app...
nunyazz said:
Just use 4.x
https://github.com/imnuts/android_bootable_recovery
Click to expand...
Click to collapse
The idiot needs help (that's me). Does anything need to be done to the files after download? I assume you can't just flash the .zip, it couldn't be that simple.
Hey folks,
I just bought the white international SGS II and i'm loving it!
I previously had an Infuse 4g, so I am pretty experienced with flashing/backing up/ restoring...but I have questions/concerns regarding the I9100.
I am about to try out the CM9 Unstable, so I backed my current stock ROM up using CWM Manager 3.0 (I am on CF-Root 5.0) onto my Internal SD, as I do not have an external SD card.
Now, I have had bad experiences with CM7 with Infuse and ended up not being able to restore due to many problems like MD5 mismatch, different CWM version, and problems while restoring ( I think it said something like devblock??)
So I'm pretty worried about not being able to restore back to the backup i just made.
So correct me if I'm wrong folks,
1) Go into CWM, flash CM9(once? twice?), Gapps, Faceunlock,
2) Data wipe/factory reset
3) Reboot
and should I choose to restore back to the stock Rom backup,
just go into CM9's recovery and restore..?
will this method give me problems restoring? will I have different versions of CWM recovery from the one I have currently? Is there any way to check if my back up was made properly?
Thanks a lot folks! Appreciate it!
Edit: "Make sure you're already running ICS bootloader (if not, go to SamMobiles and flash XXKP2 bootloader)". Is this necessary? Cus I have seen some folks say that they've not and was fine installing CM9.
First the procedure:
1. Wipe
2. Install CyanogenMod 9
3. Reboot
4. Install CyanogenMod again
5. Install gapps and face-unlock
Worked for me every time.
Your backups should work unless there were errors while creating them.
If you want some more safety, you can create a new backup after flashing the Siyah-kernel. The latest version uses the same version of ClockWorkMod as CyanogenMod 9.
Whether you need to flash the bootloader or not, depends on whether you already have it or not. I'm running galnet-MIUI and already had the bootloader installed. I don't know how to tell if you have it.
Sent from my GT-I9100 using XDA App
Ok...
I did further research and found out that Nandroid backup backs up everything EXCEPT the kernel.
I'm pretty sure that CM has its own kernel...but will it be CWM 5.0.2.7(the one i made backup in.)?
If it's not, the correct steps for me to restore my nandroid back up is to
1)boot into download mode from CM9,
2) put the cf-root kernel that i used in the ODIN PDA, flash,
3) turn off phone, reboot into CWM, then restore my nandroid back up right??
Can anyone please confirm this method??
I only have this phone and I cannot risk soft-bricking or hard-bricking this beautiful device.
Thanks in advance!
Also, i made a back up in blue recovery of CWM 5.0.2.7..does that matter?
TheSniperFan said:
First the procedure:
1. Wipe
2. Install CyanogenMod 9
3. Reboot
4. Install CyanogenMod again
5. Install gapps and face-unlock
Worked for me every time.
Your backups should work unless there were errors while creating them.
If you want some more safety, you can create a new backup after flashing the Siyah-kernel. The latest version uses the same version of ClockWorkMod as CyanogenMod 9.
Whether you need to flash the bootloader or not, depends on whether you already have it or not. I'm running galnet-MIUI and already had the bootloader installed. I don't know how to tell if you have it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
thanks for the reply,
so I must have the ICS bootloaders in order for CM9 to work?
ooo siyah kernel method... that makes it easier! haha thanks so much!
I will proceed to do that!
btw, how is CM9 working for you?
do you think you'll be able to use it as a daily driver now that NITZ is gone??
1. Afaik cwm backs the kernel up and restores it too. (afaik = 99.9% sure, in this case)
2. CyanogenMod ships with its own kernel.
3. The kernel is not cwm. ClockWorkMod is just the recovery that is integrated into the kernel. CyanogenMod 9 has cwm-recovery 5.5 (Siyah too btw)
4. You don't need to use download-mode to restore.
Sent from my GT-I9100 using XDA App
You must have ICS-bootleggers. He did not say that for fun xD.
Is it suitable as daily driver for me?
Nope.avi
Why?
Accelerometer is unresponsive, so it takes forever to flip your screen.
Battery drainage is horrible.
Camera isn't working properly.
And the biggest no-go for me:
The device gets way to hot when using it.
Sent from my GT-I9100 using XDA App
TheSniperFan said:
You must have ICS-bootleggers. He did not say that for fun xD.
Is it suitable as daily driver for me?
Nope.avi
Why?
Accelerometer is unresponsive, so it takes forever to flip your screen.
Battery drainage is horrible.
Camera isn't working properly.
And the biggest no-go for me:
The device gets way to hot when using it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
alright,
thanks for the information!
I'll flash the Siyah kernel
Btw,
Flashing CM9 Zip does not flash the ICS bootloader right?
so then if I want to restore to my GB 2.3.5, would I need to flash GB bootloaders before restoring via Odin??
If the zip would flash the loaders, he wouldn't have mentioned it.
They're backwards-compatible.
Sent from my GT-I9100 using XDA App
If you need to make a post in the Q&A forums about flashing CM9, then you are definitely not the sort of person who should be flashing it. It is in very much a beta stage and there is a very high possibility it will **** your phone up even if you have done nothing wrong. If that happens you need to be the sort of person with enough experience to solve the problem by themselves. If you are asking questions before you've even flashed it then really, it's not for you. Use CM7, at the moment it's better than CM9 in every single way.
postfatal said:
If you need to make a post in the Q&A forums about flashing CM9, then you are definitely not the sort of person who should be flashing it. It is in very much a beta stage and there is a very high possibility it will **** your phone up even if you have done nothing wrong. If that happens you need to be the sort of person with enough experience to solve the problem by themselves. If you are asking questions before you've even flashed it then really, it's not for you. Use CM7, at the moment it's better than CM9 in every single way.
Click to expand...
Click to collapse
It's not thaaaaaaaaat bad. I mean, he won't be able to brick the device through cwm.
If he doesn't ask, he will never learn and it's always better to ask twice than to break something.
Sent from my GT-I9100 using XDA App
Thank you sniper =) really appreciate the support.
Ive been flashing and restoring before with my infuse 4g. Just sometimes ran into problems with restoring with diff CWM versions and stuff. This phone is very precious(expensive) so i thought i would learn it for sure before i attempted anything.. thanks anyways for sharing your opinion!
Sent from my GT-I9100 using XDA App
TheSniperFan said:
It's not thaaaaaaaaat bad. I mean, he won't be able to brick the device through cwm.
If he doesn't ask, he will never learn and it's always better to ask twice than to break something.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I couldnt agree more... i think people here on XDA need to stop trying to be all hot **** saying Oh you asked a question your a noob... in reality most ppl here want to ask the same question but dont because afraid of getting *****ed out... and when someone else asks... try to be badass and put the person down...
Iv used a Galaxy S and a Moto Atrix and now a S2... flashed the life out of each phone along with all kinds of stuff and mods... yet i would have wanted to ask these same questions before flashing hence googled and found this thread... So thanks to those that replied as well... i was about to flash ics till i read this and guess imma hold back now even more...
But again i think people here need to calm the hell down... a person asks a question in the thread and you call them a 'noob' and what not... a person asks a question in the Q&A section and again you tell them off... stop being such anal retentive trolls...
DrunkFuX666 said:
I couldnt agree more... i think people here on XDA need to stop trying to be all hot **** saying Oh you asked a question your a noob... in reality most ppl here want to ask the same question but dont because afraid of getting *****ed out... and when someone else asks... try to be badass and put the person down...
Iv used a Galaxy S and a Moto Atrix and now a S2... flashed the life out of each phone along with all kinds of stuff and mods... yet i would have wanted to ask these same questions before flashing hence googled and found this thread... So thanks to those that replied as well... i was about to flash ics till i read this and guess imma hold back now even more...
But again i think people here need to calm the hell down... a person asks a question in the thread and you call them a 'noob' and what not... a person asks a question in the Q&A section and again you tell them off... stop being such anal retentive trolls...
Click to expand...
Click to collapse
Most people should not flame some one as long as they show they have at least tried to look for an answer first. Yes we were all new at one time but we all learned.
Like you said you Googled and found your answer. Not that hard.
Think it's bad now. Should have seen it a few years ago. Lol clutter up the threads with questions that the answers were found with a search. You got warned. Do it twice and you went on vacation for a few days to learn how to search. So the next time you think people are being too hard. Remember it is not as hlbad as it was.
When I search for the answer, I ended up here.
are these considered ICS bootloaders? If not, when would you flash them, because they are completely unmentioned in any of the instructions or FAQs
CWM flashable Modems:
XXKP8 Modem: http://www.multiupload.com/64J2P1MZL6
XXKP4 Modem: http://www.multiupload.com/NYUYFOT1ST
I'm planning on getting this device shortly & was wondering if the stock kernel will work with most of the roms developed here? I'm just trying to do my homework so I can be ready when I have it in hand. I'm so ready to ditch the g2x.
Sent from my LG-P999 using xda premium
TBH I haven't seen a stock kernel NOT work with a Custom ROM. The only thing is some of the features i.e. Wifi Calling may not work. So it's always best to flash the recommended to avoid boot loops or bugs.
I just looked at four of the most popular ROMs, and in less than five minutes read that only one of them said stock kernel was ok. The other three say to flash either faux's kernel, xboarder's newest kernel, or the included boot.img in the download.
But yes the stock kernel will work but like just mentioned it will have limited functionality. In my opinion, read what the dev says in their OP and throughout their thread, but a whole thread on this isn't necessary.
I don't mean to be rude, just saying it like it is. Welcome!
Sent from my HTC_Amaze_4G using XDA App
Thanks for ur replys guy's. I have always used the stock kernel with every rom on every device I've used. I'm new to flashing kernels & every time I tried flashing a kernel I've always had issues. Thanks again for ur answers.
Sent from my LG-P999 using xda premium
I wonder how this thread's topic relates to development...
Okay let me clarify the whole kernel thing.
We have three types kernels to chose from.
The stock OTA kernel. That's what your phone comes with. It is secured which means it will not allow scripts to auto-start (which means that init.d is worthless) and does not default with superuser access from adb or terminal. You can still get root access but you always need to do "su" command.
The unsecured kernel. This is the kernel that comes with your rom. This is commonly found in the zip file of the custom rom that you download. The custom rom DOES NOT (which also means DOESN'T, WON'T, WILL NOT, CAN'T and CAN NOT) update the kernel by recovery like almost all the other phones do. We believe this is because we have bootloaders with S-ON. When or IF we get s-off we may be capable of flashing a kernel by recovery.
Faux123's kernel.
Refer to [Kernel]HTC Stock[2.6.35.13](v0.0.7)OC~1.73/UV/CIFS+UTF-8[Dec-30]
Q&A
But can't we flash Faux's kernel by recovery?
Yes and no. I developed a workaround to make that work however it doesn't directly flash the kernel from the recovery. It flashes the kernel after the phone has already booted which is why a second reboot is required.
Well... why not? I don't understand.
Unfortunately since the phone MUST come to a complete boot from a kernel that initiats init.d scripts (unsecured kernel as described above), we cannot use the above method going from a pure rooted OTA rom or when going from SenseUI 3.0 to SenseUI 3.5 or ICS roms. Let me know if you're confused by this.
Alright... so can you tell me more about Faux's kernel?
Well since I'm not Faux123 I'll try to answer this.
It's a slightly modified version of the unsecured kernel (capable of executing init.d scripts) that has been tweaked to allow slight over clocking and control over the voltage going to the CPU and RAM of the phone. This can help you or hurt you. You can push your processor harder and faster to increase performance but you may lose stability and drain your battery faster. Alternatively you can reduce the voltage and preserve battery life. At this time the kernel is NOT complete due to HTC not releasing the full source of their TI drivers. It would appear that since it is not technically their drivers, they don't have to release it.
So... what's the problem making the kernel?
Faux123 tried to make the kernel from source, unfortunately without the full source attempting to do so will lose wifi and wireless tethering abilities. Again... blame HTC for that. Until they release the full source we're stuck with this limitation.
So all this talking about kernels you still haven't explain how to flash it?
This part is easy.
Use this: [Guide][Tool] Kernel Flasher 2 Step/Kernel Restore Tool||Noob Proof||V3 released || or whatever directions are included with the ROM or kernel that you're interested in flashing. If you're skilled enough you can just use the fastboot commands.
From bootloader:
fastboot flash boot c:\directorytoboot\boot.img
(replace c:\directorytoboot with actual directory)
So in conclusion... as soon as HTC releases s-off for our devices as well as the full kernel source code we can have some really kick @$$ phones! Until then... we have to [email protected]$$ everything such as fastboot flashing our half-a$$ modified kernels. It's not the rom or kernel developers fault... it's HTC's.
Felinos11 said:
I wonder how this thread's topic relates to development...
Click to expand...
Click to collapse
Yeah yeah... I'll move it.
Thank you binary for your excellent explanation. I posted it here because the people with the knowledge frequent this board & hope they would see it. I apologize if I posted this in the wrong place.
Sent from my LG-P999 using xda premium
Binary100100 said:
Yeah yeah... I'll move it.
Click to expand...
Click to collapse
so how do I go back to stock kernel binary!!!!! i kid, i kid!!!
Stock kernel works fine.
seansk said:
so how do I go back to stock kernel binary!!!!! i kid, i kid!!!
Click to expand...
Click to collapse
Go choke on some nitrous.
Binary100100 said:
Go choke on some nitrous.
Click to expand...
Click to collapse
I love nitrous oxide, we had to try in in school, you should try it sometimes, we use it on kids, and some adults unfortunately that act like kids on the dental chair
seansk said:
I love nitrous oxide, we had to try in in school, you should try it sometimes, we use it on kids, and some adults unfortunately that act like kids on the dental chair
Click to expand...
Click to collapse
I'll try it while at the range. The range masters should love that.
Binary100100 said:
I'll try it while at the range. The range masters should love that.
Click to expand...
Click to collapse
Hmm...I don't know if those two will mix well!!!
Hi guys,
I am one of galaxy s2 die hard fans and i love it! however currently, i am on GB, not planning to move to ICS due to all those bugs and force close thing.
I am planning to make a new ICS custom ROM base on official xwlp7(latest Russian release) and wanna share it with you all.
However, i need some opinions and advises from you all.
Example, what you want/need for a ROM that suits you. I am thinking of OTA thingy for ease of customization, but i might need to "rent" or host my own server for that. I am too new for that, and I don't think i can afford it.
Tell me what you want, like, need, must have and so on.
Btw, can i replace old bootloader for official ICS firmware for usb jig purposes?
What apk is a need and what not. I am still new on this, so my so-call future ROM might or might not come out. Hope i don't give up half way. I know this is gonna be tough for someone new to cook a new ROM like me. I love challenges!
So please leave a comment, i will try to evaluate and hopefully make a useful ROM for you guys. Let's keep the development alive! WEEEEEEE!
Yes you can include old bootloader. Thats what I do when repackaging firmwares.
Also, include the usual, Superuser, Busybox, CWM Recovery.
Personally thats all I would need but cosmetic changes are more my thing. So extra window animations and transitions would be great with a menu in settings to choose from!
Good luck!
Sent from my GT-I9100 using Tapatalk 2
lyriquidperfection said:
Yes you can include old bootloader. Thats what I do when repackaging firmwares.
Also, include the usual, Superuser, Busybox, CWM Recovery.
Personally thats all I would need but cosmetic changes are more my thing. So extra window animations and transitions would be great with a menu in settings to choose from!
Good luck!
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks man. Appreciate it. I will try to make a simple ROM and remove bloatware as my first try. If I am not wrong, only ubuntu can be use to make custom ROM?
Sent from my GT-I9100 using xda premium
It is new information for me that each Custom Rom (CWM package) also contain Bootloader?
zaheedahmed said:
It is new information for me that each Custom Rom (CWM package) also contain Bootloader?
Click to expand...
Click to collapse
I suppose so. You need bootloader to boot up your phone. That's why it is called bootloader!
Sent from my GT-I9100 using xda premium
Hello, I keep getting a low disk space warning when I have almost 12 gigs of space free. Does anyone me have a solution for this?
Sent from my GT-I900 using xda app-developers app
This is the vibrant forums, not the galaxy s forums, please post this to the correct forums.
Sent from my SGH-T959 using xda app-developers app
Also, I dont see the problem cause it says low storage but you didn't say how it interfereres, by like not letting you download more things, maybe its a glitch, but for now leave it alone.
Sent from my SGH-T959 using xda app-developers app
I'm in the right section and it is a issue. I've read about it but I have yet to find a fix. Maybe someone on this section can point me to the right direction.
Sent from my GT-I900 using xda app-developers app
Shiv4m said:
I'm in the right section and it is a issue. I've read about it but I have yet to find a fix. Maybe someone on this section can point me to the right direction.
Sent from my GT-I900 using xda app-developers app
Click to expand...
Click to collapse
what ROM and kernel are you using?? i had a similar problem with ICS_Euphoria_RC2.1 wile using the devil kernel. i was able to correct it with a datafix_11032012.zip and switching to subZero kernal. but that was me
I'm using ICS PASSION and the kernel that cones with it. Can you link me to the data fix link?
Sent from my GT-I900 using xda app-developers app
Read here and here and then choose which is best for you.
This is an old issue with Passion and had been discussed in that thread many months ago. I am sure if you searched the thread, the answer would have *eventually* pooped up but with that many posts, it would take all day to do so.
That being said, Passion is extremely outdated (still 4.0.3) and I suggest upgrading to a different ROM (4.0.4 variant). There was vast improvements from Google with the newer version, plus Passion isn't really supported anymore.
Woodrube said:
Read here and here and then choose which is best for you.
This is an old issue with Passion and had been discussed in that thread many months ago. I am sure if you searched the thread, the answer would have *eventually* pooped up but with that many posts, it would take all day to do so.
That being said, Passion is extremely outdated (still 4.0.3) and I suggest upgrading to a different ROM (4.0.4 variant). There was vast improvements from Google with the newer version, plus Passion isn't really supported anymore.
Click to expand...
Click to collapse
Thank you. Just a side question, if I were to move from Passion to a 4.0.4 ROM such as ICZen, would all my info get deleted? Or does that only happen if I was to upgrade specific Passion updates if I have that ROM already?
EDIT: I just realized you linked me to the I9000 section. I have the Vibrant.
Shiv4m said:
Thank you. Just a side question, if I were to move from Passion to a 4.0.4 ROM such as ICZen, would all my info get deleted? Or does that only happen if I was to upgrade specific Passion updates if I have that ROM already?
EDIT: I just realized you linked me to the I9000 section. I have the Vibrant.
Click to expand...
Click to collapse
Yes and no. You can preserve you app data, browser links, SMS/MMS, Launcher Setting,...through Titanium Backup and then restore the DATA part later. I capped that so as to warn you not to restore the /system/apk (only restore the data on the Green highlighted /system/apps in TBPro).
Yes I did link you to the I9000 section bc those are what you want. All it is is a script that converts your /data/data to /datadata. AKAIK, all the newr ICS ROMs already do this, hence why I suggested you get out of the outdated ROM. ICZen does this on install already btw>
Thanks.
And to confirm, I would only have to install the ICZen ROM right? It states that the subzero kernel is included. ( I saw your name on there, so I thought I'd ask)
Yes it is included. Install instructions are similar to most every other ICS ROM out there except for the additional WIPE.
Steps
-Download ICZen and place it on your internal sd
-Reboot to Clockwork Recovery
-Perform a wipedata/factory reset
-Go to mounts and storage and format the system partition
-Flash your downloaded ICZ rom file
-From the main menu of recovery, perform a wipedata/factory reset again <--THIS IS THE SECOND WIPE I AM TALKING ABOUT
-Reboot
-On bootup, give it a few minutes to settle in, reboot and use as normal.
-Enjoy your ICZen!
Click to expand...
Click to collapse
Just installed everything and it's nice and quick.
Just one problem, how can I disable the vibration when I type? I searched for an option under Settings and didn't find anything.
Shiv4m said:
Just installed everything and it's nice and quick.
Just one problem, how can I disable the vibration when I type? I searched for an option under Settings and didn't find anything.
Click to expand...
Click to collapse
that should be under the sound tab...in your setting (Vibrate on touch)
Tried that and it still continues to vibrate when I touch.
Sent from my SGH-T959 using xda app-developers app
Download NS Tools from Play.Store.
Woodrube said:
Download NS Tools from Play.Store.
Click to expand...
Click to collapse
Sorry but I yet again don't see an option for vibrate when typing. I'm passing it would be under the keyboard settings but its not.
Sent from my SGH-T959 using xda app-developers app