yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] [Ramad]:
These are the deodexed apk files(app and framework) of Gingerbread XWJV1.

This is not a ROM so don't download if you are not a developer, wait for the Gingerbread ROM releases.

All the apk files except Email.apk are deodexed, Email.apk just kept throwing errors so I did not want to waste time on it. I have included the Email.apk from XWJS5 which worked fine and I would like to advice using it, however, that is up to you.

This is a 7zip compressed exe file, so it's extractable on both Windows and Linux.

I wish you all good luck and good night. :)
[Galaxy S I9000 Android Development] Daneshm90:
Haven't tested it fully but it runs soo....

its this firmware's email.apk

Nothing different from the looks of it.
[Galaxy S I9000 Android Development] g00ndu:
Wow, most people got errors deodexing, how did you get to deodex it? Got to hand it to you. :)

@Daneshm90, thanks for the deodexed version of the email.apk.
[Galaxy S I9000 Android Development] Daneshm90:
A lot of times it looks for proprietary libs that are non existent in the rom but were present at compile time. So in those cases you have to take a risk and ignore those mismatched classpath's and hope its irrelevant to the functionality of the apk (A lot of the time, if a classpath is not found within the jar's in the rom, it is not critical)
[Galaxy S I9000 Android Development] taha_e:
perhaps you are working on framework files now, :D ;)
[Galaxy S I9000 Android Development] Daneshm90:
Why ? Whats wrong with those ?

Those deodexed without a hitch.
[Galaxy S I9000 Android Development] [Ramad]:
Thanks Daneshm90 for the Email.apk. :)

Regarding the uploaded apk files, they include both app and framework apk files, and with the Email.apk file provided by Daneshm90 all are complete and ready for download.

I'm not so exited about this firmware, it does not bring much and I think that in a few days we are going to hear a lot about it not being good especially regarding GPS and Kernel panic!.

It seems that Samsung did bind recovery to boot.bin, boot.bin does check recovery every boot, and if it's a 2e or a modified 3e then it will reinstall the original and the unmodified 3e, what I think is that the unmodified 3e is located in initramfs, so this needs to be removed or replaced.

The phone runs fine without flashing boot.bin that is included in the firmware, but that does give a screen corruption in every boot and GPS will not pick a signal.

My opinion is not to get so exited about this release and maybe not for the next release either..:)
[Galaxy S I9000 Android Development] Daneshm90:
I havent kept up with apktool revisions.

Upon checking his site seems his latest one is still using baksmali 1.2.4 which did not have gingerbread support if i recall.

