Database Develop

[Q] Deodexed Stock XXJVT - root problem

I installed Deodexed Stock XXJVT stock rom from here, and everything went well. Than I wanted to root it. I did that with this kernel CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.zip, and it also went well. After that I wanted to "restore to factory settings" - format my user data. When I tried that, phone rebooted, than went to Android system recovery, and ask me to choose one of the options (see picture). I tried "wipe data/factory reset", but I got error messages from picture bellow. Tried again with same result.
Than I flashed phone with stock rom and stock kernel AGAIN. Tried to restore to factory settings, and 1. phone DIDN'T go to system recovery, and 2. erased all data WITHOUT any errors and with complete success.
Than I tried AGAIN (for the second time) to root with same kernel (again it went well). Than AGAIN tried to restore to factory settings (erase private data), and AGAIN problem mentioned above happened.
Now I have stock rom and stock kernel again. I need root for some things, but I don't know how to solve this problem. Could someone please help me with this?
Thanks.

hello
use odin to flash it see here
original rom xxjvt : http://www.techgom.com/2011/10/install-235-gingerbread-xxjvt-on.html
how to root it : http://www.techgom.com/2011/10/cf-root-for-gingerbread-235-xxjvt.html
-----
you must translate page to english with google chrome

You've already done a hard reset, so just install cf kernel again. Most instructions say wipe before flashing, you have still removed previous files etc
Sent using TCP/IP

