Database Users

HELP : accidentally uninstalled TouchWiz

I accidentally uninstalled Touchwiz using Titanium Backup. Since I already use ADW.Launcher, I thought its not a big deal, until I did a hard reset.
Upon hard reset, my Galaxy S tries to install Touchwiz, which of course fails, and the darn phone just crashes and hangs. I managed to get it to boot up eventually after some trouble, but I'll prefer not to have to do this everytime I hard reset.
Can someone please please send me the TouchWiz apk and odex files so that I can put them back in the system directory ? I'm using stock Froyo 2.2 ( Build FROYO.DXJPA, Kernel 2.6.32.9 ). Please email them to [email protected], or tell me where I can download them.
I know this would cease to be a problem if I just flash a custom rom, and I would love to try that in future, but not now.
Thanks so much in advance.

Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje

JJEgan said:
Easy way would be to go to the Rom Kitchin build update zip with only the Touchwizz in it and flash it from SD card via CWM.
http://romkitchen.org/sgs/?s=generator
APK might be in Perkas file stash from this forum ..###
jje
Click to expand...
Click to collapse
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.

I agree with jje. The best and probably easiest way would be to flash 2e recovery. Chainfire has created a kernel for that purpose and as long as you can access download mode you should be fine.
Sent from my GT-I9000 using XDA Premium App

chriszzz said:
Thanks, but I'm on 2.2, which means I have the 3e loader which does not allow me to setup update.zips which are unsigned. For this reason, i was also not able to get CWM installed. I know there's a way to downgrade the loader to 2e, but I'll rather not try that at this moment.
Click to expand...
Click to collapse
Flash SpeedMOD kernel with Odin and you'll get CWM.

Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Intratech said:
Flash SpeedMOD kernel with Odin and you'll get CWM.
Click to expand...
Click to collapse

I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
chriszzz said:
Hi JJEgan, anfearg, Intratech
Thanks for the advice so far. But would it be possible for me to just simply use a file manager to copy the TouchWiz apk and odex files to my system/app directory ? My phone is rooted, so I know it's possible as long as I can get those files. I'm just not sure if there's anything else that needs to be configured to get Android to use those files during setup. If this is workable, this would be the easiest route. Now I just need to get my hands on those files.
I know Odin can fix this, but I'll rather just stick to the current stock rom for now, and just add the missing 2 files.
Click to expand...
Click to collapse

OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
chriszzz said:
I'm going to take a look at Odin and see if its not too risky to flash my i9000. I've flashed my old WinMo phones in the past, so flashing is not new to me. But I've yet to try it for Android. Maybe I'll give it a go.
Click to expand...
Click to collapse

chriszzz said:
OK, so I spent a couple of hours googling and downloaded Odin, a couple of stock ROMs, PIT files and USB drivers. Fired up Odin, followed instructions, and I'm now back to 2.1 with the 2e loader. Sweet. Had a heart stopping moment when Odin said "FAILED" in red, so i just reflashed another ROM and it went through successfully.
Looks like I'm in the ROM flashing crowd now.
Quick question : some ROMs ( like the one I flashed successfully with Odin ) contains just a few tars - 1 each for CODE/PDA, CSC and MODEM/Phone.
Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Does each ROM come in both forms ? Can they be converted from 1 form to the other ?
Click to expand...
Click to collapse
the .tar types are to be flashed via odin only whereas the ones with the directories are to be flashed via CWM(2e recovery).... mix them up and you'll be in trouble... ;-)

You only needed to flash the recovery 2e zip file through Odin from the forum .
jje

chriszzz said:
<snipped>.. Others ( like the one that Odin failed to flash ) just contains a bunch of directories with files that have bin, rfs, lfs extensions.
Why are there 2 different types of ROM packaging ? Is the first one ( with the tar files ) specific to Odin ? How do I flash the other type then ? With ClockWorkMod ?
Click to expand...
Click to collapse
The single .tar file with .rfs, .bin, etc. is a high-level package. It's sort of a firmware update and can only be flashed on top of an existing firmware. That is, you don't tick re-partition in odin. The ones that come with 3 separate files for CSC, PDA and MODEM are either medium or low-level packages. I think, the low-level ones come with bootloaders. These can be flashed with re-partition ticked.

