yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] jevan24:
Did you Odin to stock ics before you started all this? I think you need the stock ics bootloader first but I'm not one hundred percent positive.... Someone backup this statement please.

Sent from my cm10.1 wonder
[Samsung Captivate Glide] Cory_branch:
Yep i believe i found away to fix it but im having trouble saving my efs folder
[Samsung Captivate Glide] jevan24:
http://xdaforums.com/showthread.php?t=2019540

Sent from my cm10.1 wonder

---------- Post added at 11:51 PM ---------- Previous post was at 11:43 PM ----------

See if this guide helps on the efs subject.

Sent from my cm10.1 wonder
[Samsung Captivate Glide] ninthsense:
whats the issue you found ?
[Samsung Captivate Glide] Cory_branch:
the efs folder is getting wiped but im not sure what to do about it
[Samsung Captivate Glide] ninthsense:
First and foremost make a backup of your EFS folder using the utility mentioned in the post http://xdaforums.com/showthread.php?t=1308546 while you are running ICS.

Then if you are brave enough to try, you can install JB ROM and restore your backed up EFS with the same utility.
[Samsung Captivate Glide] Cory_branch:
My ics backup was corrupted Im stuck on gingerbread i have to update with kies but im stuck on the infinite connecting
[Samsung Captivate Glide] jevan24:
Since your backups were from a different cwm and you flashed a new one they won't work. But you may be able to flash the old one you had and restore your ics.

Sent from my cm10.1 wonder
[Samsung Captivate Glide] Lysander:
I have the same problem and restoring it doesn't work. The ROM thinks it's invalid/missing and generates non-working EFS files.

---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------

I'm wondering if there's some way to make the EFS partition read-only.
[Samsung Captivate Glide] ninthsense:
Well the list of 'unknown baseband' users are increasing. So first we need to find the common thing between them to probably arrive at the problem source.

Did anyone of you ever upgraded through the original one click provided by samsung ?

Or does anyone who did not use one click to upgrade is able to run JB roms withou the baseband issue ?
[Samsung Captivate Glide] Cory_branch:
I only used kies to update to ics no other updatez
[Samsung Captivate Glide] ninthsense:
Follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/ and report back..
[Samsung Captivate Glide] Cory_branch:
I have already flashed the official ics earlier today after having cprrupted backups is that really necessary
[Samsung Captivate Glide] ninthsense:
Don't know, hit and trial...
[Samsung Captivate Glide] roothorick:
So the speculation is that /efs is getting corrupted/wiped?

Should be easy to test... go back to a working ROM, copy the contents of /efs somewhere, flash non-working ROM, copy the backup back... make sure you get the permissions right too.

P.S. We could use a full logcat from a non-working ROM. Might be some clues in there.
[Samsung Captivate Glide] Lysander:
I have tried restoring /efs from manual backup (fixing permissions with Root Browser) and from an IMG and a TAR using EFS Pro. Nothing works; it's always detected as missing/invalid on the next boot and "restored" to the non-working dummy files by Android according to the nv_ log file.

I will try to get a logcat file -- should it be right after first boot of a non-working-efs ROM? or what?
[Samsung Captivate Glide] ninthsense:
Yup...
[Samsung Captivate Glide] Lysander:
I wiped Dalvik cache, /data, and /system then installed RootBox via CWMR. Here's the logcat file (attached).

By the way, I also updated to stock ICS via keys...and it messed up my phone. At first, there was nothing but a black screen with a notification bar, then I waited overnight and it came on, with no service.

So I did it again, and it stayed black. I installed CWMR via Odin and installed a custom ROM via CWMR. That ROM worked, but still no service. So I installed a stock ICS ROM via CWMR, which worked.

Baseband and IMEI are shown correctly in ICS, except for occasional glitches which are fixed by a soft reset.
[Samsung Captivate Glide] roothorick:
So apparently RIL doesn't log to logcat. Where does it log to? I don't know. The kernel driver drops some things in dmesg (search for "misc_sec_operation") but it's probably not all that useful other than telling us the kernel component is loaded and functional.

