Develop Bugs

[GUIDE] Flash/Revive your Galaxy Y through ODIN v3.07 (including ext4 bricks!)

Many people brick their phones by flashing ROM's and stuff (like ext4 converter)....
This is how to revive phones which are soft-bricked.
THIS WORKS WITH EXT4 CONVERTER BRICKS!!
||||||||||||| WINDOWS ONLY!!!!! |||||||||||||
MAYBE HEIMDALL IN FUTURE!
A> On your computer
1.Download and install Samsung Driver Pack for Mobile Phones (x86 and x64)
2.Download and extract this zip file, which contains latest ODIN v3 3.07 and totoro_0623.pit (For Repartitoning, which is done in case of file system change [like ext4 FS])
B> On your Samsung Galaxy Y
1.Power off the phone/Make sure its off!
2.Go into DOWNLOAD Mode.
Code:
1.After turning your phone off, press these keys together (A warning screen should show up):
[B]Power Off + Volume Down + Home (Middle Button)[/B]
NOTE: Do not press Volume Up, right now on the Download mode's warning screen.
C> On your computer
3.Open Odin3.exe
4.Download any stock ROM package from sir Doky's thread.
5.Extract the zip file, you will get:
Code:
PDA_xxxx.tar, MODEM_ or PHONE_xxxxx.tar, CSC_xxxxx.tar
6.Browse in PDA Section and select PDA_xxxx.tar
7.Browse in CSC Section and select CSC_xxxxx.tar
8.Browse in MODEM Section and select PHONE_xxxxx.tar
9.Connect your Galaxy Y through USB.
D> On your Samsung Galaxy Y
1. Hit Volume Up on Warning screen,
E> On your computer
1.Make sure phone is connected through USB, you must see Blue 0:[COMxx] in the first ID:COM and "Added" in the message box.
ADDITIONAL STEPS FOR THOSE WHO've CHANGED THE FILE SYSTEM:
Code:
1.Check the Re-Partition checkbox.
2.In Re-Partition section ,click PIT and browse the totoro_0623.pit
2.Hit Start!
3.Wait and Voila! PHONE REVIVED!

WARNINGS:
DONOT CHANGE ANY EXTRA SETTINGS!
MAKE SURE BATTERY IS CHARGED ENOUGH (atleast 50%)!
IF ANY PROBLEMS POST HERE!
Resources:
DDMD1: Download​

why not update bootloader ?
all that u describe is the standard flash routine. nothing special.

Isn't it posted before??

Yes, yes it has. :-|

So many times -_-
But still.. good luck.. an effort is good.. but try to make the guide better!
**Nothing is True... Everything is Permitted**
Muffins.. Yay, i want muffins!

Its for noobs with re-partition and with new ODIN

hello sir..
sorry i'm noob..
i've flash my sgy to many custom rom..but when i'm flash back to stock rom (DXLE / DXLF / DXLI),why when i'm press power button to shutdown the phone,there are 4 options
1. flight mode
2. power off
3. data mode
4. silent mode
all i know,the stock rom just have 3 options right??there is no data mode in the options right??
can your metode fix the problem sir??
thanks.
#sorry for my bad english

DavySML125 said:
hello sir..
sorry i'm noob..
i've flash my sgy to many custom rom..but when i'm flash back to stock rom (DXLE / DXLF / DXLI),why when i'm press power button to shutdown the phone,there are 4 options
1. flight mode
2. power off
3. data mode
4. silent mode
all i know,the stock rom just have 3 options right??there is no data mode in the options right??
can your metode fix the problem sir??
thanks.
#sorry for my bad english
Click to expand...
Click to collapse
4 options appear in stock rom when u dont set a csc
to remove data mode set csc with *#272*IMEI#

Porobu said:
4 options appear in stock rom when u dont set a csc
to remove data mode set csc with *#272*IMEI#
Click to expand...
Click to collapse
thanks for the respon sir..
i've tried your guide..but there alot off options when i do that..
there are,
XTC
XME
bla
bla
bla
what i must install?
#solved sir..i read sir Doky's thread n solved now..
thanks

