yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] xxRed5xx:
I already have cwm flashed, just wondering how to manually boot into it instead of using adb or terminal.
[Miscellaneous Android Development] confondere:
This is not manual, however if your phone is functional you could download ROM Manager (or equivalent) from the Android Market and select the second menu option to "Reboot into Recovery".
[Miscellaneous Android Development] krusir:
I am looking for a hot key to boot CWM also. I got once make the phone "un-bootable". I have to ODIN a image to make it bootable, then root, then get into CWM.
[Miscellaneous Android Development] jvnat:
I've got CWM recovery installed by jocala. I installed ROM Manager, but it tells me I have to flash the recovery. It also asks which device I have and the Exhibit 2 is not listed. What am I missing or doing wrong to get ROM Manager working for our phone?
[Miscellaneous Android Development] Wildchld:
Our CWM is an unofficial version and will not work with Rom Manager but the reboot to recovery should work. Otherwise use hold power down and press the power and keep holding the volume down
[Miscellaneous Android Development] camcory:
I power down then hold up volume and power on at the same time. To enter download mode volume down and power.
[Miscellaneous Android Development] confondere:
That is correct. Let me see if I can clarify. I am sure many newbies/lurkers have the same concerns. ROM Manager is not ClockworkMod.

As WildChild stated, ROM Manager does not support the Exhibit II, so you should not select the "Flash ClockworkMod Recovery" option on the menu. You can, however, use ROM Manager to boot into the Recovery. If you have a stock Exhibit II and have not flashed the ClockWorkMod Recovery, you should enter the stock recovery using the methods mentioned elsewhere in this thread (or you could alternatively use the "Reboot into Recovery" option from ROM Manager).

Once in the stock Recovery menu you can then install the ClockWorkMod recovery. Assuming the ClockworkMod recovery is installed, the next time you boot into recovery you will see the ClockWorkMod recovery menu.

Hope this helps.
[Miscellaneous Android Development] xxRed5xx:
Thanks for the clarification. I followed the instructions to flash the ported cwm using adb. Just having some difficult manually getting into recovery. Thanks for the help using vol up and power, however, didn't work.
[Miscellaneous Android Development] KemikalElite:
Got it after a few tries! Hold Vol Up + Capacitive Home Key + Power. Release only the Power key immediately when you see the Samsung logo but keep holding the other keys until you see the recovery menu.

I think Power + Vol Down boots into download mode.
[Miscellaneous Android Development] jocala:
Peach Sunrise V1.0

Peach Sunrise V1.0 is available HERE. Please be advised that this is a ClockworkMod release only. No more Odin releases are planned.
[Miscellaneous Android Development] feetwet:
No more volume issue.

Hi VanillaTbone,

I've had the phone for a few months now and noticed for the first month that the volume from the earpiece was very subtle. I had something curious happen on the stock OS version that came with the phone. I started using the Widget that came with the phone (shows a green bar and shows active applications) if you tap on the widget you see: "Active applications", "Downloaded", "Ram", "Storage", "Help".

I noticed clearing the Ram from time to time helped things from getting bogged down. Well shortly after discovering that I starting using it see how much Ram I could dump. I once got down to 197 +/- MB. Then I noticed the volume changed. Now it has the ability go LOUD. I did the same thing to my wife's phone which is the same one from T-Mobile and it happened to her's. I'm not sure what it did but now the volume is great! I have no more problems from the ear piece. I'm not sure if the custom Rom's have solved this problem on this phone?
[Miscellaneous Android Development] jvnat:
I just use the following commands in Terminal Emulator (simpler for me):

su

reboot recovery
[Miscellaneous Android Development] stab244:
I'm pretty sure that just pressing volume up + power and holding for a second or two works after seeing the Samsung logo gets into recovery. That's what I do and it works fine every time.
[Miscellaneous Android Development] venkat kamesh:
the rom looks nice thank u:D:D:D
[Miscellaneous Android Development] xxRed5xx:
I use that as well. When I had a problem with the bpear rom, I couldn't get into the market to download terminal, plus every app was force closing. I had to connect my phone to my computer and use adb. Just wanted a way to manually boot into recovery just in case all else fails. Power+volume up+home worked like a charm:D thanks!
[Miscellaneous Android Development] lolitsjae:
I think I'm gonna try out jocala's PeachSunrise 1.0...the bPear ROM, although it gives a TON of RAM release, it closes literally, everything that's running, when I only want some to be closed and some to stay on..Also the process of using usb storage is sort of a hassle, since when usb is connected, it only prompts the message "MTP initialisation" and I literally have to go to settings to get the actual USB storage mode enabled...also I've noticed how it keeps on telling me that MTP will restart my sd card.. I don't get why.. and my phone has been rebooting on its own randomly.. so more problems:

1. system crash & reboot on random

2. MTP restarts sd card

3. tedious to get USB storage mode going.

I will definitely miss the blueness and the ICS touch..
[Miscellaneous Android Development] AndroidSamurai:
You have to do what is best for you.
[Miscellaneous Android Development] hotsauce126:
I've always had to do that ever since I first turned on the phone
[Miscellaneous Android Development] lolitsjae:
Even on stock ROM? I've never yad a MTP initialization prompt when I had stock 2.3.5.
[Miscellaneous Android Development] hotsauce126:
yeah before I even rooted it
[Miscellaneous Android Development] samusishere:
I stopped having to do this once usb debugging was enabled

same on the stock rom.

weird I know

buttt It works

and its not necessarily his rom,

its just the way the Samsung task manager is built

if you use a different task killer

you can choose which apps to close and which to keep open
[Miscellaneous Android Development] lolitsjae:
Ok, I found out how I did before, so the MTP initialization won't prompt up ever again, only the "USB connected message" in the notification area.

1. settings

2. Applications

3. Development

4. check off USB debugging

Enjoy!
[Miscellaneous Android Development] Nilpotent:
I'm playing with the Kernel sources released by Samsung. Did someone used the zImage produced by the compilation process ? Is that a working kernel ? I think Jocala mentioned he had trouble to get it working. Is that because there are missing files ?
[Miscellaneous Android Development] jocala:
As I mentioned, I've yet to compile a working kernel from Samsung source that didn't boot-loop. What I have done is split the rootfs from the kernel for modification, then rejoin the two.

edit: If you compare stock zImage vs compiled zImage, compiled is about

300K smaller. Both initramfs are equal. What's the missing 300K?

Good luck to you! Please keep us posted.
[Miscellaneous Android Development] tagzard:
ROM Request

I request a ROM with a HTC theme.
[Miscellaneous Android Development] dennis96411:
Just get an HTC themed launcher, it's not that hard. Try GO Launcher EX.
[Miscellaneous Android Development] imhumanoid:
+1 on that. Use GoLauncher for that theme.

