Database Users

[Q] Please help formatted data partition.

Hey guys as you can tell from this title im an idiot. I was up way to late last night messing with my computer and phone decided it was time to root the gs4. I have rooted hundreds of other devices and ive only soft bricked 1 and fixing was easy just flashing the stock firmware and kernal using odin. So my phone goes into bootloop just going to the samsung splash screen. so i pull the battery put it into DL mode and connect odin it shows up in the ID"COM slot as a yellow button. I select the firmware and click start it gives me an error. I downloaded the .pit file and plugged that into ODIN which was also failed. I have done a fair amount of research and it said i will need to do the Kies emergency firmware recovery. When my phone is plugged into the computer it says device ready to use or just makes the connection sound. I start up Kies and it just gets stuck on connecting. I have gone and downloaded the msxml6 file and updated the registry through cmd prmpt and restarted Kies and still nothing. Please someone help I literally just got my phone back after it taking a swim and really dont want to have to pay more money on an insurance claim.

Relax, it can be fixed. What firmware was your device on and what are you trying to flash in Odin?
Sent from my Nexus 5 using XDA Free mobile app

I was just on stock 4.4.2 i used safestrap to install recovery, i was formatting everything to install my first rom. i am using this tar file that i found on this forum. I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME

fhate803 said:
I was just on stock 4.4.2 i used safestrap to install recovery, i was formatting everything to install my first rom. i am using this tar file that i found on this forum. I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME
Click to expand...
Click to collapse
Ok, very simple solution. The tar you're using isn't going to work if you're on 4.4.2. Use this one and you'll get your device back http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

awesome downloading now will let you know if anything doesnt work.

No luck downloaded the .rar file renamed to a .tar Loaded in the .tar file under pda in Odin3 v1.85 unchecked auto reboot and hit start and here is the message.
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> Rar!
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the same message i have been getting all along with Odin. I am about to dl the .pit for it and try to flash that first.

fhate803 said:
No luck downloaded the .rar file renamed to a .tar Loaded in the .tar file under pda in Odin3 v1.85 unchecked auto reboot and hit start and here is the message.
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
Rar!
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
This is the same message i have been getting all along with Odin. I am about to dl the .pit for it and try to flash that first.
Click to expand...
Click to collapse
You need to extract the rar using winrar or 7-zip. Don't do the pit it won't work
Edit, when you extract the rar you'll get a .tar.md5 file use that in Odin
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You need to extract the rar using winrar or 7-zip. Don't do the pit it won't work
Edit, when you extract the rar you'll get a .tar.md5 file use that in Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Alright i got odin to pass with auto reboot not checked. I pulled the battery and tried to boot into recovery to do a factory reset before rebooting to stock and its stuck on bootloop now any other suggestions?

fhate803 said:
Alright i got odin to pass with auto reboot not checked. I pulled the battery and tried to boot into recovery to do a factory reset before rebooting to stock and its stuck on bootloop now any other suggestions?
Click to expand...
Click to collapse
How long are you giving it? The first boot can take 5 to 10 minutes
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You need to extract the rar using winrar or 7-zip. Don't do the pit it won't work
Edit, when you extract the rar you'll get a .tar.md5 file use that in Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I hoild the power button down it vibrates and the splash screen comes up for like 2 seconds then it is powered back off automatically. When i hold the power button again it does the same thing.

Problem with Note 3 root

Hey guys, I've got a problem. The problem is.. that I can't get root acces on my note 3. I tried some ways, and nothing.
I've got 5.0 Lollipop, modem version: N9005XXUGBOD1, and system N9005XXUGBOD6. Everytime I try to root it, it fails.
If it's possible I would really apriciate help of someone.
@edit: I need the root acces for custom room, cuz I'm afriad that Android 5.1 or 5.1.1 won't come for Note 3.

Flash TWRP, https://twrp.me/
Flash this zip from TWRP then, https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
When I'm trying to flash by odin... >.< @edit any solutions?

You tried to flash a zip file via Odin mate? That's not possible! Odin can only flash .tar format. Download the .tar image of TWRP, not .zip.

I already did it. Still the same. Fail, fail.. and nothing else :/

How is that possible dude? Odin connects the phone fine and then it can't flash a file! That's weird! Make sure the downloaded file is properly downloaded, I mean sometimes I have noticed that using download managers like IDM or alike makes the file corrupted.
Has that Odin flashed anything successfully for you? Any ROM or anything?

<OSM> All threads completed. (succeed 0 / failed 0)
I tried all the files, and this shows after the image tar file.
@edit it flashed this actual rom succesfully

Custom binary blocked by frp [secure fail:kernel]

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!

Stock ROM with PIT file