Porobu said:
4 options appear in stock rom when u dont set a csc
to remove data mode set csc with *#272*IMEI#
Click to expand...
Click to collapse
excuse me,do i have to write the *#272*IMEI# in phone dialer or where??

Cican49 said:
excuse me,do i have to write the *#272*IMEI# in phone dialer or where??
Click to expand...
Click to collapse
Yes.. in dialer tab
**Nothing is True... Everything is Permitted**
Muffins.. muffins everywhere!

nitubhaskar said:
Yes.. in dialer tab
**Nothing is True... Everything is Permitted**
Muffins.. muffins everywhere!
Click to expand...
Click to collapse
what should i choose?? or link to doky's thread
*solved

yash wont work...yeah i bricked my phone so dads giving fr repair tomorrow
either way this is wt comes...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S6102_DDLD4.tar.md5 is valid.
<OSM> MODEM_S6102_DDLD4.tar.md5 is valid.
<OSM> CSC_S6102_ODDLD2.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1

There seems to be a problem with the timing, you put download mode before setting up/connecting ODIN so follow the instructions exactly as in thread.

c.r.e.e.d Is your mobile fixed now?

MY BAD BRO!!!!!!!!!!!!!!!!!!!!!!!!
LOOK WHAT YOU ARE FLASHING FOOL! -
<OSM> PDA_S6102_DDLD4.tar.md5 is valid.
<OSM> MODEM_S6102_DDLD4.tar.md5 is valid.
<OSM> CSC_S6102_ODDLD2.tar.md5 is valid.
YOU ARE FLASHING FOR GALAXY Y DUOS

Yash98 said:
MY BAD BRO!!!!!!!!!!!!!!!!!!!!!!!!
LOOK WHAT YOU ARE FLASHING FOOL! -
<OSM> PDA_S6102_DDLD4.tar.md5 is valid.
<OSM> MODEM_S6102_DDLD4.tar.md5 is valid.
<OSM> CSC_S6102_ODDLD2.tar.md5 is valid.
YOU ARE FLASHING FOR GALAXY Y DUOS
Click to expand...
Click to collapse
You don't have to call him fool for that... there are people who get confused a bit sometimes...
If the flashing was a success, it wouldn't have bricked his phone...
Visit bricked my phone post here thread.. you will get to know that there are many people who have done this.. they will get a white screen because its running wrong driver in kernel...
So don't go around saying fool... I don't like people calling others like that.. you may know him.. but still its not accepted in public...
I will report next time to captain. Sorry if it feels I take this seriously to you.. but I can't see how someone gets the right to say that
He might be flashing a friends duos phone for all you know..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?

Dude i gave it for repairs and ok and it got bricked before and i culd only access cwm sooo....and also gimme a link for galaxy y india u probably know which. Lets discuss in ckass tomorrow k?

Deadly. said:
You don't have to call him fool for that... there are people who get confused a bit sometimes...
If the flashing was a success, it wouldn't have bricked his phone...
Visit bricked my phone post here thread.. you will get to know that there are many people who have done this.. they will get a white screen because its running wrong driver in kernel...
So don't go around saying fool... I don't like people calling others like that.. you may know him.. but still its not accepted in public...
I will report next time to captain. Sorry if it feels I take this seriously to you.. but I can't see how someone gets the right to say that
He might be flashing a friends duos phone for all you know..
-------------------------------------------------------------------------
★Nothing is True.. Everything is Permitted©★
Have you seen a Muffin..?
Click to expand...
Click to collapse
Bro, He has told his problem in school and he ended up saying your ODIN guide isn't correct or so....
He explained me, everything and he was saying the right instructions but he said it still doesn't continue with the flashing and he got me confused.
P.S. Bro, He has GT-S5360 and he told me about HIS phone and as far as I know, he wouldn't mind that.