(dislikes HTC's looks)
[Miscellaneous Android Development] Nilpotent:
They may have removed proprietary files (drivers ?). I think that's what Sounds said in a previous post.

I will check how Arco68 has modified the kernel sources for the W, it's the same source but it's calling different part of the programs. Maybe it will help me to fill the holes...

Question@jocala: can we make a full nandroid backup and restore the system through your modified CWM recovery? I'd prefer to have a safety net before flashing my system (which works perfectly fine at the moment !)
[Miscellaneous Android Development] dswaggz:
Awesome. AN WHERE DO WE SAVE IT 2

via Dan swagger
[Miscellaneous Android Development] KemikalElite:
The kernel isn't working just yet.
[Miscellaneous Android Development] jocala:
Drivers shouldn't be an issue. All drivers present on a stock phone are available, it's just that we may be dependent on a binary supplied by Samsung w/o source. That's if the proprietary drivers are supplied as modules. I think I may have stumbled across something. I've posted the issue to the dev community here. It's a new one for me.
[Miscellaneous Android Development] Nilpotent:
Thanks, I have been checking how Arco68 has been modifying the W sources. I doubt I understand but I will modify the sources in a similar way. I don't think it will not work but it should give me a better understanding of the system (sometime understanding comes with coding...)
[Miscellaneous Android Development] jocala:
Good luck! Keep us posted, ok?
[Miscellaneous Android Development] Nilpotent:
Ok, I'm not sure I know what I'm doing, but let's be sure we are talking about the same things.

From the stock firmware, extracting the zImage from the boot.img using dsixda kitchen using option 20 gives me a file which has a size of 3847632 bytes.

If I compile the sources myself (make ancora_tmo_rev00_defconfig then make), I get a zImage which has a size of 3725900 bytes. If after extraction of the stock zImage, I replace it by this compiled zImage (in the kitchen BOOT-EXTRACTED file) and build the boot.img, I have no error from the kitchen, but the boot.img is smaller.

So my first question is what are exactly the sizes of the zImage files you mentioned ? I am missing 120K not 300K, I don't know if it's better but it's different. Is that toolchain dependent ? What did I miss ?
[Miscellaneous Android Development] AndroidSamurai:
Edited OP to reflect rom name change by bpear.
[Miscellaneous Android Development] jocala:
When you compiled your kernel it sounds like you didn't edit in a location for the initramfs. In my edited ancora_tmo_rev00_defconfig, you'll see

CONFIG_INITRAMFS_SOURCE="../initramfs", meaning one level up from the kernel source is where my initramfs (rootfs) lives.

The actual difference between a stock kernel and one compiled locally is 216660.

Stock boot.img: 5509632

Compiled zImage: 5292972
[Miscellaneous Android Development] creeve4:
If you enable USB Debugging the MTP initialization notification is removed and you can connect your phone in Mass Storage mode.
[Miscellaneous Android Development] Alexsoccerboy:
application icons remain

Hello all, just snagged this phone yesterday for the g.f.

I'm stock rooted.

I removed the bloatware, some with titanium backup root, some with Estrong's file explorer but some of the bloat apps now have an empty icon showing up in the app list: calculator, mini diary, news & weather, etc. The original icon is gone and in its place, it has an android face with "SD" in the corner, but still says the name of the original app. I don't know crap about the Touch Wiz world, I'm used to Sense UI for HTC devices.

Ideas? Thanks.
[Miscellaneous Android Development] doc.fr33man:
Have you rebooted the phone yet?
[Miscellaneous Android Development] KemikalElite:
Those icons are left there is because the launcher creates the references (symbolic links) to apps that are stored on the SD card. I believe even just restarting the launcher app can fix this. IIRC no reboot needed.
[Miscellaneous Android Development] s0unds:
Just a random shout out, I've been hard at work locating all the odin docs I can find. Even the hard-to-get ones. In the process I've located some interesting logos/splash screens - so if you feel like customizing them you can use this info. Extract /dev/block/mmcblk0p5 and use the shell script for linux.

Or if you're interested in disassembling arm7 -- the database in the zip file should be compatible with any version of IDA out there.
[Miscellaneous Android Development] Wildchld:
Anyone want to try a theme for peach?

http://xdaforums.com/showthread.php?p=21917919
[Miscellaneous Android Development] AndroidSamurai:
Screenshot if and when you get a chance... When you add a screenshot I will add it to the OP.
[Miscellaneous Android Development] Wildchld:
Lol thx but have to get my daughters phone first maybe tonight
[Miscellaneous Android Development] AndroidSamurai:
It's no rush bro... Just when you get the chance.
[Miscellaneous Android Development] dswaggz:
Hey wildchild are u still gonna release the miui build

via Dan swagger
[Miscellaneous Android Development] Wildchld:
Never said that one based on stock Rom yes
[Miscellaneous Android Development] dswaggz:
So is that a yes also what is a cwm back up suppose to have in it

via Dan swagger
[Miscellaneous Android Development] joshua.justice:
Post it :D
[Miscellaneous Android Development] dswaggz:
Hey can I switch out my stocc build prop for the peach sunrise one

via Dan swagger
[Miscellaneous Android Development] wilson pickett:
looks good,like the gauge battery icon.
[Miscellaneous Android Development] surfnhawaii808:
Screen protector?

Screen protector

Anyone using a screen protector with this phone?

I'm considering ordering a zagg...

Samsung Exhibit II 4G SGH-T679 Screen Protector | invisibleSHIELD by ZAGG

I'm not crazy putting water on the phone, evenif it's only a few drops and I don't see a link for the zagg DRY version...
[Miscellaneous Android Development] KemikalElite:
I have the ghost armor. At the time I got the exhibit there was no invisible shield yet. Do they have one for the exhibit II now?

Anyway, I've tried everything to get my ROM built and flashable. This includes the ROMs I've built from stock dumps that I put through the dsixda kitchen after using the instructions for the galaxy w at this link http://xdaforums.com/showthread.php?t=1447422&page=1

and I've even tried taking exsisting ROMs then modifying them and flashing them just to test it but the zips I make completely refuse to flash in the cwm recovery. I've modified the updater script as the instructions thread lists but I get either error 0, signature verification failed, or the recovery freezes on installing update. I reflashed the recovery image multiple times so I know its not that. I just don't understand why it isn't working. My original posts about this from week were in the peach sunrise thread but I'd rather not overload that thread anymore with off topic posts.
[Miscellaneous Android Development] jocala:
Have you tried an Odin build? It's not as flexible as edify scripting, but I think it's easier to start off with. For those that don't know, here are the basics for a rooted phone. I've only done this under Linux:

Pull a copy of your system partition:

adb shell
su
dd if=/dev/block/mmcblk0p15 of=/sdcard/system.img.ext4 bs=4096

Make a copy of your partition, ready for Odin.

adb pull /mnt/sdcard/system.img.ext4
tar -H ustar -c system.img.ext4 > backup.tar
#
#

Put backup.tar aside. It is an Odin ready tar file that will revert your phone's system partition into it's original state. So technically, you just built your first ROM :)

