yashsingh1/xdaforums huggingface dataset:
[AT&T LG Optimus G] ushaseos:
Hi Everyone,

So I recently made the switch from 4.2.2 to 4.3 today morning. I went from dvhexer's CM10.1 to CM10.2 and found that everything is nice and smooth and fast - installed without problems etc.

Then I made my first call to check my voice-mail and I got no sound from the earpiece on the phone. Being the clever fella I am, I turned on the speaker and I could hear that the call was in progress. I next tried headphones and that worked too. So I googled the issue to see and I saw a couple people who had similar issues.

I flashed several modems/radios (including some hybrid morrislee variety), flashed several kernels but ultimately couldn't get the sound to work. I also tried bruthaedhung's PACman Rom (4.3) and it had the same issue. Does anyone here have a fix for this issue? I'm in a health related professional grad schools so privacy in calls is kinda important and I can't always have speaker phone calls!

Thanks for your help!

EDIT:

My LGOG has not been converted to an N4 (Ever) it is currently running CM10.1 without any issue (no hardware failure). The only thing that may be different here is that I am on T-Mobile instead of AT&T (unlocked AT&T model). The problem is only showing up on the custom built 4.3 roms.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] -Graff-:
So I've tried a few different times to install and every time I do when I reboot it just goes to a blank screen after the Samsung logo. No boot image. It's indefinite. I'm on latest twrp coming from 4.2 SlimBean. Anybody else have this issue?

Scribbled on my SlimBean powered I727
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
read the last few posts in the slim dev thread

Posted w/xda app w/ i727R

MY STICKIES

| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |

NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Jchef:
Had some boot issues after restoring data with titanium backup. Eventually got it working. Personally every time I tried to do a batch restore of system settings and apps, I would either boot loop or black screen. I manually restored all my system settings and then batch restored apps. I am using twrp 2.6.3.0 zip from Vincom. Boot up has been fine immediately after flashing slim bean 4.3 and slim apps before restoring apps for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Neighbor808:
Try flashing it with the latest CWM, I read that TWRP had issues with it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] -Graff-:
Thanks for the replies. I'm flashing with cwm. I'll get back about it ASAP.

Edit: worked like a charm. Thanks very much. It's appreciated.

Scribbled on my SlimBean powered I727
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] azraell33:
I wonder if that's why I had some issues installing another 4.3 ROM. I will have to experiment when I get home from work
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Devilfisher:
So just to summarize, because I'm having this problem too, the solution is to:

-Flash using the latest CWM and

-DON'T batch restore apps or system settings, do it manually.

Correct? Because I fought tooth and nail with it doing just that, but I kept having the reboot problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] vincom:
its been noted b4, never use Titu to restore system apps/settings as it might have unexpected consequences

Posted w/xda app w/ i727R

MY STICKIES

| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |

NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
[Verizon HTC One (M7)] m4rk0358:
Total noob here but was hoping to find out what it entails to port a ROM from the Sprint variant. They've got quite a few options to choose from and both carriers are using a CDMA device. Is this something that's extremely technical and time consuming to do?
[Verizon HTC One (M7)] cbrown245:
Its not hard but it is very time consuming and you will do a lot of testing along the way . there are a few tutorials on here , I do have some porting experience , I ported Tranquil from the sprint one to the DNA but it was with a lot of help from the rest of the team . if you get stuck hit me up , I will lend a hand .
[Verizon HTC One (M7)] Rebel908:
Porting is hit or miss. Just make sure you the build.props transfers over because the Verizon one will tell the phone the right instructions for spectrum use.

Same tech =/= same spectrum and that is the major difference.
[Verizon HTC One (M7)] andybones:
Try and get some time from [MENTION=3579348]newtoroot[/MENTION], he is the MASTER at porting ROMs...
[Samsung Galaxy Exhibit 4G] ptcruser:
Been lurking on this forum for a few months, learned MUCH on the T679 phone so I purchased one and "customized" it. That phone works great - flashed CWM, Cyanogenmod 9, OC'd kernel, etc. The phone works so well my wife wanted it. So I purchased another, but this one was (is) bricked. Phone powers on fine, but no recovery mode - only download mode - normal boot errors to the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."