You can always if urgent extract -> use baksmali to decompile -> make changes ....etc (ofcourse xml's will still remain in binary)
[Galaxy S I9000 Android Development] [Ramad]:
@g00ndu

You will need 1.2.6, try it.
[Galaxy S I9000 Android Development] intronauta:
Hi Daneshm90

how exactly we can deodexed Email.apk ignoring the mistmatched classpaths?

I'm bored with this error :/

regards
[Galaxy S I9000 Android Development] Daneshm90:
Im still using my old school deodexer script.

But upon looking up the syntax its, -I added
[Galaxy S I9000 Android Development] g00ndu:
I have 1.2.6, I can baksmali and smali. It's the value folder which I'm interested in actually. :D

Guess i'll have to do it differently. ;)
[Galaxy S I9000 Android Development] rlorange:
Would it be possible to post just the browser.apk? Keen to try it on 2.2.1...

I think a lot of others are too
[Galaxy S I9000 Android Development] g00ndu:
Does it mean that even if you got cwm installed, it won't boot into cwm recovery, and reverts back to 3e recovery?

Did you try to replace the boot.bin with an older version?
[Galaxy S I9000 Android Development] xmfpdlemalnz@hotmail.com:
Here you go.

Not sure if it will work on 2.2.1 though
[Galaxy S I9000 Android Development] rlorange:
Thanks... Didn't work with a simple system app transplant... Oh well worth a try
[Galaxy S I9000 Android Development] [Ramad]:
Yes, the new boot.bin will prevent using CWM, after I have flashed the whole firmware I did replace boot.bin and Sbl.bin with those I have from JPJPA and XWJS3, the device boots fine with the modified 3e and CWM can be used too, but I get graphical corruption in every boot and GPS does not work.
[Galaxy S I9000 Android Development] g00ndu:
I reverted back to XWJS5, using ulfk (speedmod) kernel. Everything seems to be fine, and I can get back to cwm recovery.
[Galaxy S I9000 Android Development] Markyyyyyyyyy:
SteelBlue v3 themed ui files

Anyone who likes the SteelBlue v3 Theme from Team Carbon.... i have created the following themed apk's

framework-res.apk (includes the shutdown aimation from Daneshm90)

twframework-res.apk

SystemUI.apk

the 2 framework files can replace the ones in the /system/framework directory

and SystemUI.apk needs to go into the /system/app directory.

hope you like.

PLEASE NOTE, THIS IS LIKELY TO BE A LITTLE BUGGY IN PLACES, AND I CAN'T GET THE EVIL ANDROID GUY ONTO THE NOTIFICATION BACKGROUND YET,... BUT I HAVE ONLY DONE A QUICK TRIAL AND THOUGHT I WOULD SHARE IT

Please note, this not a FLASHABLE ZIP... just unpack the apk's replace them using root explorer, and reboot your phone.
[Galaxy S I9000 Android Development] Siberian Tiger:
This mod is only for 2.3.2 jv1?
[Galaxy S I9000 Android Development] Netmatrix:
errors

theres a lots of blue stripes below clock
[Galaxy S I9000 Android Development] fufus:
How can I do deodexing by myself? xUltimate doesn't work ;(

PS: I do not want the package to the first post because I have a slow the internet
[Galaxy S I9000 Android Development] Daneshm90:
You can use my "old" script. was written over a year ago O_O

Just select option 2 and put

all the jar's (not odex's) from the framework directory as input

so core.jar:twframework.jar......etc

Then watch it go
[Galaxy S I9000 Android Development] fufus:
Something doesn't work. I upload /system/app/ do /app/ and choose option one. From 116 files I get only 26. What do I wrong?

I'm sorry for off-topic
[Galaxy S I9000 Android Development] Daneshm90:
You need to deodex framework first.

Upload your framework to framework folder

Once all of those are done, then you can proceed with apps
[Galaxy S I9000 Android Development] fufus:
Unfortunately it doesn't wok. I copy .jar + .odex z /system/framework/ to /framework/ and I choose first option. When the process is end files like these aren't processed:

android.policy.jar

com.google.android.maps.jar

core.jar

ext.jar

framework.jar

services.jar
[Galaxy S I9000 Android Development] Daneshm90:
What did you use as your classpath ?

Try this (copy/paste):

am.jar:android.policy.jar:android.test.runner.jar:bmgr.jar:bouncycastle.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.samsung.device.jar:core-junit.jar:core.jar:ext.jar:framework.jar:ime.jar:input.jar:javax.obex.jar:monkey.jar:pm.jar:seccamera.jar:sechardware.jar:sec_feature.jar:services.jar:sqlite-jdbc.jar:svc.jar:twframework.jar
[Galaxy S I9000 Android Development] fufus:
I do it, but some of files remain. I don't understand why it's happen.

PS: I typed them into the classpath

Screen:
[Galaxy S I9000 Android Development] Daneshm90:
Ah my bad. U need to update baksmali/smali.

Download latest ones Link
[Galaxy S I9000 Android Development] [Ramad]:
That was wrong what I wrote earlier about boot.bin/Sbl.bin, boot.bin is not responsible for CWM blocking, but there is a connection between them and the JV1 kernel.

I have tested as follows:

1. JV1 boot/SBL and JV1 kernel: Can enter Recovery(unmodified 3e), so no CWM.

2. JV1 boot/SBL and 2.2.1 kernel: Can enter Recovery(2e) and can use CWM, the device can't boot android OS course.

3. XWJS3/JPJPA boot/Sbl and JV1 kernel: The device can boot android, but no Recovery at all, if you press Volume Up + Home + Power On, the device will be stuck at boot, so no CWM.

At first I thought that the modified 3e that I have copied over to the device is being replaced by the unmodified stock 3e in the kernel, well that is not the case either, I did remove the modified recovery completely as in situation 1 and tried to enter recovery, well, that was no problem for the device and when checking if there was any recovery file in /system/bin I found out that there was no recovery file at all...my guess now is recovery is located in the kernel itself (initramfs or build in the kernel itself) and boots to recovery from there, not from the firmware as we were used to.
[Galaxy S I9000 Android Development] fufus:
Unfortunately, still not working

Screen (files with the original name (baksmali-1.2.6 & smali-1.2.6):

Screen #2 (files renamed [baksmali-1.2.6 => 1.2.3 & smali-1.2.6 => 1.2.3])

may be a bug in deoall, deoAPK and deoJAR

Sorry for my english
[Galaxy S I9000 Android Development] Daneshm90:
Are you sure ur using the bootclasspath i posted ?

Because ive had no errors with that exact thing
[Galaxy S I9000 Android Development] g00ndu:
I was only concern about rolling back to 2.2.1 without any problems. Looks like I can play with this firmware now.

Thanks for your tests. :)
[Galaxy S I9000 Android Development] fufus:
the bootclasspath effect is the same
[Galaxy S I9000 Android Development] [Ramad]:
I hope that you don't mind that I give a suggestion, I usually deodex using a set of tools, apk manager, xUltimate, deodexer..etc. I have deodexed this time using android kitchen v.0116(this is somehow old) and v.0135 and apk manager.

As did deodex stock firmwares for some time now, I rarely find any deodex tool to deodex a whole set of apk files. So if you get stuck then try another tool and so on.
[Galaxy S I9000 Android Development] Daneshm90:
Ok then manually i guess attend to the needs of the classpaths.

So start with framework.jar

See if that solves any of the odexes
[Galaxy S I9000 Android Development] fufus:
The xUltimate does not work.

I do not understand your post, speak English poorly. Sorry

I do not understand.

What exactly do I do?
[Galaxy S I9000 Android Development] [Ramad]:
xUltimate 2.2.2 does not work with gingerbread. I did mean that you can use many tools, if xUltimate does not work then you try apk manager, if it does not work then you try android kitchen...etc.
[Galaxy S I9000 Android Development] Markyyyyyyyyy:
Yes, if you want for 2.2.1 then check out the steel blue 3.0 thread on XDA or darkyrom
[Galaxy S I9000 Android Development] Daneshm90:
So start by pressing 2 and putting

framework.jar

See if that solves any issues ? Or just use the dump in the OP :p
[Galaxy S I9000 Android Development] fufus:
Unfortunately, does not work.

Thanks for your help

I downloaded the rom Ultibreat so I no longer do so.
[Galaxy S I9000 Android Development] g00ndu:
Ramad

I will be using your deodexed apps and framework files to release a custom rom.

Credit will be given. Hope you don't mind. :-)
[Galaxy S I9000 Android Development] [Ramad]:
I did upload these files to share with anybody who can use them, if you can use them then I'm glad that I could help, you don't have to credit me.

Since you are going to make a costume ROM, I would like to ask to take the following in your consideration:

1. Recovery Mode does indeed run from the Kernel as I wrote earlier, I have been able to locate it in initramfs that has been posted by supercurio yesterday https://github.com/project-voodoo/gingerbread-i9000xwjv1_initramfs-hacked/tree/master/sbin and I did ask supercurio if it can be replaced by the modified 3e, if it can be done then you will have a Kernel that is CWM friendly, I think that you are aware that if you want to use CWM on JV1 then you need to flash a froyo Kernel using Odin and flash back.