Thanks both for quick reply.
@seghier
Thanks for these instructions. I did slightly different process. Maybe this why I got all these errors. I did use ODIN, but I flashed rom with "re-partition" checked (instruction says it shoudn't be checked), and also I used PIT while I am doing this and this instruction says I should do this without it. Check attachemnt picture for hw I did this.
Also, I did root with only PDA, and this tutorial says I should also PIT file included. See attachment for how I did this root.
I am a newbie so I am not sure if this could cause these errors? And did I do something wrong flashing and rooting phone my way?
Should I do this again following this two tutorials or not?
Also I am not sure what is DEODEXED means? Is there any differences between regular stock rom, and this DEODEXED one?
I just want regular stock rom and regular root.

oxeded rom is the original rom from samsung / deodexed is rom can be modified by users and you find in xda forums the difference
the method in photo is right
or you can install deodexed rom from here and the flash very easy :
http://www.multiupload.com/E9AT600ZUC
than use the files like see in image without pit or repartition
http://img707.imageshack.us/img707/1808/ppppas.png

Thanks, I will try now.

I still checked "re-partition" because I was using before DEODEXED, and now I am flashing ODEXED rom, so I thought maybe it is a different partition type. Is this ok? Flash went okay.

hello
when you find pit file repartition cheked automaticly
tell me if you success with flashing

Yes I did, thank you. But this problem with unable to restore to factory settings, after do root, still exist, even on ODEXED rom. It is deffinatelly some bug.

if you have problems you can format your sd card but first save all your files and data files using cwm : than create backup
you can try other deodexed rom from : s i9000 developement
i used the original deodexed rom and work fine

I don't have external SD card, just internal memory. Backup isn't problem. I wanted to delete all my personal data, but this error happenes. Did you try erase personal data AFTER did a root?

try this
settings ----- sd card and phone storage-------usb storage : format usb storage
and that remove all your files : music photos ...etc
-for hard reset try this : *2767*3855#
-factory data reset : *#*#7780#*#*
save all your photos and music ....

I already bring back some things, and also I managed to erased all that before doing root, so I won't experimenting anymore for now. Thak for your help. I will try this next time I want to clean my phone completly.

i hope that work for you
and deodexed rom more better because you can add new theme or launcher or flash update without limit than oxeded rom
good luck

Thanks.

try a new kernel

working now? please give a feedback ?

Like a wrote before. DEODEXED and ODEXED both work and I CAN restore to factory settings. After do root, it can't ba done anymore. I tried every possible combination, but result is same, so I guess that can't be done (which isn't so importante to me because I already restored to factory settings before apply root).
I didn't try other kernel (don't know either where to find other kernel), because I already installed programs, made personal settings, so I don't want again to wype all that.
If someone of you could try this it would be okay.

try semaphore kernel is very nice :
http://forum.xda-developers.com/showthread.php?t=1112908
use this application to install kernel :
https://market.android.com/details?id=neldar.sgs.kernel.flasher
and this application for save all your application to external card and you can restore it :
http://fr.appbrain.com/app/app-backup-restore/mobi.infolife.appbackup
--------
and don t forget to make backup with cwm

I am not so experienced about all this. What is difference between semaphore kernel and that other kernel I used for root?
Also if someone else could try this, who need to clean phone anyway, because I just make everything to work OK, so I don't want to experiment again.

[FULL GUIDE][UNBRICK][Root] Flash custom or stock ROMs or kernels [i9000][VIDEO]

Downgrade / change a custom ROM **** unbrick i9000 **** safely upgrade to a custom ROM **** exclusively-made videos
If you find this thread useful, please click "thanks" button left beyond the post.
DISCLAIMER:
Code:
* [I]I am not responsible for any bricked devices, marriage crisis,[/I]
* [I]sleeples nights, termonuclear wars, electricity blackouts, short[/I]
* [I]circuits, or for bad weather in your region that will brick your phone.[/I]
* [I]I just try to help here, but it may not work for you.[/I]
WHAT IS THIS GUIDE GOOD FOR?
Switching between custom ROMs: sometimes it just helps to flash a stock ROM. If you already use a custom ROM with modified system partition size, flashing a stock ROM is sometimes simply easier outgoing point for flashing another custom ROM. While the opening posts of the custom ROMs development threads usually describe very well how to upgrade, but the way how to downgrade to stock gets explained very seldom. By attempt to flash across the ROMs unexperienced people run often into various unexpected problems (like bootloops, system files crash, etc) although some of those people spend some time searching for the information how to downgrade. It is simply difficult to obtain the informations so I would like to make here a checklist in almost-noob-friendly way for downgrading / unbricking. What I meant with words "almost noob-friendly" is: you must know what these words mean: Odin, ROM, kernel, CWM recovery, ADB, zip file, nandroid backup or download mode before continuing.
Unbricking: soft-bricked SGS i9000, or if you get into bootloop and lose recovery mode (if download mode is still accessible) can probably likely be unbricked by following this guide. Flashing novices: if you have bricked the phone by first flashing attempt, please check as the very first thing do you really have the i9000 in your hands, as there are about 20 sub-models. You can check HERE your IMEI number, but please always use app Android System Info, as it is more reliable. This guide is only for Samsung Galaxy S, GT-i9000!
Root: for people who just want to root their phone, everything is described here as well. Unexperienced people should please read whole the guide before doing anything. It will be very helpful to understand more, flashing should work without big stress or problems then.
FAQ (about this guide):
FAQ: this guide is for PC users, what about Linux or iOS?:
Ubuntu and iOS users can use Heimdall perfectly well for the flashing procedure. Heimdall ver 1.31 works excellent with the i9000. But as this guide indeed refers primarly to PC/Odin users, I would like to re-direct Linux und Mac users to this Heimdall Flashing Guide and advice novices to learn first some more on CyanogenMod Wiki about using Heimdall.
FAQ: restoring a nandroid backup across different ROMs:
Having a nandroid backup kept somewhere would make life of bricked i9000's owner much easier. But to restore it safely, you must first flash the same ROM, the same kernel and the same custom recovery version like you had when you have created your last nandroid backup. Otherwise bootloop might be the result.
FAQ: formatting & partitions:
Compared to the modern devices, Samsung Galaxy S GT-i9000 has quite limited RAM (500MB) so many recently developed custom ROMs must use different system partition sizes than stock ROMs. Restoring nandroid backups made while in different ROM, or flashing across differently partitioned ROMs is problematic and appear to be the most common reason for the bugs or soft bricks.
FAQ: Troubleshooting
At any point of the flashing procedure, various problems may occur. On the bottom of this post are the solutions listed for the most common, typical problems.
Click to expand...
Click to collapse
1. PREPARATION:
People with bricked devices could also benefit from reading this
1.1 like always: make a nandroid backup of your presently used ROM. It is recommended to keep the zip files of your build, gapps and nandroid backup of your presently used ROM on the phone as well as on your PC.
1.2 remember version No of your custom recovery (rename backup file) - beyond under FAQ is explained only workflow for the CWM recovery. Nandroid backups made by one version of CWM recovery usually aren't restorable in another version of the CWM recovery. Therefore it is at all times very valuable information to know which version did you use to create your nandroid backup. Same thing for kernels and ROMs: attempt to restore nandroid backup created by different kernels and by different ROMs will likely end in soft-bricking or bootloop.
1.3 backup your SMS, call logs and contact data. Use for this free apps from Play Store "SMS backup & restore" and "Call logs backup & restore" (both by Ritesh Sahu) as they work reliably accross all the ROMs, no matter if custom or stock. Who doesn't want to synchronize his contacts with his google account can simply in the settings of Contacts (People) app export a *vcf file of all the contacts to SD card. It is universal standard format acceptable throughout the ROMs (even photo/avatar of your contact will be saved)
1.4 backup your IMEI / EFS folder (if you have never flashed before, make sure which model do you really have a i9000 check HERE your IMEI number! IMEI number ocasionally gets erased after flashing of some custom ROMs. It happens often with Slim ROMs, some PA ROMs etc (and no- I didn't wanna say those ROMs aren't good or that you shouldn't try them- I just say: backup your IMEI before!) Save yourself of headache, EFS backup is easy to restore. Backup in a root shell (either by ADB or within the Terminal Emulator) for example like this. TWRP recovery has an option to backup the EFS folder.
1.5 backup your calender- app CalenGoo from Play Store (only pro version) synchronizes the android calender with google calender. Losing dates won't happen to people who use this app or other similar ones.
1.6 backup all your other data (music, photos, videos) - some custom ROMs will erase all your data during the installation, as some of them must reformat parts of the internal SD card. Keep at all times all data from your phone that you might need as backup externally.
Click to expand...
Click to collapse
2. DOWNLOADS, ODIN and ADB tips:
Check the baseband versions /CSC codes for your region HERE or also HERE, or if not sure, choose a firmware with multi-CSC
2.0 Download stock ROM and proper Odin version for your device. All ROMs for SGS i9000, PIT files, Odin and many unvaluably good advices can be downloaded HERE
2.1 Not all Odin versions are compatible with the i9000. Last compatible version is 1.83, uncompatible ones can freeze during the flashing process or won't even start it.
2.2 The most reliable devices for flashing with Odin are notebooks running on Windows XP 32-bit. Big PCs, Win7, Vista and 64-bit OSs can cause troubles.
2.3 The rule of thumb for Odin: option "re-partition" should be checked only if PIT filed is flashed together with the ROM, otherwise it mustn't be checked!!
2.4 For downgrading from the CM to stock ROM, it is strongly recommended to flash the PIT file, as custom ROMs usually use different partitioning of the system. Clicking on "PIT" in Odin will automatically check the re-partition option by default. Leave it that way and choose PIT file for the i9000 ending with numbers 512.
2.5 If your stock ROM after unzipping with 7zip consists out of 3 files, they will be set in Odin under PHONE, CSC and PDA. If the unzipped ROM consists only one big file, we will set it under "PDA" and ignore all other file fields.
2.6 Make sure that your Samsung Kies doesn't run in background (kill process in task manager, or even better: uninstall that crap!)
2.7 Make sure to have installed Samsung mobile USB driver on your PC: when your i9000 is turned on and get connect via USB cable, Windows must be able to perfectly recognize and install drivers for your hardware before you run it in download mode.
2.8 Make sure that USB debugging is enabled under: Applications/Development (it will be disabled by default in every stock ROM). Download mode will work regardless this, but if we will need to use ADB it should be enabled.
2.9 Make sure that your battery has enough juice (full charging is recommended)
Many experienced users and all android developers are using Android development tools and its part ADB tool to remote their android device or to find reason for malfunctioning. For anybody willing to learn more, check this excellent ADB guide. Who installs for the first time should mind that after installation of whole SDK Manager the ADB drivers for Android versions 4.0+ could be not pre-installed and you have to do it manually. Mind also that for CM10.x ROMs you shouldn't use ADB (SDK manager) versions earlier than 1.0.31.
(You can find on the bottom of this post is attached 7zip file of a screenshot of SDK Manager where I've marked in red colour on example of Android 4.3 which options must be checked to update ADB drivers. Your PC must be online to update and you must restart your system to enable the drivers: even if it doesn't warn that you should do so)
Click to expand...
Click to collapse
3. FLASHING A STOCK ROM (same procedure for UNBRICKING):
Following procedure can be seen beyond in VIDEO No.2 (0:00-4:45)
3.1 Steps 2.7 / 2.8 / 2.9 must be done now, switch off your phone
3.2 Run Odin as administrator!
3.3 under PIT: choose the file "s1_odin_20100512.pit" (that will check the "re-partition", it is good so)
3.4 under PDA, PHONE, CSC choose the unzipped 3 files from step 2.1, it is described under 2.6 how to do it (all three options will be checked now in Odin: Re-Partition, Auto Reboot and F.Reset Time)
3.5 run your i9000 now (not before!) in download mode now with 3-button-combo (pressing at same time the buttons: volume down&home&power)
3.6 connect your i9000 now via USB cable to your PC
3.7 Odin must display now in the "Message" tab (left, lower bigger tab) and leftmost ID:COM field must display now port number where your i9000 is connected in color.
If Odin doesn't display BOTH messages, interrupt here, disconnect your phone, switch it off (7sec long press on the power button, ignore the text "Do not switch off the target") and check again steps 2.7 / 2.8 / 2.9)
3.8 if and ID:COM port number are displayed in Odin, click on "Start"
3.9 wait until Odin finishes with the flashing process (in the upper leftmost field first "RESET" and after that "PASS" will be displayed if the flashing ends with successf), don't move the USB cable! After about 1-2 minutes your i9000 will reboot into choosen stock ROM
NOTE: if your stock ROM consists only out of only one TAR file (instead of three), you should choose that big file in Odin under "PDA" (same like in the VIDEO No.3) and if you need re-partition, unzip the PIT file (attached on the bottom of this post) and choose it in Odin under "PIT" (in that case, option "re-partition" must be checked). The flashing procedure just takes considerably longer time than in the video No.3 where only a kernel was flashed (with my PC, a firmware flashing takes always about 2min 20s, same long like in the VIDEO No.2). All stock ROMs for the i9000 (Eclair, Froyo & Gingerbread) use the same partition size for the /system. So for switching from stock to stock you don't need the PIT file. Use it only for unbricking or if you are changing from CM10.2 back to stock (or from any other ROM that uses different partition size than Samsung stock firmwares).
Click to expand...
Click to collapse
4. ROOT stock firmware and UPGRADE TO A CUSTOM ROM:
4.1: BOOTLOADER CHECK
IMPORTANT: i9000 developers recommend upgrading from Gingerbread to 4.x custom ROMs as they need a Gingerbread bootloader!!
Maybe you can skip this part: if your last stock firmware was any Gingerbread version (Android 2.3.x) you don't have to worry about this, as your phone already has a GB bootloader. If a firmware package includes the bootloader (and all stock firmwares do include it), it will get automatically flashed no matter of the chosen options in Odin.
But for all the people who upgrade directly from Froyo / Android 2.2.x into the Android 4+ world, it is recommended to update your phone bootloader to Gingerbread's one. It can be done just before flashing your new custom ROM or even after successful upgrading directly from Froyo to CyanogenMod, as you can see in the video beyond:
This is how flashing of bootloader only looks like:
repeat the steps from 3.1 to 3.2
turn off the phone
Run Odin as administrator and chose GB bootloader (tar file) under "BOOTLOADER" (unzip attached zip file!)
Check the option "Phone Bootloader Update"!
SITUATION ONE: if reboot of the system is not desired uncheck "Auto Reboot" option! (example: if you want right after this to install zip of a custom ROM in recovery mode )
SITUATION TWO: if reboot of the system is desired, leave "Auto Reboot" option checked! (example: you already have installed custom ROM based on Android 4+ and want just to replace an outdated Froyo bootloader)
Further as described above under steps 3.5 until 3.9
In the following video you can see how bootloader flashing procedure for SITUATION TWO looks like:
VIDEO No.1
or https://www.youtube.com/watch?v=zJED4wJYG8c
WARNING: Flashing a bootloader is speaking in general terms possibly the most dangerous flashing procedure for any device, so be absolutely sure to know what you're doing- use exclusively Odin 1.0, 1.7, 1.82 or 1.83 for the bootloader flashing procedure and run Odin as administrator! Any mistake by flashing a bootloader like: moved USB cable, electricity shortcut or even Samsung Kies running in background may result in a hard brick!
I strictly recommend to use for this procedure exclusively an already known PC that has been already reliably used for flashing several times. DON'T EXPERIMENT with unknown PC system here! If you flash a bootloader, be aware you do it on your own risk!
Click to expand...
Click to collapse
4.2: ROOT (for stock ROMs)
ROOT INFO: With root access and custom recovery (like CWM, TWRP etc), we can install any custom ROM (as flashable zip in the recovery mode) which is much safer way than flashing with Odin. Root access also makes us possible to use some of the greatest apps in the universe.
With a custom recovery, we can create a nandroid backup (image of our entire system) that can be later restored at any point (read FAQ to 1.2)
Easy method to gain root access on i9000 with stock ROM, is to flash a compatible custom kernel, that already features a custom recovery. The correct way for flashing with Odin is already exactly described in the steps 2.6 until 3.2
Now we will flash only kernel, so instead of steps 3.3 and 3.4 we will just choose the kernel file(tar) under "PDA", leave the "Auto Reboot" option checked (all other options unchecked) and follow further the steps 3.5 until 3.9
Gingerbread root procedure:
Option 1: flashing (with Odin) of a SpeedMod kernel for Gingerbread ROMs (be sure to choose the compatible kernel version for your GB build version). All versions of SpeedMod kernel are fast and feature the CWM recovery. In recovery mode under "advanced SpeedMod features" you can choose "ROOT" option, which will flash superuser and busybox, so after reboot your i9000 is rooted.
Option 2: flashing (with Odin) of a CF-Root. Also here, be sure to choose the compatible CF-Root version for your GB firmware build from Chainfire's thread. CF-Root is also a kernel that features CWM recovery, some versions root automatically, other just part of it and you can easily do the rest according to Chainfire's description.
Froyo root procedure:
Flash with Odin speedmod-kernel-k13e-500hz.tar that works with all Froyo firmwares (all 2.2 and also 2.2.1).
Reboot into recovery mode and choose under "advanced SpeedMod features" the "ROOT" option, which will flash superuser and busybox, so after reboot your i9000 is rooted.
Video: flashing of a kernel is shown in VIDEO No.3
Root only: (tested by me only for Froyo 2.2.x): with SuperOneClick Root Tool:
INFO: here you would get just root, without custom recovery
No download mode will be used here, your i9000 should be switched on - only USB debugging must be enabled for this. Download from one of those links SuperOneclick 2.3.3 by Shortfuse and unzip it with 7-Zip. Connect now your i9000 via USB cable with your PC and wait until the hardware is recognized by your PC. Run now as administrator (unzipped!) Superoneclick 2.3.3 and when the tool opens, just click on the left big button "Root". SuperOneclick will root your phone, you can follow the status in the big left tab. If the tool asks to install Busybox, do it. If the Superoneclick wants to run the test, you can do it but you don't have to do it, sometimes it just freezes...
Your i9000 is rooted now. To be sure all is fine, you can check the root status with some root-checker app.
SuperOneClick Root procedure can be seen in VIDEO No.2 (4:30-6:55)
Whole the procedure of unbricking, root and flashing a kernel takes less than 10min if all the files are ready and the drivers are properly installed on your PC. Watch whole the flashing/root procedure in real-time on my VIDEO No.2 without annoying talking:
VIDEO No.2
or https://www.youtube.com/watch?v=7IjzUrv9Dz4
Click to expand...
Click to collapse
4.3: UPGRADE TO A CUSTOM ROM
There are so many interesting custom ROMs for the i9000 around. As there were more than 25 million of these device sold worldwide, there is still a lot of development around. Talking only about KitKat (4.4.x) based roms, there is choice of: CyanogenMod 11, Mackay (pure), Mackay OMNI, SlimKat, Carbon, SuperNexus, CyanAOSP, DirtyUnicorns, ParanoidAndroid, Smasher X, Avatar ROM etc.
Each ROM has priority somwhere else so there is no "best" ROM, it is matter of personal choice and needs. The most considerable limitation of the i9000 is its 500MB memory, which is small for today's needs. The benchmark of today for the i9000 with KitKat ROMs is probably Mackay kernel for KK roms that enables 417MB by keeping 720p video possible. That kernel features either CWM or beautiful TWRP recovery.
We have awsome sticky threads for the i9000 here which can help with ROM or kernel choice, like this Soryuu's thread, or many ever-green threads by our important contributor, xsenman.
Video: in VIDEO No.3 one can see how flashing of any kernel with Odin looks like in real time: I've chosen here Semaphore kernel 3.3.0. Any other kernel as Odin package (tar.md5 file) can be flashed the same way
VIDEO No.3
or https://www.youtube.com/watch?v=CQVj-tPDOXo
Click to expand...
Click to collapse
TROUBLESHOOTING:
Some of the problems are quite known and this is how you can solve the most typical situations:
(all the files flashed with Odin must be in .tar format!)
Troubleshooting section 3 (stock ROM):
Note: the following red colored errors get displayed just after the modification of the system and can usually be resolved by flashing of an respective file (attached), the procedure with Odin is identic like in the third video (flashing a kernel)! (unzip file with 7zip to get a flashable rar file)
Error:
Odin didn't flash the firmware completely, nothing happens have bit of patience, if nothing happens for 4-5 minutes, this is your checklist:
If Kies installed, are you sure it doesn't run in the background? (check with Task Manager and kill Kies process)
Don't run your phone in download mode too early: do it just few seconds before flashing a firmware: the i9000 easily get into kind of standby/sleep in the download mode, so prepare the Odin first with all files so the phone can be flashed in the DL mode imediatelly.
Did you run Odin as administrator?
Are you using a compatible Odin version? Use Odin3 versions: 1.0, 1.7, 1.82 or 1.83 (last)
Few tips:
Notebooks with WinXP 32-bit seem to be the most reliable devices for flashing with Odin. Notebooks are in general more reliable than PCs, 32bit systems are more reliable than 64bit systems. Saying that, of course it doesn't mean it won't work with the PCs and 64-bit OS, just be aware of the statistical facts.
Try different USB port on your PC and use original cable, if damaged try another one. Never move the cable during the flashing process!
Error:
E:format_volume: rfs format failed on /dev/block/stl11
Flash cache.rfs with Odin under "PDA"
Error:
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
Flash dbdata.rfs with Odin under "PDA"
Error:
Boot animation problems
Flash param.lfs with Odin under "PDA"
Troubleshooting section 4 (root / custom ROM):
Error:
my device is rooted, but I still don't have root access
Check if superuser and busybox are really installed. Reboot and wait for few minutes, sometimes it just needs bit of time. Alternatively, install SuperSU and let it replace another SU applications.
Error:
CWM recovery is installed, but I reboot in stock Android recovery
Re-flash CWM recovery, download again, check if your download file is corrupted. Some root kernels don't include CWM recovery, check what do you have. Otherwise you may have flashed incompatible CWM recovery, try to use app "ROM Manager" by ClockwordMod to flash the CWM recovery with.
Error:
By attempt of flashing CyanogenMod-build.zip my phone stucks in random bootloop in recovery mode
Remove the battery, insert it again and run your phone with 3-button-combo in recovery mode again. Second attempt to flash zip usually works well, in first step CWM recovery was updated and second attempt to flash zip will be succesful.
For the case that it doesn't help, or you can neither run your phone into recovery mode nor reboot into the OS anymore, just try with different stock ROM or root method/kernel. Your download mode is still accessible then and you won't have any problem to flash again any stock ROM like this guide described above.
Error:
My screen has dark blue tint all over after flashing a custom ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution found by pawitp as of February 2014: check this guide by need4steer and hit "thanks" button for both
Error:
My IMEI number got lost
If your IMEI gets unknown, has only zeros, or displays dummy No "0049..." you may not be able to make calls before you restore it. The issue could happen for several reasons. The i9000 ususally displays "unknown baseband and IMEI" if for some reason modem isn't mounted. You can fix thaht with any root file browser by simply c&p and fixing permissions. Otherwise, under section 1.5 was explained how to backup/restore EFS folder (IMEI No) in Terminal Emulator or with ADB shell (read FAQ 2). If you haven't made any backup at all, try first to flash a stock ROM first. If your last stock ROM was Gingerbread, flash a JVU (try with and without PIT) or JVZ firmware as this procedure often restores the IMEI. If you were on Froyo before it, try to flash a JPU firmware. Otherwise this guide might help you. Restoring of a non-backuped IMEI can be painful and successful methods for one won't help another. Upgrading your phone's OS step-wise (in order: Eclair, Froyo, GB, ICS, JB, KK) usually preserves the EFS folder (IMEI No) and can save you of a headache.
Except for those quite common errors, also other unexpected situations might occur. If that happens, I recommend to check for the solution in awsome xsenman's unbricking guide where really many different situations are described and solutions for each of them.
Click to expand...
Click to collapse
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Thanks to:
We all here are part of an community that shares results of open source projects with the developers, for free.
Whoever had benefits from this thread, consider to make little donation to the developers who made us all this possible and spend their free time to improve at the end: yours and mine device.
I am not developer, so the credits go to the developers, please hit there "Thanks" buttons and consider to make little donations to the developers whose work may have brought you benefits, as we all owe special thanks to them:
dev @pawitp for bringing us all the CyanogenMod versions (up to presently Android 4.3) to our i9000, without even being an owner of it
dev @stratosk for creating the truly amazing Semaphore kernel, a true life-work with compatibility for nearly all Android versions up to date
dev Shortfuse for creating SuperOneClick, comfortable noob-friendly way to root the i9000 on Froyo
dev @Chainfire for tireless work on the i9000 and plenty of mind-blowing apps, root files and other inventions (who roots 2.3.6 stock ROM will need some of it)
dev @hardcore for creating amazing SpeedMod kernel
dev Ritesh Sahu for creating fantastic across-ROMs-compatible free apps for backups SMS and call logs in Google Play Store
I have donated multiple times to all of them, please do the same except if your budget is so tight that you can't buy a beer to the unknown friends.
Click to expand...
Click to collapse
Please let me know if you discover that any download link from this post doesn't work. REMARK: 1.5K downloads, 20K views and only handfull of "thanks" hits? Should I erase all this if it is so useless? Let me know, guys.

Perfect work!!!Thxs a lot!!!:good::good:
tetakpatak said:
Downgrade from CyanogenMod **** unbrick i9000 **** upgrade to CM without bugs
For my post it is enough to click "thanks" button if it was helpful. Cheers
Click to expand...
Click to collapse

freakymod2120 said:
Perfect work!!!Thxs a lot!!!:good::good:
Click to expand...
Click to collapse
Thank you mate! Please just edit your post and erase whole the quote, as it is such a long opening post

Hey, I think this is an awesome thread, very comprehensive and well thought out Can I add a few things to it?
This could become a "Complete reference guide" and I think it should be stickied
Sent from my GT-P7510 using Tapatalk HD

Sorry for wrong quoting...
Maybe you can write such a genious thread for "upgrading" ??? Or changing kernel ???:good:
tetakpatak said:
Thank you mate! Please just edit your post and erase whole the quote, as it is such a long opening post
Click to expand...
Click to collapse

freakymod2120 said:
Maybe you can write such a genious thread for "upgrading" ??? Or changing kernel ???:good:
Click to expand...
Click to collapse
Hey, mate_ thanks for editing and erasing huge quote :good:
Actually if you look at the last section, it is described how to upgrade to CM. I didn'n want to put it into the name of the thread, but after upgrade from Froyo & SpeedMod kernel to CyanogenMod all people so far who did so reported me to have now perfectly working CM10.1x or CM10.2
But it was only around ten people so far, so I will wait for some more reactions. The proceeding of upgrading to CM builds is then very easy: wipe all in CWM recovery, install zip CM, install zip gapps, reboot, after first time installing CM go to right after the first reboot to settings/apps/all/clock and clear cache of clock app. That's all.
EDIT: You're right, after your post I've decided to film my recent kernel flashing that might be helpful for unexperienced users. Now one can watch my short YouTube video (meanwhile added also in the opening post)

No prob...
Okay you`re right ...i`ve skipped during reading sorry...
But a short guide for installing an kernel ,will be nice ...:good:
tetakpatak said:
Hey, mate_ thanks for editing and erasing huge quote :good:
Actually if you look at the last section, it is described how to upgrade to CM. I didn'n want to put it into the name of the thread, but after upgrade from Froyo & SpeedMod kernel to CyanogenMod all people so far who did so reported me to have now perfectly working CM10.1x or CM10.2
But it was only around ten people so far, so I will wait for some more reactions. The proceeding of upgrading to CM builds is then very easy: wipe all in CWM recovery, install zip CM, install zip gapps, reboot, after first time installing CM go to right after the first reboot to settings/apps/all/clock and clear cache of clock app. That's all.
Click to expand...
Click to collapse

Awesome thread OP! Fixed my sister's soft bricked SGS with your instructions. Thanks a lot! None of the links in your post nor the ODIN had the necessary .pit files. So I had to find them myself. So anyone else who are looking for it you can get it here. Look for Samsung Galaxy S I9000 - s1_odin_20100512.pit, s1_odin_20100513.pit, s1_odin_20100803.pit in that page.
Thanks again bro! :good:

freakymod2120 said:
...Okay you`re right ...i`ve skipped during reading sorry... But a short guide for installing an kernel ,will be nice ...:good:
Click to expand...
Click to collapse
Flashing kernel procedure is actually already described in the first post under section "Root" from ninth step. It would work identic way by using CM10.2 to flash for example Semaphore kernel ver. 3.1.0. Download kernel (tar file) from HERE and the rest is same: run Odin 1.82 or 1.83 as admin, choose kernel *tar file under "PDA" and don't change anything else in Odin, put your i9000 in download mode, connect via USB, if Odin recogizes the phone just click in Odin on "START". Kernel will be flashed within few seconds and your i9000 will reboot. Then you can download Semaphore App (free) from Play store, it remotes all kernel functions.
Before any major change on the phone it is just always very recommended to make nandroid backup. But be careful after flashing the Semaphore or any other kernel:
- if everything works fine you shouldn't use your backup made by different kernel (CWM stock) as Semaphore uses its own, adapted CWM recovery mode with added functions (like auto brightness, displaying battery status in %, featuring cool aroma file manager etc).
So if you don't want to use your old CM10.2 build so soon again, copy from your phone whole folder "clockwordmod" where the nandroid backup is stored, paste it on your PC storage in the same folder together with the zip of the CM build you were using (and made that nandroid backup with it). Then you can erase that nandroid backup from your phone (with ROM manager app), reboot to recovery mode (Semaphore CWM recovery) and make new nandroid backup.
Reverting to CM10.2 is easy, just like you installed it first time: to avoid any risk of data uncompatibility, we will wipe all and restore your old nandroid backup: copy&paste your CM10.2 zip and whole "clockwordmod" folder from your PC again on the phone (no matter if extSD or internal), reboot to recovery, wipe all, make factory reset, install zip CM10.2, reboot, reboot again to recovery, restore your old nandroid backup made by that build.
Your phone will be the same like in the moment when you created your nandroid backup. That's why before reverting to stock CM10.2 mind to backup all important SMS, call logs and contacts created after flashing the Semaphore (or other) kernel. Sorry if it sounds complicated, it actually isn't so long proceeding and it possibly saves lot of time and nervs compared to situation where bootloops or other annoying things would occur.

Flashed Semaphore Kernel for the 1st Time
Hi,
with your great instruction it was no prob to flash an new Kernel.
Now i`m using Semaphore 3.1 over CM10.2-nightly ...
Great idea with the short video...
Thank you very much for this Thread and all your help :good::good::good:

Maybe a stupid question...
Is there any option that this thread stay on top and doesn`t go down when new threads are coming ...????

freakymod2120 said:
Maybe a stupid question...
Is there any option that this thread stay on top and doesn`t go down when new threads are coming ...????
Click to expand...
Click to collapse
You can write to the moderator PM with that question, he will check my OP and decide afterwards if it deserves to be sticky thread.
I would have asked myself, but I am now waiting to get some more reactions to my theory in the last section: more people should confirm me that upgrading from Froyo to CyanogenMod works perfectly well. So far it is handful of people but I would need few dozens of positive replies that it works reliable.
It is interesting that some people have bugs with CM10.x and other not at all by using the same device (i9000). So it maybe does matter which ROM was pre-installed before upgrading. If so, it would be extremely important information for all the developers of CyanogenMod.
IMO, so far it is just a helpful thread nevertheless. Confirmation of my theory would be nearly sensational, though. It would not deserve only to get sticky thread then, but it would also bring unvaluable info for further development.

Okay then we wait and see if there will be any reaction about your instruction and more experience about the upgrade-procedure from froyo to CM...
tetakpatak said:
You can write to the moderator PM with that question, he will check my OP and decide afterwards if it deserves to be sticky thread.
I would have asked myself, but I am now waiting to get some more reactions to my theory in the last section: more people should confirm me that upgrading from Froyo to CyanogenMod works perfectly well. So far it is handful of people but I would need few dozens of positive replies that it works reliable.
It is interesting that some people have bugs with CM10.x and other not at all by using the same device (i9000). So it maybe does matter which ROM was pre-installed before upgrading. If so, it would be extremely important information for all the developers of CyanogenMod.
IMO, so far it is just a helpful thread nevertheless. Confirmation of my theory would be nearly sensational, though. It would not deserve only to get sticky thread then, but it would also bring unvaluable info for further development.
Click to expand...
Click to collapse

tetakpatak said:
ROOT:
Flash via Odin stock Froyo 2.2 or even better Froyo 2.2.1
Reboot and enable USB debugging in your new stock Froyo 2.2.1 phone under: Applications/Development (it will be disabled by default after flashing)
Root it, there are several ways: for example download from one of those links SuperOneclick 2.3.3 by Shortfuse and unzip it with 7-Zip
Reboot your i9000 into android OS and connect it with your PC and wait until it is recognized (sound for "new hardware")
Run now as administrator (unzipped!) Superoneclick 2.3.3 and just click (on the left) the big button "Root"
if SuperOneclick asks to install Busybox, do it
if the Superoneclick wants to run the test, you can do it but you don't have to do it, sometimes it just freezes...
Your i9000 is rooted now. To be sure all is fine, check the root status with some root-checker app
Now we need CWM recovery and kernel, turn off your i9000 and download speedmod-kernel-k13e-500hz.tar
Click to expand...
Click to collapse
@tetakpatak.. good job in putting up this guide, was looking at this part concerning rooting and CWM, its easier just to flash the speedMod kernel and use it to root the phone , just use the universal lagfix menu in advanced features to install "superuser" saves time and less complicated, since you have to flash this eventually.
But no harm doing it as you had explained.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Thank you @xsenman, absolutely correct. Yes, the SpeedMod kernel doesn't install by default Superuser and Busybox. SuperOneClick however does install it imediatelly (very quickly also), so I've decided to form the OP this way as it is bit less complicated for unexperienced users, I assume they will be happy to enjoy the easy way.
I am sure it would make many people happy if you would post in this thread a guide concerning the upgrade from Froyo to Gingerbread and explain different variants of 2.3.x ROMs, with info about kernels (like Semaphore etc) for people who woukd like to use GB as their everydays OS.
I would paste in the OP link directly to your guide (of course, it could be also one of your older posts, you have many useful ones). Please post here or PM me the link

tetakpatak said:
Thank you [MENTION=4586061] if you would post in this thread
Click to expand...
Click to collapse
lol, man you are doing great on your own, and people comprehend things in their own unique way, so some will appreciate your methods and others won't , so don't let that stop you from adding whatever you feel like to the OP. As for me, this forum is dying, as most of the users, experts, developers have been gradually moving on to SGS Plus, S2, S3, S4 and maybe S5 soon:laugh:
Check this out! You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

What? i don`t want to read such things :laugh:
Out good old old device ,the works every day fine for us ...no chance ...:good:
I don`t give up my lovely SGS :angel:
xsenman said:
lol, As for me, this forum is dying, as most of the users, experts, developers have been gradually moving on to SGS Plus, S2, S3, S4 and maybe S5 soon:laugh:
Click to expand...
Click to collapse

SAR values
@xsenman IMHO, the Galaxy S is still very interesting device by all means.
I've attached the list of Samsung's 10 devices produced in last 3 years with the lowest SAR-value (per kg). The highest measured SAR value of each device per kg (respectivelly) is displayed in the green field. It is amazing, how low is the radiation of the i9000 by all means!
Just compare it to the SAR values of all the iPhones (other attachment, with red coloured values)
(my reference: handywerte.de website in german language)
Very few phones ever produced have such low intensity of the electromagnetic field like the SGS i9000 does. Honestly, it was my reason to choose it instead of the already released SGS2 back in 2011 and I don't regret it until today.
My main phone before the i9000 was Motorola MPx200, also for the same reason (low SAR value) and I assume my next phone might be the N7100, which will run besides the i9000, of course
(I need two phones due to frequent journeys abroad)

freakymod2120 said:
What? i don`t want to read such things :laugh::
Click to expand...
Click to collapse
tetakpatak said:
@xsenman IMHO, the Galaxy S is still very interesting device by all means.
Click to expand...
Click to collapse
hmmmm.., guys... hold your horses I am not talking about the Phone ( Galaxy S ) but this Forum. meaning, this was a very active forum, all those that are active in S2,S3 & S4 today, used to be here . So don't conclude I am trying to say, the SGS is dying, Nope most of it will be sold to some guys in the third world (like me) :laugh: and it will be used for a long time to come.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​

Ah okay ,horses were stopped :good:
xsenman said:
hmmmm.., guys... hold your horses I am not talking about the Phone ( Galaxy S ) but this Forum. meaning, this was a very active forum, all those that are active in S2,S3 & S4 today, used to be here . So don't conclude I am trying to say, the SGS is dying, Nope most of it will be sold to some guys in the third world (like me) :laugh: and it will be used for a long time to come.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.​
Click to expand...
Click to collapse

[Q] Caught in Bootscreen loop - i9305 LTE have access to CWM! [SOLVED]

My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.

likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7

PHP:
MaHo_66 said:
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
Click to expand...
Click to collapse
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?

likeasir said:
PHP:
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
Click to expand...
Click to collapse
Hmm... Good question. I understand your issue here but im afraid i cant answer this.. While it was working what firmware was running on it? What baseband? If you have any kind of info of the working firmware, analyze it with firmwares on those sites and try to find the one you need.
Sent from my GT-I9305 using XDA Premium 4 mobile app

likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )

AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days

likeasir said:
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
Click to expand...
Click to collapse
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.

likeasir said:
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
Click to expand...
Click to collapse
Cheers on getting ur phone fixed but after wiping all directories a stock rom flash would have cleared all the problems

lol i just did this to my phone, time to find a stock firmware.

[Q] Cyanogenmod 11 Problems

So toady, I tried to install Cyanogenmod 11 on my Xperia SP, model C5036.
The install worked, but now my phone is missing the IMEI and can't activate Wi-Fi.
I would try to factory reset inside of my recovery, but when I try to enter it (camera button on boot), the phone boots normally and the LED on the bottom flashes red.
Some more info:
-Phone was rooted with Towel Root
-Bootloader is locked
-Phone is locked to Bell Canada, if that helps
-I, as an idiot forgot to wipe factory data and clear cache.
-Phone was previously running Sony 4.3
-The phone now lists the model number as C5303
-Cyanogenmod version: 11-20140528-UNOFFICIAL-huashan
ROM used: http://forum.xda-developers.com/showthread.php?t=2735975&page=51
If you need any more information, I will tell you.

Enter recovery with vol up/down (philz/cwm) buttons.
Missing imei is probably related to the recovery used. Try re-flashing the ROM via cwm, after data/cache/dalvik wipe.
FYI, Newer version of cm11-LBL is available.

mrhnet said:
Enter recovery with vol up/down (philz/cwm) buttons.
Missing imei is probably related to the recovery used. Try re-flashing the ROM via cwm, after data/cache/dalvik wipe.
FYI, Newer version of cm11-LBL is available.
Click to expand...
Click to collapse
I was able to flash the newer version through CWM and now the IMEI is back and my SIM works. The only thing that isn't working now is the Wi-FI; it won't switch on at all. So the only thing I still need help with is the Wi-Fi.

Probably the WiFi module not loading. Have you flashed the .205 kernel? Your model is c5306 and the kernel posted in the OP (of cm 11 thread) is for c5303. I don't know whether flashing that on your phone would be alright (or have you already flashed it?). I don't think it would cause problems...
In any case, try these in a terminal emulator to see whether wifi modules load..
Code:
su
modprobe wlan
Any error? If nothing, run "lsmod" (without quotes) to see which kernel modules are loaded.

mrhnet said:
Probably the WiFi module not loading. Have you flashed the .205 kernel? Your model is c5306 and the kernel posted in the OP (of cm 11 thread) is for c5303. I don't know whether flashing that on your ph[one would be alright (or have you already flashed it?). I don't think it would cause problems...
In any case, try these in a terminal emulator to see whether wifi modules load..
Code:
su
modprobe wlan
Any error? If nothing, run "lsmod" (without quotes) to see which kernel modules are loaded.
Click to expand...
Click to collapse
No, I haven't flashed it yet..
In Terminal Emulator doing the modprobe command gave me this:
Code:
modprobe: 'wlan.ko': unknown symbol in module or invalid parameter
[Code]
After doing lsmod, I get this:
[Code]
cpufreq_wheatley 7320 0 - Live 0x00000000
cpufreq_lionheart 57110 - Live 0x00000000
texfat 124855 0 - Live 0x00000000 (PO)
cfg80211 135928 - Lie 0x00000000
[Code]
I also used "svc wifi enable" but it just said "Killed" after.
Am I supposed to get these?

Looks like wlan.ko is not loading (??symbol mismatch..). The solution I can think of is to flash the given .205 kernel and hope it works!

So I flashed the .205 kernel in Androxyde's flash tool. When I booted up the phone, the phone turned off twice at the boot animation, but I don't think that did anything, as it still works.
The Wi-Fi now says "Turning Wi-Fi on..." but it just stays like that. I also noticed that running lsmod (su command does nothing) it says "cfg80211 135928 1 wlan, Live 0x00000000" instead of "cfg80211 135928 - Live 0x00000000" and new string "wlan 2702117 0 - Live 0x00000000 (0)".
Also, the IMEI is gone again, even after reflashing CM through cwm multiple times.
Should I just use a different ROM other than CM11?

Wlan.ko seems to load with .205 kernel. For the missing imei, the possible "solutions" mentioned by users in other threads are..
* Flashing ROM with a different recovery (TWRP seems to have the least imei problems).
* Do a backup in cwm and restore it (weird of course) - it also fixed Wi-Fi problems for some.
For some people, this imei missing thing is random! If nothing works, may try a different ROM. Maybe can flash/restore a stock based rom to get TWRP recovery, and then flash cm11-LBL via TWRP.

I restored my phone back to Sony 4.3 and re-installed CM11. Wi-Fi now works but no IMEI still.
I also can't access TWRP after installing cm11-LBL; only PhilZ and CWM are accessible. This has happened both times installing it.
Do you have any ROMs that you can recommend to me in case we can't fix this? The reason why I wanted to update to CM11 was because Sony's 4.3 had far too many bugs and lagged too much.

Cm11-lbl doesn't have TWRP. I meant, to use TWRP to flash while on a stock based ROM. Anyway, I'm now using PA rom for LBL : http://forum.xda-developers.com/showthread.php?t=2789320
It's a very nice ROM.
Need to flash it (build #3) via cwm. If no imei, making a cwm backup and restoring it is the working solution.

I flashed PA build #4 in TWRP and IMEI and baseband is still missing like in CM11. I did the backup and restore fix in CWM but it's still missing.
IMEI and baseband does show up normally in Sony 4.3, just not custom roms.
So, I have tried SlimKat, CM11-LBL and PA build #4. All show missing IMEI and basebands.

Strange! Imei missing issue is fixed in build 4. Only old cwm is not compatible. One issue mentioned about TWRP is that, doing a /system format manually before flashing creates problems.
I suggest to go through PA OP carefully and flash build 4 with newest recoveries (Philz confirmed working). Should work!

I already have flashed the newest version of dssmex's recoveries before flashing build 4.
So, this is what I did:
1. Factory reset to 4.3 through Flashtool
2. Re-root with Towelroot
3. Install newest recoveries by dssmex
4. Enter TWRP, factory reset, clear dalvik and cache and flash PA/4.4 ROM and then GApps
5. Power off, enter flashmode (green LED) and flash .205 kernel with Flashtool
6. Reboot, and 4.4 ROM boots up normally with Wi-Fi working, IMEI and baseband missing.
Is there anything that I'm doing wrong?

Steps are correct. Try flashing build #4 with Philz. Many have confirmed it's working with Philz (checkout the responses in PA thread). If still not working, I don't know what's going on .
Edit: just thinking.. whether c5303 kernel is causing an issue on your c5306 phone?? (You got your imei once but Wi-Fi modules didn't load while on stock 4.3 (c5306) kernel + cm-11 ROM no?). Can test this by flashing the given c5303_205 stock kernel (which is meant for cm-11/PA) while on your imei working 4.3 (c5306_205) stock ROM. If imei issue crops up, then we know it's the cause.
OR if you're now on PA/Slim/cm-11-lbl (and no imei), other thing you can do to test is flash a c5306_205 stock kernel while on that custom ROM. If imei appears, it's clear that the different kernel is causing the issue (but, expect Wi-Fi modules not to load!)
*Hope I'm not confusing you.. if you're not fed-up of this issue yet ()and interested on testing things, just save all the .ko files found in /system/lib/modules of your working stock 4.3 ROM to somewhere (sdcard), so can try those later with c5306 kernel + custom ROM. (But I have no idea whether it will work).
But first thing is to make sure that flashing PA build #4 with Philz doesn't solve the issue
@others
Any idea why this strange imei issue??

Yeah, flashing with PhilZ still doesn't fix IMEI.
This isn't confusing for me, so I'll let you know about these tomorrow, but two things:
- I can't find the C5306 kernel, is leaving the kernel the way it is (not flashing C5303) fine?
- To re-install .ko files do I just place them in that same directory with a file manager?
EDIT: Yup, flashing .205 kernel for C5303 on stock 4.3 erases IMEI.

pixielikescandy said:
- I can't find the C5306 kernel, is leaving the kernel the way it is (not flashing C5303) fine?
Click to expand...
Click to collapse
-yes, leave the c5306 kernel as it is (don't flash c5303 kernel after custom ROM flashing, just reboot).
So, what you can do is, flash eg. PA build #4 with Philz, while on c5306_205 kernel/ROM (working imei), and reboot without flashing c5303 kernel. Hope imei not missing!
Then, if Wi-Fi not working, try copying those 4.3 .ko files to the same place (overwrite) and make sure file permissions are 644 (rw-r--r--). Reboot, hope Wi-Fi works! (Not sure about that really.. ). Try modprobe and lsmod commands to see what's happening..

The IMEI appeared when I flashed PA with C5306 kernel, but I haven't done the Wi-Fi fix yet.

pixielikescandy said:
The IMEI appeared when I flashed PA with C5306 kernel, but I haven't done the Wi-Fi fix yet.
Click to expand...
Click to collapse
If you have time, can read the section 6 in the following link, to have an idea why kernel modules won't load if the base kernel is different.
http://www.tldp.org/HOWTO/html_single/Module-HOWTO/
Copy those matching 4.3 .ko files (and set perms) and see what happens..

Thank you so, so much! wlan.ko from 4.3 fixed it. PA is now running with both SIM and Wi-Fi working.

Installed bagyuz's CM11 on locked bl recently. Loving it.
Just set ART, and now dolphin seems to fly instead of swimming.
Issues I need help with:
a. How do one lock the 5 buttons (on homescreen) above the nav bar?
b. the quick launch button (the one you get when you swipe up the home button) - I get the same 3 buttons on locked and unlocked screen. I can't seem to activate the quick launch for locked screen...

[Q] I9000 2.3.3 CM installation Assistance needed

I hate to post a thread about this.
But I searched and searched but cannot find the particulars of what I need help with specifically.
I wouldn't have registered if I didn't think I could get around it without some help.
Here is the situation.
Galaxy S GT-I9000 came with Android 2.3.3 installed, No further updates are on offer when I try to update.
Phone is slow and aweful, Going to install CM
What I have.
CM installer, PC and Android applications.
Heimdall client 1.4.0 in Zip.
CM-10.1.2-GalaxySMTD in Zip.
Recovery-clockwork-2.5.1.2-galaxys
And that Windows C++ thing (I have no idea what it is for, Tutorial just told me to download it)
The exe I downloaded and installed is vcredist_x86
Now then, Because the tutorials I've read mention the phone being either 2.2.3 or 2.3.6 but not 3.3
causes me concern, I do not know what I am doing, I do not want to risk muddling my way through,
I would like to get the installation of Cyanogen done as quickly as possible as my phone is in Limbo
I did a factory reset after backing everything up, I have lost all Marketplace apps but still have the apps from Amazon.
I request the help of somebody with experience with installing roms on this particular phone,
I tried the CM installer from Amazon and from the website directly, Both when used in conjunction with the PC installer
simply told me that my device was not supported.
This leaves me with trying futile diagnostics to try and make it work, however as my phone is my modem
for internet use, I really cannot have a phone in limbo on this issue.
As for the custom installation well, I don't know where to begin,
I really have no idea what ClockworkMod recovery really is, or how I install it, I have never "rooted"
Anything besides a PSP before, and the fact the tutorial just tells me to "root" to get CWM installed
just opens up a whole new can of worms and more reading that just further confuses and frustrates me.
Please if anybody can help, and put things in straight forward terms, I would greatly appreciate it.
I hope the info provided is sufficient any further questions, ask

try this thread
http://forum.xda-developers.com/showthread.php?t=2434225
make sure to read everything till the end before u do any flashing.

sirus3002 said:
try this thread
http://forum.xda-developers.com/showthread.php?t=2434225
make sure to read everything till the end before u do any flashing.
Click to expand...
Click to collapse
I Thank you for finding that, as I did not, But I did read it last night and tried my best. The results are not good.
It's pretty much just leading to me downloading more software, then google searching how to use it. and it just goes on. an unending can of worms.
Install CM11 okay simple enough, First get Clockworkmod Recovery, Okay, CWM needs Root, Okay? How do I root? Well get Odin and Flash this Rom you never heard of, and to use Odin you first need to get CWM and use Heimdall and then Root and then Heimdall and then Odin then CWM then Root then Odin then Heimdall then Flash Image then Partition thingy stuff and more jargon then root Heimdall Flash CM then Put CWM on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't get me started on a tutorial where I lookup another tutorial for software mentioned in first tutorial, that tells me to download some rom or hack or piece of software, that is a file I NEVER heard of, and needs an Unzipper, or something.
I'm not being deliberately inept, I just cannot do this unless it's step by step and comprehensive, Not to mention I cannot go downloading stuff I end up not needing, or simply has no use, Phone data is not cheap.

It is really simple.
Do the following (assuming you want to install Cyanogenmod 9 (ICS)):
Download XXJVU (Firmware)
Download Odin 1.83 (latest supported version for I9000)
Make sure the Samsung USB Drivers are installed
Disable/uninstall KIES
Backup your contacts/sms/pictures etc
Boot into Download mode (Volume down + Home + Power)
Open Odin
Unpack XXJVU. You will get 3 files
Click PDA and choose the *CODE.tar file
Click CSC and choose the *CSC.tar file
Click PHONE and choose the *MODEM.tar file
Make sure re-partition is not checked
Connect your device to your computer
Click Start and wait (A box will turn green and will say PASS!)
Then you need to Root your device in order to install a custom ROM
Download CF-Root
Open Odin
Click PDA and choose the file you downloaded
Boot into Download mode and connect your device to your computer
Click Start and wait
Now to install the custom ROM do the following:
Download CyanogenMod 9.1.0
Boot into Recovery (Volume up + Home + Power)
Wipe Data, Cache & Dalvik Cache
Select Install from SD card and then select the ROM you downloaded
Select Yes and wait (your device will reboot and then boot in your new ROM)
For a more detailed guide read this.

kalpetros said:
It is really simple.
Do the following (assuming you want to install Cyanogenmod 9 (ICS)):
Download XXJVU (Firmware)
Download Odin 1.83 (latest supported version for I9000)
Make sure the Samsung USB Drivers are installed
Disable/uninstall KIES
Backup your contacts/sms/pictures etc
Boot into Download mode (Volume down + Home + Power)
Open Odin
Unpack XXJVU. You will get 3 files
Click PDA and choose the *CODE.tar file
Click CSC and choose the *CSC.tar file
Click PHONE and choose the *MODEM.tar file
Make sure re-partition is not checked
Connect your device to your computer
Click Start and wait (A box will turn green and will say PASS!)
Then you need to Root your device in order to install a custom ROM
Download CF-Root
Open Odin
Click PDA and choose the file you downloaded
Boot into Download mode and connect your device to your computer
Click Start and wait
Now to install the custom ROM do the following:
Download CyanogenMod 9.1.0
Boot into Recovery (Volume up + Home + Power)
Wipe Data, Cache & Dalvik Cache
Select Install from SD card and then select the ROM you downloaded
Select Yes and wait (your device will reboot and then boot in your new ROM)
For a more detailed guide read this.
Click to expand...
Click to collapse
Well it is simple when people like you write well paced yet comprehensive guides, Good news too, I got my internet connection back so I can download all the tools, stick em in a folder and get down to business.
I am guessing you can install any version of CM (Jelly Bean, Kit Kat etc) So long as it is the correct build for the correct phone (in this case GT-i9000)
Odin is better than Heimdall? I have Heimdall already, I'll grab the USB drivers, I don't remember if I even downloaded them, if I did I wouldn't know what they were called at the time.
The Wiki returns results on Odin saying things such as "Unofficial leaked software" blah blah something about Heimdall being more user friendly.
Anyway I will read the guide and hope it all goes smooth from now on

It is not advised to install the latest versions of CM (i.e. JB or KK) straight from stock because you might lose your IMEI.
The correct way is to install ICS first and the JB or KK.
Heimdall is good but for someone who never flashed a ROM before ODIN is the way to go.

kalpetros said:
It is really simple.
Do the following (assuming you want to install Cyanogenmod 9 (ICS)):
Download XXJVU (Firmware)
Download Odin 1.83 (latest supported version for I9000)
Make sure the Samsung USB Drivers are installed
Disable/uninstall KIES
Backup your contacts/sms/pictures etc
Boot into Download mode (Volume down + Home + Power)
Open Odin
Unpack XXJVU. You will get 3 files
Click PDA and choose the *CODE.tar file
Click CSC and choose the *CSC.tar file
Click PHONE and choose the *MODEM.tar file
Make sure re-partition is not checked
Connect your device to your computer
Click Start and wait (A box will turn green and will say PASS!)
Then you need to Root your device in order to install a custom ROM
Download CF-Root
Open Odin
Click PDA and choose the file you downloaded
Boot into Download mode and connect your device to your computer
Click Start and wait
Now to install the custom ROM do the following:
Download CyanogenMod 9.1.0
Boot into Recovery (Volume up + Home + Power)
Wipe Data, Cache & Dalvik Cache
Select Install from SD card and then select the ROM you downloaded
Select Yes and wait (your device will reboot and then boot in your new ROM)
For a more detailed guide read this.
Click to expand...
Click to collapse
kalpetros said:
It is not advised to install the latest versions of CM (i.e. JB or KK) straight from stock because you might lose your IMEI.
The correct way is to install ICS first and the JB or KK.
Heimdall is good but for someone who never flashed a ROM before ODIN is the way to go.
Click to expand...
Click to collapse
The IMEI on the device itself that allows you to use cellular networks or just the copy google and all those apps sneakily grab?
It really reminds me of flashing a PSP ah, so un-straightforward it was amazing I didn't screw up.
Btw the Rom had Odin 1.8.3 already damn, I got two copies.
Well I have everything I need, I already wiped and backed up my phone, still have my USB files on there, no doubt they will be gone when I do the reboot wipe.
Oh wait, I got CF and I downloaded Clockworkmod recovery a few days ago, Hope they are correct.
I take it that when I complete installation all the google stuff gets put back on from the stock rom?
On a final note, aside from needing more speed, I really look forward to trying those privacy features or apps that can restrict access to personal info, and also keep my IMEI out of access, from Play store or anywhere else, I was pretty furious that such a unique ID that nobody but your cellular provider has the right to know is so easily leaked out on smartphones.

NeedHelp9000 said:
The IMEI on the device itself that allows you to use cellular networks or just the copy google and all those apps sneakily grab?
Click to expand...
Click to collapse
Your device's IMEI.
NeedHelp9000 said:
Oh wait, I got CF and I downloaded Clockworkmod recovery a few days ago, Hope they are correct.
I take it that when I complete installation all the google stuff gets put back on from the stock rom?
Click to expand...
Click to collapse
You don't need to separately download Clockworkmod recovery. CF-Root includes it.
If you want all the Google stuff you need to download Gapps (Google Apps) and flash it through Recovery.

kalpetros said:
Your device's IMEI.
You don't need to separately download Clockworkmod recovery. CF-Root includes it.
If you want all the Google stuff you need to download Gapps (Google Apps) and flash it through Recovery.
Click to expand...
Click to collapse
So to be clear, Once I install Cyanogen ICS I will not have access to the Market/Playstore until I flash the Gapps package onto the phone?
Update. CF installed, ICS installed, stuck in boot loop till I reinstalled from sd card (ACTUAL sd Card)
I dunno what to think of Cyanogen Mod so far, I was hoping it would have more choice of skins/launchers, particularly just classic stock Android, Anyway the original ROM is gone, So I now have CF+Stock or CM9
The CWM app is gone since I installed CM9 but the Droid Superuser is still there, Is there anything more besides getting access to my apps (Skype fb dropbox etc) That I need to install? one thing I do want to get done is find out what Privacy permissions thingie is best, I heard about LBE but couldn't use it, Now I can, any opinions?
By the way I cannot express how good this tutorial is, it's probably as easy as the CM installer app.
That means Job Well Done!!!!

NeedHelp9000 said:
So to be clear, Once I install Cyanogen ICS I will not have access to the Market/Playstore until I flash the Gapps package onto the phone?
Click to expand...
Click to collapse
Exactly.
NeedHelp9000 said:
Update. CF installed, ICS installed, stuck in boot loop till I reinstalled from sd card (ACTUAL sd Card)
I dunno what to think of Cyanogen Mod so far, I was hoping it would have more choice of skins/launchers, particularly just classic stock Android, Anyway the original ROM is gone, So I now have CF+Stock or CM9
Click to expand...
Click to collapse
You now run the CyanogenMod 9 ROM with the CyanogenMod 9 Kernel. CF-Root and the stock ROM are gone.
There are a lot of themes for CyanogenMod 9. See this.
NeedHelp9000 said:
The CWM app is gone since I installed CM9 but the Droid Superuser is still there, Is there anything more besides getting access to my apps (Skype fb dropbox etc) That I need to install? one thing I do want to get done is find out what Privacy permissions thingie is best, I heard about LBE but couldn't use it, Now I can, any opinions?
Click to expand...
Click to collapse
You don't need to install anything else.
NeedHelp9000 said:
By the way I cannot express how good this tutorial is, it's probably as easy as the CM installer app.
That means Job Well Done!!!!
Click to expand...
Click to collapse
Thanks!

kalpetros said:
Exactly.
You now run the CyanogenMod 9 ROM with the CyanogenMod 9 Kernel. CF-Root and the stock ROM are gone.
There are a lot of themes for CyanogenMod 9. See this.
You don't need to install anything else.
Thanks!
Click to expand...
Click to collapse
I put the stock ROM back on, the CM keyboard and weird touch sensitivity was annoying, Also no file explorer or task manager or anything that showed how much Ram was being used, It's just too un-ergonomic.

There are a lot of file explorers that you can download from the Play store that are hundreds of times better than the stock Galaxy S explorer. If you want a ROM with a built-in file explorer try CyanogenMod 11.
To see how much RAM is being used go to Settings -> Apps -> Running.
If you don't like the default keyboard you can always download a better one from the Play Store.
There are also hundreds of different ROMs to try that are way better than the stock ROM.

kalpetros said:
There are a lot of file explorers that you can download from the Play store that are hundreds of times better than the stock Galaxy S explorer. If you want a ROM with a built-in file explorer try CyanogenMod 11.
To see how much RAM is being used go to Settings -> Apps -> Running.
If you don't like the default keyboard you can always download a better one from the Play Store.
There are also hundreds of different ROMs to try that are way better than the stock ROM.
Click to expand...
Click to collapse
So there is no way to actually migrate your stock apps with you to CM from Gingerbead 2.3.6?
So this CF root what is that exactly? Just root access and superuser? because one thing I would like to be able to do is disable IMEI access before setting up a google account to install apps.
As I mentioned before, I am going to have another go at CM when I have the time, it's just a pain modding a phone you regularly use, I think at this point though even Cyanogen cannot improve my phone's performance, the battery sucks, everything force closes, slower than the phone I had before I bought this one, essentially..
Android gives me a headache these days..
By the way I've passed on your guide to others who have Galaxy phones and express an interest in rooting,
They would want to know about how to do it for more recent models, so you might at some point get people asking you for help

NeedHelp9000 said:
So there is no way to actually migrate your stock apps with you to CM from Gingerbead 2.3.6?
So this CF root what is that exactly? Just root access and superuser? because one thing I would like to be able to do is disable IMEI access before setting up a google account to install apps.
As I mentioned before, I am going to have another go at CM when I have the time, it's just a pain modding a phone you regularly use, I think at this point though even Cyanogen cannot improve my phone's performance, the battery sucks, everything force closes, slower than the phone I had before I bought this one, essentially..
Android gives me a headache these days..
By the way I've passed on your guide to others who have Galaxy phones and express an interest in rooting,
They would want to know about how to do it for more recent models, so you might at some point get people asking you for help
Click to expand...
Click to collapse
CF-root is a kernel & custom recovery package. TW based apps can not be migrated to custom ROMs, but many other can. If your apps are synced with your Google account, every custom ROM that uses GApps will automatically reinstall your apps short time after first reboot. It takes me about 30min to setup whole the phone in the new OS. Use my sticky thread on this section for another info, especially regarding backups. Try Mackay ICS CM9 2014, you won't belive it is the same phone.
tetakpatalked from Nexus 7 flo