The problem is the phone won't take a boot.img download. I can build a tar file with ANY of the other partitions (modem, kernel, recovery, and so forth) and Odin will flash it just fine. But when I flash boot.img a little message pop-up on the phone screen "Cannot read boot image header".

Nothing I try with ODIN seems to solve the problem, so I looked at using different tools. As I understand ADB/Fastboot won't work because even though I've modified the Windows driver and it "recognizes" the phone - in download mode they still won't see the device so I can send commands. I tried working with Kies - that's a lost cause. I tried working with heimdall - apparently it also doesn't talk to the T679. And I can't use an older Odin (1.85) because it doesn't work with the T679 (older Odin support the PIT which would allow me to repartition).

Researching this tells me the problem is that the boot loader is finding the partition table & recognizes where the partitions are - but when it goes to read the first boot block it fails, thus the error message. So why does the reflash fail? My guess is the boot partition has be either resized, corrupted, or in the wrong spot. I hate to completely blow-away everything because I'll loose the IMEI. I need to save the current encrypted partition, then completely re-partition and restore.

Any ideas?
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
http://xdaforums.com/wiki/Samsung_Galaxy_Exhibit_4G

Did you try this
[Samsung Galaxy Exhibit 4G] ptcruser:
Yes, as I said Odin can successfully flash all the modules (from it's point of view), but the phone screen shows the error after writing boot.img, thus after the flash the phone reboots and I'm right back where I started. I'm trying to determine what tools have been used to partition the sd card for this phone. I'm not having much luck finding ANYONE who's done this.

Thanks though, I'll keep looking. Thing is I don't think even a USBJig would help because right now download mode works.
[Samsung Galaxy Exhibit 4G] TripFX:
have you tried flashing cwm in odin mode? version 6.0.3.5 nontouch has odin file http://xdaforums.com/showthread.php?t=2031921
[Samsung Galaxy Exhibit 4G] ptcruser:
Yes, I've flashed the recovery.img from Odin several times with no error. Here's the log:

<0> Create File...

<1> StartThread Detected : 1

<2> StartThread Detected : 0

<3> StartThread Detected : 0

<4> StartThread Detected : 0

<5> StartThread Detected : 0

<6> StartThread Detected : 0

<7> StartThread Detected : 0

<8> StartThread Detected : 0

<1> setup connection...

<1> odin mode.. check plcatform verification.

<1> VerifyPlatform:V0, P0,R0

<1> START!!!

<1> set download environment.

<1> recovery.img download..

<1> 1/1 Finished.

<1> PASS!!!

<1> Close serial port and wait until rebooting.

<0> Destroy instant..

<0> Killed timer

As I read source code I see this problem isn't exactly with the boot partition. Obviously the phone boots, and boots into download mode when I hold volume-down. It also boots into RAMDUMP when holding both volume-up/volume-down. I don't get the boot error when the phone boots, only when the download mode receives the boot.img. So then why doesn't the phone boot into recovery mode when I hold volume-up?

T679 partition table is suppose to look like this:

/dev/block/mmcblk0p1 secboot2 partition map

/dev/block/mmcblk0p2 dbl.mbn (boot loader)

/dev/block/mmcblk0p3 osbl.mbn (boot loader)

/dev/block/mmcblk0p4 MBR extended partition table

/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)

/dev/block/mmcblk0p6 amss.mbn

/dev/block/mmcblk0p7 emmcparam.bin

/dev/block/mmcblk0p8 boot.img (linux kernel)

/dev/block/mmcblk0p9 adsp.mbn (baseband)

/dev/block/mmcblk0p10 rmt

/dev/block/mmcblk0p11 rmt

/dev/block/mmcblk0p12 persist.ext4

/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)

/dev/block/mmcblk0p14 param

/dev/block/mmcblk0p15 system.ext4

/dev/block/mmcblk0p16 cache.ext4

/dev/block/mmcblk0p17 data.ext4

