Hello
I have installed Mobile ODIN pro 2.36 .
It tells me that is not compatible with my Samsung GT-I9100P.
In Chainfire's thread "Getting your device supported"
- I cannot find the .PIT or .OPS file for your device, please attach it !
Any idea where these files are located ?
Thanks
Why do you want to mess with the very dangerous PIT file easy way to brick a phone .
PIT will be with the stock firmware on sammobile.com
jje
JJEgan said:
Why do you want to mess with the very dangerous PIT file easy way to brick a phone .
PIT will be with the stock firmware on sammobile.com
jje
Click to expand...
Click to collapse
According to chainfire this is how to get your device supported
The list of devices currently supported by Mobile ODIN is rather short. Not all devices are created equal, and devices need some work to be supported. Currently I am only considering Samsung devices for future support.
At the minimum, I will need some information from you about your device to figure out the partitions, their layout, and how to flash them. You can gather this information by downloading and installing the app. If your device is not supported, it will offer to make a dump file for you. This will take a while. Post the dump file in this thread.
If you can find a .PIT or .OPS file for your device, please attach it !
After that, I will also need a kernel for this device running preferably CWM5, but if unavailable, CWM4 or CWM3 may also do.
If you are lucky, this will allow me to make your device compatible. It may be required that you do some rather lengthy and extensive testing for me.
Click to expand...
Click to collapse
The OP needs the .pit for his device in order to send to chainfire and get his device supported.
Sent from my GT-I9100 using xda premium
Open root explorer.
Navigate to system.
Change to R/W
Long press build.prop.
Change,
ro.product.model=GT-I9100p to
ro.product.model=GT-I9100
Save and exit.
Reboot phone.
Mobile Odin will now work.
[EDIT]...PS So will ktool so you can backup your EFS Folder.
Mobile Odin I9100P support
Dear bored_stupid.
Your solution works perfectly.
Thank you for your suggestion.
Great....
bored_stupid said:
Open root explorer.
Navigate to system.
Change to R/W
Long press build.prop.
Change,
ro.product.model=GT-I9100p to
ro.product.model=GT-I9100
Save and exit.
Reboot phone.
Mobile Odin will now work.
[EDIT]...PS So will ktool so you can backup your EFS Folder.
Click to expand...
Click to collapse
Thank you - U R A diamond!
Related
I have no Imei, No baseband, No reception (obviously)
ive been running cognition 1.51
and have downloaded csc selecter or something similer (that never worked) but i think that may be the issue when i opened it..
But i was wondering if there is a fix for this yet? or if someone can help me with resoring my phone to factory including the format of the efs folder?
ive searched for help about this, but noone has seemed to come up with a solution..
any help would be greatly appreciated
FIXED
cantelog said:
1st off i have a macbook running OSX 10.6.8
i take no responsibility for any bricking
make a backup of efs
NOTE: - Buy Root Explorer
- You have to have root!
- You HAVE to Have SUPERUSER installed
- USB debugging ON on your Phone (Settings>Applications>Development)
- Google is your friend and so am i
-- INSTALL SDK
1. Downloaded the android SDK http://developer.android.com/sdk/index.html
2. unzip the SDK and changed the folder name from "android-sdk-mac_x86" to something simple "android"
3. drop the folder into Applications
4. open up terminal and copy "export PATH=$PATH:/Applications/Android/platform-tools/" WITHOUT THE "
(now you have SDK INSTALLED)
-- THE FIX
1. plug in your phone
2. open Terminal, and open Superuser app on your phone
- NOTE: when you write "su" into Terminal, accept on the superuser app.
In Terminal Write -
adb shell
su
cp -r /efs /sdcard
3. Mount your Sdcard
4. copy and save a backup of the folder efs
5. download hexedit for mac
6. open Hexedit and open NV_data.bin, search for i9100
-should be something like "XX 1.500XSAGT-I9100XXXXSAXXXXXXXX"
7. change the RED codes to your CSC country code and save
here are some country codes
8. open /IMEI/mps_code.dat in Hexedit
- change the Code for your country code aswell and save
9. unmount Sdcard
10. MAKE SURE U HAVE A BACKUP OF EFS
11. Goto Root Explorer and copy contents of sdcard/efs to efs/
12. reboot
13. Yippee
Click to expand...
Click to collapse
Did you back up your efs folder?
Sent from my GT-I9100 using xda premium
cantelog said:
I have no Imei, No baseband, No reception (obviously)
ive been running cognition 1.51
and have downloaded csc selecter or something similer (that never worked) but i think that may be the issue when i opened it..
But i was wondering if there is a fix for this yet? or if someone can help me with resoring my phone to factory including the format of the efs folder?
ive searched for help about this, but noone has seemed to come up with a solution..
any help would be greatly appreciated
Click to expand...
Click to collapse
Just reflash modem.
If you didn't back up your efs folder, you might be out of luck. Try flashing the stock firmware for your provider and see if that helps.
Sent from my GT-I9100
all the flashing i have done over the past year with my sgs i9000 and now sgs2 i9100 i have never seen anything todo with efs.
so no i havnt backed up that folder, that cant be the only way to fix this?
i have looked in my efs folder and there is some files with .bak in them so im thinking some of the roms ive flashed in the past may have done a backup or something?
cantelog said:
all the flashing i have done over the past year with my sgs i9000 and now sgs2 i9100 i have never seen anything todo with efs.
so no i havnt backed up that folder, that cant be the only way to fix this?
i have looked in my efs folder and there is some files with .bak in them so im thinking some of the roms ive flashed in the past may have done a backup or something?
Click to expand...
Click to collapse
If you are missing baseband, there can't be imei either so flashing modem should restore it.
Happened to me a couple of times.
Daagen said:
Just reflash modem.
Click to expand...
Click to collapse
ill do that now
cantelog said:
ill do that now
Click to expand...
Click to collapse
ive just reflashed the modem KH3 and still
NO IMEI
Baseband Unknown
WTF
cantelog said:
ive just reflashed the modem KH3 and still
NO IMEI
Baseband Unknown
WTF
Click to expand...
Click to collapse
It means you still dont have modem for some reason.
If you have flashed new kernels recently, go back to kernel which worked and then reflash modem.
Daagen said:
It means you still dont have modem for some reason.
If you have flashed new kernels recently, go back to kernel which worked and then reflash modem.
Click to expand...
Click to collapse
Im going to flash stock KH3 Kernel, Rom and Modem
because that worked for me in the past
do you recommend i re partition from odin? (could it help/hurt?)
No need for repartition.
Daagen said:
No need for repartition.
Click to expand...
Click to collapse
I flashed Stock kernel KH3, Stock Rom KH3, and Stock Modem KH3, Still have NO Baseband still NO IMEI and still NO Reception. aarrgghh
djnoicatse said:
If you didn't back up your efs folder, you might be out of luck. Try flashing the stock firmware for your provider and see if that helps.
Sent from my GT-I9100
Click to expand...
Click to collapse
Telstra Firmware for I9100 isnt available at samfirmware.com yet, so i cant flash that Branded Rom
cantelog said:
Telstra Firmware for I9100 isnt available at samfirmware.com yet, so i cant flash that Branded Rom
Click to expand...
Click to collapse
When you changed CSC, Your IMEI got corrupted. Only way to restore is efs back up or reverting back to original firmware. This should work ...
If not , You may try this one , http://forum.xda-developers.com/showthread.php?t=837239
I was able to solve it using this method. You need to be rooted to do this ...
This will void your warranty ... so be careful.
I would definitely not recommend using a i9000 method of getting the baseband, imei back on a i9100.
The EFS folder contains critical files for the IMEI, Baseband, serial number of the phone etc.
Check in the Q&A threads and in here someone else also had the same issue and they managed to resurrect their phone with some developer support.
Good luck, only other option is a repair job and just say kies crashed through the firmware update and now the phone doesn't boot.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Virtualsk said:
When you changed CSC, Your IMEI got corrupted. Only way to restore is efs back up or reverting back to original firmware. This should work ...
If not , You may try this one , http://forum.xda-developers.com/showthread.php?t=837239
I was able to solve it using this method. You need to be rooted to do this ...
This will void your warranty ... so be careful.
Click to expand...
Click to collapse
FIXED
Thankyou for putting me in the right direction Virtualsk
if you arent using a pit file dont touch the re-partion box or your will screw your phone completely and dont tick the EFS box either although now that doesnt matter as its already to late.
1st off i have a macbook running OSX 10.6.8
i take no responsibility for any bricking
make a backup of efs
NOTE: - Buy Root Explorer
- You have to have root!
- You HAVE to Have SUPERUSER installed
- USB debugging ON on your Phone (Settings>Applications>Development)
- Google is your friend and so am i
-- INSTALL SDK
1. Downloaded the android SDK http://developer.android.com/sdk/index.html
2. unzip the SDK and changed the folder name from "android-sdk-mac_x86" to something simple "android"
3. drop the folder into Applications
4. open up terminal and copy "export PATH=$PATH:/Applications/Android/platform-tools/" WITHOUT THE "
(now you have SDK INSTALLED)
-- THE FIX
1. plug in your phone
2. open Terminal, and open Superuser app on your phone
- NOTE: when you write "su" into Terminal, accept on the superuser app.
In Terminal Write -
adb shell
su
cp -r /efs /sdcard
3. Mount your Sdcard
4. copy and save a backup of the folder efs
5. download hexedit for mac
6. open Hexedit and open NV_data.bin, search for i9100
-should be something like "XX 1.500 XSA GT-I9100XXX XSA XXXXXXXX"
7. change the XSA codes to your CSC country code and save.
here are some country codes
8. open /IMEI/mps_code.dat in Hexedit
- change the Code for your country code aswell and save
9. unmount Sdcard
10. MAKE SURE U HAVE A BACKUP OF EFS
11. Goto Root Explorer and copy contents of sdcard/efs to efs/
12. reboot
13. Yippee
I was trying to make a call, the person on the other side could not hear me. I reboot and...lost my baseband. Checked IMEI, it was also missing. Tried the solution above, but when I get to the below command:
cp -r /efs /sdcard
I get the message: "-r /efs /sdcard: not found"
I'm using Windows 7, BTW.
Please, please help.
Thanks.
Hi!
I know that I'm asking about forbidden subjects but I have no intention of doing something stupid just want to understand some things about S2.
That's what I think I understand:
- PIT is a file that contains partition layout on our device, that partitions are later flashed with files from rom package (files are partition images in fact)
- Normally we do not need to re-partition because there is only one partition description available on S2 - so all ROM share it (also it's not recommented coz if sth goes wrong we have big problem - device without partitions)
- EFS is one of the partitions and it shouldn't be touched (contains IMEI etc)
Here is my question:
Some people flash ROM with PIT and repartition and still have working device - how is it possible ?? - re-partition should wipe everything including EFS.
EDIT:
One more thing - when exploring XXKP8 rom package from sammobile.com noticed that there is PIT file and some file named
I9100_EFS_I9100XXKP8_CL42141_REV02_user_low_ship.tar.md5
that contains efs.img file I wonder what is this file for. Some generic EFS image ??
Regards
Slig
The pit is used for partition mapping, basically telling the program which block device is which partition. You dont need to use the pit as Odin can pull it from the phone, this also prevents people from using i9000 pits (sgs1, and yes this has happened)
Efs has both generic files and device specific files, I think.
Sent from my GT-I9100 using Tapatalk
Thanks for response !
veyka said:
this also prevents people from using i9000 pits (sgs1, and yes this has happened)
Click to expand...
Click to collapse
Yeah I read about that epic failure. That is why I'm asking - want to know everything before doing anything.
Regards
Slig
slig said:
Hi!
Here is my question:
Some people flash ROM with PIT and repartition and still have working device - how is it possible ?? - re-partition should wipe everything including EFS.
The recommendation is not to flash PIT file or repartition unless you know what you are doing .
PIT does not wipe EFS .
Their is a PIT file description post on the forum .
jje
jje
Click to expand...
Click to collapse
Hi ! Thank You for Your response.
JJEgan said:
The recommendation is not to flash PIT file or repartition unless you know what you are doing .
Click to expand...
Click to collapse
Yes, I'm fully aware of that. I'm just the kind of person that like to know why so I decided to investigate this subject deeper. Another thing is that I'll probably try to use heimdall and that program requires better understanding than "use PDA field in Odin".
You can just flash a .pit file and check repartition. You just have to make sure your flash won't fail. If you have faulty drivers or a damaged usb cable, then it will brick your phone.
If you want to try it, make a flash without .pit and repartition and if it works you can use them. Its just something unexperienced users should not use.
Unless something changes, we don't need to repartition, (one case might be if android plus tw is bigger than 500 ish megs Samsung would need to make the system partition bigger) so we just don't need to use it, and making the risks sound worse it keeps newbies away.
Sent from my GT-I9100 using Tapatalk
I've found Odia's thread GT-9100 PIT v Flash analysis
http://forum.xda-developers.com/showthread.php?t=1104139
Very interesting informations that answers many of my questions.
Hello xda team
Since my Samsung Galaxy SII had many pre-installed apps, I have rooted my phone with the CF root kernel. Now I want to flash back to the original firmware. However, I was always warned in various forums, I shall first make a backup of my EFS folder. Immediately, I was looking for an app to back up, but I need a Hellcat Kernel. I've already found and downloaded the correct version, however, is in the. Zip file contains a folder named "modules_XWLA4" one cifs.ko file. Do I need to flash the file also, or I can ignore? If after flashing the kernel, the software to back up the EFS folder already included or do I have to download yet? Can the EFS folder secure a mistake of my cellphone occur destroyed? How can I later delete the custom kernel without notice it? Just the one-piece flashing official firmware XWLA4 and then use a USB jig?
I have tried very translate the text into English. But can still be errors in it. Please forgive me.
Riseofdead said:
Hello xda team
Since my Samsung Galaxy SII had many pre-installed apps, I have rooted my phone with the CF root kernel. Now I want to flash back to the original firmware. However, I was always warned in various forums, I shall first make a backup of my EFS folder. Immediately, I was looking for an app to back up, but I need a Hellcat Kernel. I've already found and downloaded the correct version, however, is in the. Zip file contains a folder named "modules_XWLA4" one cifs.ko file. Do I need to flash the file also, or I can ignore? If after flashing the kernel, the software to back up the EFS folder already included or do I have to download yet? Can the EFS folder secure a mistake of my cellphone occur destroyed? How can I later delete the custom kernel without notice it? Just the one-piece flashing official firmware XWLA4 and then use a USB jig?
I have tried very translate the text into English. But can still be errors in it. Please forgive me.
Click to expand...
Click to collapse
Do not extract the tar file.
As you have flashed CF-Root, your phone is already rooted and you can use Mobile Odin to flash another kernel.
Here is Chanfire's thread for Mobile Odin => http://forum.xda-developers.com/showthread.php?t=1347899
A little bit work to do, as the free lite version needs the additional FlashKernel.apk to be installed manually. Or just buy Mobile Odin from the Market and everything needed will be installed automatically.
After this, do the following:
1. Connect your phone with USB cable to your PC and copy Hellcat's kernel tar file to your phone (directly into the root of the sd card).
2. Just start Mobile Odin app and select to flash a new kernel.
Then select the tar file for Hellcat's kernel from your sd card.
Please stick to HellcatDroid's description => http://forum.xda-developers.com/showthread.php?t=1182922&highlight=hellcats+kernel
After flashing this kernel, you can start Companion app and backup your EFS folder.
P.S.: If you only want to backup your EFS folder, you can alternatively use the following app => http://forum.xda-developers.com/showthread.php?t=1308546
It is a Windows application which saves the backup to your PC.
Good luck !
Hi. i cant understand the sticky threads at all. i have read it 1000 times.
Lost the signal after flashed Imperium ROM.
I believe i can recover that by restore a cwm backup i did some time ago ?
BUT i have formated the internal phone and no restore files are located. I have it on PC but
have not been able to copy the backup folder to the phone so that CWM can find it ??
And the stickys makes no sense to me..
Damn it.
Just knew i was going the wrong way in Imperium AROMA installer .. :/
Any help plz ?
I have found a way in the forums to find the files in CWM...
/data/media/clockworkmod/backup..... I put them there and i could find the recovery file.
But i just glanced somewhere that i wont restore them modem . :/
Anyway its restoreing, and i hope it works.
If you made a full nandroid then it will restore your modem, but not your efs folder - which is responsible for most no network issues.
You'll have to read through the stickies, particularly the 'before you root' and 'imei know this stuff' ones. I'm not going to type it all out for you.
Follow the instructions to flash a stock ROM with an EMG4 baseband, which solves many efs issues. If it doesn't then you'll need to pay for a repair, about £20.
just realised its bricked.
i have a copy of efs folder on pc but not sure what to do.
EFS Proffesional cant find a backkup in restore tab, even though i believe i did make one.
In my efs folder are.
bluetooth
drm
factoryapp
emei
wifi
and 7 files.
can i copy and paste something to the phone to make it work ?
Yes , copy those backed up efs folder files to your phone's efs folder and reboot. It should work.
sent from the state where marijuanated muffins are NOT illegal !
I would recommend using ADB as copy doesn't retain the required permissions.
Full step-by-step adb guide for this in my IMEI / EFS thread
rootSU said:
I would recommend using ADB as copy doesn't retain the required permissions.
Full step-by-step adb guide for this in my IMEI / EFS thread
Click to expand...
Click to collapse
I use root explorer to copy paste and it did retain permissions but yeah to be on safer side using bridge is more preferable
sent from the state where marijuanated muffins are NOT illegal !
kangerX said:
I use root explorer to copy paste and it did retain permissions but yeah to be on safer side using bridge is more preferable
sent from the state where marijuanated muffins are NOT illegal !
Click to expand...
Click to collapse
Yes root explorer may be better than other file managers with root permissions to be fair. But most people think root exploring is a simple thing that can eb done by any free app
hi and thank you.
I was not able to copy efs folder to phone, or to say, i managed to copy it via Es file explore to the root efs.
But phone ended up with Factory error, so now i have the screen thing on the phone.
I tried to type the guide from root SU in Terminal with no luck, nothing worked or would be regonized, sadly.
I read somewhere that i stock rom might solve the things, so thats where im going now.
I have removed binary counter to 0, and it says im on stock firmware and recovery.
I have installed stock recovery.
BUT im stuck at finding my STOCK ROM.
Im using THIS guide......
http://forum.xda-developers.com/showthread.php?t=2323847
AP: I9300XXEMG4
CP: Unknown
CSC: I9300NEEEMG2
As far as i can read i shall find I9300NEEEMG2 on this page.....
http://samsung-updates.com/device/?id=GT-I9300
But its not there, there are many I9300XEMG4 ?.
I have tried installing KIES, to find my firmware/model. But it wont find my phone.
Im stuck at those 1000 stock roms.
Help plz.
sup3rbuck said:
I was not able to copy efs folder to phone, or to say, i managed to copy it via Es file explore to the root efs.
But phone ended up with Factory error, so now i have the screen thing on the phone.
Click to expand...
Click to collapse
This is because you did not follow suggestions. ES will not do the trick because it will not retain permissions. ADB was your option, or perhaps root explorer.
I did try this page http://developer.android.com/tools/index.html and downloaded SDK pack.
Its pure madness to me, and i was unable to find something that looked like a file browser.
Root explore i did look at, but it did cost some money. And maybe it wont work !
sup3rbuck said:
I did try this page http://developer.android.com/tools/index.html and downloaded SDK pack.
Its pure madness to me, and i was unable to find something that looked like a file browser.
Root explore i did look at, but it did cost some money. And maybe it wont work !
Click to expand...
Click to collapse
FX Explorer and Root add on is free .
Service centre repair is relatively cheap .
I have paid 5$ a month in some insurance, so last resort is i smash it with a hammer so they wont be able to connect it to a computer.
And get a new one. But i wanna learn this stuff for the future.
I tryed fx explore, and the Factory mode has gone now. But still no network, and eimei says null/null ?
sup3rbuck said:
I have paid 5$ a month in some insurance, so last resort is i smash it with a hammer so they wont be able to connect it to a computer.
Fraud and theft is not allowed on XDA .
Click to expand...
Click to collapse
Sure no problem.
as a Blacksmith, stuff might happens when sheit hits the fan.
Thanks for all you answers.
I have fixed my phone with a stock firmware install. :highfive:
firstly i request all moderators of xda in grand 2 forum,
as i am unable to post on developement section,
i am posting the thread here..
plz move it to developement section.
ok now back to topic,
try at your own risk!
i will not be responsible if anything happens to your phone
To all the users who have succesfully rooted grand 2,
there can be a way to install (flash) recovery on your phone!
i was exploring the system and i found a file in "/system" folder
called "recovery-from-boot.p"
i THINK this is the file that causes problem!
you may delete it or rename it...(renaming is safer)
once you delete it, you may flash custom recovery via ODIN
and even if the recovery gets currupted or if you cant boot into recovery, you can simply boot normally and restore the renamed or deleted file!!!
and then once again you may try to flash custom recovery from ODIN (as stock gets deleted as soon as you modify recovery-from-boot.p file)
press thanks if this post helped!
dindt find any file like u wrote.... plss provide specific path.. so we can try
Rakesh251 said:
dindt find any file like u wrote.... plss provide specific path.. so we can try
Click to expand...
Click to collapse
Its located here:
bro no such file is available.. this wont help to solve .and still custom recovery not available for grand2
how would u know that it won't help..
i only post threads as i know what i am doing.
the file which i uploaded up there is taken from MY PHONE ITSELF i.e galaxy GRAND 2..
and That FILE (recovery-from-boot.p) IS present on my phone and i m using Stock rom and not any other rom..
Same with me... none of them named exactly like you mention above.
Sent from my SM-G7102 using XDA Premium 4 mobile app
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
vrushabh sutar said:
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
Click to expand...
Click to collapse
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.
NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
00hacktheworld00 said:
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.
NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
Click to expand...
Click to collapse
Thank you for replying.
I know that it can't be deleted,
but one may understand the importance of that ".p" file and understand its working, as it plays a vital role in booting up recovery...
the only thing I wanna let users understand is that,
stock recovery includes that file and
it got deleted when rooted because the rooting package (eg. CF root) didnt contain the .p file
when I studied that strange file,
it consisted of mapping and accurate memory address as well as accurate size of stock recovery image in bytes,
so that whn new recovery gets flashed, it verifies with the .p file!
and talking abt modifying the .p file,
we must create a custom linux binary with zerglings and packed into .tar file which gets flashed to phone via Odin!
for build creation you can use this tool..
http://www.xda-developers.com/android/comprehensive-guide-to-the-android-build-process/?__utma=60652090.747738090.1398670920.1400078979.1400132113.21&__utmb=60652090.0.10.1400132113&__utmc=60652090&__utmx=-&__utmz=60652090.1400132113.21.12.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=163283131
So I found the reason behind this
It is a file used by Software Update Application to flash updates.
If you want proof go-to the data folder of the SOFTWARE UPDATER and there will be a 3mb file. Copy it to pc and open using winrar. You can see many files including boot.img.
So the author of this thread was about to update his/her phone when he found the file :thumbdown:
SO MYSTERY SOLVED
SCOOBY DOOBY DOOO
Sent from my SM-G7102
i didnt't get what you are on to...
i noticed that the Update Package (i.e the OTA) easily jumps over all the restrictions imposed by Bootloader(locked one) and gets easily flashed to the phone...
therefore the whole matter is now pointing out to the 'ro.build.fingerprint' as well as Verification of MD5 hashes linked directly to Flashing InstructionSet