I have down the TWRP recovery and then installed SU Root. It was working fine untill I mistakenly disabled developer options in my settings.
I have done the following already but none of them worked:
Downloaded Kies 3 and Smart Switch Firm Upgrade and Initialization. Tried giving my S/N and Model, but somehow, it is not recognizing my details correctly.
I do not want to load a stock ROM since I do not have a backup of my calls and contacts which are most important to me.
Thanks
amjadakmal said:
I have down the TWRP recovery and then installed SU Root. It was working fine untill I mistakenly disabled developer options in my settings.
I have done the following already but none of them worked:
Downloaded Kies 3 and Smart Switch Firm Upgrade and Initialization. Tried giving my S/N and Model, but somehow, it is not recognizing my details correctly.
I do not want to load a stock ROM since I do not have a backup of my calls and contacts which are most important to me.
Thanks
Click to expand...
Click to collapse
Ive had same problem earlier, just because ive wrote "stop" command in terminal emulator without knowing what it does lol, so never write that.
At me was saying FAP, not FRP though, but the way i solved my problem should solve yours too.
GUIDE to restore phone from "Custom binary blocked by FRP/FAP"
If you dont have a backup and you dont want to re-flash stock rom and lose all your stuff, then this will help you.
1. Download ODIN program. I'm using v3.09.
2. If you have J500FN model, then download this .rar file (made by me): J500FN stock recovery & kernel and skip to 3.
If you dont have J500FN model, then download the official stock firmware for your model from HERE or other website.
a) If the downloaded stock rom has .tar.md5 extension, remove .md5, then it should be only .tar
b) Extract the .tar file.
c) Now you will see recovery.img and boot.img. You need to make those two to .tar . To do this, you need a small program.
d) Go HERE and download Caboomi's_Recovery_img2tar_odin_maker from attachements.
e) Now, extract the .zip file, delete the actual recovery.tar.md5 from folder and then copy recovery.img and boot.img from the folder where you extracted .tar file to Caboomi's_Recovery_img2tar_odin_maker.
f) We will make recovery.tar.md5 first. Right-click Runme.bat and choose edit and replace
PHP:
bin\tar -H ustar -c recovery.img > recovery.tar
with
PHP:
bin\tar --group=1 -H ustar -c recovery.img > recovery.tar
And now save it, then run it. After you ran it, you will see recovery.tar.md5
g) Now lets do boot.tar.md5. Right-click Runme.bat and choose edit again. Now replace
PHP:
bin\tar --group=1 -H ustar -c recovery.img > recovery.tar
bin\md5sum -t recovery.tar >> recovery.tar
bin\mv recovery.tar recovery.tar.md5
with
PHP:
bin\tar --group=1 -H ustar -c boot.img > boot.tar
bin\md5sum -t boot.tar >> boot.tar
bin\mv boot.tar boot.tar.md5
And now save it, then run it. After you ran it, you will see boot.tar.md5.
3. I assume your phone is already powered off. Reboot your phone in download mode by keeping pressing Power button + home button + volume DOWN button at same time for few seconds. After an blue screen will appear, press volume up button.
4. Connect your phone with usb cable to your PC.
5. Open ODIN program (if it doesnt work, then right-click it and run it as administrator) and an number should appear at ID:COM. If it doesn't, then make sure that the phone usb drivers are installed.
6. Click on BL and go to the directory where is located the recovery.tar.md5 which we made, click on it and then click on Open. Now click START in ODIN. Wait until the process finish.
7. Now the phone should reboot byself. Power it off and repeat steps from 3. to 5.. Now, click on AP or PDA ( according to the version of odin which you downloaded) and and go to the directory where is located the boot.tar.md5 which we made, click on it and then click on Open. Now click START in ODIN. Wait until the process finish.
8. Phone should reboot again and this time it will boot. All your data is there.
9. Re-enable OEM unlocking in Developer Options again and now you can flash TWRP & kernel again.
10. If this guide helped you, then reply saying that or click thanks button. This way i know that i didnt wrote this guide for nothing Thank you!
Click to expand...
Click to collapse
Like me, you shouldve learnt something from this. ALWAYS have a backup.
Firmware link is bust
Im not sure what you mean by "bust", but you can download stock firmware from other website too, although sammobile is recommended.
got the same issue (but with J5 (2016))].
Is this working as well?
About data backup I do not care.
Thanks a lot. Followed all the steps and worked like a charm. Working on model SM-J510GN
HI
I have same problem with custom binary blocked, I tried your fix, but I can't download in download mode, it says MDM MODE CAN'T DOWNLOAD !!!!!
Please help!!
Thanks
Hi
I have the same problem . but I can't download in download mode, it says "MDM MODE CAN'T DOWNLOAD"
Please help!!!!!!!!!!!!!
Hi would this method work if i have the recovery.img and not .tar ??
Thank you #Henkate, very cool!
Jokes and Trump references aside, this method really worked, worth a try. I downloaded the firmware from sammobile, the speed was limited to 300 kB/sec so it took me 50 minutes but the everything went quite well after, the whole thing took about an hour.
Hi, doen't work, see comments,
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't have choise to execute step 6 : BL choise not activate,
Thanks for Help.
Thank you
I've spent a week trying to open my phone again! It worked. I watched videos etc and changed each file to tar with Odin tool but I couldn't figure out where each img went once it was in tar format! You are awesome
Your selfmade J500FN stock recovery & kernel broke my phone now it wont boot and theres green screen
After aaaaall tose years this method still works! You are a legend. The only thing to note is that I was not able to locate "Caboomi's_Recovery_img2tar_odin_maker". I just googled "img2tar_odin_maker" and I found a working program. Time to see what I had on my very old phone!
Related
Hello everyone,
I'm trying to flash a stock rom on a Verizon GS5. I say trying because so far it hasn't been working, unless I'm doing something wrong, which I think I am. When I got the phone, it had a Sprint rom flashed to the GS5. The original Verizon IMEI under the battery is clean and verified good with Verizon. There is nothing physically or cosmetically wrong with the phone, it powers on sometimes and randomly restarts. When it does turn on, the Sprint Spark logo comes up, the phone boots up normally and then randomly shuts off, taking a long time to be able to power back on. The only way that it says on is by putting it on Download Mode.
When in download mode, it shows as a G900P,
As far as my understanding goes, shouldn't it be a G900V?
I attempted to flash a stock Verizon rom I downloaded and tried to flash it with Odin 3.04 but it fails each and every time. I have installed the Samsung drivers that I got from the website, I restarted the computer, I restarted the phone but Odin give me a fail error.
Then I tried a newer version of Odin 4.43 but I'm not sure I'm using that one correctly but it's not working for me either.
I left the phone in Download Mode and it has been on for about 30 mins (the longest so far without it restarting on me).
Is there something that I'm missing here? Something else I could try to fix this?
Any ideas? Suggestions?
Any help would be greatly appreciated!!
..
-> It's a Verizon Galaxy S5 Phone I got from eBay
-> It's flashed with the Sprint rom version of the GS5
-> The phone restarts on and off, randomly, unless it is in Download Mode
-> I want to flash it back to the original Verizon GS5 rom.
-> I attempted to flash the phone with Odin 3.09 and rom SM-G900V_VZW_1_20140331185350
-> I get an error message when using Odin 3.09, it FAILS
-> The progress bar in the GS5 phone advances a small amount but that's it.
-> I attempted to use Odin 4.43 with the same rom file but that also fails and I get an error message.
-> I researched on Google before signing up and asking for help.
-> I have read many Threads and Posts on several Forums, and I have also tried many tutorials without any luck.
-> I researched how to use Odin, there is lot's of pictures, easy explanations but that's not it.
-> I found a GS5 stock rom, file name mentioned above.
-> Samsung drivers are installed, phone is recognized by Odin.
1.) Am I using the correct rom?
2.) Which version of Odin should I use?
..
SewerDweller said:
Hello everyone,
Any ideas? Suggestions?
Any help would be greatly appreciated!!
Click to expand...
Click to collapse
Download this version of Odin and extract the folder in the zip.
Make sure you have downloaded the correct firmware, extract the MD5 / tar file from inside the firmware.zip file you downloaded and put it in the Odin 3.07 folder
Start Odin.exe, put your phone in download mode and connect to your PC, if you have Kies installed make sure it is not running, Odin and Kies don't mix.
Once you have the Blue ID.COM indicated, click on PDA, find the MD5 / .tar file wait for teh file check Odin runs then click Start, wait for Odin to finish and your phone reboots.
Guide for Odin use here it is from the S3 but the use of Odin is the same for the S5
It took me a while to get it to turn on but here's what I got from trying ag4751's suggestions.
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANI2_G900VVZW1ANI2_G900VVRU1ANI2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
It's the same thing that I was getting before, I'm sorry if I did not explain myself in detail at first.
I have used 2 versions of Odin 3.09 (which I used on my own and got the above message).
3.07 as suggested by ag4751.
I have used 2 different roms and both fail.
->G900V_VZW_1_20140331185350
->G900VVRU1ANI2-20140919141518
@fffft
To answer your question as to what tutorial I followed, I followed ag4751's tutorial/explanation on his reply. It's basic, just like all the other tutorials I googled.
1.) Put the phone in download mode
2.) Open Odin
3.) Select PDA
4.) Wait for the file check
5.) Click start
and then it fails.
That's what @ag4751 suggested, that's what I tried, that's what I tried before, that's what I'm trying now and all that is failing for some reason.
..
..
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background
AS of March 27, 2015, the most recent firmware for Note Pro 12.2 international version is the Russian P905XXUAOB1 (with CSC905SERAOB1 and Modem905XXUANA7), Since it doesn't seem that any country is in a hurry to push a lollipop update into this device, I made these files to update the tablet to the latest available firmware. The procedure is designed to achieve two thing: 1- by leaving the bootloader untouched, it is reversible to your current version, if you have the firmware corresponding to your current version at your disposal, 2- it gives you root.
This procedure should not in theory wipe your data but DO MAKE A BACKUP, in case.
And no, it doesn't trip the knox.
Upgrade Procedure
All files that you need are available at the link further down. The are zipped but you should unzip them before using them.
1- Backup everything you have on your tablet
2- Reboot the tablet to the "Download Mode" (by pressing down vol + home key when the device is rebooting, right before you see the first splash logo, then push Up Vol to continue).
3- Run PC Odin v3.09 and load these files (remember to unzip the files after downloading) :
BL: leave empty
AP: AP.tar.md5
CP: CP.tar.md5
CSC: CSC.tar.md5
Leave everything else unchanged and Start.
4- Let the tablet reboot. It will first go to recovery to complete the upgrade and then reboots and initializes your apps.
Note 1: This process should not erase your data but I suggest you do a factory reset yourself (provided you have saved you data somewhere)
Note 2: After the upgrade is complete, the tablet may run slow and get hot for about 20 min because all the apps are trying to get set up and catalog your system. However, if after 30 minutes is is still slow and hot, first try to wipe the data for Google Plus App. If that doesn't work you may want to disable Google Plus, or as a last resort do a factory reset.
Note 3: If you end up doing a factory reset, the tablet will start up in Russian. You can change the language to English at the very first step of the initial set up. After that, go to settings and change the keyboard and input language to English. Then everything will be OK.
Note 4: If you try this out and don't like it, download your old firmware (must match or be newer than what you had before) and flash your tablet back to how it was (you have to do a factory reset after the downgrading).
Root Procedure
If you need to root the tablet, do the following after you finish the upgrade procedure:
1- Install towelroot v3 on your tablet, but don't run it. The app is inside a zip file at the download site and you should unzip it with the password 12345
This is done because some systems flag this app as a virus when it clearly is not. There are two versions there in the zip file. Either one should work just fine.
2- Install SuperSU, but don't run it.
3- Reboot to download mode.
4- Run PC Odin and load ANC3_Kernel.tar.md5 in AP field and start.
5- Let the system reboot. You may get some force closings after the reboot but ignore them.
6- Run the towelroot app and make it rain!
7- Reboot to download mode.
8- Run PC Odin and load AOB1_Kernel.tar.md5 in AP field and start.
9- Let the system reboot.
10- Run the SuperSU app and let it update the binaries the "normal" way.
11- Allow it to disable knox for you.
12- If SuperSU freezes up for more than 5 minutes reboot your tablet and run it again. Everything will be fine.
13- Your tablet is rooted now.
Download Link
https://mega.co.nz/#F!491wSaQa!wxjErs3ZamrmEPKjYVi50A
Hi
My p905 is on p905xxuanh3. Is it ok to use your method? Tnx
vvkuz said:
Hi
My p905 is on p905xxuanh3. Is it ok to use your method? Tnx
Click to expand...
Click to collapse
Yes. Make sure a matching nh3 firmware is available from sammobile.com if you think you may want to go back to your existing rom at some point.
successfully updated & rooted a p905 with your instructions,
thanks for your help.
Any idea if I can flash this rom into a P905M? Thanks in advance
andrew.mackew said:
Any idea if I can flash this rom into a P905M? Thanks in advance
Click to expand...
Click to collapse
No, because 905M has different cellular and LTE bands and the modem is different. If you still feel adventurous and want to try it, exclude the CP tar file when you are flashing. Make sure you have your current firmware available to restore in case you soft-brick your tablet.
najoor said:
No, because 905M has different cellular and LTE bands and the modem is different. If you still feel adventurous and want to try it, exclude the CP tar file when you are flashing. Make sure you have your current firmware available to restore in case you soft-brick your tablet.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I really wish to change, I mean, since Samsung stuck us on 4.2.2 so far.. I just wish, at least to get a minimal improvement.
If I get to merge things to have a P905 rom working on my P905M it would be an achievement in direction to break the P905M rom prison.
It worked!
Now I have the latest firmware into my P905M.
Thanks!
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
Background
AS of March 27, 2015, the most recent firmware for Note Pro 12.2 international version is the Russian P905XXUAOB1 (with CSC905SERAOB1 and Modem905XXUANA7), Since it doesn't seem that any country is in a hurry to push a lollipop update into this device, I made these files to update the tablet to the latest available firmware. The procedure is designed to achieve two thing: 1- by leaving the bootloader untouched, it is reversible to your current version, if you have the firmware corresponding to your current version at your disposal, 2- it gives you root.
This procedure should not in theory wipe your data but DO MAKE A BACKUP, in case.
And no, it doesn't trip the knox.
Upgrade Procedure
All files that you need are available at the link further down. The are zipped but you should unzip them before using them.
1- Backup everything you have on your tablet
2- Reboot the tablet to the "Download Mode" (by pressing down vol + home key when the device is rebooting, right before you see the first splash logo, then push Up Vol to continue).
3- Run PC Odin v3.09 and load these files (remember to unzip the files after downloading) :
BL: leave empty
AP: AP.tar.md5
CP: CP.tar.md5
CSC: CSC.tar.md5
Leave everything else unchanged and Start.
4- Let the tablet reboot. It will first go to recovery to complete the upgrade and then reboots and initializes your apps.
Note 1: This process should not erase your data but I suggest you do a factory reset yourself (provided you have saved you data somewhere)
Note 2: After the upgrade is complete, the tablet may run slow and get hot for about 20 min because all the apps are trying to get set up and catalog your system. However, if after 30 minutes is is still slow and hot, first try to wipe the data for Google Plus App. If that doesn't work you may want to disable Google Plus, or as a last resort do a factory reset.
Note 3: If you end up doing a factory reset, the tablet will start up in Russian. You can change the language to English at the very first step of the initial set up. After that, go to settings and change the keyboard and input language to English. Then everything will be OK.
Note 4: If you try this out and don't like it, download your old firmware (must match or be newer than what you had before) and flash your tablet back to how it was (you have to do a factory reset after the downgrading).
Root Procedure
If you need to root the tablet, do the following after you finish the upgrade procedure:
1- Install towelroot v3 on your tablet, but don't run it. The app is inside a zip file at the download site and you should unzip it with the password 12345
This is done because some systems flag this app as a virus when it clearly is not. There are two versions there in the zip file. Either one should work just fine.
2- Install SuperSU, but don't run it.
3- Reboot to download mode.
4- Run PC Odin and load ANC3_Kernel.tar.md5 in AP field and start.
5- Let the system reboot. You may get some force closings after the reboot but ignore them.
6- Run the towelroot app and make it rain!
7- Reboot to download mode.
8- Run PC Odin and load AOB1_Kernel.tar.md5 in AP field and start.
9- Let the system reboot.
10- Run the SuperSU app and let it update the binaries the "normal" way.
11- Allow it to disable knox for you.
12- If SuperSU freezes up for more than 5 minutes reboot your tablet and run it again. Everything will be fine.
13- Your tablet is rooted now.
Download Link
https://mega.co.nz/#F!491wSaQa!wxjErs3ZamrmEPKjYVi50A
Click to expand...
Click to collapse
Hey mate,
Can you make the same with the latest Lollipop for P905? I wish to flash them into my P905M.. Thanks
andrew.mackew said:
Hey mate,
Can you make the same with the latest Lollipop for P905? I wish to flash them into my P905M.. Thanks
Click to expand...
Click to collapse
Hello from Sao Paulo. Please let us know if you have succeed in installing the italian lollipop on your p905M.
js345 said:
Hello from Sao Paulo. Please let us know if you have succeed in installing the italian lollipop on your p905M.
Click to expand...
Click to collapse
Yep I did. But lost signal.. I am testing a few things..
---------- Post added at 01:13 PM ---------- Previous post was at 01:02 PM ----------
Anyone knows if I can flash a P905 modem into a P905M device?
thanks! successful!:good:
Thank you so much! I've been worried about rooting without tripping knox and this worked perfectly.
One question... If I didn't want to upgrade, could I have just flashed the two firm ware to root?
One of the clearest rooting guides I've used.
Thanks,
Zabben W
zabbenw said:
Thank you so much! I've been worried about rooting without tripping knox and this worked perfectly.
One question... If I didn't want to upgrade, could I have just flashed the two firm ware to root?
One of the clearest rooting guides I've used.
Thanks,
Zabben W
Click to expand...
Click to collapse
No because the second firmware in step 8 should match the existing kernel on your device.
najoor said:
No because the second firmware in step 8 should match the existing kernel on your device.
Click to expand...
Click to collapse
Oh right. That makes sense. Great root guide. If I think about upgrading, I will definitely take a peek at your lollypop one.
Upgrade to P905XXSABQC1_P905BTUABOF1_BTU for SM-P905
Hi All,
Need your help, Tried to upgrade my SM-P905 using ODIN V3.13, using the file downloaded P905XXSABQC1_P905BTUABOF1_BTU. connecting ODIN via USB Cable to the tab. Tried all USB Ports, same issue.
but ODIN unable to move forward with error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2365 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help.
After, and if, aboot and boot are flashed, the rest should get flashed with no issues.
99% of the time this kind failure is either due to a bad USB cable or unnecessary physical movement of the device (which affects the connection) during the flashing process.
So my suggestion is:
1- Make sure you have the latest Samsung drivers installed.
2- Find the best quality cable you have and use that.
3- If the problem persists download another firmware (maybe from another region) and try flashing that.
Hope this helps.
felix_sashi said:
Hi All,
Need your help, Tried to upgrade my SM-P905 using ODIN V3.13, using the file downloaded P905XXSABQC1_P905BTUABOF1_BTU. connecting ODIN via USB Cable to the tab. Tried all USB Ports, same issue.
but ODIN unable to move forward with error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2365 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Please help.
Click to expand...
Click to collapse
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
gokhan04uk said:
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
Click to expand...
Click to collapse
I have identical problem. Same device, same stock firmware. Trying to update to BOD4
Dancing around:
I've installed last TWRP (https://twrp.me/devices/samsunggalaxynote4exynos.html) from Odin after multiple failed attempts with N910UXXU1BOD4
Device booted normally (long boot with "updating applications")
TA-DA!
it booted to 5.0.1
It's creepy magic, but it works.
BTW, sammobile has newer version (N910UXXU1BOE3_N910UZZT1BOE3_BRI.zip)
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
gokhan04uk said:
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
Click to expand...
Click to collapse
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
stari4ek said:
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
Click to expand...
Click to collapse
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
a_ballads said:
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
Click to expand...
Click to collapse
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
gokhan04uk said:
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
Click to expand...
Click to collapse
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
stari4ek said:
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
Click to expand...
Click to collapse
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
gokhan04uk said:
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
Click to expand...
Click to collapse
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
stari4ek said:
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
Click to expand...
Click to collapse
Ok, Well if i do it the way you done it, will i get future ota updates or not ? i dont mind voiding warranty because the device is from hong kong, even if something goes wrong it will be a headache to send it back there and wait for it to come back. If I can get future updates wirelessly then i dont mind rooting it.
Nope. It rejects to check OTA. Manual update via Odin is still an option.
Probably, if flash original recovery and reset device, so it switches to new CSC - OTA will work. Probably.
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
This sounds interesting, can you please expand on the inductions as I am I little confused about when to flash hidden.img.
Thanks[emoji1]
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
gokhan04uk said:
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
Click to expand...
Click to collapse
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Salim.Keady said:
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Click to expand...
Click to collapse
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
gokhan04uk said:
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
Click to expand...
Click to collapse
Yes
How do you even flash the hidden.img,ext4 files through odin?
Hi,
I wouldn't normally post unless I really need help and I do, I've been at this for days, I'm stressing out because I really need my phone for work and I can't fix it myself...
My phone is stuck in a loop where every time I turn it off/on it goes straight into download mode.
It's doing this because I foolishly (without knowing what I was doing) used a .pit file I downloaded off of the internet.
I installed Clockworkmod 11 on my i9507 with the jfltexx i9505 rom.
It worked flawlessly except the 3G would drop out every time I locked the screen. Only 2G would work.
To try and fix it I downloaded a I9505DVUAMD8_MODEM.tar because I'm on Australia's 3G Telstra network through ALDI (medion) mobile.
The problem I had was that when I tried to flash the new modem, Odin would say that it failed.
So without knowing what I was doing, I used CSB_signed_Fusion3_TDD_0906_V2.pit
Now my phone is stuck in a loop where it goes straight into download mode.
Can someone please tell me how to fix this, I'm stressing out because all of my work is on this phone.
Please help, I'd really appreciate it.
Just flash a stock rom for the I9507 and you will be fine.
Lennyz1988 said:
Just flash a stock rom for the I9507 and you will be fine.
Click to expand...
Click to collapse
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
alex8337 said:
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
Click to expand...
Click to collapse
http://samsung-updates.com/details/41041/Galaxy_S4_TD-LTE/GT-I9507/OPS/I9507XXUFOA1.html
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
alex8337 said:
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
Click to expand...
Click to collapse
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
alex8337 said:
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
Click to expand...
Click to collapse
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
I don't understand what you mean by 'reflash recovery'?
I downloaded clockworkmod touch 6.0.4.7 but its a .img file and I don't know how to use it with Odin.
So I continued with what you told me to do the first time.
Lennyz1988 said:
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Click to expand...
Click to collapse
I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 with Odin 3.09, AP.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I reset the phone a good 10min after and now it still boots into Odin mode but this is on the screen instead.
Odin mode
Product name: GT0i9507
Current binary: Samsung official
System status: Custom
Knox kernel lock: 0x0
Knox warranty void: 0x1
Csb-config-lsb: 0x30
Write protection: Enable
eMMC BURST MODE: Enabled
START [224, 1440]
ODIN : Invalid ext4 image
FIRMWARE UPGRADE ENCOUNTERED AN ISSSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN.
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
ludoke said:
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
Click to expand...
Click to collapse
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
alex8337 said:
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
Click to expand...
Click to collapse
Open Odin ,connect your phone to pc via usb ,developers options enabled in ...settings ...about phone ..tap 6 or 7 times on build and enable usb ...foutopsporing in Dutch...also enable unknown sources .gO IN download mode ..search for how to do it. When phone is recognized in Odin
(If in the section ID COM is blue or yellow with a number it ,youre ready to go...
Tap on AP and it will ask for a file ...navigate on your pc to the location where you have stored the file,at first choose the Chainfire root file(,leave all the settings in Odin as the are) .it will appear in the AP section and hit Start ,wait until PASS appears in Odin...Disconnect phone from pc ,shut down Odin , Start the phone again in Download mode connect to pc and follow the same steps as with root,NOW UNCHECK automatic reboot in Odin,hit start and wait for Pass.
This should do the trick
---------- Post added at 01:10 PM ---------- Previous post was at 12:56 PM ----------
For root you need .tar file so unzip the zip file only once and flash that .tar file . For TWRP use the zip file,it contents the recovery.img NO need to unzip!!!
Sorry if i put you on the wrong leg.
I kept getting the same fail message in Odin.
I've fixed it now. I used Samsung Kies > Tools > Firmware upgrade and installation. It's taken the phone back to the stock Australian Optus rom. Not the original optus rom with baseband XXUAMH2 but a newer one running 4.2.2 with baseband XXUFOA1. Unfortunately I've lost all data on it but thankfully the phone still works. I was stressing out of my mind.
Thanks to everyone for helping, I appreciate your input
Hello folks!
I had a problem on which I was sitting 3 days to solve it. Finally I did, and as I promised, I am going to write a guide for You to step-by-step recover Your phone to life.
Below You can check, what exactly we are going to fix. It is a problem description wrote by me.
Hello guys.
I am really tired of looking for a fix for my problem. I am asking for help rarely and today is that day that I need your fast help with fixing my phone.
So...
I wanted to create a backup of 2 partitions - modemst1 and modemst2.
I have used the command "reboot nvbackup" - phone restarted, but no files created in backup and restarted already without IMEI code, and then I realized that phone is not recognizing SIM card.
First thing I have thought of - okay, lets reflash this thing. That's what I did, never with a success. I have tried flashing the original Samsung software into my phone, no help.
Tried to enter to service mode to fix it - nope - just blank window with rows, probably because SIM is not recognized.
Full wipe? Didn't help. Busybox and GSII_Repair neither.
Then by browsing root stuff I found out that I am missing 2 files:
- /dev/block/mmcblk0p10
- /dev/block/mmcblk0p11
I think that might be a problem which needs to be fixed. (I have tried to backup those two files, with no success, and as it seems, I have probably deleted the accidentally)
I was thinking if someone can back those blocks up and send the images to me so I can somehow recover those two files (Lollipop)
I have no backup of EFS folder.
I have tried to flash the modem.bin from stock firmware, no luck, no fix.
So I am looking for help from you guys, you are my last hope to get that thing fixed.
Problems to fix:
No SIM detected
No GSM signal
Unknown Modem version
Null IMEI
Missing files in /dev/block folder
EDIT: I promise that I will create a guide if I will fix it. But I need to fix it by tomorrow.
Serious stuff. My phone turned into tablet. I'm not going to add anything more. Let's get to work - but remember, any even more serious damage that you can do to your phone is not my responsibility!
What You will need - I was not able to post links due to having less than 10 posts
Newest Samsung Firmware - Sammobile
Newest TWRP Recovery - TWRP Website
Note 3 PIT file - 32GB version (Lollipop version)
CF Auto Root Kit - yes, your Knox will be tripped - ChainFire website
BLK files (17 and 18) - Going to add them here when I will have 10 posts
Newest ODIN - DroidViews webiste
Terminal - Google Store
KIES
If you cannot find PIT file for your Note 3 - you need to have already rooted phone
Method 1
Install Terminal and Busybox from Google Play store
Run Terminal
Execute these commands:
PHP:
su
PHP:
dd if=/dev/block/mmcblk0 of=/sdcard/SM-N9005PITJustCinek1.pit bs=8 count=580 skip=2176
Plug your phone to computer through USB
Copy the SM-N9005PITJustCinek1.pit file from your internal storage to your PC
Method 2
Install Android SDK on your computer
On your phone, go to Settings->Developer options and enable USB Debugging
On your computer, click CTRL+R and type cmd, click Enter
Connect your phone to computer through USB
In CMD window, type these commands:
PHP:
adb devices
It should show that your phone is connected. If not - plug your phone to other USB port or reinstall KIES
PHP:
adb shell
PHP:
su
PHP:
dd if=/dev/block/mmcblk0 of=/sdcard/SM-N9005PITJustCinek1.pit bs=8 count=580 skip=2176
Copy the SM-N9005PITJustCinek1.pit file from your internal storage to your PC
Let's get to work
Backup your all personal files - we are going to delete them
Pull out the SD card if you have one
Go to TWRP
Make a full wipe - System, Data, Cache, Dalvik Cache, Internal Storage
Reboot to Download mode
Plug your phone into computer by USB
Open ODIN
Go to Options tab and make sure that Auto reboot, Re-Partition, F. Reset Time, Phone EFS Clear and Phone Bootloader Update are checked
Go to PIT tab and click PIT button
Point on the PIT file you have for Your Note 3
Start flashing original Samsung firmware from Sammmobile
After flash is done, let the phone reboot and load, fill the settings on phone, get to the Home screen
Enter Download mode again
Flash CFAutoRoot package and wait until it will reboot again to the system and you will see home screen on your phone
Enter Download mode once again
Flash TWRP recovery again and wait until it will reboot to the system and you will see home screen on your phone
Copy both mmcblk0p17 and mmcblk0p18 file to your internal storage
Download Terminal from Google Play store
Enter to Terminal and execute those two commands:
PHP:
dd if=/sdcard/mmcblk0p17 of=/dev/block/mmcblk0p17
PHP:
dd if=/sdcard/mmcblk0p18 of=/dev/block/mmcblk0p18
After successfully executing those commands, restart your phone
It will load for a long time - but wait patiently
If it will show you that system stopped working - click OK. It should give you black screen. Restart the phone again.
If it will show you the error again, go back to step 22
After system is successfully loaded, you should have your baseband and signal back.
Did that guide help you? Let me know under this post!
I will upload the files if I will have 10 posts or more.
I reserve full copyrights of this article for my person and CompPyramid company.
To mods: I am not sure if it is the right forum to post this guide. If it is not, please move it and delete this comment.
Reserved.
Good luck with your copyrights that you have just posted in the public domain .
JJEgan said:
Good luck with your copyrights that you have just posted in the public domain .
Click to expand...
Click to collapse
Thanks, I just hope that it won't be copied without permission.
Well where exactly can we get pit files from apart from your copyrighted stuff?
P.S. Guess you will get ur 10 posts on replying to my question
He said me Secure check fail pit , what to do?
had no errors at saving the pit
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)