/dev/block/mmcblk0p18 preload.ext4

Partition mmcblk0p5 (boot loader/odin download mode) works and since it boots with the default Samsung download screen I know that's stock/correct. I don't know if mmcblk0p13 is correct, I suspect it isn't since even after Odin successful download of recovery.img the phone still can't enter recovery mode.

I suspect Odin just sends an identifier to tell the phone what partition it's sending, and download mode determines which linux partition to write it to. I need to keep reading.
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
Did you try flashing cwm via Odin and then try going into recovery.

http://d-h.st/WeX
[Samsung Galaxy Exhibit 4G] ptcruser:
Yes, tried that. Odin downloads clean but upon reboot I still can't get into recovery mode. So Odin is Samsung proprietary, what about the download mode code? I've also tried flashing a complete image like XquiziT (odin version) and that doesn't change anything. Of course even this isn't a "complete" image as many of the partitions are still left unchanged, like download mode.
[Samsung Galaxy Exhibit 4G] ptcruser:
Found an article on EMMCBOOT (tjworld.net/wiki/Android/HTC/Vision/BootProcess). Yea, it's HTC but I expect the Galaxy boot process is similar.

Boot reads the partition map, "After some hardware initialisation the PBL reads the Device Boot Loader (DBL) from the first partition of the flash memory device (In Linux, mmcblk0p1).". Then "It then loads and executes the combined REX/AMSS from partition 5 (Linux mmcblk0p5)", so that explains how things get started.

Which leads me to get the hboot/fastboot interface working. Then I can ask for "listpartition" and "test_partition". Maybe?
[Samsung Galaxy Exhibit 4G] jfbs:
recovery.img is correct at /dev/block/mmcblk0p13.

edit: I'd try another Odin version besides the one you're currently using.
[Samsung Galaxy Exhibit 4G] ptcruser:
I tried odin 4.44, flashing does work, but it didn't fix the problem. I don't know, maybe the boot partition is bad. Riddle me this: at what point does the kernel start? When the phone power's up I see the "SAMSUNG" screen then the failure condition. If I hold the volume down key I boot into recovery mode. Is it possible that the eMMC boot processing is detecting the volume key and starting the download mode? In which case it never tries to boot the kernel? Also, if eMMC boot is directing the startup then there should be no problem going into recovery mode - that is unless the recovery partition is corrupt. But then why can odin flash that partition without an error?

Back to kernel start, after the "SAMSUNG" screen normally you see the "Samsung Galaxy Exhibit 4G" screen, then the boot-up screen (T-mobile, Cyanogenmod, etc). This phone never reaches the "Samsung Galaxy Exhibit 4G" screen, it drops into the failure mode. Perhaps this goes back to the boot partition being corrupt.
[Samsung Galaxy Exhibit 4G] jfbs:
Android boot sequence: power -> internal ROM -> bl1 -> uboot -> kernel -> ...

edit: removed stale link
[Samsung Galaxy Exhibit 4G] ptcruser:
Odin doesn't understand what to do with a zImage file.

Here's the odin trace:

Download Start...

<0> Create File...

<1> StartThread Detected : 1

<1> setup connection...

<1> odin mode.. check plcatform verification.

<1> VerifyPlatform:V0, P0,R0

<1> START!!!

<1> e - unknown file - "zImage"

<1> set download environment.

<1> reset pda..

<0> Started Timer

<1> Close serial port and wait until rebooting.

I've tried Heimdall, but the interface protocol with download mode isn't correct. Isn't that what usually flashes zImage?
[Samsung Galaxy Exhibit 4G] jfbs:
Which ROM or kernel did you pull boot.img?

edit: this http://xdaforums.com/showthread.php?t=1644240 may be worth trying.

edit2: or http://xdaforums.com/showthread.php?t=2281287