Now, mount your system.img.ext4 file as loop:

mkdir temp
sudo mount -o loop system.img.ext4 temp
cd temp ## you are now inside the system.img.ext4 file!

Now you can make changes to the /system partition. When you're done,

#
sudo umount temp
tar -H ustar -c system.img.ext4 > test.tar
#

The file test.tar is ready to be flashed with Odin. Rinse & repeat until you are happy. There are other methods, but this is an easy way to start.
[Miscellaneous Android Development] Wildchld:
Isn't linux great

Fruit cake maker from the market will make the system.img file for you also.

Well done!
[Miscellaneous Android Development] pendoric:
Any chance you can fill in what to do fill what you need to do to run adb and how to flash the tar file in odin? The only adb I know of is an old assemby debugger on Unix :o, I have done searches and there is LOTS of information on flashing much of it contradictory.

Also if you can dd off the image why cant you just dd it back on? Why do you need to run odin?
[Miscellaneous Android Development] jocala:
Actually, you can dd it back. However, if you intend to distribute your ROM, you'll want a more user-friendly method. Odin packages are just one way, cwm files another.

adb = Android Debug Bridge. Shutting down here now )
[Miscellaneous Android Development] KemikalElite:
Very Good Suggestion! I'll continue working on it tomorrow. Odin packages seem easier than I thought. First I just want to make sure I get a working build flashed, then I'll worry about fixing it for cwm later. I know something will work.
[Miscellaneous Android Development] Wildchld:
Screenshots added thanks to Jocala

http://xdaforums.com/showpost.php?p=21956958&postcount=462
[Miscellaneous Android Development] lce67:
Thanks

Just got this phone a few days ago and i am very pleased..i had a att captivate that i droped and broke ...this phone to me is just as good for 1/3 the price..i just wanted to say thanks to all dev for all you do...
[Miscellaneous Android Development] Nilpotent:
I continue on the topic of kernel developments as I don't know if it's on stanby or if there are advancements on this.

As Jocala mentioned, if we add initramfs on the .config we can get a zImage of the size close from the stock boot.img. I've been playing with compiling the kernel using different initramfs (samsung galaxy S and S2. I have since realized that the exhibit 2 is like the galaxy S plus so different from those phones but it does not matter much for now). This does not create compilation problem but the final zImage will be of different sizes.

The problem I see is none of those zImage are recognized by the dsixda kitchen whereas the stock zImage seems ok.

I am not sure we should include the initramfs during the compilation. The kitchen does not create any error messages if we replace the zImage (compiled without initramfs) of the stock boot.img

I will continue to play with the sources...
[Miscellaneous Android Development] surfnhawaii808:
Going back to stock NOT BRICKED

I've rooted using Zerg and backed up the tmo apps via titanium FREE.

My previous phone had clockwork recovery support (mytouch 4g) but there is no clockwork recovery for this phone (that I know of!)

My question is should I want to go back to totally stock, new aS it came out of the box, will the built in recovery (wipe device) in the phones recovery mode put this phone back to bone stock including the apps I removed after rooting?

Again, my phone is NOT BRICKED and works fine... Just wanted to know what I need to do to get it back to fully stock should I need to have it serviced by Samsung ... This is my first SAMSUNG phone... I've had HTC phones before this.

Thanks again and Aloha!!!
[Miscellaneous Android Development] KemikalElite:
The best way to return this phone to complete stock ROM is ODIN and a factory data reset.

http://ultimatephoneguide.com/index.php?title=Samsung_Exhibit_II_4G#ODIN