s4 mini won't boot

I have a Samsung S4 Mini on the Verizon network (SCH-i435). I restarted my phone this morning and it took a much longer than usual to boot. My screen showed the Verizon logo for about 5-10 minutes and when the phone finally booted I was greeted with the utility to set up the phone (pick language, setup email, etc. etc.). I was confused because I had done this already a few months ago when I bought the phone. I skipped the steps and I was greeted with the stock home screen (all my custom shortcuts and widgets were gone). All my marketplace apps were still installed, but some of them had been reset (had to reconfigure waze, winamp, etc). My best guess is that there was an OTA update or some security patch that reset everything. Finally I got things running again the way I liked them. I was using my phone and suddenly it went dead. I tried to restart it but nothing showed on the screen. Oddly enough the phone just vibrates over and over again, but the screen remains black. No matter what I do I can't boot it. The only way I could stop it from vibrating was to pull out the battery. Is there any hope to recover this phone? Thanks.

Did you try to enter recovery mode?

Yes, I followed the instructions on the manufacturer site. I held down the home button, up volume, and powered the device on. A small bit of text appeared for a split second, it was so fast I couldn't read it. It disappeared and the screen went black and the same vibrate pattern started up again.

I got a video camera and managed to capture the text that was being displayed. Here is a screenshot...
It looks like...
MMC: mmc_read fail
Movinaand Checksum Confirmation Fail
Any hope of fixing this?

I asked for recovery cause it was easier to reset to factory the phone. If that's not working, i don't know if there's hope for it to enter download mode, for manual flashing with odin.

I'm able to get into download mode. Is there a ROM I can flash with? This S4 Mini is the Verizon phone so it is the SCH-i435, I didn't think there were any custom roms I could use with this phone.

Stock rom.
Try http://www.sammobile.com/firmware and see if your firmware is there.

Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.

RoyaLKurTx3 said:
Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.
Click to expand...
Click to collapse
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?

droid2501 said:
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?
Click to expand...
Click to collapse
I am not sure since this is the first time for me with experience with that phone...
In Odin, make sure Auto Reboot and F. Reset Time check boxes are only two that are selected. DO NOT SELECT ANY OTHER OPTION! Click the AP/PDA button and select that file you downloaded earlier with extension I435VRUBNE1_I435VZWBNE1_VZW.tar.md5 Click the CSC button and select file with CSC in its name. Ignore if there is no such file. Click the PIT button and select the .pit file. Ignore if there is no such file. (You should have this file, do it if you are having that error) Now, once you are ready, hit the START button to begin the flashing process.
If you have any other problems please ask.

RoyaLKurTx3 said:
(You should have this file, do it if you are having that error)
Click to expand...
Click to collapse
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.

droid2501 said:
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.
Click to expand...
Click to collapse
The file should be one of the extracted files in the file you have downloaded from my links. If the file is not there, then most probably Verizon modded the phone to not be able to flash via Odin Mode.
The error during the update may have happened because of low battery, making your phone shut down during the update, which is serious.
You can check yourself if your phone is under warranty (excluding the warranty period)
-Just go to download mode and you will see: KNOX WARRANTY VOID: [if it is 0x0, than it you are still under warranty, but if it says 0x1, you are not.]
Yeah, you should go to the place you have bought the phone from, if none of the above steps worked for you.
Good Luck.

I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?

droid2501 said:
I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?
Click to expand...
Click to collapse
You got the same version of your previous phone?

Yes, that's all they would do for free. They did offer me a Droid Turbo for and extra $100.00 but I really don't like the large phones they're coming out with these days so I declined.

Then you shouldn't get OTA Updates. I don't think that it was needed since the problem you got earlier was because of a faulty firmware from Verizon, which is unlikely or your phone had no battery while your phone was updating.

SM-T211 wifi + bluetooth not working after root and bloatware removal