[Tool][[windows] Make CWM Recovery .img's into .tar.md5 odin flash-able files 1 CLICK
[Samsung Galaxy Exhibit 4G] ptcruser:
Again, I've learned a lot working on this, but I still don't have it solved.

First, after searching many posts I've realized that Odin flashes the phone rom based on the file names specified in the Ancora.ops file. The T679 ops file looks like this:

0,partition

1,dbl

2,osbl

3,amss

4,emmcboot

5,adsp

6,boot

7,system

8,cache

9,userdata

10,recovery

11,persist

12,preload

This means you can create a tar file with backup file names that match the above. I.e. to rewrite the partition you need a partition.img file. I don't see anyone that has done this but 4.43 odin did flash a partition.img I made from a backup from my working T679. The same thing goes for the dbl, osbl, and persist .mbn files. I created these using dd from my working phone. Thus I have flashed almost all the partitions on this phone, except userdata and emmcboot. I can't flash emmcboot.mbn because I don't have the samsung cert to sign. You can download it with odin, but an error message pops-up on the screen about the sig.

But, in the end I still cannot successfully rewrite the boot partition. Even after successfully rewriting the partition table, and reboot, I use Odin to try to flash boot.img and the "Cannot read boot image header" message still pops-up on the phone.

I am pretty sure that since the phone will not boot to the "Samsung Galaxy Exhibit 4G" screen, I can't get into recovery mode. Which I suspect is due to a problem with either the boot partition OR possibly with /dev/block/mmcblk0p4 MBR extended partition table partition. Next step is to figure out that this table entry is and how modify .ops so that odin will accept this img.
[Samsung Galaxy Exhibit 4G] ptcruser:
The error is occurring because the boot_image_hdr is missing or invalid in the boot.img file. I'm guessing the download mode software is checking this before it writes it to the boot partition. But this doesn't make sense as others have been downloading the "uvlg3.odin.zip" and odin installs this boot.img just fine. What's different with this phone? What am I missing?
[Samsung Galaxy Exhibit 4G] ptcruser:
Today I dumped mmcblk05 (emmcboot) on my working t679, then ran strings on the dump and looked at what I found. Not surprising I found the " Cannot read boot image header" string. I also found

ODIN MODE

PRODUCT NAME: %s

SGH-T679

CUSTOM BINARY DOWNLOAD: YES (%d counts)

CUSTOM BINARY DOWNLOAD: NO

CURRENT KERNEL: CUSTOM !!

CURRENT KERNEL: SAMSUNG !!

CURRENT KERNEL: UNKNOWN !!

I looked for the kies error, but didn't find it and I suppose that's because this message is actually in some graphics pic.

There are two copies of the "Cannot read boot image header" messages, one with ERROR: before the message and one a few lines lower without. First one must be for the aboot.c kernel startup, where I think the second must be from the download mode.
[Samsung Galaxy Exhibit 4G] TripFX:
how long ago did you get the phone also does it say SGH-T679 or SAM-T679 under the battery on both working and non working phones.
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
If you can get in Odin try 1 click unbrick or even a jig android doesnt let anything through if it sense something corrupted as part of its security protocal it needs to forced through.
[Samsung Galaxy Exhibit 4G] ptcruser:
Both phones say SGH-T679.

I'm sure any experienced andriod developers are laughing when they read this post. Me, I just keep learning in baby steps.

I'm not sure why recovery mode isn't working, recovery has it's own kernel/ramdisk and should alternate boot with a bad boot partition. I discovered I can enable ro.debuggable=1 in the default.prop, but I need to unpack boot.img and modify it.

Next I'll learn how to unpack boot.img. Then, just to be sure I'll unpack the dd dump i took of my working phone partition 8 (should be boot.img). If that works then I'll see if I can unpack the dump I took of the emmcboot partition from my working phone - I can review config files there. Where I'm going is if emmcboot has a default.prop config file then maybe I modify that, rebuild the emmcboot image, and possibly find some way to flash this on the broken phone.
[Samsung Galaxy Exhibit 4G] ptcruser:
Tried 1 click unbrick a while ago, correct me if I'm wrong but I think that tool requires Odin 3 capable phones.
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
Not sure I use software from the manufactor .worth checking into it though. But again android wont let you flash anything through fue to the fact to prevent the bootloader from being corrupted id just force it through with a jig.
[Samsung Galaxy Exhibit 4G] TripFX:
ya a jig should work and reason why i wondering bout sgh or sam was cause me and wife have same phone except hers is sgh and mines a sam. was pondering if there really was a diff between them but both yours is same so thats out of the question. I would just go with the jig as it would be your best bet at this point.
[Samsung Galaxy Exhibit 4G] ptcruser:
I don't think a jig will work. A jig will simply put the phone into download mode, this phone will already boot into download mode. So using the jig to startup will put me right back where I am.
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
It also bypasses the security potocal and you can also reset your binary counter
[Samsung Galaxy Exhibit 4G] TripFX:
that would be correct
[Samsung Galaxy Exhibit 4G] ptcruser:
Ok, spent 2 hours building a jig, works great. Plug in the jig, plug the battery in and the phone boots right to Odin download mode. Then, unplug the jig, plug in the laptop and use odin to download boot.img. As I expected same cannot read header error at the end of download. Reboot the phone and same Kies error.
[Samsung Galaxy Exhibit 4G] TripFX:
starting to wonder if the storage isn't defective. if you bought it recently exchange it, I know in windows you can do a check disk for it to scan for bad sectors but being you can only get into odin not sure if there is a way to do anything like it except for maybe an odin script but dont know. can you get into fastboot or adb?
[Samsung Galaxy Exhibit 4G] ptcruser:
Fastboot or adb require CWM to be running, I tried using both with the phone in download mode and it won't communicate.

I got the phone from my son, who got it from a friend because it "stopped working after he upgraded it". This has been a learning project, I'd rather play with a cheap phone and possibly brick it than buy an S3 or S4, then screw something up customizing it.

Maybe I'll just set the phone aside for a while and come back to it after I have more Andriod experience.
[Samsung Galaxy Exhibit 4G] TripFX:
well i wish ya the best of luck. i;m just getting used to linux based os's. If I come across something or end up making something for it to work ill pm ya. Otherwise if you ya figure it out pm me with the solution. it would be nice to know for future refrence xD
[Samsung Galaxy Exhibit 4G] jfbs:
What happens when you flash recovery.tar.md5?
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
Long as the pins are pressed through the process odin should force the boot image through this might take a few tries to stick. Unplug the jig once odin is finished. ( long as the pins are pressed it bypasses the protocol)
[Samsung Galaxy Exhibit 4G] ptcruser:
Wait, I don't understand. The jig plugs into the micro-usb port, how can i plug the phone into the laptop? Is the jig suppose to still have the cable lines to connect to the laptop at the same time? Are you sure of this? Send a link with a jig setup like this, I didn't see when I search for the jig spec's.
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
On my jigs there's the micro for the phone also a usb slot so i can plug in my usb cord. Most homemade jigs are just built to get into odin but the hack to bypass protocal is to keep in the jig once in dowload mode and keep it in til odin is finished. Keep in mind it might put up a fight and might require you to repeat the process a few times. Warning this process might corrupt you boot loader since theres a corrupted file but this is the only way other than sending it to get serviced or replacing the board. And yes im positive this one of the things i do for a living lol. If this process doesnt means you might have a corrupted com port and it needs to be serviced or replace the board.
[Samsung Galaxy Exhibit 4G] ptcruser:
Ok, I'll try this tomorrow. Should I start with trying to flash a new boot.img, or new emmcboot.mbn?
[Samsung Galaxy Exhibit 4G] ptcruser:
Modified the jig so that it's a jig/USB cable and it works. Plug one end into the laptop, the other jig end into the phone, power on the phone and it boots into download mode. Then the laptop beeps as the Samsung USB device is detected. Startup Odin and flash boot.ini... same error. Restart everything and try flashing emmcboot, get the same "==odin_sign_fail!" error. Tried this several time with no success. As I said I can flash recovery.img without a problem, but the phone won't boot into recovery. Something is preventing it from taking a new boot.img flash.
[Samsung Galaxy Exhibit 4G] schuylkillparanormal:
Then the device needs to be serviced or just get a new board. id say go with the cheapest route.