Thanks guys.
Today I learned how to flash using ODIN (flashed a European 2.1 ROM onto my international i9000 originally with Asian ROM, and downgraded my 3e loader to 2e).
Then I learned to use ClockWorkMod, which I used to flash Darky's ROM 9.5 ( nice ROM, although booting up seems to take an usually long time. Not sure why ). Finally, I almost had a heart attack, twice, when my phone refused to boot after flashing. Nothing a 3 button combo to download mode couldn't fix though.
Fun fun fun. Thanks all.

[JVH Install Help] Bell Canada

Here's what I did to get JVH (with 850mhz band) and CSC for Canada on my phone. It worked for me at least
Files:
SpeedmodK15E_withLoaders.tar.md5 (8.38 MB)
http://www.multiupload.com/SRVH1BTK8R
JVH_KC1_BMC.zip (169.32 MB)
http://www.multiupload.com/1FHETKJOWA
StockJVH_Kernal_noLoaders.tar.md5 (5.47 MB)
http://www.multiupload.com/PM3AXR7JFG
**************Disclaimer:***************
I'm not responsible if this bricks your phone, as "the boss" said if I break mine, she'll break me... or I get a $20 replacement phone
Backup your /efs folder, backup EVERYTHING, just in case... I'm paranoid so I did it all
ROM NOTES:
Got deodexed from here:
http://forum.xda-developers.com/showpost.php?p=11256520&postcount=1
Modem:
KC1
Busybox:
1.18.4
Hosts file updated for ad blocking using:
http://winhelp2002.mvps.org/hosts.htm
Here's the steps I followed:
Save all files to folder/desktop
Connect phone via usb and copy JVH_KC1_BMC.zip to root of sdcard
Restart phone in download mode
Open Odin and click PDA
Select Speedmod tar file
Uncheck Auto-Reboot
Check F.Reset Time (I don't know what it does, but it's always checked)
Flash the tar.
Once complete and the box says "PASS" in green, unplug your phone and pull the battery (I was told it's safe, as it's in the MIUI instructions as well)
Put battery back in and start phone in recovery with VOL UP+HOME+POWER
In recovery choose to update from zip
Choose file from sdcard
Choose the JVH_KC1_BMC zip file and update
The phone will restart/install.
Once it's started up for the first time I recommend restarting in download mode and flashing the stock JVH kernal
You can also use any kernal you want.
Let me know if I can help at all. I was trying to make a completely odin flashable tar for this but failed miserably :9
I'll do my best to answer any questions however this is my first time making something to flash for you all
Note:
I'm not sure where to put this, sorry to mods/admins if it's in the wrong spot, please let me know

Hi,
I saw your thread, and I found it very interesting for people who own a Bell SGS 9000m Vibrant and wanna upgrate to Gingerbread.
So I decided to flash the Gingerbread JVH ROM just like you did, but I need to know a few things:
1. Will I be able to downgrade to my original stock froyo after this flash ?
2. Will I be able to update via Kies in case Bell release an official gingerbread update ?
3. Right now my phone is SIMUnlocked, will I lose my SIMunlockation after the flash ?
4. And is my actual configuration right to excecute this flash or should I flash something else before ?
My configuration is the following:
Baseband version
I9000UGJL2
Firmware
2.2
Kernel
2.6.32.9
[email protected] #3
Build number
FROYO.UGJL2
galaxy s vibrant bell
gt-i9000m
Thanks for your hard work, I hope to read back from you soon.

I have exact same configuration and exact same questions as poster above!!!

Still no answer... Guess we'll have to try if wanna know...

nguetto said:
Hi,
I saw your thread, and I found it very interesting for people who own a Bell SGS 9000m Vibrant and wanna upgrate to Gingerbread.
So I decided to flash the Gingerbread JVH ROM just like you did, but I need to know a few things:
1. Will I be able to downgrade to my original stock froyo after this flash ?
2. Will I be able to update via Kies in case Bell release an official gingerbread update ?
3. Right now my phone is SIMUnlocked, will I lose my SIMunlockation after the flash ?
4. And is my actual configuration right to excecute this flash or should I flash something else before ?
Click to expand...
Click to collapse
1. yes, it's possible
2. yes, but you would either need to downgrade first or do a kies hack
3. no
4. you can do it straight

Thanks zorxd.
I am going to try. So there is no need for me to select any Pit file or did the guy forget to mention it ? Also can we tick the repartition option in Odin?
Sorry if I ask usekess question I am used to flash android but new to the SGS flashing...

when you repartition you need a PIT file.
My advice is to not repartition unless you need it.