2. GPS might not work, it runs fine on the stock and untouched JV1, GPS did not work for me while my device had XWJS3/JPJPA boot.bin and Sbl.bin I did not test that on XWJV1 boot.bin and Sbl.bin (this needs more testing before saying that it's a fact), but if GPS only work while the device is on the new boot.bin and Sbl.bin then this might be a problem since the majority of Galaxy S do have old boot/Sbl installed.

3. I can confirm now from my own device and supercurios thread http://xdaforums.com/showthread.php?t=975349 that a graphics/screen corruption does accrue upon boot while the device has old boot/Sbl installed.

I think that in 2 (if it's a fact) and 3 it will be hard to ask users to flash there devices to the new boot/Sbl to have fully working device/ROM, it's hard to swallow when Odin hangs during flashing these two files and the device for sure is dead. I think that we can live with a small graphics corruption on boot screen while the device is on old boot/Sbl, but not a non working GPS (this needs more testing of course).

I will be testing the GPS issue and report back as soon as I can, I wish you good luck on your costume ROM. :)
[Galaxy S I9000 Android Development] g00ndu:
Thanks Ramad.

Gps is not working. I cannot get any satellites.

Fyi, what i did was flashing the stock xwjv1 using odin. First i flashed speedmod kernel with reboot unticked and go to recovery.Then i tried to do an update zip, but failed miserably. Can't even go to bootup screen. Then went back to recovery and restore my nandroid backup. It was fully restored. I then d/l tricky essential rom and replaced his apps with yours. This time just directly flash via cwm. Notice that there is no screen tears as reported. Maybe my boot.bin and sbl.bin has already been updated during the first odin flash.

Swype doesn't work too, but i thought someone changed the build.prop to get Swype working.

The biggest challenge now is decompiling the Settings.apk. It gives me errors. Without this, we won't be able to have an extended menu anymore.

Edit: I am using supercurio's hacked kernel, which i believe he changed the 3e recovery to voodoo recovery. Works real fine.
[Galaxy S I9000 Android Development] webstar1:
guys you want a deodexed rom try my new ultibread. Updating shortly with some fixes. Its deodexed along with some other feautures which will build up eventually.
[Galaxy S I9000 Android Development] webstar1:
Its Ultibread :)
[Galaxy S I9000 Android Development] [Ramad]:
Making a ROM is the easy part when you have deodexed the apk files, and they are all there in posts #1 and #2. The problem is the not working GPS, does GPS work on your ROM?

It's good that supercurio did change he recovery with the modified one, I'm waiting for Chainfire to release his with the stock kernel.

I have done some testing again, and GPS not running is not related to new or old boot/Sbl but the screen corruption is related to old boot/Sbl for sure.

I have attached a deodexed Settings.apk, I hope that will help you complete your ROM.
[Galaxy S I9000 Android Development] g00ndu:
It is the problem of apktool. Can't decompile without any errors...

Edit: Your name difficult to quote man... :D
[Galaxy S I9000 Android Development] [Ramad]:
:D

Try the latest android kitchen, I have tested it today and it did deodex the whole set but not Email.apk, but that is OK. Just make sure that all of your apk files are not "Read only", andriod kitchen does not force extract/re-pack.

It took me 2 hours deodexeing the first time using a set of tools, if I knew that the latest andorid kitchen could do then I would have tried it from the beginning.
[Galaxy S I9000 Android Development] webstar1:
Deodexing is the easiest part. I put all my files in the deodexer i use and whabam left it for half an hour and deodexed, making a good rom is the difficult part. You got it wrong my friend ;). I did get a lock on gps with my rom. Try and see if it works for you.
[Galaxy S I9000 Android Development] g00ndu:
GPS works now, but still ****ty. :D

