Hi guys, rooting my galaxy S2, or trying to. Downloaded the GT-I9100_XXKI3_insecure file from http://forum.xda-developers.com/showthread.php?t=1101671, but when I extracted the file I get a XWKDD_insecure.tar file, in other words a different name from XXKI3. I don't want to mess up my phone in odin by using the incorrect kernel, so can somebody explain why I'm getting a XWKDD when I (seemingly) should be getting a XXKI3 .tar? is it the correct one despite the different name?
Thanks.
Related
Need help. I am trying to restore my Skyrocket to factory. I down loaded the necessary files
-ODIN
-SGH-I727-UCKJ2-k0nane
The thing is that when I open Odin, click PDA and browse, I don't see the tar file(SGH-I727-UCKJ2-k0nane)? Do I have to convert the file to tar?
The SGH-I727-UCKJ2-k0nane is in the download file and I see it but when I use Odin to browse, I don't see the file?
Am I doing something wrong or am I missing a step?
I am using Window's Vista. Does it make any difference?
I have read instructions many many times and I can't figure it out.
anyone out there?
Sorry bro. I would help you but seeing as I have yet to have my SkyRocket in Hand and have not gone through the rooting and ROM process on THIS device. I am not comfortable giving advice. Best to wait for someone who has more experience with the SkyRocket than I.
Juroid said:
Need help. I am trying to restore my Skyrocket to factory. I down loaded the necessary files
-ODIN
-SGH-I727-UCKJ2-k0nane
The thing is that when I open Odin, click PDA and browse, I don't see the tar file(SGH-I727-UCKJ2-k0nane)? Do I have to convert the file to tar?
The SGH-I727-UCKJ2-k0nane is in the download file and I see it but when I use Odin to browse, I don't see the file?
Am I doing something wrong or am I missing a step?
I am using Window's Vista. Does it make any difference?
I have read instructions many many times and I can't figure it out.
Click to expand...
Click to collapse
the .tar file is INSIDE the file you downloaded. the file you downloaded is a .7z or 7zip file. 7zip is a free archive/extractor. unzip it with 7zip and you will find your tar file.
i find it always helps to have your WINDOWS configured to show file extensions to keep confusion like this to a minimum, since you would have actually seen the file extension type.
careful! this method trips the ROM counter. why are you returning to stock?
I figuered it out. I bricked my phone trying to update to 2.36.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
You know there is a cwm flashable rooted zip for 2.3.6 right? Its here http://forum.xda-developers.com/showthread.php?t=1361144
I have a Samsung Galaxy Tab Plus Wi-Fi only GT-P6210 that I want to flash back to stock ROM using ODIN. I have found two packages at this thread. (I can't post to the following thread because I'm a noob)
http://forum.xda-developers.com/showthread.php?t=1367478
One package has only one file that I know is the PDA file. The other package has 3 files:
GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5
P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5
P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5
The CODE file is the PDA file, correct?
The CSC file is the CSC file, duh.
What is the APBOOT file?
Can you also explain what the different files are? What is a CSC file? What is a PIT file? Why does the other package only contain the PDA file?
I've never ODIN'd before so I want to make sure I know what I'm doing and flash the correct package.
bdarc said:
I have a Samsung Galaxy Tab Plus Wi-Fi only GT-P6210 that I want to flash back to stock ROM using ODIN. I have found two packages at this thread. (I can't post to the following thread because I'm a noob)
http://forum.xda-developers.com/showthread.php?t=1367478
One package has only one file that I know is the PDA file. The other package has 3 files:
GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5
P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5
P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5
The CODE file is the PDA file, correct?
The CSC file is the CSC file, duh.
What is the APBOOT file?
Can you also explain what the different files are? What is a CSC file? What is a PIT file? Why does the other package only contain the PDA file?
I've never ODIN'd before so I want to make sure I know what I'm doing and flash the correct package.
Click to expand...
Click to collapse
I have the same question my self but didnt know where to look... Hopefully you get an answer soon cause id like to know to, my tab got screwed up and i dont know how to get the original firmware back and no clue how to properly flash the odin with out screwing it up more, so hopefully this works
I have spent several weeks working on this (reading thread after thread) on modifying stock firmware and im running into a problem. I more or less want to know if what i want to do is actually possible. I have downloaded the original .tar.md5 firmware image, opened with 7zip and "extracted" the .tar file (more or less just removed the hash) and then extracted the .img files from the .tar file. I have unpacked/mounted/modified/repacked using several methods (dsixda kitchen -which havent been able to work around adding the java path since after i add the path cygwin thinks im missing clean app until i remove the path in which case i get an error saying it cant find java/ i have tried mounting using ext4_utils in ubuntu) my issue arises when i take my modified and repacked system.img file i cant get it to work either by 1. zipping it in a .tar with the other .img files and flashing with odin, 2. zipping system.img alone into a .tar and flashing with odin, 3. installing cwm/root and flashing the system.img)
More or less my question is
1. is it possible to modify the stock firmware and load it onto the tablet without rooting
2. can system.img be flashed by itself or does it need the other .img files in the same .tar
3. does the tar file require being signed before flashing even with CWM recovery and root already on the tablet?
I have used these forums for a while to find answers, but i am new to posting, i havent needed to post a question until now since i spend as much time researching as i can before bothering people with a question (i like to figure stuff out and hate to admit defeat) Thanks in advance for the help despite my noobishness
every time i flash a custom rom it says no md5 file found i need help with it please. i have a samsung gs3 verizon 1535
Unless the file you're flashing ends in .md5 it will always say that. If you're just flashing a standard .zip, you will have to verify the md5 yourself before you flash the file with a third party app on your phone or pc. Other than that, nothing to worry about.
ok thanks alot
Hello y'all.
I got this SM-A530F/DS, a galaxy A8 (2018), from a relative that got a problem. I am not sure about specifics, but it was never tampered with or rooted, I believe that things start to go bad after an unsuccesful OTA update. The phone does not boot, it just stays on samsung logo screen indefinetly, I can put the phone on download mode though so I think this is fixable by flashing the stock rom anew.
Now I got the stock firmware from sammobile and it seems good, but it is on a format for Odin, unfortunately I dont have access to a Windows computer, just Linux. So I got heimdall and read through whatever info I could find and I think I grok the fundamentals.
TLDR:
I have the following questions about the process:
1) Inside the stock files there is a .pit file that I assume is tailored to the stock ROM being distributed, should I use this .pit or should I use the one that I can extract from the phone with Heimdall?
2) The .img files seem to be lz4 compressed so should I first decompress those, or can I pass the compressed file to heimdall?
3) Inside the tar file for Odin {AP, BL, CP, CSC} there are a meta-data folder with a fota.zip file, does this file in any way influence heimdall flashing process?
p.s. I not sure if this should be moved to the device subforum as the questions mainly deal with the Samsung devices and heimdall in general and I could not find a Samsung sub forum to post this to
So I got the situation sorted.
1) The .pit file in the stock rom was the same as the phones, so I didnt have to do anything about that
2) The .img, .bin files must be decompressed first, not a great deal just had to 'lz4 -d' those
3) Those fota.zip didnt matter for heimdall, I just followed the phones .pit file to match partition names to partitions file and did a single 'heimdall flash' command