Hi all
I just wondered if someone was able to direct me to a stock to flash via Odin. I actually need the PIT file as I am getting an error every time I try to reflash, any guidance would be greatly appreciated. I have looked around but can't seem to find what I need.
Thanks

what phone model?
search on google - SM-N910x (where x is your model) 4 Files Repair Firmware
for example - SM-N910C 4Files Repair Firmware
and flash them responsible accordingly with Odin [the god of samsung flashing ]
good luck

There is some good information on your subject.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114/page84

I've extracted the PIT file for the SM-N910F if needed, (also have PIT files for the SM-T800, SM-T700 and SM-T705). I had to use one for one of the Tablets recently so extracted them all just in case.

Big Elf said:
I've extracted the PIT file for the SM-N910F if needed, (also have PIT files for the SM-T800, SM-T700 and SM-T705). I had to use one for one of the Tablets recently so extracted them all just in case.
Click to expand...
Click to collapse
i know post is old but worth to ask you still got pit file for 910F?

Link to SM-N910F Pit file. Let me know if there's any problem accessing it:

Big Elf said:
Link to SM-N910F Pit file. Let me know if there's any problem accessing it:
SM-N910F Pit file
Click to expand...
Click to collapse
thanks for file unfortunately another fail :/
<ID:0/009> Odin engine v(ID:3.1301)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 0 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

I copied this from another thread on here recently that I can't find for the moment but it's in this section which lists the steps for using the file. Once I find it I'll give credit to the person who listed the procedure:
1. Boot the Galaxy Note 4 into download mode screen then connect to PC.
2. This time load the N910F/C/T/W8.pit Pit file on Odin’s PIT Button (Select pit file of your variant) (SPECIAL INSTRUCTIONS FOR C Variant SEE POST 2)
3. Load your original stock firmware on the Odin’s AP button.
4 Make sure repartiton is automatically checked in options
5. Click on “Start” to flash the stock firmware and PIT file then wait.
After the process is over
Turn off the phone and set it into recovery mode
– Press volume “volume up, home and power buttons”
– Once in recovery mode, perform full wipe
– Select ‘wipe data/factory reset’
Maybe it'll fail if you don't follow these steps. I copied them because I knew I'd forget otherwise.
EDIT: It was from this thread by Ashwin Prabhunerurkar so all credit to Ashwin

Big Elf said:
Link to SM-N910F Pit file. Let me know if there's any problem accessing it:
SM-N910F Pit file
Click to expand...
Click to collapse
This file gave me trouble, better the one found in the first post of the thread you mention here:
Big Elf said:
I copied this from another thread on here [...]
EDIT: It was from this thread by Ashwin Prabhunerurkar so all credit to Ashwin
Click to expand...
Click to collapse

Did something wrong (I think) during HavocOS flashing process on J730G. Now I can not access recovery mode and Odin is not working.

I have a Galaxy J7 Pro (j7y17lte) with:
-LineageOS 17.1
-TWRP Recovery
-Magisk root
Recently, I tried to move to HavocOS and CronosKernel for the game mode and extra performance.
What I did:
1. Used TWRP to flash the "CreateVendor", rebooted and flashed "Spaget_X" scripts listed https://forum.xda-developers.com/t/treble-arm64-aosp-j730x-project_spaget-x.3929286/
2. Unzipped the HavocOS 3.2 archive (.img.xz) into .img on my PC, then transferred it onto the phone. https://forum.xda-developers.com/t/rom-treble-havoc-os-3-8-unofficial-for-j7-users.4085317/
3. I used TWRP to flash the .img file above in step 2 as "System image" (This is where I think I did it wrong)
4. Rebooted
Click to expand...
Click to collapse
Now, I can NOT get into TWRP.
I can NOT power off at all.
I am shown this animation screen when I try to reboot: https://www.youtube.com/watch?v=_o1XkIoe5oE
(It is not a static image, it has lighting effect animations.)
I CAN still get into download mode.
I tried Odin to go back to stock ROM downloaded from sammobile, but I am getting this error log:
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 2986 M
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I have tried using a Windows 7 PC, different Odin versions, and multiple USB cables that I can confirm are working properly.
I can provide any and all information needed for troubleshooting/fixing.
Does anyone have any idea what could be causing this? Is there a way to recover the phone? Is it bricked?
I'd appreciate all help given. Thank you in advance.
P/S: Writing this at 1:30 AM. I will reply to all your responses as soon as I wake up.
I am *very* new to all of this, so please explain like I'm 5. Thanks.

UPDATE!
I drained the battery and got into recovery.

AlexNguyen06 said:
UPDATE!
I drained the battery and got into recovery.
Click to expand...
Click to collapse
Ok now can Odin stock fw already....