Howto make it work?

Changing permission to the following via root explorer (make sure you have it on rw):

/system/vendor/bin/gpsd to rwxrwxrwx

/system/vendor/bin/launch_gps.sh to rwxrwxrwx

/system/vendor/etc/gps.xml to rwxrwxrwx

/system/vendor/etc/gps_ExtLNA.xml to rwxrwxrwx

Note that this is the configuration that I tried and it worked. Able to see satellites and managed to get locked. Accuracy is ..... sighz....
[Galaxy S I9000 Android Development] franksames:
Check this, already solved:

http://xdaforums.com/showpost.php?p=11790078&postcount=33959
[Galaxy S I9000 Android Development] AdamJuva:
Did anyone solve problem with boot screen? (I think boot screen granular picture.)
[Galaxy S I9000 Android Development] topimax:
Gingerbread screen off

Does the gingerbread screen off works on 2.2.1? haven't found the anser yet, even after reading 100 pages in this thead [ROM][2.3.2] I9000XWJV1 (GINGERBREAD) for Galaxy S
[Galaxy S I9000 Android Development] [Ramad]:
This can be easily solved by flashing the stock JV1. The old boot/Sbl from froyo and earlier does not play well with Gingerbread.

If you want to flash the new JV1 make sure that you only use Odin 1.7 or 1.82, connect directly to your PC (no Hub), flash a stock 2.2.1 which does not have boot/Sbl to make sure that your device have a good connection to your PC, when you are sure it's all good flash JV1. If the device hangs during flashing boot.bin or Sbl.bin then it's gone for good.
[Galaxy S I9000 Android Development] Daneshm90:
Its a hella lot of java,opengl,xml code to implement and considering we're dealing with closed source, you're looking at a smali nightmare :)

Anyone runnin linux can you give dex2jar a shot ?

Heard good things about it but never got around to testing it on a linux machine. Link
[Galaxy S I9000 Android Development] AdamJuva:
Thanks :D but I don't flash this version, I am creating new Custom ROM based on XWJV1 and I want to fix it in my version. Is any other path how to solve it, because a lot of people don't be careful on this.
[Galaxy S I9000 Android Development] illdroid:
for those who are interested, deodexerius script can fully deodex XVJV1 (except email.apk)

the script will support future ROMS as well

http://xdaforums.com/showthread.php?t=909149
[Galaxy S I9000 Android Development] rktcool:
Hi, a late addition to the thread, but I am half-hoping that it will help people in the future :

I think you have to first deodex it using baksmali with

-c :twframework.jar

included...
[EVO Shift 4G General] l2icky:
I am running MikShift with 1.8 kernal with Cyan Dragon Theme.

The wireless tether works just fine with the 4g, but it doesn't work with the 3g, are there any threads or a fix or anything info on this?
[EVO Shift 4G General] corybucher:
I'm also having problems with this. I have thread a few post down but unfortunately we haven't found a solution.

Sent from my Evolution
[EVO Shift 4G General] HolyShift:
The only problem I'm having is that devices connected to my phone via Wireless Tether get a LOT LESS speed than my phone will. Full 4G signal on my phone ~5Megs while a connected device will be pulling about 500K.
[EVO Shift 4G General] l2icky:
The 4G works just fine for me, I just can't get the 3G to work.
[EVO Shift 4G General] foolforfood:
I'm having this exact same problem. I haven't been able to figurre anything out either. One this I've noticed is that if I switch to a different app, the tether will stop working until I go back to the wireless tether app itself and then the data will start to flow again.
[EVO Shift 4G General] beezie916:
Ok so I am not the only one...4g works..3g dosen't give me internet access....on my GF EVO too...but I can tether through her hacked sprint hotspot....this thread and the other one needs to be combined i think...
[EVO Shift 4G General] l2icky:
Probably so, is there anyway someone can gain access to a "hacked" sprint hotspot for the Shift?
[EVO Shift 4G General] beezie916:
Well it looks like newkidd might of found out the tether issue..../system/bi/sh is symlinked to bash....