At that link you will find step by step instructions from the original thread for how to use ODIN to flash the stock build. ODIN does not perform a factory data reset so that can be done either through the settings/privacy menu or through the recovery.
[Miscellaneous Android Development] Tokinjedi:
i bought the skinomi dry screen protector. bout $6 on amazon. just as good as the wet protector for my g2.

had some bubbles after applying but they were all gone within 2 days. also, if you scratch the protector it self heals.

still looking for a decent case though. i'm hoping casemate or otterbox makes a case for this phone.
[Miscellaneous Android Development] jocala:
That does work, but I had some wifi issues. I didn't try to diagnose or fix them though. Please keep us posted!
[Miscellaneous Android Development] JakeeExhibit2:
If I unlock my phone carrier say..to Verizon, would I have to start buying Verizon prepaid cards instead of T-Mobile?
[Miscellaneous Android Development] krusir:
This is GSM phone, why Verizon. If you unlock, you can use ATT SIM. But data frequency is different between ATT and Tmobile.

If you like to use Verizon Prepaid, try www.pageplus.com. They run in Verizon network, you got the same coverige with less $$.
[Miscellaneous Android Development] JakeeExhibit2:
I'm not exactly sure what carrier I'm gonna switch to yet, I love the phone but my coverage Is very spotty around my house so I would just like to see which carrier will get good coverage for me
[Miscellaneous Android Development] Wildchld:
What about wifi calling?
[Miscellaneous Android Development] JakeeExhibit2:
Wifi calling works at my house and boosts my signal but once I don't get service for about 7 miles then when I do get signal it usually varies between 1 or no bars

---------- Post added at 09:31 PM ---------- Previous post was at 09:30 PM ----------

Once I leave*
[Miscellaneous Android Development] stab244:
You can edit your posts btw.

Yeah you should probably change providers then. Ask around your area and see who's better I guess. Nothing we can do to this phone will make it suddenly have better signal. Well unless if at&t works great in your area then you could buy an unlock code and still use this phone.
[Miscellaneous Android Development] JakeeExhibit2:
Okay thank you, just one more question, when I pay my bill I use a T-Mobile refill card, if I switched say to att would I have to go buy an att card instead?
[Miscellaneous Android Development] jose makalolot:
Yes. You can also try att mvnos.

-----------

sent from my calculator with android
[Miscellaneous Android Development] jryan79:
has anyone notice a display problem while watching online videos usually flash content it seems part of the picture is darker then the rest its kind of annoying but no big deal, dont kno if im the only one with the problem or not may uninstall the flash player update and see if that fixes it. i hadnt noticed it on the stock ROM idk if there is anyone still using it that can check it out or not...

ok after using titanium to uninstall completely and rebooted the phone i opened market and reinstalled and it seems to have stopped the videos are playing allot smoother as well not sure y it had started doing it it had kept getting darker and farther over will keep an eye on it and see if it starts to do it again if so it may not be a problem with the ROM or the phone but adobes flash app...... wouldnt be to surprised about that tho it is adobe
[Miscellaneous Android Development] Nilpotent:
Ok, when I'll have time I'd like to go baby step by baby steps and test the following. I think Jocala has been up to number 2 (and beyond ?). Let me know.

1) Use the dsixda kitchen and the stock firmware without any changes to create a CWM flashable stock ROM.

1bis) Modifications of the stock ROM with dsixda kitchen (root, etc)

2) Same thing with the zImage replaced by the one compiled from sources (no changes to the source code)

3) Same thing after the kernel sources have been slightly modified (the source already have 1.4GHz in the frequency table, so to overclock we may just need to find how to change the PLL value or modifying the .config will be enough ?)

Also, the default .config would not compile as a cyanogen kernel, I will play with the .config and the sources to make it ok to compile. It does not mean at all we can get a workable cyanogen (at least not from me, no idea how to do that), I think we will have to wait more developments on the galaxy s plus and w but I may learn something about the phone.
[Miscellaneous Android Development] dswaggz:
Guyz we need this checc it out

http://xdaforums.com/showthread.php?p=21755937

via Dan swagger
[Miscellaneous Android Development] jocala:
I've made it to third base, but not home plate :) Great to see you making such progress! BTW, I don't use the kitchen, except for the kernel split/rejoin.
[Miscellaneous Android Development] dswaggz:
So can we say custom kernel

via Dan swagger