Hi everybody, with the release of JL2 that supposedly "fixes" the SD card corruption, I have some questions.
Last week when I finally got my phone back (with JH2), I flashed JK4 using Odin (no repartition or PIT), and it worked flawlessly. I have not been having any issues with GPS or any crashing/freezing. I have two questions:
1. If I flash JL2 over JK4, do I need to wipe my data / cache afterwards, or can I leave it to keep all my settings and programs? They're both Froyo roms, so I'm not sure what is safe to do in this situation.
2. What is the difference between JL2 and JK4? I've compared the individual files inside the tar files, and they all seem to have the exact same size, but different dates. See the attached image for reference. Is it possible for the files to actually contain different code that fix the problem, even though the files are the same size? Has anyone noticed a true difference between the two ROMs?
Basically, I'm trying to decide if it's worth the risk to flash a new rom and/or have to go through the trouble of reconfiguring everything, if I may not need to.
Thanks, Mike.
have same question got my phone from repair and they installed JK4 on it... should I update it to JL2?
1. You're probably safe to flash without any wiping. If you do happen to run into any issues though a factory reset would likely take care of it.
2. I can't say for sure what's different, but GPS for me is much better - it locks on much faster and seems to be able to maintain the locks it has. I've also noticed no issues with WiFi so far - I did have an issue with WiFi on JK4 where it would not turn on and throw the occasional error, but I've played on WiFi on and off a few times on JL2 and it's been fine.
I'd say flash it - I was on JK4 but fell back to JH2 due to the bricking problem - even if I had no issues on JK4 and kept with it I'd flash JL2 anyway.
What risks are you talking about that your not already taking with JK4? An update is an update so you should update. I like how you say everything is working flawlessly so I do not want to change it and risk "something happening" 90% of users who have had there phones fail from custom roms and JK4 there phones were working flawlessly. Mine worked flawless for 2 weeks then boom Sd corruption some phones last even longer.
got_milk said:
1. You're probably safe to flash without any wiping. If you do happen to run into any issues though a factory reset would likely take care of it.
2. I can't say for sure what's different, but GPS for me is much better - it locks on much faster and seems to be able to maintain the locks it has. I've also noticed no issues with WiFi so far - I did have an issue with WiFi on JK4 where it would not turn on and throw the occasional error, but I've played on WiFi on and off a few times on JL2 and it's been fine.
I'd say flash it - I was on JK4 but fell back to JH2 due to the bricking problem - even if I had no issues on JK4 and kept with it I'd flash JL2 anyway.
Click to expand...
Click to collapse
I must say, your sig is classic. Hahahah.
The file that supposedly fixes the corrupt internal SD card is the sbl.bin
It's some type of secondary bootloader, and it may be that it needs to be a specific size and reside in a specific location for the hardware to process it during boot.
If that is the case, the fact that the sizes match does not mean the files are identical, and you should definitely update to the newest sbl.bin by flashing jl2.
Also, I love that quote about the '10 types of people' because anyone who understands binary should actually correct it to '1 types of people' In binary 0 is a valid first type of people; and '10' means there would be 3 types.
I guess that makes you the 3rd type...
Sent from my GT-I9000M using XDA App
Related
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
JP2
JP3
BOJI
HVJHI
GJH2
JM2
JM4
XWJM5
JM7
JM8
UGJH2
1.20Ghz Kernel
Bad:
JPC
JPH
(possibly caused by One click lagfix)
To keep 850mhz radio
Modem: http://www.mediafire.com/?qic38waf8px13mz
CSC: http://www.mediafire.com/?7ow6p25nhzle5jo
JPC worked fine on my Bell Vibrant. Any of the international firmwares will work without any issues short of the issues inherent in the firmware already.
That was my understanding as well, but many people and all of the seem to have Bell Vibrants are getting corrupt sd cards from JPC, which basically bricks the phone.
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Fuzz21 said:
My Bell Vibrant was Bricked no idea why ? because i didn't root or use a custom ROM so Bell [email protected]#$%# me over. Dammit 500 $ paper weight.
Now i gotta wait 3 to 6 weeks unless someone knows how to unbrick one without the 3 button recovery mode ?
Anyone ideas ? lol
Click to expand...
Click to collapse
No exactly what this thread is about sorry.
I also have a brick sent back to Bell/Samsung for repairs due to JPC.
I'm pretty sure any other firmware is fine. I had the HK JP2 installed without issue. Other than that I just stuck with the UGJH2 as it's nearly as new as any of the international firmwares and runs smooth, even without a lagfix.
mafiaboy01 said:
Hi, I was just wanting to clarify what firmwares are safe to use on the Bell i9000.
I previously screwed up my phone because I flashed JPC and it corrupted my internal memory.
I was hopping to clear up what can be flashed on the Bell version of the i9000 and what can't me.
So far this is what I know.
Good:
HK JP2
JP3
UGJH2
Bad:
JPC
JPH
Click to expand...
Click to collapse
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
For me and some others JPC did it :S
jentech said:
I've had no problem with JPC. I've flashed it a couple of times over the past few weeks. It ran extremely well. JPH on the other hand has hooped my phone.
Click to expand...
Click to collapse
JPC ran like garbage on mine but no major issues aside from the lag, JPH though has been a champ for me thus far.
Sent from my GT-I9000 using XDA App
we need to pin down as to what caused these SDCARD errors so we can all avoid that.
I'm thinking maybe repartitioning with the wrong pit file might cause something like this ?
I'm using JPC on my I9000m now, working nicely (some lag here and there, but nothing AutoKiller can't take care of), and since I saw the post about the SDCARD error on one of the i9000m, am a bit hesitant to flash JPH.
Problem is, if it does get bricked, its basically paper weight because am in the US and doubt Bell or Samsung US/Canada would be willing to help.
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
mafiaboy01 said:
I also would like to find out what is causing the problems, it has to be an issue with only some of the Bell ones because there are people running these frimwares with no issues.
Click to expand...
Click to collapse
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
JPC messed mine with no lagfix installed. This has been ruled out in several threads on xda.
Sent from my I7500 using XDA App
it is also highly likely that us bell users are flashing with bell modem so that we can keep 850 out of the box and is root of the sdcard corruption.
for some reason i remember having nexus one that every firmware and mod always strongly warned that froyo modem is required as well as flushing dalwik cache right after upgrading from éclair.
and here most of us are doing just that using jh2 with froyo.
well as for me i know i wont be upgrading to froyo as long as this thing with sdcard keeps happening as my 30 days was up on sept 9 so no more DOA and even if under warranty still not willing to be without the phone for more than a month.
madmack said:
am just throwing out ideas here, but it could be one of the lag fixes causing corruption in the internal memory if not correctly uninstalled before flashing new firmwares ?
jentech, did you use any of the lag fixes prior to flashing JPH ?
Click to expand...
Click to collapse
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
mafiaboy01 said:
I lag fixed mine but as others have said it doesn't seem to be the cause.
Though I did seem to find a progressive decay in the phone until it finally shut off and never started. It wasn't all of a sudden.
Click to expand...
Click to collapse
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
madmack said:
Which lag fix ? if you used OCLF, did you allocate the entire internal memory to it ?
Click to expand...
Click to collapse
Yes I did use OCLF, I only allocated the default so something like 800mb.
Sent from my GT-I9000M using XDA App
All the ones bricked, were you also having issues with the 3 button recovery? Trying to see if there is any connection there.
I'm reading around regarding this error, and it seems some guys with other phones and the same error got things running back by using Parted. You basically boot into recovery, push Parted to the bin folder, and then repartition/format that failed block: mmcblk0p1
I'm not sure what the file system currently is on that block, but the guys I got this info from were formatting it to ext2. I think if we modify it to match the filesystem that our ROMs require, then we're good. It's a long shot though, and if anybody has a bricked phone with them now, they could give it a go before sending it back for repair.
I used kies yesterday and upgraded to UGJH2, don't remember what it was before, whatever was factory loaded but now I am having all sorts of problems that I did not before.
GPS is way out of wack. Phone freezes. Signal disappears. Right now it's running smoothly but all day it was going retarded.
I give it a bit, if it doesn't sort itself out by the time froyo rolls I'll be flashing this sucka.
Thanks for the heads on good roms.
In an effort to get BLN back on my I9000M, I'm trying to decide if it's worth switching to the SpeedMod kernel. Since I've got my I9000M back from repair and upgraded to JL2 it's been running flawlessly so I don't want to mess with it - but I do want BLN.
So JL2 users with SpeedMod - any problems so far? (and which version of SpeedMod are you using?)
I'm referring to this SpeedMod, btw:
http://forum.xda-developers.com/showthread.php?t=822756
I would definitely switch to SpeedMod. It's a great, fast kernel with a ton of options.
It wouldn't cause the SD card to die, if that's what you're thinking, because by flashing the JL2 firmware you're flashing the secondary boot loader (Sbl.bin) which fixes the issues with the SD card. The kernel is like an entirely separate entity than the sbl, which means it won't brick.
So, go ahead and flash it.
Thanks for the feedback. I wasn't worried so much about the internal SD as I was about things like WiFi battery drain which seems to have become an issue in some of the 2.2.1 releases.
But since I'm not too familiar with Android/Linux development, I'm don't know if it has more to do with the JP* firmwares or the kernel itself.
I've been running it with speedmod k10k all lagfix/speed options disabled (I don't need them, this rom is quick!) and my phone is working like a champ. wifi/gps off, push/pull on w/ hsdpa, I can go just about two full days without charging. With wifi on and gps on plus everything else, I can go about 10-12 hrs.
seeARMS said:
I would definitely switch to SpeedMod. It's a great, fast kernel with a ton of options.
It wouldn't cause the SD card to die, if that's what you're thinking, because by flashing the JL2 firmware you're flashing the secondary boot loader (Sbl.bin) which fixes the issues with the SD card. The kernel is like an entirely separate entity than the sbl, which means it won't brick.
So, go ahead and flash it.
Click to expand...
Click to collapse
I was under the impression that the sd card issue was a bit deeper than just flashing a new bootloader. Is there a thread with more about this? i dont want to brick any more phones, and if flashing JL2 will correct the memory issues, i'll gladly go back from jpy. and is there any way to flash the SBL (if it in fact fixes the sd corruption) without changing anything else? ie: sticking with my jpy without a whole pile of flashing to jl2, then back, etc.
Thanks for the input. Running now with all the recommended tweaks but no lag fix... Maybe a bit more fluid in the ui, but honestly jl2 was so fast to begin with its hard to tell All i really care about is that i got bln back.
Will be watching battery overnight with fingers crossed.
Sent from my GT-I9000M
pervert said:
I was under the impression that the sd card issue was a bit deeper than just flashing a new bootloader. Is there a thread with more about this? i dont want to brick any more phones, and if flashing JL2 will correct the memory issues, i'll gladly go back from jpy. and is there any way to flash the SBL (if it in fact fixes the sd corruption) without changing anything else? ie: sticking with my jpy without a whole pile of flashing to jl2, then back, etc.
Click to expand...
Click to collapse
I too would like a little more official information about this, and whether the new SBL fixes this. As this seems a little to quick for Samsung to say they've fixed the problem. Who knows that would be a great not to live in fear each and everyday I use my SGS
I'm so new to this - is this easy to do ? to flash this rom ?
where's the best way to start, you tube? is there any reccomended tutorials ?
I have a SGS from bell, it's my 2nd one. I haven't upgraded to Froyo yet b/c I can't connect to Kies. Should I just flash instead ?
radeon_x said:
In an effort to get BLN back on my I9000M, I'm trying to decide if it's worth switching to the SpeedMod kernel. Since I've got my I9000M back from repair and upgraded to JL2 it's been running flawlessly so I don't want to mess with it - but I do want BLN.
So JL2 users with SpeedMod - any problems so far? (and which version of SpeedMod are you using?)
I'm referring to this SpeedMod, btw:
http://forum.xda-developers.com/showthread.php?t=822756
Click to expand...
Click to collapse
Running JL2 + Speedmod + lagfix, phone is fine so far. BLN was causing the touch aspect of my screen to not work so i couldnt even unlock it. havent had a change to fool around with it though.
Been running Super Optimized Kernel instead of SpeedMod in my custom ROM, and I've noticed that its been much faster. Gonna stick with it for now.
I'm not sure what the source of the problem is, but WiFi is slower than 3g and doesn't maintain a stable connection even though I'm 50 feet from the router. I have Cog v3.04 and Firebird Kernal v2.05. I just installed the KP1 modem, but I had these issues before that. Any suggestions?
run a speedtest.net on your pc. Make sure your getting decent bandwidth.
do you have cable or DSL?
What speed?
also.
delete network
reboot router/modem
restart phone
re add network
&& possibly try changing wireless frequency on router, maybe there is a lot of interfearence or something.
I've had something similar with the latest Cognition release (cog kernel and modem as well). My Wifi connects and works for webpages but won't download apps from the market or other files. It uploads files to dropbox fine. Any help is appreciated. And I'm getting ready to flash the kernel to SpeedMod and use a i9000 modem to see if it's any better.
dont you have to run a radio thats consistent with the kernal/rom? i thought to run i9000 id need a rom/kernal based on the i9000 firmware...
I'm running Cog 3.04, SpeedMod K12r – 500hz (SpeedMod installed with Odin is the only installation that does not quickly drain battery for me), and JL3 modem. Everything is working great and fantastic battery life!
I'm also playing around with Cog 3.04 at the moment with this issue -- no wifi internet. No, it's not the router, there are multiple LANs around in my area and I was connecting and using them just fine on stock Froyo + Captivate Voodoo + JI6 modem. It's definitely something that came up after installing Cog.
I think the general rule of thumb says that you shouldn't mix and match, but so far, the JI6 and JJ4 modems have not given me any Wifi connection (the phone says it will connect, but no internet services work).
Meanwhile the JK4 modem for I9000 works, it will connect to LANs and let me browse to pages, although it's a little slow.
As of this typing I *just* tried out JL3, but the result is no good. I can load Google.com and nothing else.
I'm wary of trying the XXJP* modems due to changing bands (I'm no expert) but if nothing else works (or JK4 breaks) then it'll be on the table.
Is there anything else we can change aside from modems and kernels? I like how fast Cog is but if I can't get Wifi then I have to go back to stock Froyo.
Edit: Just tried out the Firebird 2 kernel. Wifi with the JI6 modem is back! Albeit slow. Battery life is also depleting VERY quickly. JJ4, JL3 still no good; JK4 works and is very fast, however internet only works with one wireless network, which happens to be unencrypted. Now going back to the original Cog 3.04 kernel, see if I can get any more data.
ive recently installed the cog 3.04 rom on mine.. currently deployed and can only use it with the wifi and so far, have not really noticed any issues.. i can download from the market and access the wifi's as needed.. only thing is sometimes it will disconnect when the phone locks, but when i unlock, it logs back on.. but that is about it for me.. so far loving it..still too new at the phone to really know much though
Ok, I think I may have found what I did wrong.
I used Titanium Backup to backup ALL of my system data from the leaked Froyo install, and restored it to the Cog install once it finished. I just re-flashed Cog to my phone (from leaked JI6 Froyo) WITHOUT restoring system data -- I only restored user apps and user app data this time. Tentatively, I seem to have Wifi working on all available LANs! Haven't changed a thing from the Cog install (using the modem that came with it, etc.) and all seems to be good.
Sad thing is, I think DG's page on Cog 3.04 specifically mentioned we shouldn't restore all system data after flashing. So for anyone else having Wifi troubles, you might want to make sure you didn't restore everything from your old ROM.
yeh.. i believe they changed it to do the restore missing apps and data instead of restore all apps and data... the video linked on their to show how to flash cog 3 has the guy telling you to restore all but once he made the video, he went in and put a splash on the screen for a correction to only do the missing apps + data and not restore all as it is known to cause issues
Actually, a correction on my part: Wifi's dead again. Seems to work for a few minutes at a time. Not sure what to do, going back to normal Froyo for a spell then...
I too am having issues with wifi on Cognition v3.04, I did not restore any data from my previous ROM.
I simply copied the rom (.zip) to my internal SD and used Clockwork rom manager to reboot and install from sd card. The wifi seems to be intermittent.
I will be following this thread to see if there is a fix.
Cognition 3.04 ROM and the firebird kernel
i would like 2 use this combo but i read they drain batt like crazy.
would like 2 know if anyone has found a combo that fixs this.
I have been running the cognition 3.04 rom for a few days, every thing works perfect with flash from stock 2.1. btw great rom i love it thanks for this rom.
Cognition 3.04 ROM stock kernel
hopeing for firebird read nothing but great things about it.
Edit: Nevermind, wifi eventually broke again.
This took several tries, but the procedure that finally let it work for about 12 hours follows.
I flashed back to JF6, used Odin to Master Clear, then installed ROM Manager from market. When flashing CWM, the phone went into 2e recovery of course, so I hit "reinstall packages" to flash CWM, but then it didn't update into CWM so I hit "reinstall packages" again, which gave me CWM recovery proper. Then reboot the phone, transfer the Cognition ZIP from computer to phone, then go into ROM Manager, and hit "Install ROM from SD Card".
I did NOT backup the stock JF6 rom, I DID wipe data and cache. Once the ROM was successfully flashed and rebooted, I checked Wifi -- nope, no good, wouldn't connect to any secured networks. It would connect and be able to use the one local unsecured network, but that was it. I went and retrieved a few Captivate-compatible kernels out of my computer:
Speedmod K12T
Firebird 2
supercurio's JJ4 Stock+Voodoo kernel
Rebooted into recovery, flashed over the Cog stock kernel WITHOUT converting the datasystem back to RFS (I left everything on EXT4 including /system), rebooted back into recovery, then wiped Dalvik cache and then wiped battery stats for good measure. Then rebooted normally.
Firebird did not give me the wifi result I wanted, I don't know why; Speedmod and supercurio's JJ4 Voodoo both fixed my wifi issue. Page loading is very snappy, the phone connects to and is able to use all the secured networks it sees and the only "issue" remaining is that it sucks up quite a bit of juice whenever it's connected to wifi. I don't know if this is the Cognition ROM or the JL1 modem causing it, but it's my only remaining quibble.
Click to expand...
Click to collapse
Now it's been a couple more hours and I am sad to report that the secured networks are once again unreachable on the JL1 modem, or any other that I have as far as I know. *Sigh* back to trying more things.
Edit 2: I have tried the "rm bcm_supp.conf" method of wiping wifi stats for a clean start, tried it on the stock Cog 3.04 kernel as well as the supercurio kernel. Doesn't fix the issue.
Edit 3: I dunno guys. I just did a fresh install again:
Flash back to JF6 Stock
Master Clear using Odin
One-click root
Move Cog 3.04 ZIP file to internal SD
Install ROM Manager
Flash CWM Recovery
"Reinstall packages"
"Reinstall packages"
In CWM recovery mode now, "install .zip from sdcard"
Choose the Cog 3.04 ZIP, install
Wipe Dalvik Cache, wipe battery stats
Boot
Click to expand...
Click to collapse
Now I can connect to all the unsecured networks and ONE secured network. I'm willing to write off the other secured network that I can't connect to because it wasn't compatible with the stock 2.1 Eclair ROM either (i.e. some protocol is probably in error). Nonetheless, the connection seems very fragile and I wouldn't be surprised if I rebooted and suddenly lost the capability to connect to that one secured network. *Shrug*
I've found a robust, working workaround!
I think that something about flashing kernels via Clockworkmod Recovery may be what's breaking wifi -- I have no idea why, but I flashed SpeedMod K13A via CWM and I couldn't connect to anything, then immediately afterwards flashed the same K13A, but via Odin, and absolutely everything works! The cause may be a particular version of CWM, it could be that the CWM and Odin versions of kernels are different, I don't know jack about the innards of software. But if you're having Wifi troubles try flashing a kernel via Odin, then flash (by whatever means, I still use CWM) a compatible modem, and see if it works.
Right now, I have Cog 3.04 running with SpeedMod K13A and the JL2 modem -- very robust and quick connection, data flows fairly quickly as well (10Mbps down/up). Have tried several different I9000 modems since then and they all work. JL2, KP1, JP5, JL3, JK4 are the ones I have in my "stash", every single one works so I've pretty much ruled out the modem question.
Hope you guys can also get your Wifi fixed! As a starting point I'd definitely try SpeedMod (via Odin) + JL2, the two of them work very well together and it gives me the best Wifi, GPS, voice quality, smoothness and battery life out of all the combos I've tried so far.
Thanks color0, I am going to try this right now. Flashed to Cog 3.04 yesterday and my Wifi has been sporadic at best.
EDIT: Well I flashed the K13A speed mod using ODIN and I still have issues with my Apple Time Machine Router. It connects fine but I receive no data (always worked great in the past). The connection to my other router seems to be working ok though, let's see if it lasts.
I could not install the JL2 modem as I am on a SGH-i897 and I understand that is a I9000 modem.
color0
Having same problems as you R.
Been pulling my hair out and flashing my ass off.
Only way I can get wifi to work is going back to stock.
Will try your work around and C if that helps
Thanks !
At work, we have 2 wifi networks : one is open, the other uses PEAP and MSCHAPV2 (?)
On my brand new (unflashed) Captivate I could connect to either one.
I flashed Cognition 3.04 and now I can connect to the open network, but not the PEAP secured one. There is an endless loop of scanning-> connecting -> disconnected, and the network appears as "disabled" after several attempts.
Unfortunately the open network has limitations, and requires a manual login.
I hope someone finds a fix, as I really like Cognition 3.04 so far.
I tried backdating the dhcpcd as mentioned in one of the developer threads, as well as re-booting, but that didn't help.
parabolee said:
I could not install the JL2 modem as I am on a SGH-i897 and I understand that is a I9000 modem.
Click to expand...
Click to collapse
Mine is also an SGH-I897. The SpeedMod K13A, however, is a I9000-based kernel, so you SHOULD actually use an I9000 modem to pair with it. JL2 is one of the best ones available, JK4 is also tried-and-proven, but drains battery. KP1 works very fast but voice quality drops.
JS22, Tzabka, yep, this is the exact same problem for all three of our Captivates. I can't guarantee there isn't something else that might break Wifi for you guys, but I can report what is working for me now. Best of luck! Once we at least have Wifi we can start working on other things like voice quality and battery life (currently trying out BVJJPD, I've heard some great things about its power consumption).
OH OK great. Could you point me in the right direction for installing the JL2 modem, never installed a modem before. Can I just use Odin3?
Thanks!!!
Hello great guru internet:
I have had few issues trying to flash CM7 for the first time and I spent a fair bit of time at it so I think that I did the right things.
OK I started with stock Froyo (JL2 Bell Canada) and then speedmod to get root again and recovery. I also tried EZ base and even EZ boot.
Regardless I seem to lose my IMEI settings (which I think I can restore but any tips on avoiding the need would be great - but I have back ups). Otherwise the install went fine and everything looked OK (via recovery - rom manager seems to have issues too that I have yet to look at and I am fine for the recovery approach). I mean if fine is 1/2 storage and no phone functions....
The bigger issue that I was trying to avoid is the lack of access to the external SD. I understand that it should be now in /mnt/emmc but how come when I open a file explorer it still shows an sd/external_sd (but no data) and no files in the mnt/emmc folder. The system settings also show the space of the existing data as used (ie not included in available space).
So I read that Froyo bootloaders are a must must must and I did did did but still cannot seem to get it. The JL2 firmware does have a .sbl in it as all the 19000m variants were dying and that was part of the fix so maybe that screws up the process? I tried another stock froyo rom but it would not boot. I could try eclair jh2 to EZ base but have not yet as apparently the body still needs sleep.
I have been on GB roms for the SGS (various) but I have been getting some errors with the file system (that is somehow relatedthe external SD - as have some other users in another q/a thread). I started this project on Darky 9.5.
Getting back to JL2 has been OK Thanks to Got_Milk on Cyanogen forums!!! if I had realized that the samfirmware was missing the DB_data for JL2 I would have saved about 1/2 the flashes I've done in the last week.
Any pointers - threads to review (or re review) - thoughts -suggestions - flaming etc?
Thanks
G
ok, hi fellow cappys... first i wanted to say that im started to learn more and more about all this (developments, modding, custom flashing, etc etc) which is cool, cuz ive gotten ballsier and flashed leaked roms (sometimes soft bricking my cappy and what not, but been able to fix the error with help from the forums), which leads me to my next train of thought...
ive just flashed [ROM] 2.3.5 Stock KJ2 with extended power menu.... (http://forum.xda-developers.com/showthread.php?t=1297223&page=1) and right off the bat have got to say that this rom is awesome! very fast, love the new looks, tweaks, etc, but have noticed that i am getting quite a bit of forced closes, and system freezes where the only thing that helps is taking he battery out, waiting a min or 2, and restarting the phone... wondering if anyone else has or is having this problem??? and if so, is there or will there be a workaround or fix for this?
second i just noticed that when i went in the settings, then about phone, my csc says UNKNOWN... what does that mean? is this bad? what should i do to fix?
third, my iternal sdcard space is almost gone, been through it with a fine tooth comb and cant figure out why there only like 300MB left for storage...
fourth, what bloatware can i safely remove from the stock 2.3.5 rom?
fifth, my settings for ringtone/notification/etc keep getting revert back to default after i reboot my phone... anyone else noticed this?
sixth, can someone please help me figure out how the naming of builds is done, am confused if kh3 is better/newer than kj1 or kj2, or jvr, etc? also, what does odexing mean and what is the benefit, as well as zipalign?
ok, think thats all it for now. thanks to everyone who posts replies on the forums for helping noobs like me, and to the devs for being so flippin incred for all their work in the creation of developments for all us cappys
p.s. was running uckb2 build 1106, and getting the sleep death issue.... since ive flashed the new rom i havent noticed that happening hardly at all... could this possibly be a fix, or is just temp? do/should i really send my cappy to samsung for fix or just deal with it...? thanks again!
1. When you upgraded, did you restore from a backup, and if so did you restore any system settings. Restoring apps is OK, restoring system data results in FCs. I would do clean install and then restore only your apps from backup (you can usually get away with restoring data from games, but never restore any system data).
2. CSC is Consumer Software Customization and has all of the carrier-specific software and settings. If your cell service, data, MMS, etc is all working, don't worry about it.
3. Are you referring to your application space or your mountable storage (where you would store music, pictures, etc)?
5. If you restored system data from backup, my guess is that is causing this problem as well. As with #1, I would start with a clean install.
6. As I understand it, if you treat the letters as if they were numbers (A < B < C), and then treat the whole version number as a 3 digit "number," you can figure out what is newer. KJ2 is newer than KJ1, but both are newer than KH3.
As far as deodex/zipalign goes, I have no first-hand experience but from what I understand deodexing moves all relevant data into the application .apk so it can be altered without messing up other programs. Zipaligning is a way of compressing the APKs so they can be read more efficiently.
I believe the sleep death issue was resolved after KB2 so it shouldn't be a fluke.
Good luck!
tjp419 said:
sixth, can someone please help me figure out how the naming of builds is done, am confused if kh3 is better/newer than kj1 or kj2, or jvr, etc?
Click to expand...
Click to collapse
apbthe3 said:
6. As I understand it, if you treat the letters as if they were numbers (A < B < C), and then treat the whole version number as a 3 digit "number," you can figure out what is newer. KJ2 is newer than KJ1, but both are newer than KH3.
Click to expand...
Click to collapse
Here's my understanding of the letter naming conventions (at least for I897 ROMs...I900 ROMs "JVx" still don't make sense to me except for saying A<B<C, etc). Don't remember where in the forums I saw it though:
1st letter: year of the build
2nd letter: month of the build
number: build# within that month
Ex: "KH3" = 3rd build in August 2011
"KJ2" = 2nd build in October 2011, etc
As I said, "JVR" & "JVT", etc from I9000 ROMs still doesn't make sense to me though...