Hi all, new guy to the forums. After rooting my T211 (4.1.2) via Odin and with TWRP and SuperSU, I started to remove some of the bloatware that Samsung sticks on the tabs. everything was working great until I rebooted one day and then the wifi and bluetooth stopped working. I've flashed the 4.4.2 in preperation to flash a custom rom, but it seems no matter what I do, the wifi and bluetooth issue remain. Can anyone help me with a zip to reinstall the wifi and bluetooth? or an instruction on how to do it? I have the 4.1.2 rom as well as the kitkat rom from italy and a few custom roms. If I knew how to make a flashable zip and which apks and such to use I would be happy to do it myself. Any help would be greatly appreciated. Thanks in Advance, James.

Bump
Bump

Tried just re flashing stock nonrooted bloated os back on?
---------- Post added at 03:41 AM ---------- Previous post was at 03:41 AM ----------
With odin of course and use the pit file for a full reformat wipe

Flashing stock rom
Trying it now. I'm a bit of a idiot, when I was trying to flash the stock rom, I forgot to unzip and wondered why I was getting an error...haha. I wanted to try a dirty flash just in case it worked but no kewpie doll. Trying it with the pit file now. fingers crossed.

Ugh...no luck. here's the read out from Odin. Not sure whats going wrong yet. Maybe not the right pit file.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T211XXAML1_T211OXXAML2_T211XXAML2_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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Yea double check the pit file is for your model tablet

LT02.pit, this is the one that keeps getting reccomended in all the posts I've read. Says its for the T210 but it is supposed to be the same?

This is very frustrating thought I had it fixed. Wifi button turned on...bluetooth button turned on...just kept scanning. then both shut off and wont stay on

So after reflash they still do it?

yeah, they still do it. puzzling that it turns on but only scans and has no connection.

Using a file manager with root access, delete the following 2 directories:
/data/misc/bluedroid
/data/misc/wifi
Then, reboot.
Can't promise it will work, but it may.

Cool, gonna give it a try in a bit.

Any luck?

well, yes and no... after loading up root browser, I navigated to /data/misc. I don't have a bluedroid directory. I have a bluetooth and a bluetoothd and I have a wifi and a wireless directory. I deleted the first three and rebooted. I then was able to turn on the wifi and it recognized my router and connected...for about 10 seconds then shut off again and wouldn't turn on again. So, I think we're on the right track but not quite there yet. The fact that it did work even if temporarily was encouraging.

If it were me, I would go to sammobile.com and download the full firmware package for your region and flash it with Odin. That will ensure that you have a matching set of firmware (boot, radio, system, etc.) It will not wipe your data. If it works correctly after that, then you can reinstall your custom recovery and whatever rom you want.
Sent from my SM-G920V using Tapatalk

well, that didn't work either. Still has the same problem. I went into twrp and wiped everything except the external sd card. then with Odin, flashed 4.1.2 rom for UK and wifi will not turn on. Scratching my head now

Any other ideas?

Try using Heimdall with a full firmware package. You'll have to extract the firmware package (change the filename ending with ".tar.md5" to ".tar" and use 7-zip to extract it.
Then open up Heimdall, go to "Utilities -> Download PIT -> Destination File" and pick a location and name for the pit file.
Following this step, go to "Flash -> Options -> PIT" and browse to the pit file.
You will then have to go through the process of adding each partition that you want to flash, browsing to the location of the firmware package, and then flashing it.
I've done this several times, although I have not tried with "Repartition".
You will probably want to flash "SYSTEM", "MODEM", "KERNEL", and "RECOVERY" at a minimum. That said, it would be a *good* idea to use all the files inside the firmware package.
I'd upload packages I've made for my own convenience, but I'm unclear about their legal situation. I think I can get away with PMing links around though. Maybe.
EDIT1: Please post the output from the "Status" box if it fails.

Apologies for not responding sooner. Been busy with work, will try this soon and post results. Thanks

Can't get Heimdall to work. All I get is its not a valid win32 application. I refuse to give up on this, I know it's a software issue so there has to be a way to fix it. ...pulling my hair out though.

