Develop Bugs

Firmware upgrade for dummies (from P1000XXJID to P1000XXJK5)

This is my guide for dummies:
INTRODUCTION: I'm an italian user with a standard Samsung Galaxy Tab purchased via Vodafone. I would like to upgade my firmware from P1000XXJID to P1000XXJK5. I search in XDA and in samfirmware and this is the sequence of my upgrade.
1. You need some software.
a. KIES software (from www.samsungmobile.com): download and install
b. P1000XXJK5.rar (from www.samfirmware.com): download and unzip (use WinRar and password is "samfirmware.com")
c. NEW Odin: DOWNLOAD Version 1.7 (from www.samfirmware.com)
2. unzip New Odin 1.7 and run "Odin3 v1.7.exe"
3. Press the [PIT] button and select the "P1_20100909.pit" file
4. Press the [PDA] button and select the "P1000OXAJK5.tar" (which was in the 'P1000XXJK5.rar' file - see 1.b.)
5. Put a cross-chek on 'Auto Reboot' and 'F. Reset Time' (NOT on 'Re.Partition')
6. Now we are ready to flash our Galaxy Tab:
a. power off the device
b. extract SIM and SD card (if you have one)
c. power on the device pushing 'Volume down' + 'Home' + 'Power button'
d. the device will start in dowloading mode (yellow triangle)
7. Connect your usb cable (if you have correctly installed the KIES software, drivers are ok and device is recognized by the PC)
8. In Odin you must see on the left "0:[COM3]" (yellow background), or something like that
9. Press [START] and wait till has finished (4 minutes); Odin will reset the device itself.
10. After boot check if all is ok using *#1234# code
PS: I have found all my apps, no backup/restore needed ! But this is my case...

( trying to update to -> P1000XXJK5 )
Hi,
thx
but I the device gave me an error.
update media, please wait
e:can't mount /dev/block/stl10 (invalid argument)
E:copy_dbdata_media:can't mount DBDATA
your storage is not prepared yet. please use UI menu for format and reboot actions...
any help thats my device before I tried to update
PDA
P1000XWJJ3
Phone
P1000XXJID
CSC : P1000CPWJJ3
Build Time : 2010.10.07
Changelist : 615445

dorenthe said:
( trying to update to -> P1000XXJK5 )
Hi,
thx
but I the device gave me an error.
update media, please wait
e:can't mount /dev/block/stl10 (invalid argument)
E:copy_dbdata_media:can't mount DBDATA
your storage is not prepared yet. please use UI menu for format and reboot actions...
Click to expand...
Click to collapse
No problem, theres two ways to fix this:
1: Flash the full JJ4 firmware with the P1_20100909 file and check partition
Then let it reboot, and flash JK5 after that without the .pit and partitioning on..
2: just flash the dbdata.tar from the end of this post:
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
I'd do option #1, I think you need to have JJ4, coming from your older version (pre-JJ4)
This is also for anyone flashing a non-European Tab:
so steps:
3.1 Press the [PDA] button and select the "P1000XWJJ4.tar"
3.2 Put a cross-check on 'Partition', 'Auto Reboot' and 'F. Reset Time'
3.3 Do steps 6-9
.

usa
What benefits does this give us in usa? thx

kevinniven said:
What benefits does this give us in usa? thx
Click to expand...
Click to collapse
Hi, in my european Tab I notice a little better 'scroll speed' between home screens (horizontally scroll). It's the only advantage, IMHO (In My Humble Opinion).
Please remember that for 'usa TAB' you have different firmware; consult www.samfirmware.com

