Database Develop

[Q] Boot loop after ROM Install via CWM -w/VIDEO

Hi there!
Recently I've been trying to upgrade my SGS with a custom ROM, Darky's 4.0. After installing the ROM as instructed (using CWM and copying the ROM to the internal SD card), the ROM Installs, after the 1st boot it keeps looping, see video:
http://www.youtube.com/watch?v=kWrijyv-8PM (not edited, sorry for that)
Original SGS:
GT-I9000T
I9000TUBJG7
Product code: GT-I9000HKTPCW
kernel: 2.6.28
Build: eclair.ubjg5
The first upgrade I made was via Kies reg-hack to: GT-I9000HKDXEU, 'I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3, and it installed Stock Froyo update. The SGS worked fine with exception of the radio, which didn't lock my 3G over the 850 band.
Currently:
9000M running STOCK Australian I9000UGJG8 (due to radio issues, besides the Canadian ROM, this is pretty much the only ROM which modem.bin's works properly with my network, 3G 850MHz).
FW:2.1-update1
Kernel 2.3.29 [email protected] #2
Eclair.UGJG8
I tried with the following STOCK ROMs prior to the custom ROM install: I9000XWJM1, I9000XWJG5, I9000XWJM9 and I9000UGJH2.
I have ALLWAYS made an SD unmount and format, formatted the cache and factory reset. After it loops, the only way to get it back is using downloader mode and installing a STOCK ROM via ODIN (always do a .512 pit repartition)
Any suggestions to make this SGS get the ROM? maybe the kernel is bad?
Cheers!

Have u tried to format everything (exept for sd) and flash again?
Btw i love infected
Sent from my GT-I9000 using Tapatalk

Format everything? Using which app or program?
I've always used the recovery's wipe commands and the *2767*3855# command. Is that enough? or am I missing another cooler and invasive method ? A friend has suggested to use davlik.
Yeah! Infected rulz, that's what I listen when I'm in the bricking-mood lol

As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk

shrooms90 said:
As i saw you have cwm installed... Boot in recovery and select mount and storrage and then select eveeything that contains format (boot wont work to format) and dont select format internal sd but DO select format sd-ext
Edit: if it doesnt work write again then ill upload u the kernel that fixed it for me yesterday. Its from this forum but since ive discovered it by coinsidence, i cant remember how its called. U can format everything then select mout usb storrage (in cwm) and push it on the root of sd. Its an update.zip
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I gave that a shot, still no cigar. I guess that it goes deeper than just a formatting... maybe that secret kernel u have might brick me... erhm! I mean help me
Shoot! and I'll try it.... this OEM sucky ROM aint working that good over the Australian ROM lol. now I lost access to my cam ! sucks.
Thanx!

Try any universal lagfix kernel with clockwork enabled. Since ur phone is still flashable and ur phone still has funktionality (cwm works) im pretty hopefull that it is software/sd format related. Thats one of those cases where servic centre sais a full flash is needed by now only they are able to do that:-( but till now i always found a way to work around that by trying everything in every way. I always thought my phone is bricked anyhow so it can just get better and by coincidence it worked all of a sudden
Sent from my GT-I9000 using Tapatalk

Ihave I900T with same rom image
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!

zevrosenthal said:
and am trying to upgrade to FROYO as well. Any advice on how to do so would be appreciated. Tried the various registry hacks and none have worked. I'm happy to use Odin but not sure which is the correct ROM image to use (from samfirmware). Thanks!
Click to expand...
Click to collapse
Well, first thing is first. I've been a couple of weeks away from my SGS tweaking. I'm right know figuring a way to make a backup of my ROM (non-nandroid), in which I can extract the Kernel, Modem and CSC (I received a brand-new unit from my provider, so I will take advantage of it )
That way I can flash them back in case of a screw-up. I didn't have that much luck with modems offered in other ROMs, so I need to keep an OEM copy of my stuff.
Also make a good copy of your /efs folder in case you mess it up. It took me around 3 weeks of reading before I started making any changes to my phone, so I'll recommend doing the same; there's no "quick-start" or quickguide on how to start. You will en up with 6 different windows open reading from everywhere
The FWs from samfw are OEMs. Theres like "not much" of improvemente if you switch to those. Take special attention to the one you chose cause most likely you will lose your 3G and/or 850MHz band. I recommend using only Australian and Canadian ROMs(I9000UGJG8 and I9000UGJH2 worked for me, you might try also I9000UGJK3). Regarding custom ROMs, you will need to try and try until you get it right as our SGS model is not the most popular. This means endless flashing
Cheers.

Sgs froyo flash nam bands
Thanks for the advice. This project consumed my thanksgiving but I finally got a good working SGS in the ATT network. I bought an unlocked SGS from Negri Electronics with the USA 3G bands but it came without FROYO and didn't have the 3 button restore available. After reading and reading (your note about multiple open windows at the same time is all too true!) and trying and trying, I was finally able to get to download mode by installing all the Android SDK tools onto my PC then going in by way of ADB. Far more complicated than a simple registry hack and ODIN but it worked.
I installed the DOC BUJP8 v9 ROM with all the enhancements and AOSP Email (I tried and tried to get stock FROYO email to work with 2 exchange accounts but it was impossibly slow and didn't work) while AOSP is working fine.
It seems, because my SGS had the 850 bands to begin with, that it's working fine. I found this other post on XDA (#770041) that had some keycodes I was able to use (*#2263#) and confirm I still have the 850 band.
Needless to say, make a good backup and be prepared - as already warned - to flash several times and it was ultimately a "trial and error" process that worked.

does anyone have the original brazilian/latinamerican i9000T firmware? I flashed the SGS I got from Negri with spike speedy and it looks like I lost my 850 3G band.
I never did find out how to totally back up the SGS as in back up each PDA, PHONE, and CSC file so as to be able to truly factory default it.

[SOLVED] Help to choose rooting method and backup method

Got my phone (AT&T Captivate, firmware 2.1-update1 version JH7, kernel 2.6.29, build eclair.UCJH7) on december 28 from a AT&T store (it even came with a pic taken december 20 ) and I've already been able to boot into download mode (power off, hold volume keys then plug usb) and into that menu used to install packages (power off, hold volume keys then power on). Guess my hardware and firmware are ok, so I may be able to recover my phone by myself in case things go south.
I've been doing my homework lately (been reading stickys, tutorials and faqs for 10 days) but I'm still confused about some procedures. I'm not going to list everything I've read here, but I would like someone to correct me if I've learnt wrong. I don't really need the easiest methods, I want to understand the options available and to choose the best ones (aka the hardest path).
First of all, it seems I need to root my phone in order to be able to create backups, carrier-unlock it and flash custom roms. But it doesn't make much sense to me, since rooting it seem to be enough to prevent it from receiving FOTA updates - and I want to make the most comprehensive backup possible, in such a way I could restore my phone to 'factory condition' if needed.
Second, I realize there are many ways, programs and guides to root the phone - the most famous ones, One-Click root/unroot and z4root, seem to be listed in the wiki (http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897), but there is also CLShortFuse's One-Click Root and Allow Non-Market Apps, which sounds interesting but I don't know if it is undo-able. So there are different ways to root the phone, but there is little to none information on what's the difference between these methods, which is 'better' and what difference does it make if I root it permanently or by some reversible method. Does it affect performance? How each of them work? I have no clue.
The mess gets even greater when it comes to creating backups. People mention different programs to make these backups (clockwork recovery, titanium backup) but I don't understand if they back up different parts of the phone. Some even seem to change the bootloader of the phone - shouldn't it be backed up prior to any modification? Do I flash these backups using Odin? Which programs should I use to have a full backup? Is there anything left I should back up manually?
I'll quit talking for now because I've already written a lot and I still have many questions; if I write all of them at once, no one will ever have the patience to read them.

Erk, a long post deserves a long answer
So first off, il tell you about recovering your phone. Since you just got it, you can go back to the store and play dumb to get a new one in case anything goes wrong. You can also use the 3 button combos to get into download mode and use odins back to stock to get back to your original 2.1 eclair firmware . To do that you would need to get into download mode. Now there are a couple ways to do this, and i can only explain two since ive actually used two. (Well 3 actually, but il get to the third after these 2)
The first method is using the 3 button combo which you should already know. The second method is using adb commands such as (adb shell, adb reboot download, adb reboot recovery, adb devices). The third way is building a jig. Thats basically connecting 301k 1/4 watt worth of resistors together and placing them on pin 4 and 5 on your micro usb slot. You can read more about that on the tutorial on how to build a jig for your phone.
To restore to your factory setting, odin's one click back to stock thing should do the job. It simple installs the stock 2.1 eclair all over again (without the root).
To root your phone, any method from the wiki should work. None of them are really "better" :S, they all do the same job and give you super user permissions. None of them root your permanently since you can always go back to stock using Odin's... It does not really affect performance, not to any extent i have noticed :S, and unfortunately, i dont really know how it works.
As for creating backups, Titanium Backup is the best solution. Whether you have the few extra bucks to spend for the premium one or simply want to use the free one, its one of the best tools out there. I personally use it and its one of the best. It backs up all the data (except for my text messages). It creates a folder on your internal memory which you can just copy to your desktop. When the time comes that you need to restore your backup, just copy the folder back into your internal memory, load up titanium backup. Restore it and voila .
I think ive answered everything, if ive missed anything, let me know
Edit : Forgot to mention this . If your truly interested in customization. Custom roms are the best there is a howto in the themes and apps section on how to install it. It comes pre-rooted (if that is the word to use :S) and theyre much better than the stock firmware. Im currently using serendipity v3.0 (flashed it yesterday)

supaphreek, guess I'll have to thank you twice: once for reading my enormous post, and again for you supacompleteanswer.
I'm being paranoid with recovery because I actually bought the phone in the US then came back to my country (Brazil), so I'm a few thousand miles away from the simple lets-return-this-thing solution.
From everything I've read, I believe the most instructive were the wiki at http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897 , the FAQ at http://forum.xda-developers.com/showthread.php?t=858765 , the PDF guide from user nbs11 at http://forum.xda-developers.com/showthread.php?t=761819 and the wiki at http://www.capfaq.com/w/FAQ. These contain most of the info a newbie user would ever need and I'd definitely recommend them to any newbie user who happen to be reading this. And for everyone afraid of bricking, it's a tremendous relief to know pretty much any mess you do can be reverted using download mode and Odin, so the first thing to test is if you can get into download mode using one of the ways described by our buddy supaphreek.
On the rooting matter, I found no discussion at all about which is better, so they should be pretty similar (though I have no idea which is the oldest version, I'd assume the recent ones might be a little improved). There is some discussion on what's the better lagfix and many of the cooked ROMs already come with some lagfix installed, but this is another story...
Once I get my phone rooted, it seems to be trivial to carrier-unlock it. There's even an app on android market for this, so I won't even need sideloading. Since all this procedure does is just give me a number, there's hardly any difference among all the unlocking procedures out there.
For the backup, I'll still do it using both titanium and clockwork, as suggested by nbs11 on the pdf I've linked on this post. Better safe than sorry, right?
And yes, I'm truly interested in customization and I'll go deep down that path, I'm just packing up my head with some knowledge to avoid being desperate if things eventually go fubar.
As a last question, is there somewhere I can get 1-click Odin with my exact firmware version? (2.1-update1, I897UCJH7, Kernel 2.6.29 [email protected] #2, build eclair.ucjh7) And how important is it to get the exact same firmware?
As I've done my research, I found 1-click odin with JF6 here: http://forum.xda-developers.com/showthread.php?t=731989
I've also found the 'standalone' I897UCJH7 on this topic (where this guy even flashed succesfully his phone using old JH2 firmware without problems, so finding the exact firmware version might not be the greatest issue): http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but this process is a bit more complicated and uses regular Odin and clockwork recovery. Nonetheless, from what I've understood, I can still use any old version of odin to flash JF6 then use my own clockwork backup, right?

Hmm, unfortunately, im not sure if there is a specific Odin for that firmware :S. However what you can do is use one that reverts you to any stock version, and then flash the version you want through clockwork mod

I'll do that. Thanks again!

Also if you one click to stock, you can OTA update to the most recent firnware. I suggest titanium premium if you are going to flash a lot of custom roms, it is a lot faster to restore and also syncs with dropbox
Sent from my SAMSUNG-SGH-I897 using XDA App

Be careful trying to flash with odin. Some newer builds get instabrick flashing back to jf6 and must go with jh2 or newer.
So, you may want to invest a few bucks in a jig setup before blindly using odin.

Thanks for the tip, sixstringsg.
Newter55, as my phone is brand new I believe I may have one of these insta-brickable devices. If I happen to try flashing it with a recent rom, does it get recoverably bricked (fixed by flashing an older rom), or I'm left with a $500 paperweight?

You just need to use the correct firmware version of odin if you manage to get in trouble. Many people flash rom over rom, including myself, but it is highly likely that at some point you will need odin if you are flashing roms so it is best to ensure that you have that set up first. Look for the odin thread by c3popl (sp?) in development forum and you should find what you need. Read through that and look for others with your base firmware. Or look through q&a at the "help I bricked" threads . On my phone and posting links is a pita or I would make it easy for you.

If your phone came with JH7, follow this guide:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
If you use one of the Odin one-clicks and brick your phone, you'll need a USB jig to recover.

You guys are awesome. Thank you newter55 and GGXtreme for this info! I hope I'll never need it, but I'll buy a cable and make a jig.
The news: I've rooted my phone using One Click Root / Unroot by TGA_Gunnman (for the record: it worked with my JH7 Captivate bought in 28 dec). Once I booted windows, installed dotnet framework 4 and the samsung drivers (easy too, but a pita), rooting was easy and failproof. However, someone using linux might find it easier to just download 1-click root, find the root.zip file in there, rename it as update.zip, put the zip in the internal sdcard, boot the phone holding the volume buttons and then 'install packages'. This way there will be no need to fight Wine nor install anything nor look for a windows computer with admin privileges.
Also unlocked my phone using SGS Unlock Tool, available in the Android Market. The unrooted option won't work, but once rooted it worked like a champ. Next step: I'll do the backups, and then... start messing up my new toy!

First time using Android, please give some advices!

Hi all, in a couple of days time I will be receiving my first ever Android device, the Motorola Milestone. I've already done some research on the phone as well as on Android itself, and understood most of the necessary basics. However, there are still many things I don't understand quite yet, and would like some help with clarifying them.
My first question is regarding the custom roms. I myself have been a long time user of Windows Mobile so I know most of the stuff that is relevant to Android as well. From what I know, the bootloader on the Milestone is still locked, but people have found ways to load custom roms on it. Can someone link me to the guide on how to do this? Now before someone tell me to search on the forum or on Google (which I already have), I just want to point out that the ones I found seemed to be outdated, and that they're for older Android versions??
My 2nd question is, do custom roms like IceandFire or Froyomod come with their own custom kernels? Because I want to be able to overclock my phone, and if it comes installed with its own kernel then I don't want to risk bricking it by flashing another kernel on top of it......I hope that makes sense??
3rd question is, which rom is the best for speed and battery? I'm guessing it's IceandFire and it builds upon the latest CM7?
And lastly, are there any crucial apps that you guys recommend I should install, or any tweaks etc I should use?

chaoscreater said:
Hi all, in a couple of days time I will be receiving my first ever Android device, the Motorola Milestone. I've already done some research on the phone as well as on Android itself, and understood most of the necessary basics. However, there are still many things I don't understand quite yet, and would like some help with clarifying them.
My first question is regarding the custom roms. I myself have been a long time user of Windows Mobile so I know most of the stuff that is relevant to Android as well. From what I know, the bootloader on the Milestone is still locked, but people have found ways to load custom roms on it. Can someone link me to the guide on how to do this? Now before someone tell me to search on the forum or on Google (which I already have), I just want to point out that the ones I found seemed to be outdated, and that they're for older Android versions??
My 2nd question is, do custom roms like IceandFire or Froyomod come with their own custom kernels? Because I want to be able to overclock my phone, and if it comes installed with its own kernel then I don't want to risk bricking it by flashing another kernel on top of it......I hope that makes sense??
3rd question is, which rom is the best for speed and battery? I'm guessing it's IceandFire and it builds upon the latest CM7?
And lastly, are there any crucial apps that you guys recommend I should install, or any tweaks etc I should use?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=983516
This is still the best way to get a custom ROM loaded up onto your phone. What you want to start with is flashing the vulnerable recovery from http://android.doshaska.net/rootable by using RSD Lite. To do so, you need to put the phone into Bootloader mode (power+Dpad-up) You can google RSD Lite, make sure you use the latest version along with the latest USB Driver version from Motorola.
RSD Lite is a very finicky program, if you have any errors flashing, your best bet would be to try this post: http://androidforums.com/droid-all-...hing-process-0x7100-rsd-lite.html#post1274587
Once you flash the VR (vulnerable recovery), you will want to put OpenRecovery on your SD Card. I recommend using OR 1.46 and placing FuFu's minimod on the SD Card as well. It will overwrite existing files in OR (look for it in Milestone Development). From here you can root the phone in OR (by using power+x, then camera+volume up) and reboot, backup all data you want saved, before flashing a ROM.
Once that is done, get the custom ROM that you want (I find speed + battery can be Cronos, CM7 or FroyoMOD for a Froyo ROM) and place it in OpenRecovery/updates. You will also want the most up-to-date version of Google Apps for Cronos or any Gingerbread ROM (except MIUI).
Gapps: http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
Now, turn the phone off, and put it into recovery mode (power+x, then camera+volume up), select apply update.zip and you are now into OpenRecovery.
Here is where you will flash your custom ROM and Gapps. Wipe both cache partition and dalvik cache, then wipe all data. Select Apply Update under Miscellaneous Menu and select the ROM you want. Once it is done, wipe both caches (not data) and flash Gapps. Wipe caches again. Finally, change the baseband to your country and reboot.
The first reboot will take a while, as the ROM is configuring itself for first time use.
That is how to flash a custom ROM and get started.
2- Custom kernels are not available for Milestone, as our bootloader is locked. Overclocking the phone is done through the 10overclock file in system/etc/init.d . All ROMs that I know of are overclock, most to 1GHz (from 550MHz). You will not be able to flash any kernels, and DO NOT try ROM Manager, it will temporarily brick your phone.
Crucial apps, I would say are Root Explorer, TitaniumBackup. Those are the two that are very useful for root users, if you flash multiple ROMs or need to access system files.
Hope this helped.

awesome, thanks for the reply mate!
Hmm 2 things i'm confused with. Isn't there an app called "Milestone Overclock" that lets u overclock without installing custom kernels?
Also, from what I know you need to have the bootloader unlocked in order to install custom roms. I already know that Motorola is still keeping the bootloader locked and that as of now, there isn't a way to unlock it. Then how come we can install custom roms?
Also, since you mentioned ROM Manager, I did a quick search and it seems to be able to manage multiple custom rom installs that you have. But then you said don't try it or it will brick the phone, so I don't understand whether I can install it or not?? Personally, I love testing out different roms as well as new builds. It would be nice to dual boot or choose between different roms to use. But i'm not sure whether I want to go forward with this since your comment implies to me that I shouldn't install Rom Manager?
Lastly, this is the part I found most confusing with Android (or with Windows Mobile as well). I found some guides that tells you to install Clockwork Recovery Mod or something like that. Some of them even mentioned using Nandroid or something. There seems to be different methods & tools/softwares for different devices (or even the same device) and it can be confusing to keep up with them. My question is, are there major differences between them? Which one is better and should I keep them up to date?

chaoscreater said:
awesome, thanks for the reply mate!
Hmm 2 things i'm confused with. Isn't there an app called "Milestone Overclock" that lets u overclock without installing custom kernels?
Also, from what I know you need to have the bootloader unlocked in order to install custom roms. I already know that Motorola is still keeping the bootloader locked and that as of now, there isn't a way to unlock it. Then how come we can install custom roms?
Also, since you mentioned ROM Manager, I did a quick search and it seems to be able to manage multiple custom rom installs that you have. But then you said don't try it or it will brick the phone, so I don't understand whether I can install it or not?? Personally, I love testing out different roms as well as new builds. It would be nice to dual boot or choose between different roms to use. But i'm not sure whether I want to go forward with this since your comment implies to me that I shouldn't install Rom Manager?
Lastly, this is the part I found most confusing with Android (or with Windows Mobile as well). I found some guides that tells you to install Clockwork Recovery Mod or something like that. Some of them even mentioned using Nandroid or something. There seems to be different methods & tools/softwares for different devices (or even the same device) and it can be confusing to keep up with them. My question is, are there major differences between them? Which one is better and should I keep them up to date?
Click to expand...
Click to collapse
I have tried Milestone Overclock, but I never really used it to overclock the phone. I prefer changing the voltages and speeds with the 10overclock file. If you read the description of Milestone overclock, it "tricks" the kernel into thinking it's supposed to run at a certain speed.
ROM Manager and Clockwork Recovery Mod do not work on Milestone. The only recovery that works with the Milestone is OpenRecovery or Androidiani OpenRecovery. Unfortunately, the only way to flash the ROMs is through OR or AOR, so you will have to repeat the processes every single time. I have gotten used to where all of the options are for FuFu's Minimod, so I am able to do it quite efficiently
The best way to backup a ROM, system data and the such is by Nandroid backup. That is the only sort of backup that you can do. It is recommended to do one every time you flash a custom ROM, but I only did it after I rooted and before I flashed my first custom ROM. You can do it through OR. That is the only way that will work. CWM and ROM Manager will just temp brick the phone and you will have to reflash a stock SBF all over again.

i see.....in that case there's no way to install 2 different roms to allow dual booting then? What about the app "Boot Manager", will that work? I found it on this site here:
http://www.androidpolice.com/2011/0...ted-user-should-know-about-part-4-apps-26-33/
One last question, I came across this popular app that is recommended by many Android users, called Apps2SD. My understanding to this is that by default, any apps/games that you install on your device will install to the internal memory, and that this Apps2SD app basically lets you install to your memory card? So my question is, does this lag the phone somehow? I like to have many apps and especially games installed on my phone, would doing this affect the performance or something? I know this is the case for Windows Mobile, but not sure about Android.....

chaoscreater said:
i see.....in that case there's no way to install 2 different roms to allow dual booting then? What about the app "Boot Manager", will that work? I found it on this site here:
http://www.androidpolice.com/2011/0...ted-user-should-know-about-part-4-apps-26-33/
One last question, I came across this popular app that is recommended by many Android users, called Apps2SD. My understanding to this is that by default, any apps/games that you install on your device will install to the internal memory, and that this Apps2SD app basically lets you install to your memory card? So my question is, does this lag the phone somehow? I like to have many apps and especially games installed on my phone, would doing this affect the performance or something? I know this is the case for Windows Mobile, but not sure about Android.....
Click to expand...
Click to collapse
I follow AndroidPolice as well. I don't know about Boot Manager, I heard about it, but I haven't heard any reviews of it yet.
Two things when it comes to phone storage and apps on the Milestone: Old hardware makes for a lot of games to not work at all, and low phone storage space.
Almost every ROM comes with apps2ext support, which is a more advanced version of Apps2SD. You can follow this tutorial here: http://forum.xda-developers.com/showpost.php?p=10994672&postcount=226
Apps2ext will trick your phone into thinking space on the SD Card (the ext partition) is actually part of the phone's internal memory. You will be able to get a lot more apps on the phone this way.

Ahh cool, that saves me the trouble of me having to install an extra tweak.
Hmm I know Milestone is old, but not that old is it?? I don't know of any games now days that require heavy hardware specs or anything......i'm just hoping that emulators will work fine on it. I mean, my iPod Touch 3rd Gen only has about 120MB of free RAM, and the CPU is crap as hell and yet I could run GBA games like Pokemon or Golden Sun fine no problem (with sound of course). I'm hoping it'll at least work smoothly on the Milestone since I'll be attempting to overclock it to 1Ghz, which should run it significantly faster in theory.
BTW I found this great tweak for the CM7, here's the link:
http://chromloop.com/2011/07/how-to-make-cyanogenmod-7-for-milestone-a853-lighter-and-faster/
are there any ones similar to this? I'm a tweak junkie addict, I like to make my device run as smooth and as fast as possible. When I still had my HTC Touch Pro and Xperia X1, and even Nokia N900 (which uses Maemo 5), I tweaked the crap out of them and got more juice and power and made its performance so much better. I'm hoping I can at least do the same for the Milestone, except I couldn't seem to find many tweaks...
Oh lastly, I know one of the big problems with Android is fragmentation. There're already some apps out there in the Android market that are exclusive to certain Android versions. The same app has a version for Froyo (v2.2) and Gingerbread (v2.3). This is true for some of the mods or tweaks on XDA. So my question is, are custom roms like CM7 using Gingerbread? I'm guessing yes since it says 2.3.5? In that case, would I be able to simply install the latest mod/tweak or apps/games from XDA or the Android market? Or must I find the versions that is identical to mine?
E.g. if I install CM7, can I still install a mod that is for Froyo?

chaoscreater said:
Ahh cool, that saves me the trouble of me having to install an extra tweak.
Hmm I know Milestone is old, but not that old is it?? I don't know of any games now days that require heavy hardware specs or anything......i'm just hoping that emulators will work fine on it. I mean, my iPod Touch 3rd Gen only has about 120MB of free RAM, and the CPU is crap as hell and yet I could run GBA games like Pokemon or Golden Sun fine no problem (with sound of course). I'm hoping it'll at least work smoothly on the Milestone since I'll be attempting to overclock it to 1Ghz, which should run it significantly faster in theory.
BTW I found this great tweak for the CM7, here's the link:
http://chromloop.com/2011/07/how-to-make-cyanogenmod-7-for-milestone-a853-lighter-and-faster/
are there any ones similar to this? I'm a tweak junkie addict, I like to make my device run as smooth and as fast as possible. When I still had my HTC Touch Pro and Xperia X1, and even Nokia N900 (which uses Maemo 5), I tweaked the crap out of them and got more juice and power and made its performance so much better. I'm hoping I can at least do the same for the Milestone, except I couldn't seem to find many tweaks...
Oh lastly, I know one of the big problems with Android is fragmentation. There're already some apps out there in the Android market that are exclusive to certain Android versions. The same app has a version for Froyo (v2.2) and Gingerbread (v2.3). This is true for some of the mods or tweaks on XDA. So my question is, are custom roms like CM7 using Gingerbread? I'm guessing yes since it says 2.3.5? In that case, would I be able to simply install the latest mod/tweak or apps/games from XDA or the Android market? Or must I find the versions that is identical to mine?
E.g. if I install CM7, can I still install a mod that is for Froyo?
Click to expand...
Click to collapse
Of course you still can. The best tweak for Milestone is under Android Hacking, it's zeppelinrox's supercharger script, which you run through Script Manager. That's the best you can get.
Sent from my Milestone using XDA Premium App

I thought custom roms like CM7 or IceandFire come with the supercharger script included?

chaoscreater said:
I thought custom roms like CM7 or IceandFire come with the supercharger script included?
Click to expand...
Click to collapse
Some do, such as HO!NO!, but not all of them do.
Sent from my Milestone using XDA Premium App

Ok so I finally got my Milestone today!
I'm about to start rooting it and install CM7 on it. But before I do that, I have one important question. I know for Windows Mobile, almost all of the device requires you to do a hard reset after flashing a custom rom. I was wondering if the same needs to be applied to Android custom roms? Because it doesn't seem like it, I did a quick Google search and found this:
http://androidforums.com/optimus-v-...4-do-not-factory-reset-your-rooted-phone.html
So ya I'm not sure....
UPDATE:
Ok so I got my Milestone rooted, and installed CM7 on it. I came across a weird problem while doing it though. First of all, I'm using a 8GB Kingston microSD class 2, and it's brand new and hasn't been used before, so it obviously has nothing stored on it as it's empty to begin with. Ok, so as I followed the instructions, the first step is obviously rooting the Milestone, so I simply copied OpenRecovery to the memory card while my Milestone was connected to my PC. The weird thing is, when I opened "My Computer", I didn't see my memory card. Instead, I see "Milestone", so I opened it and then I see my memory card "Removeable Storage". I opened it again and here's the actual weird part, there're 2 files stored in it, called:
DevIcon
DevLogo
At first, I didn't think it was a problem because I thought they were just some dummy file or something. Also, the memory card is empty other than those 2 files. So after copying OpenRecovery to it and rooting it successfully, I then proceed to copy the CM7 custom rom file to the memory card. But this time, I still see the same thing. I don't see my OpenRecovery folder on it at all, there're no other files other than those 2 files on it. I tried Unmount and Mount in the SD Card settings, also unplugging my USB cable and re-plugging back in but it's the same. In fact, after 'Unmounting' the memory card, I couldn't even access it on "My Computer", as nothing shows up after I open "Milestone". Only 'Mounting' works, but again I only see those 2 files and nothing else.
HOWEVER, I then tried to take out the memory card and use my own microSD card reader, and bam I can see all the files on it, such as OpenRecovery and even the nanDroid backup that I made while following the instructions on that guide. So this is weird, why can't I access or see the contents on my memory card while the phone is connected to the PC??

I don't wanna create another topic for this since it's unnecessary, so here's my final question. In case something goes wrong in the future, what's the best way for me to revert back to stock?
I know I can use nandroid for this, but here's what i'm confused about. Nandroid makes a backup of the complete system, including the settings and apps installed correct? But what if you flash a custom rom, and then use a nandroid backup of the stock rom, will that still work? Or would you have to install the stock rom first for you to be able to use the nandroid backup?
Lastly, if the nandroid backup works regardless of whether you're using a different rom than the rom that the nandroid backup was made, then which option is better:
use nandroid to revert to stock, or using this guide here:
http://forum.xda-developers.com/showpost.php?p=11902513&postcount=7
Now I understand that for Milestone, custom roms are not actually flashed since the bootloader is locked. So would using nandroid be good enough?

chaoscreater said:
I don't wanna create another topic for this since it's unnecessary, so here's my final question. In case something goes wrong in the future, what's the best way for me to revert back to stock?
I know I can use nandroid for this, but here's what i'm confused about. Nandroid makes a backup of the complete system, including the settings and apps installed correct? But what if you flash a custom rom, and then use a nandroid backup of the stock rom, will that still work? Or would you have to install the stock rom first for you to be able to use the nandroid backup?
Lastly, if the nandroid backup works regardless of whether you're using a different rom than the rom that the nandroid backup was made, then which option is better:
use nandroid to revert to stock, or using this guide here:
http://forum.xda-developers.com/showpost.php?p=11902513&postcount=7
Now I understand that for Milestone, custom roms are not actually flashed since the bootloader is locked. So would using nandroid be good enough?
Click to expand...
Click to collapse
The best way to revert to stock will be to flash an sbf for your region that will wipe everything. They have those sbf's on and-developers.
Sent from my Milestone using XDA Premium App

Ahh I see, so in what situations will we be using nandroid to restore from the backup?
Also, the SBF file i'm using is from the guide that you linked me in your 2nd post. I'm using the EUROPE one because apparently it covers most of the countries around Europe, which includes New Zealand (where I live). I've had no problems with it, but just then I checked out the AND-Developers site like you suggested, and found this here:
http://and-developers.com/sbf:milestone221
It doesn't seem to have New Zealand but it does have Australia, which is like a neighbour to us. Will it be better if I flash the SBF to that instead?
Also, will flashing a SBF change the radio? Or does only changing the baseband change the radio? Because i'm getting weak signals from 2G/3G sometimes, and my Wifi has problems sometimes not being able to connect properly. Either that, or it shows that i'm connected but i'm not getting any data, apparently a lot of people have problems like this after I did some searching around.

chaoscreater said:
Ahh I see, so in what situations will we be using nandroid to restore from the backup?
Also, the SBF file i'm using is from the guide that you linked me in your 2nd post. I'm using the EUROPE one because apparently it covers most of the countries around Europe, which includes New Zealand (where I live). I've had no problems with it, but just then I checked out the AND-Developers site like you suggested, and found this here:
http://and-developers.com/sbf:milestone221
It doesn't seem to have New Zealand but it does have Australia, which is like a neighbour to us. Will it be better if I flash the SBF to that instead?
Also, will flashing a SBF change the radio? Or does only changing the baseband change the radio? Because i'm getting weak signals from 2G/3G sometimes, and my Wifi has problems sometimes not being able to connect properly. Either that, or it shows that i'm connected but i'm not getting any data, apparently a lot of people have problems like this after I did some searching around.
Click to expand...
Click to collapse
1. when you're phone will not start anymore, it's good to have one before every new flash cause you never now what's gonna happen.
2. funny thing is i know where New Zealand is (not near Europe) . about the baseband ... yes every sbf has the region specific baseband 's (you cant flash a radio only change baseband 's).
baseband can be found on dexter's (http://dext3r.komodin.org/) page but they are already included in OR (not sure about fufu's). i can't be very precise because i don't remember.
custom rom's don't think they change baseband 's, (the .zip ones)

Ya ur right, NZ is not anywhere near Europe lol
but I did do some research on which SBF I needed before I flashed it, and I found out that the Europe SBF works for NZ as well, it was mentioned somewhere I can't remember.
About the baseband, I'm still a little bit confused. First off, I already know that you can change the baseband under OpenRecovery. The thing is, there are no options to change the baseband to New Zealand, so which one should I pick? Also, here's the part I'm confused about. You said that the baseband are region specific, and yet we can choose the baseband we want in OpenRecovery.
So since I flashed the SBF for Europe, what will happen if I then change the baseband to say Argentina (one of the options under OpenRecovery)? Will it crash or something?? I don't even know what baseband i'm using right now, I haven't changed anything, I only flashed the SBF for Europe and that's it. I can still go online using 2G/3G and txt no problem, but I'm just not sure if the baseband i'm using is suppose to be correct for New Zealand or not...
BTW just another side question (sorry I'm really new to the Android scene!):
I've found a few custom roms that doesn't use the current kernel we have for Milestone. As far as I know, the bootloader for Milestone is locked, therefore we can't properly flash a custom rom onto it, as well as replacing the kernel as well. So what I'm confused with is, if some of these custom roms don't use the current kernel on the system, then how does it work? Does it use its own kernel, and if so then shouldn't that replace the system's own kernel before it can be used??
Here's one of the custom rom topic where I read from, in case ur wondering:
This is the Froyo FRG22 image for our Milestone. but as this is not using the kernel, there are some limit to functions based on kernel requirement. But its close, and works great and is alot faster.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=734802
The same goes for the custom roms. I don't understand how they can run on Milestone even though it's not properly flashed. Like some others have mentioned, the so-called "custom roms" that we have now are just a layer of image or skin on top of the stock rom. The weird thing is, it runs faster and most of the pre-installed stock apps that came with the stock rom are removed, thus giving us more space for internal storage. But how does this work if the custom roms haven't actually flashed onto our phone? Or did it overwrite/modify the files on the stock rom? If so, then isn't that just flashing onto the phone then?

chaoscreater said:
About the baseband
Click to expand...
Click to collapse
changing baseband's that are not supported by your network op will lead to no signal whatsoever.. i don't remember if there is a problem with only data. try other baseband, in theory it will not crash anything, so do a nandroid backup before
http://forum.xda-developers.com/showthread.php?t=734802
Click to expand...
Click to collapse
that is an old post from "25th July 2010, 05:52 AM" moto started to leak kernel from January 2011 give or take a month, so back then froyo was used with the eclair kernel. kernel from milestone was never changed to other than moto signed, only modules loaded at an early stage, thanks to kabaldan/nadlabak and other if exists
custom roms =
moto kernel
kernel modules (this helps on overclock , app2ext ... others)
mods to system files, apps
hope you understand cause i don't know if i make it clear at the end of the post
edit:
The same goes for the custom roms. I don't understand how they can run on Milestone even though it's not properly flashed. Like some others have mentioned, the so-called "custom roms" that we have now are just a layer of image or skin on top of the stock rom. The weird thing is, it runs faster and most of the pre-installed stock apps that came with the stock rom are removed, thus giving us more space for internal storage. But how does this work if the custom roms haven't actually flashed onto our phone? Or did it overwrite/modify the files on the stock rom? If so, then isn't that just flashing onto the phone then?
Click to expand...
Click to collapse
i doesn't make any sense, you will end up with no memory , only kernel remains, other things gets rewritten.
Code:
http://www.vodafone.co.nz/roaming/welcome-to-nz.jsp
this get out of what i know. with the frequencies,
basebands/frequency i have 900/1800
for data check if there is a problem with your apn settings

I see, thanks for your thorough explanation
Ya I know that changing my baseband will probably give me better signals, but I'm asking which one is best for Vodafone NZ because there isn't a baseband for New Zealand.
For the data part, were you talking about my wifi problem, and suggesting I check the APN settings? Don't worry that's been solved already. I flashed to the New Zealand v2.1 SBF and now it's working very stable. But like I said, after flashing to that I now have problems with connecting to my operator whenever I switch to 2G. However, 3G works fine so there's no problem with that.
BTW, I have another problem. After flashing to the New Zealand v2.1 SBF, I couldn't access my OpenRecovery anymore. I didn't delete or change any files on my memory card, so if I could access OpenRecovery and root my device as well as flash a custom rom when I was still on Froyo, then why can't I do it again when I flash to Eclair?
I *think* I know the reason, is it because it patched the vulnerable recovery or something? I think this is what I need to do to fix this:
http://android.doshaska.net/rootable
I haven't done it yet coz i'm busy these days, but i just need a confirmation so I know that it is indeed the case.

I *think* I know the reason, is it because it patched the vulnerable recovery or something? I think this is what I need to do to fix this:
http://android.doshaska.net/rootable
I haven't done it yet coz i'm busy these days, but i just need a confirmatio
Click to expand...
Click to collapse
true story . it should say something about eocd marker and fail.
http://forum.xda-developers.com/showthread.php?t=698059
For the data part, were you talking about my wifi problem, and suggesting I check the APN settings?
Click to expand...
Click to collapse
sorry... i don't know, last night i thought i read something else, about working 3g and 2g not ..must be the skittles... to much rainbow
i suggest finding out what country baseband are similar to New Zealand and flash/apply that one )

Few Galaxy S questions

Hello
I own a French Galaxy S for more than a year, it's an unlocked unbranded one bought in Pixmania
Model number is I9000 and PCode is GT-I9000HKYXEF
Installed firmware is 2.3.3 updated officially by Kies one year ago
PDA: I9000XWJVH
PHONE: I9000XXJVO
CSC: I9000XEFJV2
It seems to be the latest version released for my phone in France (CSC XEF)
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do

You could use this guide for rooting your phone:
http://www.theandroidsoul.com/fuguroot-galaxy-s-how-to/

Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.

albertocastillo2001 said:
Hello
Thank you, however, there are lots of rooting guides out there and that's not my question exactly. My question is how doesit work internally and what does it do to the phone. Just to clearly know what I am doing to my phone at all.
Click to expand...
Click to collapse
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app

AlwaysDroid said:
I'll answer your whole load of questions tonight when I'm back from work.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Thank you.

why donn't you upgrade it to 2.3.6
for root use cf root kernel or semaphore kernel

I cant post in this thread for some reason. Ill try later

albertocastillo2001 said:
I am going to split this post in two cause there is alot...
I have been checking samkiesupdates twitter page often but there hasn't been any update coming out which updates my phone to 2.3.4, 2.3.5 or 2.3.6 while other updates based in CSC OXA and DBT have already received the update (Seems OXA is the Open Europe version)
- Being upgraded to 2.3.6 or whatever isnt really that great. A few changes were made, but really not much. Like some sgs devices have 2.3.4, mine came with 2.3.3 and you really cant tell the difference. here is a complete list of the changes if you want.
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
What does rooting do exactly?, I know this is something like on UNIX systems where you need a super user account such as root to access system folders, but I only find threads about how to root the phone, but not what does it do exactly and what does it modify. However it seems, from what I read, that it is possible to return to stock (could Samsung Service Centers detect this modification?)
-I am to lazy to type how it works so go here. I learned off of that website. As for the other part, You can return to stock and never have samsung notice because we dont have a flash counter.
Click to expand...
Click to collapse
There you go. /Part 1
---------- Post added at 04:15 PM ---------- Previous post was at 04:01 PM ----------
albertocastillo2001 said:
According to what I read, in case I flashed my phone with a custom ROM I would have to root my phone, why is this exactly needed? Why do stock ROMS seem to not need root at all?
-Technically all roms use root. The difference here is that what you are referring to is the user having root acess. And of course Samsung doesnt really want uneducated people messing with the phones software, so it is locked away from the user. But the system still has to use it. But you do not have to have a custom rom rooted, but fact is that almost all are. For example I tried out a new jellybean port early on and it had no root access. The only thing in this case is that you must flash anything via odin instead of CWM.
Custom roms seem to already have different bootloaders. Is it possible to revert everything back to stock (including ROM and bootloader) just like if the phone was untouched in a way Samsung Service Centers could detect?
- I dont know where you heard this, but the bootloaders so not change on flashing a custom rom. Anyway, when you flash back to stock with odin, EVERYTHING goes. It will be 100% stock, not a single trace of you being rooted, having kernel and recoverys installed etc. Totally new.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
The PIT files, I know these are like partition size limits. Is there any advantage of using one or another?
- Indeed, they tell odin how to partition your device. There is no advantage to either or. Read here.
I think this is enough for now. I have been having trouble finding information about these and it seems that all Samsung Galaxy S phones, even if they are the same model, won't receive the same updates for different countries/carriers. I bought an unbranded phone, and I should receive the same updates as other countries like UK do
- Indeed each country seems to recieve a different version for some reason.
Click to expand...
Click to collapse
Part two. Hope that helped!

Hello
Thank you very much.
I'm at work but I will read it again when I get home. It really helped, the rooting technical guide was pretty clear, and the PIT file information as well.
About the other questions:
With this 2.3.3 version I'm having a few problems, such as a faulty GPS and a lack of free RAM. The gps problem doesn't seem to be a hardware problem (like the one with the GPS antenna in a few models) and I checked signals with GPS Test and it seems to be catching more or less the same number of satellites around the same signal level as other phones that have a working GPS.
-There is nothing that you can do about your ram issue other than get a new rom or kernel that handles ram better and uses less of it. As for GPS, i know nothing about that sorry.
Click to expand...
Click to collapse
It's ok, the GPS is driving me nuts
So I would like to know a few things about rooting and flashing ROMs. I have thought of updating my phone to the 2.3.6 CSC OXA version
When flashing a phone, are protected phone contents affected like the /efs and folders that can only be accessed when rooting the phone?
- Folders like your /efs /data and /cache should never be touched. Only the system and kernel files are replaced. It is possible for /efs to go corrupted during a flash, HIGHLY unlikely using Odin though. But once your rooted, do a backup of the folder and keep it in many places.
Click to expand...
Click to collapse
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
In case I flashed OXA 2.3.6, will Kies download new updates released for that version even if the PCode is XEF?
- What sorry? I dont understand
Click to expand...
Click to collapse
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
Few more questions
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
What's the [Dump] option in Odin? Haven't seen that anywhere
I have to read some more info about the bootloaders first before being able to ask more.
Thanks

albertocastillo2001 said:
That's pretty interesting, I've seen options as Clear EFS in Odin that seem to be pretty dangerous at all since the EFS seems to contain specific phone data such as the IMEI
-I very much so agree, i dont know why you would want to use that. But Odin is the official samsung flash tool, so i bet that samsung uses it in their repair centers for something.
I understand these are partitions and not just folders. I remember getting into the recovery on my Galaxy S and formatting the cache partition. Does this cause any trouble at all?
-Yes they are separate partitions
- This is not bad at all. Usually before i do nandroids in will do a /cache clear to make it smaller. I think it might actually be beneficial to clear it once and a while anyway. Sometimes i just clear it. Your phone will boot fine. Keep in mind that clearing cache does not clear the dalvik cache, as this is kept on /data and has to be cleared from the advanced menu. Also a word of caution, i wouldnt clear the dalvik while your phone is on, everything will force close. So just do it from recovery
/data partitions holds all the settings in the phone (according to the rooting guide formatting this partition causes a factory reset)
I will keep looking info on the forums for this to understand the details of these folders more in detail.
-What more details so you want? and yes whenever you perform a factory reset, the dalvik cache, /cache and /data partitions are cleared. But just wiping /data will be the same, but the cached reminants will still be there, which isnt an issue, its just wasted, thats all.
Well. I am not sure how Kies works but I remember reading that it only tries to apply updates if the PCode matches with the CSC of the ROM
In my case my PCode is GT-I9000HKYXEF and my ROM's CSC is XEF
If I flash the Open Europe 2.3.6 ROM, my CSC will be OXA, and in future updates Kies might report that it cannot update my device as I've read on some forums because my PCode doesn't match the ROM's CSC anymore.
All could be fixed by reinstalling the 2.3.3 XEF ROM image as well tho.
-Ah i get it, and yes you are correct. Even though there will never be another update for your device.
PIT repartitioning, does this only affects /dbdata and /system. Correct? No risk of messing up with /efs (as it seems to be the most critical partition in the device, is it?)
-Yes, i believe that the 10mb is transfered between the two. But when you install cyanogenmod 9, it gets rid of /dbdata. There should NEVER EVER EVER be a risk of messing with /efs. It is a rare occasion for it to go corrupt. Possible though, so do your backups.
- As for being the most important partition, it is hard to say. Your phone will boot with no /efs, it will just lag like hell, have no service or imei. Kinda hard to explain that one to the repair center since nothing touches that partition, ever.
I am taking a look at Cyanogen's MOD 7.2 for Galaxy S
On their install instructions they ask you to download a kernel and clockwork mod recovery and then Heimdall
Where is the kernel stored after installing it? /system?
If so, just reflashing a new ROM (or the stock ROM again would get back to the official kernel, correct?
-I believe that the kernel parts are mainly stores in /sys, although there are pieces in other places as well. (ex: /data/local/devil for devil kernel settings)
-Also, unlike my old galaxy gio, the recovery is packaged with the kernel on galaxy s. So changing the kernel replaces the recovery as well. You cant do it individually.
-Yes, all aftermarket and stock roms come packaged with a kernel. For example, i use devil kernel with my cm9. But when i flash a new version of cm9, it replaces the kernel and i have to flash devil kernel again.
What's the [Dump] option in Odin? Haven't seen that anywhere
-DONT take my word on this, i am not 100 sure. But i think dump, performs a dump of all the partitions to your computer. Not sure, so i dont advise trying it without research.
I have to read some more info about the bootloaders first before being able to ask more.
-Okay, let me know!
Thanks
Click to expand...
Click to collapse
.......

Hello
Thanks again
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
I guess these are all the questions I need to ask to cover all doubts.
Thanks!

albertocastillo2001 said:
I guess ROMs like CM9 (this seems to be the one I am interested on) don't mess with PBL like boot.bin or the secondary bootloaders right? Or do they? (Only ClockWork Mod modifies the SBL to install it's own recovery I guess?)
-Nothing unless otherwise stated messes with the bootloaders on most devices. But our bootloaders are unlocked, meaning the partitions arent signed and the bootloader doesnt check for sigantures, so it doesnt care if we have a custom recovery. When we use the three button combo, all it does is trigger the bootloader to boot into the recovery partition. But since they arent locked (bootloaders) and partitions arent signed the bootloader doesnt care whats there. Itll boot whatever is there. So no mods needed for custom recovery.
********NOTHING MESSES WITH BOOTLOADERS UNLESS OTHERWISE STATED ***********
Are all the needed folders on the stock ROMs as well? Like boot.bin, the secondary bootloaders and all the folders such as /dbdata /cache /data /dev /etc /lib /mnt and all these folders that are typical to see on UNIX and Linux installs?
- Yes everything you need to go **********100000000000000000000000000000000000000000000000000000% back to stock ************ is in there, even bootloaders. The primary bootloader isnt, cause nothing will ever touch it.
As seen in here: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Partitions it seems they contain the PBL, SBL and folders like /mnt. So I guess they have everything on them ready to go
It's just to know which folders to backup in case it's needed.
-The only thing you should backup is /efs
Does ticking repartition with a PIT file in Heimdall or Odin repartition the whole device in a way where important files/folders get deleted (/efs for example) or does it just repartition /dbdata and /system without touching anything else on the device?
-Odin only will repartition /data /cache /dbdata and /system back. Removing things like /datadata in the process.
****************NOTHING EVER EVER EVER MESSES WITH YOUR EFS> EVER****************************
Except unlock attempts
Does installing ROMs from Odin or Heimdall format the partitions before installing them? Seems CyanogenMod 9 has a script to turn partitions from RFS format to EXT4
What if I wanted to get back to stock, would Odin format them in RFS format as well?
-This is a question i wish someone had answered for me when i was new here. Odin wont format the /data and /cache and dbdata(i think?) when flashing back to stock, so if you try to boot, you will bootloop. Only the stock recovery can format to rfs and knows how to handle it, so you must do a factory reset to format the rest of the partitions back to RFS.
Click to expand...
Click to collapse
Hope that helps you out

Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added

Samsung stopped genuinely supporting this phone quite a while ago. The burden of updating the device has fallen onto the development community. Given that the I9000 is one of the most popular Android phones, LOTS of development has taken place since then.
The kernel on this device is part of the boot image, on its own partition. Recovery is coupled to that partition.
Rooting a device adds a new binary (su) to the system partition. This file is given permission to run as user 0 (root) and acts as a proxy for other processes to perform privileged actions (deleting system files, mounting partitions, accessing all data, etc).
Most custom ROMs come pre rooted since rooting is quite popular. Titanium Backup is the exemplar for what an application can use root privilege for.
Installing a custom ROM does not require the stock ROM to be rooted, it requires a custom kernel (with a cwm or twrp based recovery).
Most high quality custom ROMs (read CyanogenMod) have scripts to protect the efs partition while flashing.
As long as you can get into download mode on your phone you can always get back to stock firmware. The service centre won't know the difference.
The bootloaders are provided by Samsung, these are not replaced by custom ROMs.
Personally I run a modified build of CM10 and use a radio from the Nexus S (KJ1). I'm very happy with the overall battery life of my phone, signal quality is good in Australia (can't say with certainty for any other part of the world) and performance is quite snappy.
Sent from my Nexus 7 using Tapatalk 2

albertocastillo2001 said:
Hello
Thanks again for your infinite knowledge
I think that's all. Anything else you suggest or something I should read? WIki is pretty good, but I think it's far from complete and more could be added
Click to expand...
Click to collapse
Jus read things that come up in the questions/answers forum. Learn from other peoples mistakes
Sent from my GT-I9000 using xda app-developers app

Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs

albertocastillo2001 said:
Thanks all of you
One more question
What is baseband exactly? Is it related to modem/phone firmware?
I see it's never changed or replaced by installing custom ROMs
Click to expand...
Click to collapse
Baseband/modem (samething,)is the little piece of software that talks to the cellphone towers. And because each area uses a different frequency, there are many different ones.
Also good to note that it is not ATS all related to GPS or WiFi.
Sent from my GT-I9000 using xda app-developers app

[Q] N7000 emmc bricked can now only run GB

Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers

You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app

ttibbetts83 said:
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks ttibbetts83, I will try that and see how i go

Thanks Arobase40.
I'll get a strong coffee and read your reply from top to bottom and then plan my next move.
The repair was done by people unrelated to Samsung.
I currently have GB v2.3.5, (SGN_XX_OXA_KJ1_FACTORYFS) which works well, it would seem.
I'd love to get ICS back on it but need to gather info (such as that from yourself) before I do anything.
A bit more info on the state of the emmc storage: Using 'adb shell' and executing the command DD did in fact find bad blocks in partitions 9-11 (can't recall right now exactly which ones), so there are issues there.
The partition that is in place now, __appears__ to have successfully skipped those bad blocks.
And on something slightly tangential to the current topic, I know that doing a 'WIPE DATA' from the recovery menu zaps emmc, but does that also happen when you do a factory reset from within Android? From memory, when doing so, it seems to go into recovery mode and do it, so I'd expect that it'd also damage emmc.
Cheers

arobase said:
As opposed to all alarmist and contradictory posts about eMMC bug on stock Samsung ROM : GB or ICS, I never got any issues with this so called eMMC bug and never got bricked G-Note as long as I kept at using the stock kernel, nevertheless I made various and numerous wipe whichever the ways (from recovery or the settings)...
For rooting, I always used the temporary Touch CWM to flash (which has been may be removed from XDA, I guess as it was supposed to cause bricked devices) anything : superuser, busybox, and other custom ROM... ^^
BUT when I flash a custom ROM, I always removed the custom kernel (so called "safe"), and replace it for a stock kernel and never got issues with it.
The first and last time I flashed a custom with custom kernel I got my G-Note bricked (just forgot the replace the custom kernel for a stock one... ^^) !!!
So, if you want to flash an ICS version, get one from Sammobile, and flash it with PC Odin !
You shouldn't have any problem with them !!!
Get all root and busybox files from dr Ketan, and if you can find it again use the temporary Touch CWM which has NO kernel inside : it WORKS quite fine !!!
Click to expand...
Click to collapse
Unfortunately there are no high trees on XDA beause you should look for one before typing this utter personal nonsense that could brick anybody's Gnote.
Taking your own convictions for thruth is one thing, sending innocent ppl into the jungle is another...
What you are saying is: If there is a lightning storm, just go into an open field en enjoy. I cannot say it is 100% safe, but I never got struck....I think they removed the tree i used to seek shelter from the rain, but if you search real hard you might find it anyway.
---------- Post added at 10:33 AM ---------- Previous post was at 10:17 AM ----------
amanmasgaman said:
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
Click to expand...
Click to collapse
Actually you should be happy that they revived your Note after brick even if it's only running GB for now.
However if you are a brave person you can do the same trick on ICS.
Just read and understand the thread that is a guide on doing so.
You can root your GB without a problem, but there is no obligation for it to install ICS with odin.
However what you do need is the following (besides a lot of patience and courage) :
1. get the ICS files you want to flash including the pit file.
2. get a program called PIT MAGIC to recreate a suitable pit file
3. determine where your bad blocks are located
4. Load the pit file into the magic program and alter the stock pit file
with the values needed to ommit your bad emmc area
5. save it and then flash your note in odin with your newly created pit file and repartition ticked.

@OP: could you please check your internal storage capacity? Is it aroung 8GB?

Arobase we are not going to rediscuss this matter for another 556643 pages.
Just ask yourself : if there was no problem then why did samsung patch their JB kernels for it. http://forum.xda-developers.com/showpost.php?p=34933643&postcount=683
Also nobody asks you to reconsider your own experience and beliefs, but the day someone follows your instructions and bricks his phone, are you going to pay for a new motherboard ?
I'll stop this discussion here, and just hope nobody will get struck under the tree.