Related
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.
Okay.
So I'm very new to all this, but I managed to get safestrap (3.75) working on my Galaxy note 3 (AT&T) and attempted to install a custom rom. However, in my ignorance I somehow managed to screw something up majorly and cannot restore to my stock rom nor can I seem to use the method in the guide that involved Odin and Heimdal to do so. Using safestrap I am able to enter download mode and still create ROM slots, however I have noticed system errors when I do so. Most confusing of all however, when I use safestrap to check the stock rom and why I cannot copy system files to it, it says that there is a system partition size of 0. I would appreciate any advice on where to go from here.
If this is actually very simple to solve, please forgive me.
Hi All,
I'm not sure if this is the right place to post this as I'm relatively new to posting on XDA. My girlfriend has a Galaxy S4 (I337) that I quickly and easily installed Cyanogenmod on. It's awesome and significantly better than TouchWiz. So, I bought an S4 off Ebay assuming it would be similar enough. It turns out this new S4 is an I9500 and before shipping it was updated to 4.3, which appears to lock the bootloader and prevent downgrading. I've tried Odin, Heimdall, ADB, Philz, Chainfire, Cofface, stock ROMs, etc with no luck. Today I did manage to root the phone and confirm root with TowelRoot. I'm wondering/hoping someone might have some resources to get CM on this thing. While I'd prefer not to brick it I am willing to take risks as I have a Razr (soft-bricked and unbricked) running CM and am relatively comfortable with computers/Linux.
I've been Googling and trying things for a month now and can't even find that much information on the locked bootloader. Any help would be greatly appreciated, thanks.
--
SL
The I9500 doesn't have a locked bootloader. You just can't downgrade from 4.3 to 4.2.2 with official roms. Same applies when you are running 4.4, then you also can't downgrade officially.
Just flash a custom recovery true Odin and flash away.
Why would you even want to downgrade? Are you sure you are picking the right files? You cant flash the files for the I337 on the I9500. So just go to the section for the I9500 roms and flash away.
Hi Lennyz1988,
Thanks for the quick reply. I don't specifically want to downgrade but that's the last option I've tried. Ultimately the goal is to put Cyanogenmod on the phone. When I attempt to upload any file via Odin I get "secure magiccode check fail : boot" (or fail : recovery) depending on what I'm flashing. All the reading I've done says that when these phones are updated to 4.3 a fix has been applied that stops Odin from working. Thus, I my last resort is/was to try and downgrade. As I said, I've been Googling for the last month and while few people have posted about this I have not found any solutions.
Hoping someone might have a solution or anything new to try that I haven't tried already, thanks again,
--
SL
Download the latest TWRP recovery:
http://techerrata.com/browse/twrp2/i9500
Fire it up in Odin under PDA. You need the .tar (DON'T EXTRACT IT).
If it fails:
- Different usb port
- Different cable
- Different pc
- Reinstall drivers
- Make sure Kies is not running the background.
Or you can use heimdall to flash it. Use the command line though:
heimdall flash --recovery nameoftherecovery.img (you need the .img instead of the .tar)
No luck there, Odin still fails with the same message. I have tried Heimdall on 2 different computers (4 different usb cables) and always get the libusb 12 error.
Since I have root access I figured I might be able to wipe the recovery partition from a terminal emulator. I copied recovery.img from the I9500 CWM to the internal sd card. I then went to /dev/block/msm_sdcc.1/by-name to figure out what partition is recovery, turns out its 21. I then did “dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21”. I then booted into recovery and it just hung up. I had previously found a stock recovery partition so I flashed that via Odin (the only file I have found that works flashing via Odin). I could then boot back into the normal recovery. I then tried flashing both recovery and cache with the CF Auto files (cache is partition 18). Same result, it just hangs when trying to boot into recovery. At one point I did manage to flash a recovery that then came up with a warning about “software installed that is not supported by AT&T” and I couldn’t get past that so had to flash the stock recovery again.
On a side note, I accidentally wiped the EFS partition in this process (if found a tutorial that shows the S3 had recovery in partition 10, which is EFS on the S4). As a result 1.) the menu didn’t pop up when I hit the power button and 2.) wifi didn’t work. So, I made an .img of the EFS partition on my GT-I337 and moved it to the I9500 and that worked restoring both. In case anyone makes the same mistake.
I have now also used CWM ROM Manager and GooManger and tried installing recovery that way with no luck.
Just check if the internal memory partitioning is correct ( number, size and format) (use fdisk or parsed).
ODIN will install according to the PIT file and if drivers and cables are OK it is no other explanation than that.
PS: do not trust heimdall data because it just read the PIT file and do not give the true info from the memory part.!
Uhm on the TWRP website they say that the I9500 has it on partition 10.....
This would be the proper partition based on their website:
mmcblk0p10
Are you absolutely sure you have an i9500? Because my guess is that you don't.....
Boot into download mode. What does it say your model is?
Because on the AT&T it's partition 21.... So my guess is that you are messing up....
Thanks everyone for the input/feedback,
Something I think I had forgotten to mention previously, when the initial root/recovery attempts didn't work I downloaded an app to verify it is a genuine Samsung as I have heard of very good knock-offs. It is genuine according to the app.
Good point/catch regarding the location of the recovery partition. Under About Phone it shows as an I9500 and always has. When in download mode it currently shows as I337 but I wasn't sure if that was simply a result of all my attempts so I figured best to go with the one I am certain has been the same since I bought the phone. I had been hesitant to try wiping the recovery with for the I337 as that is how I soft-bricked my RazrHD (ultimately un-bricked it).
Tonight I will try the I337 files and see if Odin is successful. Thanks again.
Damn! Turns out my phone is an I337. The hardward (under the battery) says I9500 and when I plug it into a computer it shows up as I9500. On the weekend I thought I read that there is now the ability to flash recovery and install CyanogenMod on I337 if its updated to 4.4.2. So, I donwloaded the firmware and flashed with Odin. It flashed successfully but now I realize I am mistaken and 1.) cannot flash recovery, and 2.) cannot downgrade. For the time being I have installed Nova Launcher and removed as much of TouchWiz as possible. It's not perfect but at least usable. I'd like to start researching what it would take to flash recovery on this phone but I suspect I'm too busy at this moment.
Thanks everyone for the help,
[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.
[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks
I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.
free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.
Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar
This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?
I am able to extract System.img from the 4.4.4 ODEN install and mount it in Ubunto. I can modify the folders and files to remove bloat, etc. I am able to repack back and use FlashFire to flash the 4.4.4 modified firmware.
My question is related to 5.0. I have tried the same method and after several modifled attempts, was able to extract and mount the System.img. After debloating, etc. I tried to repack it the same way but in FlashFire, it fails the MD5 check.
I tried another approach. Instead of repacking the full firmware package, I just created the System.img as a stand alone flash-able package. I then install 5.0 through ODEN, install Root and FlashFire.
When I try to flash my modified System.img through FlashFire, it passes the MD5 and installs successfully but it never boots. It never even makes it to the initial boot screen.
After that, I have to ODEN back again and start over. Any dev's out there that might know what I might be missing or can point me to some documentation on the process for 5.0?
I used SuperR's Kitchen to customize my Note 3's Lollipop, then Flashed via FlashFire.
http://forum.xda-developers.com/chef-central/android/kitchen-superrs-kitchen-t3202296
Looks like the kitchen will make it a lot easier. I checked one out a while back but the dev said it wasn't supported anymore. Thanks!
Sent from my SM-N900V using Tapatalk