he is working on a fix...but i was helping test and can say fixing the symlink and tether worked perfectly....on 3g...although i know i didn't do this fix Friday when we toyed with it so who knows what the deal was....

The hack apparently takes a lot of work to change from EVO to ours....not sure what dev is going to be able to port it....
[EVO Shift 4G General] JKILO:
Nfinitefx just added a mod to him rom which is a sprint hotspot hack..whether it works or not no clue but it was in his change log just recently..maybe you could pull something out of there?
[EVO Shift 4G General] foolforfood:
Has anybody tried deleting their spint hotspot? I'm going to try that and check back later tonight.
[EVO Shift 4G General] foolforfood:
Well deleting the spint hotspot made no difference. Now a few days later I can't even tether on 4G. Quite frustrating, this. Any suggestions?
[EVO Shift 4G General] JKILO:
What rom are you on...I know stock it works..mikrom has an error on sh 3.2 which is being worked out and evervolve it works
[EVO Shift 4G General] foolforfood:
I was using miks rom, which was letting me use tether on 4G until today. I just switched to nfx stock, still not working.
[EVO Shift 4G General] JKILO:
I meant the actual stock rom but nfx is working on a sprint hotspot hack
[EVO Shift 4G General] danaff37:
Guys, I submitted an issue on their google code page, feel free to go comment and knock this thing up to a hot issue so they will look into it. lol

http://code.google.com/p/android-wifi-tether/issues/detail?id=878
[EVO Shift 4G General] Jeezimus:
OK I'm glad to see others are having this issue.

Prior to yesterday, I was only able to tether on 4G using Wired Tether OR Wireless Tether. As of yesterday, I can no longer tether AT ALL.

I've tried flashing back to the completely stock ROM (only had root mod) that preludedrew posted and I'm still experiencing this issue. The only other thing I could possibly do is RUU and then re-root.

Has anyone found a solution to this? Is this a sprint issue or individual phone? Are some people not affected at all? I have been using the stock ROM, rooted and with bcnice's 1.8 GHz kernel since root.

I use my phone as my primary internet so this is a HUGE detriment for me and also a GARGANTUAN downside for the phone. I'm wondering if Sprint is finding a way to outsmart us...

EDIT: Azilink appears to still be working fine for tethering. Although it does take a bit more of a setup and some familiarity (marginal) with adb, it also typically performs much better as well. Brandock made a post about it in the apps forum, a search should pull it up fairly quickly.
[EVO Shift 4G General] djquestt:
Well with stock root wireless tether wasw working fine once I switched roms it stopped working so you do the math
[EVO Shift 4G General] foolforfood:
My 4G tethering came back oddly enough. Maybe it was my area.
[EVO Shift 4G General] Jeezimus:
Mine is back working now too...that's really weird.

NYC here.

Guess I wasted my whole day yesterday trying to figure this crap out =(
[EVO Shift 4G General] beezie916:
This is an issue with the ROMs not the app or anything. The symlin for /system/bin/sh is wrong....thats why when you go into terminal you see sh3.2 if you remove it and make a new symlink wireless tether will work....i can post the commands I was given that worked fine but I make no guarantees it will work or that it wont do something bad to your phone but I will give you the commands I used.

using terminal and your /system will have to be r/w

rm /system/bin/sh

ln -s /system/bin/sh0 /system/bin/sh
[EVO Shift 4G General] danaff37:
I can tether 4g fine with my sh linked to bash. Doesn't fix 3g does it? didn't for me
[EVO Shift 4G General] foolforfood:
Me too I guess haha. Los Angeles here.
[EVO Shift 4G General] foolforfood:
Quick question to the OP, are you using the BFS kernel or just the normal 1.8?