I ran the update on my tab from the UK, specs beforehand were:
PDA XWJJ3
Phone XXJID
CSC CPWJJ3
Click to expand...
Click to collapse
After flashing directly to JK5 it rebooted happily although it basically did a factory reset (formatted the internal SD card - which is a pain as that's where Titanium Backup put its backups)
Firmware specs now are:
PDA XXJK5
Phone XXJK5
CSC XAJK5
Click to expand...
Click to collapse
It does look like there's a number of missing applications, so I'm going to get the full JJ4 package and flash that and then put JK5 over the top of it.
So while it works and does feel a bit snappier, it's not what I'd call a huge success going straight from JJ3 to JK5 I'll get there though.
EDIT: Before I did the flashing, I did a factory reset and the "missing" apps popped up, so while it looks like it's not entirely happy going from JJ3 to JK5, it does appear to work ok.
I'm still going to put JJ4 on there just for the heck of it and then reflash to JK5.
Looks like JJ4 defaults to Russian:
PDA: XWJJ4
Phone: XXJID
CSC: SERJJ2
Click to expand...
Click to collapse
Final Edit:
Nope, no noticable difference having gone from JJ3 to JK5 or JJ4 to JK5, other than having to manually do a factory reset to get everything behaving after having gone from JJ3 to JK5.
Fair warning, I may have done something wrong, but if not, it WIPES your internal user storage when you do the update!
Still, happily on JK5 now, not a big deal to re-transfer my stuff over.

Thank for this thread.
But why would someone not choose to upgrade firmware when Samsung releases it via KIES?

sanderh said:
Thank for this thread.
But why would someone not choose to upgrade firmware when Samsung releases it via KIES?
Click to expand...
Click to collapse
Because Samsung have a history of not releasing official updates.
Plus, we want new stuff NOW

Big thx to you rotohammmmmmmer ...

I suggest to do also the following after the first boot: *#272*your imei# (dial all your imei digits!),then select your original Sales code,in my case for Italy Itv.This allow you to have all the Samsung Apps of your country.
Also the problem with the missing data at boot is because JK5 isn't a full flash.you can also flash the JJ4 with repartition and then JK5 without.
For newbies: Make a Titanium Backup before the 272 code!! (thanks to brunino1967 to remind me, I forgot to mention )
Sent from my GT-P1000 using Tapatalk

knightnz said:
After flashing directly to JK5 it rebooted happily although it basically did a factory reset (formatted the internal SD card - which is a pain as that's where Titanium Backup put its backups)
Click to expand...
Click to collapse
You can change where Titanium sticks it's backups by going to
Preferences/Backup folder name
and change it to
/external_sd/TitaniumBackup
Or if you've got the full version you could have sync'd your backup to Dropbox.

I also have JJ3. I think I will follow the suggestion to install JJ4 first with the repartition and then JK5. If I backup all my system data and apps to the external SD card (or Dropbox) using Titanium Backup, is it OK to restore the system data as well after the upgrade or might there be some conflict with the new version? TBH I don't realy know what the system data is so may you will tell me I only need to restore the apps.
TIA

How languages are included in this ROM? I need Polish.

vahanara said:
How languages are included in this ROM? I need Polish.
Click to expand...
Click to collapse
Yes in P1000XXJK5 there is "polski".

zerocool76 said:
I suggest to do also the following after the first boot: *#272*your imei# (dial all your imei digits!),then select your original Sales code,in my case for Italy Itv.This allow you to have all the Samsung Apps of your country.
Also the problem with the missing data at boot is because JK5 isn't a full flash.you can also flash the JJ4 with repartition and then JK5 without.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Advice for all newbies: please be carefull with this code *#272... etc etc.
because if you apply it, you will have a wiped SGT and it will go back at factory status (I mean that the default apps will be there but no one of your already downloaded apps will be there !). You will have your home screen reset to default too. If you have the fortune, like it has been for me, to see your SGT (after the firmware update) restart as it was before (with all your apps, etc.) don't use this code.
Obviously if your installation is not complete and you wish to have all default/factory installed apps, use this code.

sooooo say u do this and it reboots but gets stuck at the samsung logo and vibrates every few seconds. what does that mean?.....and how do u fix it? i really hope i dont gotta reflash and repartition...if so.....FAAWWKKK!
update:
flashed dbdata.rfs.tar from:
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
end of the first post
still waiting for the results.....

Guys did the update but now cant download from market what's happened

Difference from xxjid and xxjk5 ?
Sent from my GT-P1000 using XDA App

brunino1967 said:
Advice for all newbies: please be carefull with this code *#272... etc etc.
because if you apply it, you will have a wiped SGT and it will go back at factory status (I mean that the default apps will be there but no one of your already downloaded apps will be there !). You will have your home screen reset to default too. If you have the fortune, like it has been for me, to see your SGT (after the firmware update) restart as it was before (with all your apps, etc.) don't use this code.
Obviously if your installation is not complete and you wish to have all default/factory installed apps, use this code.
Click to expand...
Click to collapse
Guys, who is doing a flash needs to make backups!!! Use titanium before flashing or apply 272 code and so on. If for example you are flashing with re-partition you will lose not just the apps but also the entire content of your internal sdcard.With 272 code you will lose the apps but no the sdcard content.You can restore everything with Titanium Backup.

norm2002 said:
I also have JJ3. I think I will follow the suggestion to install JJ4 first with the repartition and then JK5. If I backup all my system data and apps to the external SD card (or Dropbox) using Titanium Backup, is it OK to restore the system data as well after the upgrade or might there be some conflict with the new version? TBH I don't realy know what the system data is so may you will tell me I only need to restore the apps.
TIA
Click to expand...
Click to collapse
Sorry to ask again but is there anyone who can help me with this? I am nervous of making a mistake.

Samsung Galaxy Gio GT-S5660M Discussion - Rooted Stock ROM, Partition Mapping

(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado

Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!

Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado

Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado

Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.

I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.

Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.

red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?

Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!

steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty

Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.

red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425

I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)

Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks

Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?

steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App

Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....

Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...

ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..

waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.

[RECOVERY]Samsung Galaxy W i8150 RZRecovery

I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
DOWNLOAD
TEMPORARY LINK .... USE THIS IF FIRST ONE DOESN'T WORK
THANKS TO andynroid FOR PROVIDING LINKS!
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!

great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?

Will this work on the Samsung Exhibit II?

thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..

klingel_One said:
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Click to expand...
Click to collapse
I've tested it and it works
radgoos said:
Will this work on the Samsung Exhibit II?
Click to expand...
Click to collapse
I wouldn't bet that this will work on Exibith II cause every phone has different partitions.

after giving me the command you said to me reacts to: permission denied.. Whi?

lipanz said:
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
Click to expand...
Click to collapse
Definitely...BTW can anyone adv us the rooting method Odin or....

can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu

qzem said:
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
www.rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-ancora-rec.img
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
Click to expand...
Click to collapse
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?

Do I need to have stock ROM for it to work?

snake873 said:
after giving me the command you said to me reacts to: permission denied.. Whi?
Click to expand...
Click to collapse
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
irishpancake said:
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Click to expand...
Click to collapse
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
nakTT said:
Do I need to have stock ROM for it to work?
Click to expand...
Click to collapse
Do you know any custom rom for our phone ? But no it is not rom related.
snake873 said:
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
Click to expand...
Click to collapse
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.

qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Do you know any custom rom for our phone ? But no it is not rom related.
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
Click to expand...
Click to collapse
From computer
---------- Post added at 12:09 PM ---------- Previous post was at 11:41 AM ----------
ahahaha ok ok I did thank you very much for your patience

qzem......top marks for your persistence
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Click to expand...
Click to collapse
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
File: RZR-2.1.4-ancora-rec.img
Size: 5230592 bytes
Publisher: Unknown
Checksum (MD5): 3b9cc641aa898910b5bad911bd38f675
*File generated by MD5 Checksum Tool*
http://www.novirusthanks.org
Click to expand...
Click to collapse
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.

irishpancake said:
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
Click to expand...
Click to collapse
Well I really don't know that is better to use Kies or Odin. If you want official and (what is supposed to be tested) firmware, tha you better use Kies (but well even with kies your phone could get bricked, I've learned that from one user here ). If you want to flash latest firmware, which sometimes is not availible on all the countries, and you can't get it from Kies fast enaught, than I suggest odin is the choice. I prefere Odin, cause I don't like official stuff .
To use Odin is very simple. You need to turn on phone with Volume Down + Home + Power. When you are prompt (on hte phone),wether to conutioue od cancle, you connect phone and computer with USB cable, and choose contuinu, now you are in download mode. Then all you have to do, to choos proper .ops file (button OPS) in odin, an proper firmware (usually you choos that under One Package button, if you have one package in tar.md5), then you wait for chekcking md5. When is checked you just click Start, and wait for stuff to happen.
Don't forget that there is a possabiltiy that something might go wrong with flashing, but it is not that big one. I suggest, that you first made full nandorid backup with recovery, if something goes wrong, you can boot you phone in recovery and restore it totaly. And one more suggestin when flashing, do it with latop(if possible), so that you have battery and power cable plugged in laptop, if electricyty goes out, that you still have battery to run laptop.
And thanks for the support you guys are showing to me, since I'm not a developer. I try really hard, to get people that are willing to help us developing better roms for our phone !

qzem said:
There are two possible reasons for this either you
Do you know any custom rom for our phone ? But no it is not rom related.
Click to expand...
Click to collapse
Spot on. I just need to know if it is ROM related (that I need a ROM file on my PC).
Thanks for the reply.

Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!

Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance

fender90 said:
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Click to expand...
Click to collapse
For adb, you need to download Android SDK from here. Download zip file and extract it somwhere. Than go in folder where you have extract it and run SDK Manager, from there you will install adb rivers and everything else. When you are done (it could take a while, to download and install everything), open Command promnt and follow the instrucions I've wrote in first post.
klingel_One said:
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
Click to expand...
Click to collapse
The same goes for mac users, there is also Android SDK for mac. You can install Kies before this, but you need both because kies includes drivers for this phone exactly. As far as recoverey goes, if it is not included in ROM, which you flash, I think you'll need to install it again. I hope that developers will include recovery in their roms.

Thanks so far qzem,
It seems like theres someone in your Cyanogenom-Forum-Post qzem, who is trying and willing to help making a custom rom. But he seeks for som guidance!
Perhaps someone with experience like, arco can take him under his wings!

Hi there,
i would like to thank you. Everything works like a charm.
Did the flash, tried the recovery.. and uaaaahhhh....
...i forgot to backup the original recovery!
can someone please, please upload it to somewhere??
thx.
Zetup-EXe

[Q] Brand new T999V running Cyanogenmod 10, camera doesn't work! Please help!

*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.

Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?

KingKostas said:
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
Click to expand...
Click to collapse
May I ask quickly what steps are involved in "reflashing"? Just to make sure I don't do some extra step or miss something.
As far as the stable version goes, I looked for the d2tmo file on get.cm under the Stable tab. I'm assuming that would be the most stable build?
(Perhaps a nightly might fix it??)
Question: Is there not a way I can just install/add this "4.2" camera? I've seen videos and read that people are using that just fine on CM10. Alternately if I boot into recovery would "fix permissions" be any help?

re: odin flash
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone
or restore any backups unless the the backup is corrupted in some way or another.
Here is the link to the Tmobile Stock & Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Here is a step by step guide for you.
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)