Could use a little advice on ROM flashing/Odin not working

I'm flashing the Stock ROM for verizon 5.1.1 on my used (but new to me) Galaxy Note 4. The .tar.md5 file once extracted is appx. 4gb. It is the correct file for the model and build. It is currently the same ROM (attempting to fix something as noted at bottom).
N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5 from sammmobile.
I have tried with Odin 3.11.1, 3.10.7, 3.10.6 - once each...I ran each in Administrator Mode on Wdws 7. The same thing happens with each as below.
Only Auto Reboot and F. Reset Time (the defaults checked off) are checked in the Options Tab.
The Log window currently shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
(the 3.10.6 version noted the file name as above here in the process, but not the other versions)
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
All appears fine on the phone. It just stays on "downloading", and Odin stays at the above.
As it stays there and does nothing, I am at least able to pull the battery and start it. I've done a factory reset before starting just to make sure it's all clean to start (not that it's necessary). Thankfully, it didn't brick it when nothing worked.
I'm doing this as a last attempt to remove an error in 5.1.1 that causes Setttings to crash then trying to view Google accounts and still keep 5.1.1 in case I can ever figure out the bootloader/root thing.
I am new to this. Am I missing something obvious?
Other details...the download mode does indicated Odin enabled (high speed), so it's set for use. All else is legit. This is a newly purchases used phone.

jecilop said:
I'm flashing the Stock ROM for verizon 5.1.1 on my used (but new to me) Galaxy Note 4. The .tar.md5 file once extracted is appx. 4gb. It is the correct file for the model and build. It is currently the same ROM (attempting to fix something as noted at bottom).
N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5 from sammmobile.
I have tried with Odin 3.11.1, 3.10.7, 3.10.6 - once each...I ran each in Administrator Mode on Wdws 7. The same thing happens with each as below.
Only Auto Reboot and F. Reset Time (the defaults checked off) are checked in the Options Tab.
The Log window currently shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
(the 3.10.6 version noted the file name as above here in the process, but not the other versions)
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
All appears fine on the phone. It just stays on "downloading", and Odin stays at the above.
As it stays there and does nothing, I am at least able to pull the battery and start it. I've done a factory reset before starting just to make sure it's all clean to start (not that it's necessary). Thankfully, it didn't brick it when nothing worked.
I'm doing this as a last attempt to remove an error in 5.1.1 that causes Setttings to crash then trying to view Google accounts and still keep 5.1.1 in case I can ever figure out the bootloader/root thing.
I am new to this. Am I missing something obvious?
Other details...the download mode does indicated Odin enabled (high speed), so it's set for use. All else is legit. This is a newly purchases used phone.
Click to expand...
Click to collapse
Try re-downloading the .tar file. Make sure you have ADB debugging enabled. Did you extract the .tar file from the .zip?
You'll want to uncheck auto reboot because you're best served to do a factory reset before your first boot.

douger1957 said:
Try re-downloading the .tar file. Make sure you have ADB debugging enabled. Did you extract the .tar file from the .zip?
You'll want to uncheck auto reboot because you're best served to do a factory reset before your first boot.
Click to expand...
Click to collapse
Thank you for the input.
I will redo the download. It appeared fully successful the first time as the zip extract did work (thus the " The .tar.md5 file once extracted is appx. 4gb") file inside. Should the .md5 NOT be on the end? This is what was contained in the zip file: N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
Oddly enough, my searches on this do NOT return specifics with plenty saying .tar/.tar.md5 - either one.
I can remove the .md5 and open/extra the .tar file and see the appropriate files inside that one. I think this is the semi-OBVIOUS part I did not know.
Can you confirm, I should be using the .tar file in this case with Odin and not the .tar.md5?
In case I haven't been clear:
* Downloaded a .zip file containing a .tar.md5 file. This does not work for me on Odin.
* With .tar.md5, I cannot extract anything (I'm using Winrar-not 7zip-for this extension).
* If I remove the .md5 leaving only .tar, I can open the .tar file and see the image files and such in this one.
* I think this .tar is what I should be adding, but again I am new to this and the instructions I saw online mentioned adding the .tar.md5 file. (instructions found here: https://androidmtk.com/flash-samsung-stock-rom-using-odin ).
I'm sorry if this is a "duh" question, but I really don't know. I'm new to flashing this but not completely new to rooting. I am in Dev mode (build tap 7 times) with USB debugging and install from unknown sources. And I do have the correct ADB sdk tools and drivers and such. In fact, I'm playing with the commands that at least let me backup apps and data onto a PC right now. (I'm really missing using Titanium backup right now!)
Thanks for your help and the advice about the auto reboot. I know about the factory reset, but I didn't think about this being unchecked to allow that. I'm watching some good vids on rooting the VZ model and getting close to braver to try it, but not quite there yet. I'd just really like to be able to modify what sync in my accounts right now!

Custom Binary Blocked by FRP Lock - How I Fixed It Without Data Loss

YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.

"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.

koop1955 said:
"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.
Click to expand...
Click to collapse
He's crazy if you ask me
Sent from my SM-G920P using Tapatalk

I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it

fentezi said:
I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it
Click to expand...
Click to collapse
First off, you should probably post in the correct forum.
Secondly, did you try flashing the firmware for your phone: https://www.sammobile.com/firmwares/galaxy-j1/SM-J120F/

I fixed it
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it:laugh:

My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.

THANK YOU
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!

killroot said:
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!
Click to expand...
Click to collapse
Hey! Glad it helped. I was really active back in the HTC Hero days and around 2013 I slowed down. I like to keep my phones rooted but i getting more and more worried about manufacturer warranty being denied over being rooted... Fortunately I was able to iron this whole thing out with some meticulous research and some help from awesome people here, and it's still satisfying knowing I've helped at least one person who appreciated it enough to say thanks!
Sent from my SM-N920P using Tapatalk

finalc said:
My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.
Click to expand...
Click to collapse
Sorry, not sure what the g928p is and unfortunately I can't help with your issue. I just wrote what I did to fix this issue and if you're still having problems I recommend doing some very in depth research to make sure you didn't miss some tiny but crucial step.
Sent from my SM-N920P using Tapatalk

fentezi said:
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it[emoji23]
Click to expand...
Click to collapse
That's what the instructions said to do [emoji6]
Glad it worked.
Sent from my SM-N920P using Tapatalk

Same issue on my Samsung A%
The file is not there anymore bro. Where do i get the file for my device please(Samsung A5) ? i found a way to solve this using kies 3 and wiping the phone. But u did it without data loss? amazing ! glad if you can help. thanks!
jerry43812 said:
YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.
Click to expand...
Click to collapse

i just had the same problem on my mothers phone and your method worked perfectly thank you so much i didnt want to do a stock flash and have her loose everything so thanks for your knowledgeable and easy to follow post

Hello @jerry43812 and @koop1955 that file has been deleted from android file host, would any of you please care to upload it again? Thanks very much. I have a Samsung Galaxy Note 5 btw, I think it works right?

I dont even remember making this thread, I definitely dont have the file you're looking for. Maybe koop can help.Sorry!

@koop1955 I don't have knowledge about any of the android OS. But I have an issue and it still is an issue from 2016 to 2022. I have an android phone launched in 2016. I rooted it using SuperSU binary. By turning ON all the necessary features required for making custom recovery (TWRP) installed and installing SuperSU binary as well.
Therefore my developer options were turned ON and OEM unlocking was ON aswell. My phone name was Samsung J2 2016 (SM-J210F). I by mistake disabled OEM unlocking switch. And restarted the phone and it never
rebooted after that.
I need the data it is very precious to me. I don't need root privileges back or anything like that.
I just need the data and state of operating system the way it was before restarting.
Please help me @koop1955.
I will be very thankful to you.

I have no idea. Good luck.