Too late... I did it got stuck into bootloop. I had an error when I tried to install the zip from the recovery (I had recovery 3e) : E : Short write of /tmp/sideload/package.zip (No space left on device) . However, I flashed the back eclair JHL and went back to the stock eclair rom. I am going to restart from there following your intructions. I now have recovery 2e ( Somehow I can't get ClockWorkMod Recovery to load directly; it always send me to recovery 2e and there I apply update.zip to go to CWM recovery)
Thanks for your help, I'll let you know if I manage to get it done.

Still get the error E:Short write of/tmp/sideload/package.zip (No space left on device) when try to install JVH_KC1_BMC.zip from the recovery 3e ( this recovery comes right after I flash SpeedmodK15E_withLoaders.tar ...
Don't know what else to try... Help please..

I did it a slightly different way. From 2.2, I flashed a stock 3 part gingerbread rom (phone, PDA, CSC) with bootloader update using ODIN 1.82. I then flashed CF root gingerbread kernel for CWM3 and then flashed the KC1 modem from clockwork recovery for the 850 band.

Could you please show me the exact files you used so I can try to do the same ?

Aren't there at least a couple threads on how to install jvh/jvp on an i9000? Its the exact same process as those you just have to flash the kc1 modem via cwm after you are done. It sounds like you guys are experimenting too much.
Sent from my Darky's i9000m

nguetto said:
Could you please show me the exact files you used so I can try to do the same ?
Click to expand...
Click to collapse
Our canadian phone is not really different from all the other ones, so you don't need a special "Bell Canada" installation.
If you want JVH, you can follow this thread:
http://forum.xda-developers.com/showthread.php?t=818556
You don't have to do everything like fugumod, etc. I would flash JVH via odin and then flash CF root kernel via odin so you get CWM3.
There's also leaked 2.3.4 JVP gingerbread out, if you feel inclined:
http://forum.xda-developers.com/showthread.php?t=1102881
There's a way to enable 850 band on the different gingerbread modems, but i never bothered, I just flashed the KC1 modem for Bell which has the band (via CWM3). Search for I9000UGKC1
http://forum.xda-developers.com/showpost.php?p=9874879&postcount=1

Okay I am really starting to freak out now...
I am stuck in bootloop, I can't get out og it. I tried flash Back the Stock Bell Firmware but it keeps boot looping. Download mode is okay. But it started doing this I had a message like sd could not be mounted in recovery 3e. Now I can't even access recovery after I flash Eclair but Download mode is still okay...
Aby ideas ?

Have you tried flashing back the stock JL2 firmware from bell? (found on samfirmware.com)
I've never encountered this error before, I wonder if it is a problem with the bootloaders, as the official froyo firmware from bell had a secondary bootloader and gingerbread has its own bootloaders as well.

nguetto said:
Okay I am really starting to freak out now...
I am stuck in bootloop, I can't get out og it. I tried flash Back the Stock Bell Firmware but it keeps boot looping. Download mode is okay. But it started doing this I had a message like sd could not be mounted in recovery 3e. Now I can't even access recovery after I flash Eclair but Download mode is still okay...
Aby ideas ?
Click to expand...
Click to collapse
I imagine you'll need the stock bell firmware as said above and also the proper PIT file to go along with it.
Sent from my Darky's i9000m

Also if you repartitioned it when you tried to flash the whatever it was when you tried you will also have to repartition it when going back down to froyo.
2.2 and 2.3 use different bootloaders therefore if you try to mix and match rom's without the bootloaders and repartioning you will get a ****y phone.
Sent from my Darky's i9000m

Thanks for your help guys. I didn't solve it yet, but i will open a new thread to prevent this one from getting to messy.

Bootloop while flashing JW4

Hey, I tried flashing JW4 stock rom via ODIN which I downloaded from sammobile.
The name of the file is I9000XXJW4_I9000OXAJW4_XEU.zip and on extracting there were 2 files called JW4_JW4_JW4.tar & SS_DL.dll. I selected the tar file in PDA and flashed. The process passed but am stuck with bootloop. Plz help

I also flashed a jw4. But that was without the dll.
Anyway, after i flashed and it booted up i got a doozen errors telling me it couldnt mount different partitions.
So i gave it up as a bad one and found a thread here at xda with different stock roms and ended up with jw5.
No complications whatsoever. Yet
just google for "stock roms i9000 xda" and you should stumble over the thread i believe.
Good luck
Sent from my GT-I9000 using Tapatalk

I faced exactly the same problem: bootloop after flashing XXJW4 and many mount errors in the screen. I concluded that this firmware is not standalone in the sense that you cannot flash and repartition the device using it. Following this logic I performed these steps, leading me to a successfully recovered and fully functional XXJW4 phone:
Flash it with a full stock firmware, e.g. XXJVU (mark "repartition" as well).
Flash XXJW4 as you have done it, but make sure "Repartition" is not selected. That is, just select the tar file in the PDA field and leave the rest with the default options.

Another huge problem Got Black Screen Of Death. Am able to get my phone on to download mode but odin is not detecting my phone. HELP ME What to do?

bindaasathar said:
Another huge problem Got Black Screen Of Death. Am able to get my phone on to download mode but odin is not detecting my phone. HELP ME What to do?
Click to expand...
Click to collapse
Use another USB port. You can flash deodex version of JW4 which doesn't have any problems

bootloops
Factory Reset / Cache Wipe /
use by the Pitfile from JW 1 and flash the JW 4 ,that`s it !!
LG.G.

jpabloae said:
I faced exactly the same problem: bootloop after flashing XXJW4 and many mount errors in the screen. I concluded that this firmware is not standalone in the sense that you cannot flash and repartition the device using it. Following this logic I performed these steps, leading me to a successfully recovered and fully functional XXJW4 phone:
Flash it with a full stock firmware, e.g. XXJVU (mark "repartition" as well).
Flash XXJW4 as you have done it, but make sure "Repartition" is not selected. That is, just select the tar file in the PDA field and leave the rest with the default options.
Click to expand...
Click to collapse
great job. thanks for this

bindaasathar said:
Hey, I tried flashing JW4 stock rom via ODIN which I downloaded from sammobile.
The name of the file is I9000XXJW4_I9000OXAJW4_XEU.zip and on extracting there were 2 files called JW4_JW4_JW4.tar & SS_DL.dll. I selected the tar file in PDA and flashed. The process passed but am stuck with bootloop. Plz help
Click to expand...
Click to collapse
Your PDA file might be missing the dbdata.rfs file, see here: http://forum.xda-developers.com/showthread.php?p=24182099&highlight=dbdata#post24182099, which can cause boot loops.

Help before I break it....

Have S5 SM-G900F - 16GB with PhilZ Touch 6.26.2 and Clockworkmod V6.0.4.7
Was using XtreStoLite_ROM_v2.2_LP_XXU1BOD3 and Blaze.Kernel_ver15 that I installed through SD card and Recovery.
As my S7 has shipped (finally) I want the GF to have my old S5 but need THL (Thailand) system support (I.E. not just thai language but also on the system menus).
I downloaded what I thought was a ROM for this but at the end of Odin flash I had Bad EXT4 flash and on phone 'invalid ext image size is too big'
Reading through the thread someone stated you need the .PIT.
I have ALWAYS avoided these but tried the SM-G900F_pit_16GB file. Yes I need a slap, I know better.....
OK so here it is, I do not know if NAND is corrupt as I do not know the symptoms.
Also, if I only have a soft brick, what is the best approach for recovery / ROM flash ?
Do I always need to do it from SD card / Recovery using a .zip?
Current state of phone.
Seen in Odin.
Can go into download mode.
Can now go into Recovery mode after flashing philz_touch_6.26.2-klte.tar.md5 in Odin.
Reboot loop (obviously, not valid ROM on it now).
I am assuming all is good and it's not a BAD brick, but still have not had a successful flash.
Many thanks
Yes I don't have many posts because I have always searched and found answers, but this time I am a little unsure and don't want to royally screw it up.
Help is much appreciated.

FizzerUK said:
Have S5 SM-G900F - 16GB with PhilZ Touch 6.26.2 and Clockworkmod V6.0.4.7
Was using XtreStoLite_ROM_v2.2_LP_XXU1BOD3 and Blaze.Kernel_ver15 that I installed through SD card and Recovery.
As my S7 has shipped (finally) I want the GF to have my old S5 but need THL (Thailand) system support (I.E. not just thai language but also on the system menus).
I downloaded what I thought was a ROM for this but at the end of Odin flash I had Bad EXT4 flash and on phone 'invalid ext image size is too big'
Reading through the thread someone stated you need the .PIT.
I have ALWAYS avoided these but tried the SM-G900F_pit_16GB file. Yes I need a slap, I know better.....
OK so here it is, I do not know if NAND is corrupt as I do not know the symptoms.
Also, if I only have a soft brick, what is the best approach for recovery / ROM flash ?
Do I always need to do it from SD card / Recovery using a .zip?
Current state of phone.
Seen in Odin.
Can go into download mode.
Can now go into Recovery mode after flashing philz_touch_6.26.2-klte.tar.md5 in Odin.
Reboot loop (obviously, not valid ROM on it now).
I am assuming all is good and it's not a BAD brick, but still have not had a successful flash.
Many thanks
Yes I don't have many posts because I have always searched and found answers, but this time I am a little unsure and don't want to royally screw it up.
Help is much appreciated.
Click to expand...
Click to collapse
Have you tried to flash a stock rom from sammobile ?

Soufiansky said:
Have you tried to flash a stock rom from sammobile ?
Click to expand...
Click to collapse
Yeah!
I tried various and get EXT4 file size incorrect errors.
It was the .PIT incident that was lead from that error.
I have since re-acquired the original de-oxed ROM and flashed that from .zip on SDcard.
All good now, I just thank god I didn't screw it up with a .PIT file.
I was lucky! Leave them files for the DEV's and ignore posts that suggest getting a .PIT file and trying that for .EXT4 partition errors.
Reading posts later, chances are that your getting that error because you have the wrong ROM to flash, having a hidden partition in the ROM, from someone like the UK EE provider.

Hope you remembered to disable reactivation lock during first boot
The reason the ROM was removed in the first place...

Paying to get this fixed

My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol

Re-download the stock rom and flash it

Meboyzram said:
Re-download the stock rom and flash it
Click to expand...
Click to collapse
i did that lol thats when it says "model dismatch fail"

Do you have custom recovery?

Do you have a custom recovery?
Do you have the right and the newest Odin Version?
Did you try it with another transfercable or USB-Port?
Do you have the newest samsung drivers?
Did you have any Odin problems like this before?
My suggestion:
Just do a full wipe on your phone. Downlad the newest Odin Version. Get your device into download mode (maybe try different transfercables or USB Ports and the newest samsung drivers) and see if it works now.
If yes, flash the right Bootloader and Modem for your device and then flash the rom you wanted to flash.
If this didnt work, (and you have a custom recovery) try to reinstall the rom without any backups via the recovery at first and check afterwards, if the device is now recognized by Odin.
Good luck

JustAnotherAndroid said:
My s7 edge got stuck at boot screen so i reflashed stock rom and rerooted then restored the backup i had, it said fail because of low memory while restoring the system and now when i try to reflash the stock rom on odin it says model dismatch fail.
If someone could help me fix this I'm willing to pay something decent, but not a whole lot lol
Click to expand...
Click to collapse
I guess you still have twrp installed.
1. Step: go to TWRP and wipe everything except your SD-Card
2. Step: enter download mode on your device and then plug your usb in (maybe try a different usb-port or even another computer, or another usb cable)
3. Step:Flash the newest bootloader & modem in one step.
4. Step: Enter TWRP again and flash the firmware.zip via the installation process

I dont have TWRP, but i got it fixed, somehow my roomate got it, thanks anyways guys

So all he got was my phone to turn on, im still having this model dismatch fail issue..

Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.

ProtoDeVNan0 said:
Maybe You're trying to flash wrong firmware? What model did You buy?(check box) and what firmware did You download?
If nothing works then download 7zip. And remove all files from that tar.md5 file and leave system.img only. And then try reflashing it.
This way no matter what device You connect it should force flash this image file. Although it might be dangerous (a tiny little bit) so first make sure that You have proper firmware for Your model.
Click to expand...
Click to collapse
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.

If system.img by itself will flash successfully and Your phone won't boot then add slowly more files to that tar file (boot.img, recovery.img etc)
You could also try looking for a pit file for Your phone and then flash it with it. Pit file usually fixes most problems even broken partitions.
And make sure that You put that tar file in AP/PDA.
If nothing above works then send me screenshots of ODIN and the file that You're trying to flash. Maybe I'll notice something. But I hope You'll fix it

JustAnotherAndroid said:
Yes, I've used these files multiple times before i did what i did, ill give that a try, if it works, i owe you.
Click to expand...
Click to collapse
So I tried, and i get some invalid file error
These are the files that are in the AP one
https://gyazo.com/a72785631ad62d412a8c40eb464d3126

I found out my problem, i was still uing the modified version of odin that i used to root my phone