Misterjunky said:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
Click to expand...
Click to collapse
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!

re: camera issue
Malumen said:
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
Click to expand...
Click to collapse
Just download any of the custom rom zip files based on the jellybean v4.1.1 stock rom.
All of those custom roms will have the files you are looking for.

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

d2vzw
This also works on the sch-i535 as well. Thank you so much.

kingsugar said:
This also works on the sch-i535 as well. Thank you so much.
Click to expand...
Click to collapse
Yes, I tried all the other options for getting my camera back on track, but only going back to a full stock (rooted) ROM got my camera up and running again. FWIW, I was running an AOSP ROM for months without issue. What kicked my camera offline (the dreaded can't connect to camera) for some strange reason was when I updated to the most recent firmware VRBMF1. Now its straight back to AOSP for me! Thanks for creating this post! Very helpful!

My fix
I'm going around posting my fix to all the camera threads in hopes of helping people find a solution sooner. I created a thread over in d2vzw http://forum.xda-developers.com/showthread.php?t=2492304

fix camera error on i9300 with cm 9 (4.0.4)
Malumen said:
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Click to expand...
Click to collapse
thanks a lot, i read your post, i take your advice to copy "SlimISP" to built in (cm system) folder, its work for me perfectly.
Thanks a lottttttttttttttttttttttt, have a nice day.

Explain like I'm a three year old, I beg of you.

I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.

Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.

I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.

I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.

tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.

I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...

Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs

xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?

tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs

Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew

azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.

azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs

bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!

So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...

tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.

Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...

tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.