About Phone currently shows your REAL IMEI, not the generic (004999010640000), right?

So at this point, if you flash say CM10.1 (without restoring /efs, obviously that's not working) your radio dies again? Actually try it, humor me. (-E- Check "mount" to make sure /efs is actually mounted, and read-write "rw". Make sure /efs/nv_data.bin exists. Look at nv.log for anything from today. etc. Try to find anything, anything at all, that's abnormal vs. a working phone.)

Are you unlocked? If so, via code or nv_data bitflip? -E2- Turn the phone off, remove the SIM, and turn it back on. Do your IMEI and baseband come back?
[Samsung Captivate Glide] dman3285:
Ril does logcat. Done it many times. If its not then the firmware cannot access the ril.java it needs therefore doesn't recognize any modem and or radio.

To logcat ril type in terminal while accessing adb. " adb logcat -b radio" and it will logcat your ril and radio.
[Samsung Captivate Glide] Cory_branch:
So is this a fix to the problem if so I will have to try it later since I'm in school
[Samsung Captivate Glide] roothorick:
We're still in the information gathering stage, and frankly, if you don't cooperate, we'll NEVER be able to fix this since nobody with dev knowledge has direct access to a misbehaving device.

Do "adb logcat -b radio" starting from the boot (reboot the phone and start the command while it's at the Samsung logo) and paste that here. Also follow up on everything in my previous post.
[Samsung Captivate Glide] Lysander:
The log says dev/log/system, but it apparently there's also dev/log/radio -- perhaps it doesn't include that? Anyway, I'm attaching the logcat -b radio log as requested, as well as the nv_log file (with annotations). It looks like it fails the hash check? like it thinks the bin file and md5 don't match?

Correct, on the stock ICS and Inception GB ROMs, it shows the IMEI that's printed on my phone.

I flashed this ROM (again) because I already had it downloaded and on my phone. Yep, no service, baseband and IMEI unknown.

It's not SIM-unlocked.
[Samsung Captivate Glide] Lysander:
Looking on ICS, I have four files in /sbin, but they're all zero bytes with a 1969 creation date, so it seems likely they're invalid. Probably got corrupted during the Kies update along with my /efs.

Would that stop JB from reading the baseband and IMEI, but not ICS and GB? Can I just replace those files with another Glide's?
[Samsung Captivate Glide] roothorick:
/sbin is in the rootfs, so it SHOULD be part of the kernel bootimg... which only makes the whole thing weirder. It also means any changes made won't carry between reboots.

Here's a healthy /sbin from a working device. Notice the dates.

-rwxr-x--- root root 161808 1969-12-31 18:00 adbd
-rwxr-x--- root root 113876 1969-12-31 18:00 cbd
lrwxrwxrwx root root 1969-12-31 18:00 ueventd -> ../init
lrwxrwxrwx root root 1969-12-31 18:00 watchdogd -> ../init
[Samsung Captivate Glide] Lysander:
Yeah, my files have december 31st, 1969 as the date, but the time is 7 , not 1800. I also don't have watchdogd; instead is ua_loader. All files show as 0 bytes.

So, what do I do then? Isn't boot.img part of the ROM? I see it in the rootbox ROM zip, at least.
[Samsung Captivate Glide] dman3285:
Boot.img consist of a zimage and a ramdisk.img that contain the initramfs for the specific device boot init. The sbin folders containing the cbd and other binarys are symolicly linked during the build process. In the init.rc has all the commands and permissions given during the boot process. In there is a command to start cbd. And ua_loader. Watchdogd is added to 4.2.1 and shouldn't exist in 4.1.2. Check your init.rc for the command to start cbd oneshot.
[Samsung Captivate Glide] Lysander:
The only mention of cbd in my init.rc is:

service cpboot-daemon /sbin/cbd -d -o t -p 7
class main
user root
group radio cache inet misc audio sdcard_rw log

I tried running the first line as a command in terminal but it says cpboot-daemon is unknown. I don't seem to have an executable by that name on my phone. Do I have to run it somewhere other than terminal? It looks like an OO function definition or something.

At the top if init.rc I found:

# setup the global environment
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH

I assume this is the symlinking you were talking about? Several of those directories don't exist, like /vendor/bin.
[Samsung Captivate Glide] Lysander:
So, is everyone stumped?
[Samsung Captivate Glide] dman3285:
No this is not symlinking, its making boot directory paths.. symlinking is done when being built inline from source..
[Samsung Captivate Glide] roothorick:
Something jumped out at me:

E/RIL ( 107): open(nv core) fail. No such file or directory.

That's not in my logcat.

Does /efs/.nv_core.bak exist?

I don't know where the actual file that is supposed to be backed up comes from. But I've got an idea how to find it.
[Samsung Captivate Glide] roothorick:
I disagree. cbd is running and logcatting; in fact it gives us the second sign of trouble. Here's where things start to go to hell:

E/RIL ( 107): Modem_Boot:
E/RIL ( 107): check_cracking
[b]E/RIL ( 107): open(nv core) fail. No such file or directory.[/b]
E/RIL ( 107): load_md5_state: MD5 state 1
E/RIL ( 107): factorymode Error : /efs/FactoryApp/factorymode
E/RIL ( 107): md5_enable: on 1
E/RIL ( 107): check_nv_data_validity:
E/RIL ( 107): check_nv_data_size:
E/RIL ( 107): check_md5:
E/RIL ( 107): compute_md5: path /efs/nv_data.bin
E/RIL ( 107): MD5 check OK.
D/RIL ( 107): wait xmm6260_boot_hsic boot ready
D/RIL ( 107): modem status [ 0x3 ]
D/RIL ( 107): modem status [ 0x3 ]
D/RIL ( 107): modem status [ 0x3 ]
D/boot ( 106): <4>cbd: hsic_xmit_boot: PSI send ----
D/boot ( 106): <4>cbd: hsic_xmit_psi: Sent ATAT 4 byte
D/RIL ( 107): modem status [ 0x3 ]
D/RIL ( 107): modem status [ 0x3 ]
D/RIL ( 107): modem status [ 0x3 ]
D/RIL ( 107): modem status [ 0x3 ]
D/RIL ( 107): modem status [ 0x3 ]
[b]D/boot ( 106): <4>cbd: s_read: select TIMEOUT[/b]

It's all downhill from there, tons of "Connection refused" and "select TIMEOUT". It's like secril just straight-up bails early in the boot process. I think this "nv core" is somehow critical to the modem's function (a runtime-loaded firmware maybe?), and the JB secril can't find it for some reason.
[Samsung Captivate Glide] dman3285:
You can disagree all day.. but that's the error. I know as we fought with no service for days when it first booted... all of it stems from that error.. I assure u
[Samsung Captivate Glide] roothorick:
Hold it, this line isn't present on a healthy device either:

E/RIL ( 107): loadOpnameDb(): db open error

-E- I want to see dmesg too. Someone with a misbehaving device, do "dmesg > /mnt/emmc/dmesg.txt" from an affected ROM (preferably just after rebooting) and post it here. (You will have to be root btw.)
[Samsung Captivate Glide] Lysander:
I didn't have .nv_core.bak in my EFS folder. I had one in a backup of a corrupted EFS folder, so I moved it to my live EFS folder. I don't see any change.

I did dmesg twice, once after first boot, and again after rebooting. I also redid logcat -radio in case anything changed.
[Samsung Captivate Glide] roothorick:
Again, are you looking using ls -a in adb shell? They're dotfiles, they won't show up in most file managers.

There's an OOPS in this dmesg! And I do believe this is modem code!

<4>[ 5.343732] ------------[ cut here ]------------
<4>[ 5.343872] WARNING: at kernel/irq/manage.c:1158 __free_irq+0x98/0x1c8()
<4>[ 5.343940] Trying to free already-free IRQ 362
<4>[ 5.344059] Modules linked in:
<4>[ 5.344212] [<c00142f0>] (unwind_backtrace+0x0/0xf8) from [<c00528f0>] (warn_slowpath_common+0x4c/0x64)
<4>[ 5.344341] [<c00528f0>] (warn_slowpath_common+0x4c/0x64) from [<c005299c>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 5.344470] [<c005299c>] (warn_slowpath_fmt+0x30/0x40) from [<c0091314>] (__free_irq+0x98/0x1c8)
<4>[ 5.344599] [<c0091314>] (__free_irq+0x98/0x1c8) from [<c0091484>] (free_irq+0x40/0x88)
<4>[ 5.344675] [<c0091484>] (free_irq+0x40/0x88) from [<c0289744>] (xmm6260_on+0x11c/0x184)
<4>[ 5.344802] [<c0289744>] (xmm6260_on+0x11c/0x184) from [<c0287118>] (misc_ioctl+0xec/0x31c)
<4>[ 5.344931] [<c0287118>] (misc_ioctl+0xec/0x31c) from [<c00e60e0>] (do_vfs_ioctl+0x80/0x53c)
<4>[ 5.345006] [<c00e60e0>] (do_vfs_ioctl+0x80/0x53c) from [<c00e65d0>] (sys_ioctl+0x34/0x60)
<4>[ 5.345138] [<c00e65d0>] (sys_ioctl+0x34/0x60) from [<c000e100>] (ret_fast_syscall+0x0/0x30)
<4>[ 5.345263] ---[ end trace 64165b4be40cbe03 ]---

I'll have to check if this is in my dmesg. But why would the modem code be freeing IRQs? And it does seem to be at the exact point where things go to hell.

Btw, this is concerning:

<3>[ 4.189473] EXT4-fs (mmcblk0p11): VFS: Can't find ext4 filesystem

There very much so most definitely SHOULD be an ext4 filesystem on p11. It's (probably... I hope) not important in and of itself, but if that's corrupt, what else is corrupt?
[Samsung Captivate Glide] Lysander:
I'm doing this all directly on the device, not through ADB. As I said, I looked in root browser, saw no .nv_core anything, checked my EFS backup, found .nv_core.bak and .md5 and copied them to my EFS, where I can see them now in root browser.

My current EFS was, I believe, generated by a GB ROM that I flashed for that purpose.

Judging from this, .nv_core.bak, .nv_core.bak.md5 are not unique to devices and are used in SIM locks. If someone wants to share theirs (AT&T), I would be happy to try them.

Which one is that on JB/CM 10.1? I can see it in /dev/block but I'm not sure what it mounts as.
[Samsung Captivate Glide] dman3285:
You guys really have no idea what your doing do you... take your time in source and see how it builds while compiling and the obvious error will pop out. In all that log mess there is only 1 error causing your issue. All other errors are caused by that one line. Find it..The logs are a mess of nothing.
[Samsung Captivate Glide] roothorick:
What error would that be? The OS obviously had no problem finding cbd as it's up and running and outputting to logcat. Also, he didn't say anything about building the ROM himself.

---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------

Nothing is more direct than ADB. Remember that. File manager apps on the phone itself can't be trusted to see everything.

Do something like

adb shell ls -a /efs

If it's in there, your file manager is just hiding it from you.

You know, it's strange, I didn't think it got mounted at all. I wonder where it's mounted to and why.
[Samsung Captivate Glide] risis78:
I have the same problem reported in this thread.

I have unlocked my AT&T phone by code.

If I flash Stock ROM UCLJ3 the network work but when I flash a custom ROM the phone not recognize the SIM card...

I also tried to flash only the ICS lite kernel over stock rom but the problem persists...

It 's the custom kernel that going to change some file to create the problem?

EDIT:

No I do not make calls and even after restarting phone the network not work. In the baseband info there is "Unknown" text.

The strange thing is that if I install the LiteRom with the stock kernel there is always the same problem but if I going into recovery and restore only the boot that I have backupped from the stock UCLJ3 Rom with working network also in LiteRom the network works.
[Samsung Captivate Glide] aliesky:
I'd like to join

I have the same problem with JB, I'm willing to provide any information from healthy or broken system. I already tried with different baseband and nothing good so far :(

Current: Stock ICS 4.0.4

Baseband: I927UCLJ3

Kernel: 3.1.10-I927UCLJ3-CL970642
[Samsung Captivate Glide] yohan4ws:
What did you guys do to unlock your phones ??

I unlocked mine on fastgsm.com (not an advert... I unlocked my Galaxy ACE in an airport with my laptop and my glide the day I switched to a new provider...)

Just had to download the software, plug it in .. my phone has NEVER unlocked..... $15 may be priced high but it beats the headaches i've seen people go through in choosing cheap/free alternatives ..
[Samsung Captivate Glide] aliesky:
I got mine unlocked from eBay, but with GB. So, When I moved to ICS I got a already unlocked stock ROM :D
[Samsung Captivate Glide] yohan4ws:
and what exactly is the issue then when you flash a custom ROM ? .. can you flash litekernel for ICS on your current rooted rom ?
[Samsung Captivate Glide] aliesky:
When I flash a custom ROM it says "unknown baseband", I tried with 4 different ROMs but never with custom ICS. I will try to install it today.
[Samsung Captivate Glide] aliesky:
AHHH! It broke my phone again "Unknown Baseband". So, do I must assume the problem it's because the kernel?
[Samsung Captivate Glide] aliesky:
AHHH! It broke my phone again "Unknown Baseband". So, do I must assume the problem it's because of the kernel?
[Samsung Captivate Glide] aliesky:
Does anybody have a clue about what's wrong with this model or with "my phone"??
[Samsung Captivate Glide] notso34:
Unable to flash custom ROM

Did anyone ever figure this out? I have the exact same problem with the I927 I'm using stock ICS and I noticed no one has posted on this thread in a while. Is it an efs folder problem? I've been searching this forum for days trying to find a solution. Im obviously a nob. Please help.
[Samsung Captivate Glide] aliesky:
Welcome to my world :(

I bough this phone because I love the physical keyboard but with this issues I'm thinking to go for a Galaxy SII :crying:
[Samsung Captivate Glide] Cory_branch:
it is possibly a difective phone i recently got a new one and i am about to try to root today
[Samsung Captivate Glide] Cory_branch:
im not sure if the problem but i recently got a new glide and i rooted it last night and everything went smooth my baseband disappeared but came back once i reflashed the rom i am now running twmr and oacman rom and rootbox

bottom line id say its a defect
[Samsung Captivate Glide] aliesky:
But how a defective device works with Stock Rom and no with custom? Also, I installed LiteRom 0.9, my baseband disappeared, then I restored the Stock boot and baseband came back but the kernel was restored to original too. I though it was my mistake and installed LiteKernel again and once again the baseband gone.

So, it's a defective device or a defective kernel?
[Samsung Captivate Glide] Cory_branch:
im not to sure on that one
[Samsung Captivate Glide] notso34:
Ok, if you dont mind could you tell me how you rooted it and flashed it this time step by step?
[Samsung Captivate Glide] Cory_branch:
I followed this guide http://xdaforums.com/showthread.php?t=1378082

i then flashed twrp

flashed rom

wipe dalvik wipe cache

factory data reset
[Samsung Captivate Glide] notso34:
which version of twrp and how did you flash it?
[Samsung Captivate Glide] Cory_branch:
http://xdaforums.com/showthread.php?t=2093431 choose 2.4.1 odin zip download it extract it run odin hit pda and choose the recovery file that was inside the zip boot in download and start
[Samsung Captivate Glide] aliesky:
OK, I will try your way, I hope to have so luck as you.

---------- Post added at 10:55 PM ---------- Previous post was at 10:16 PM ----------

Report: No luck :crying:
[Samsung Captivate Glide] davidpartay:
Hi Aliesky,

When I rooted my phone, I managed to find one of those 'OneClick' things that does it all for you. The ROM isn't rooted, and it doesn't put CWMR on, but those are easily done afterwards using Odin.

I think this is the one that I have: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/

But I don't recall where I got it from. It may be worth running that to see if it works for you, and then install a custom rom using CWMR or whatever.
[Samsung Captivate Glide] aliesky:
Hi davidpartay,

Mine, already came with a rooted ICS "UCLJ3", so let me ask you something:

When you install custom ROM do you format /system or you just factory reset? I think I tried both but honestly I've been trying so many ways that I can't remember all of them :(
[Samsung Captivate Glide] davidpartay:
I've started doing a format /system as I was having other issues which seem to be resolved now.

I just read back and realised you're having that baseband issue... sorry but I can't help you there! Perhaps you could try flashing the Rogers radio? There were instructions on doing this somewhere.
[Samsung Captivate Glide] aliesky:
Thats exactly what i'm doing. I will try to get the Rogers radio as my last hope.
[Samsung Captivate Glide] aliesky:
I can't find it. Can somebody share it with me, ICS Rogers RADIO??
[Samsung Captivate Glide] kick buttowski:
the latest literom version has all the radios, just download decompress and search I'm currently using the rogers radio and I took it from there.
[Samsung Captivate Glide] aliesky:
Thanks but I tried all of them and still no baseband with JB. Once again, I believe the problem remains in the Kernel. If I could get a official JB kernel i could probe it but as it don't exist :(
[Galaxy S III Q&A, Help & Troubleshooting] NeoXTC:
Hi,

It's been awhile and I've tried most things and I'm still getting fairly big battery drain compared to others here on the forum :(

I was wondering if you are able to help me identify what is causing my huge battery drain? (anywhere from 2%/hr to 8%/hr)

I have here the betterbatterystats dump file. When looking through it I dont' see any problems but yeah I'm getting big drains.

I've tried disabling fast dormancy to no effect. Tried turning off wifi when not needed still nothing. I can only think it's of the widgets I have? Beautifulwidget, APW Widget and agenda plus widget.

have tired powersaving mode on and off, brightness set to auto. NFC disabled.

I can't seem to identify what's causing battery drain. I even bought a new battery (it's a spare) and yeah same thing.

Anyway here's the dump file. oh yeah I'm using Omega v35.

I noticed there's also another thread on this. Maybe me and him have same problems? lol

bugger dammit!!
[Galaxy S III Q&A, Help & Troubleshooting] xcly:
Might be better to add to that post instead of making a new one. Work together?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
I'm thinking of trying an experiment to see if I can get USB-DAC's working on AOSP Rom's.

Do you guys know what would happen if I flashed a Touch Wiz kernel on an AOSP ROM? Would it just not work that great, or is there a chance it could hard-brick the phone?

I already hard-bricked one phone this month, so I'm a little more cautious than brave right now. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d3athsd00r:
It shouldn't brick, it should just boot loop at best (ie that is the best you will get, it's not going to boot at all)
[Galaxy S III General] Crest+:
​

SAMSUNG KIES <-- Point Arrow and Press - Download straight fromSamsung Server with Official Firmware

PDA: XXELLC

MODEM: I9300PHEELL3

CHANGELIST: 742798

VERSION: 4.1.2

ROM: STOCK SAMSUNG

LINK - Download - <- Jan. 11, 2013

~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~o~

PDA: XXELLA

MODEM: XXELLA

CHANGELIST: 742798

VERSION: 4.1.2

ROM: STOCK SAMSUNG

Method 1: via ODIN

LINKS:

HOTFILE

GOOGLE DRIVE

Method 2: via KIES

Open Kies -> Select Tools -> Select Firmware Upgrade and Initialization -> Enter Model "GT-I9300"

Enter Serial "RF1C56VAJYF".

It will download the latest Android from kies.

DISCLAIMER: DO IT AT YOUR OWN RISK.

I prefer flashing from kies than ODIN...

KIES -> Accepted Method of Flashing by Samsung

ODIN -> By Developers.

I suggest Using kies to avoid problems etc.

View attachment 1611934

Have Fun!

<-- Please Press Thanks