Alright,
I'll first start by telling you my story so you guys can retrace what I may have done wrong during the process. I'm a noob but I made a lot of research before posting here and I'm posting because it's been 2 days of trying to make things work with no results.
My goal was to root the phone and install CM10 so I flashed CWM in download mode and I rebooted in recovery. Then, I installed the zip package (CWM-SuperUser-v3.1.3) and rebooted. I transfered CM10 (The ROM dates from 30/09 so I guess this is a pretty recent version, I tried others anyway) on the root of the phone and I rebooted in recovery. When I tried to run the zip package from the internal sd card, I got an error message. All I can remember is that it was looking like this: assert failed: getprop("ro.product.device")
I did a lot of research on google for this error and everybody was suggesting to flash a stock ROM and start all over. At this point, I was getting a little frustrated because I had done a factory reset for nothing so I decided to abandon the project and wait for the upcoming Jelly Bean update.
I rebooted the phone and when after I entered my google informations, Google+ always stopped working but the operation completed. I went to the Play Store and always got a server error message. It was working an hour before so I started to fear something was going on. In fact, it's been like this for two days and it never worked again. I made many factory wipes and I tried to flash a stock ROM with Odin. Odin is always giving me an error message: Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1)
I tried with an earlier version of Odin as a guy in a thread was suggesting, didn't work either. I changed USB port, everything! The only solution I think could work would be to get the Play Store APK file and flash it with Odin but I'm unable to find it.
PS: I also tried to clear data/cache of Google services and Google Play Store. Somebody somewhere suggested to clear Google framework or something like that but I don't have this in my application manager. Guess this could be indicating that some stuff is missing?
I'm very disappointed right now.. I assume that I was in a bit of a rush by trying to root my phone a single week after I got it but I honestly think I did everything right... I really need your help!
First, you need root access. Second, you need an app like Root explorer. Third, you need to edit the build.prop. More specifically, the line "ro.product.device"
Edit that so it reads d2att
Reboot. Should be good after that.
You may need to be on a stock, rooted ROM, maybe not.
mrhaley30705 said:
First, you need root access. Second, you need an app like Root explorer. Third, you need to edit the build.prop. More specifically, the line "ro.product.device"
Edit that so it reads d2att
Reboot. Should be good after that.
You may need to be on a stock, rooted ROM, maybe not.
Click to expand...
Click to collapse
I got root access. Second, root explorer is an app on my computer? Cause I can't get access to the Play Store so this could be a problem for the moment... Third, alright, what do I change in there?
System/build.prop/ro.product.device
Change that to d2att.
Root explorer is an app for your phone, not your computer.
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
http://db.tt/vgBjRVTR
Try upgrading cwm to 6.0.1.2. I've heard some have had good results with this. That link is for ROM Manager, which you just need root for.
If I understand correctly, you think something I did modified this parameter so the phone isn't recognized as a d2att anymore? For the play store, would it help to rerun gapps?
I'm I able to do the modification without root explorer? How do I install the app without play store?
EDIT: I just found a thread where a guy with a Bell phone (also I747 and from Canada) had a problem with this also. It seems it was written d2can (probably for Canada) instead of d2att. He was getting the problem while installing cm10 but I still don't see what this could have to do with three market?
Could you just give me a little more info about modifying this. At least a link? I'm a noob I told you
pelteux said:
If I understand correctly, you think something I did modified this parameter so the phone isn't recognized as a d2att anymore? For the play store, would it help to rerun gapps?
I'm I able to do the modification without root explorer? How do I install the app without play store?
EDIT: I just found a thread where a guy with a Bell phone (also I747 and from Canada) had a problem with this also. It seems it was written d2can (probably for Canada) instead of d2att. He was getting the problem while installing cm10 but I still don't see what this could have to do with three market?
Could you just give me a little more info about modifying this. At least a link? I'm a noob I told you
Click to expand...
Click to collapse
What he's saying is that you need to modify that particular file (ro.product.device) in your phone. For that you need to use something like "Root Explorer."
You don't need to get it from the play store; you can get it on the internet also just seach google for it. "root explorer.apk" and load it.
Just google it, install root explorer and mod the file...it's easy. It takes longer to explain than to do it.
rpavich said:
What he's saying is that you need to modify that particular file (ro.product.device) in your phone. For that you need to use something like "Root Explorer."
You don't need to get it from the play store; you can get it on the internet also just seach google for it. "root explorer.apk" and load it.
Just google it, install root explorer and mod the file...it's easy. It takes longer to explain than to do it.
Click to expand...
Click to collapse
Although your right on the file explorer to change the build.prop I'm not sure why you would advise trying to find ripped copy of a paid app. Aside from not supporting a good dev there is also the real consideration of finding an .apk that may have been modded and not in a good way. To each there own I guess. There are lots of free file explorers on the play store that will more than suffice to do the job such as es file explorer that is pretty popular.
jethro650 said:
Although your right on the file explorer to change the build.prop I'm not sure why you would advise trying to find ripped copy of a paid app. Aside from not supporting a good dev there is also the real consideration of finding an .apk that may have been modded and not in a good way. To each there own I guess. There are lots of free file explorers on the play store that will more than suffice to do the job such as es file explorer that is pretty popular.
Click to expand...
Click to collapse
You have a point; I wasn't aware that Root Explorer was a "paid only" app and I'd certainly not encourage him to not support the devs...I wasn't thinking.
My mistake; go with one of the free ones for now since you can't access the play store.
Crap, I forgot to add that you can access the play store from any computer, just Google play store and sign in with your Google credentials and find what you want and install it. It will auto download and install on your phone. I did this last night, bought and installed nova prime without opening play store on my phone.
If the store won't recognize your phone, how are you going to push the install to it?
Did you try the ROM Manager app i linked?
Alright,
I was able to install file explorer, open build.prop and do the modification. I rebooted in CWM and tried to install CM10, same error : assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product"") == "d2att E: Error in /emmc/cm-10-20210930-1849-SKANK-d2att.zip
(Status 7)
Installation aborted.
I modified the two lines where "d2can" was written instead of "d2att". I would be more eager to get my market back for now...
pelteux said:
Alright,
I was able to install file explorer and open build.prop to do the modification. However, I am unable to save the document as it give me the error: Error occured when trying to save the file. It will not be saved.
What can I do about this?
Seriously, I am a bit sceptical about this modification... I guess it could help to install CM10 but, will I get access to my market..?
Click to expand...
Click to collapse
This should allow Odin to work properly. Your post said that Odin wouldn't work because of an error. This should correct error so that Odin works.
Nice! The phone is softbricked now! Nothing appears after The galaxy S3 logo. The phone seems to be running since I hear it connect to the computer via usb but nothing appears. What do I do now..............................................
mrhaley30705 said:
Your post said that Odin wouldn't work because of an error.
Click to expand...
Click to collapse
Yes but the "d2att" error was on CWM. Now I can't access the phone at all since it seems to be softbricked.
Here is what I see when I try to flash the stock firmware into Odin. No error message but nothing completes anyway...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
EDIT: Now, I obviously need to do an adb pull to get build.prop and change the line the way it was before. I absolutely have no clue how to do this. Any advice would be welcome.
Is there a blue box lit up, says something like "com"in it? If not, Odin does not see your phone.
Odin always sees my phone, this is not the case. I always see the COM:5 while in download mode.
http://forum.xda-developers.com/showthread.php?t=1903516
Toward the end of the first post is a section on Odin. Try those things.
Odin is currently the least of my problem... The modification I made in the build.prop softbricked the phone so I try to bring it back!
Flashing the stock ROM should do that for you.
I think he can't flash a rom cause he gets an error in odin or it doesn't take cause it doesn't recognize the proper device id because of the messed up build prop? Not sure, not too familiar with odin.
Here is what I see when I try to flash the stock firmware into Odin. No error message but nothing completes anyway...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
With cwm 5.5.0.4 I believe it has access to external sd card. What would happen if you downloaded the same CM10 version you originally flashed to your phone on your computer and extracted the build prop and put it on your external sd card(if you have one and an adapter) along with a cwm flashable version of twrp recovery(which i have), flashed twrp and rebooted recovery, then used twrp's built in file explorer to replace the messed up build prop with the original, that should give you a booting phone. The only catch is that you would have to a battery pull and manually boot into recovery, not sure what pulling the battery would do, wouldn't want to mess up your phone more....anyone think this will work?
Related
hi, i've tried manually updating my s3 to 4.1.2 with the multi window feature through odin but it fails. here is the log. I would really like some help
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELKC_I9300OXXELK4_I9300XXELKC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/031> Odin v.3 engine (ID:31)..
<ID:0/031> File analysis..
<ID:0/031> SetupConnection..
<ID:0/031> Complete(Write) operation failed.
<ID:0/031> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/031> Removed!!
Do you have a sprint s3? If so you have the wrong file and should download the one located here. Otherwise you're in the wrong section
i do have sprint. the one in that link you've posted looks like its for rooted phones or will root my phone. I have and dont want either.
Look a little closer. Theres a rooted and an unrooted version. Both are identical with the exception that one has root, the other one doesnt.
Edit:
Heres a direct link to the unrooted version
http://rwilco12.com/Files/Devices/S...nrooted/SPH-L710_MD4_1130792_Stock_Nodata.exe
is it this? if so do i install both files or just the tar.md5. file.
JustMikeOnlyMike said:
is it this? if so do i install both files or just the tar.md5. file.
Click to expand...
Click to collapse
You only need one. I recommend the exe. It's an odin one click and takes the guesswork out of using regular odin
sorry for being semi oblivious and hope im not bothering BUT. .with that exe. file, it will update my phone and allow me to multi task right?
also will these same steps work for the installation on odin?
"In ODIN window you have to click on 'PDA' and then browse your PC for the '.tar.md5′ file you've extracted at step 2. That's the Android 4.1.2 XXELKC firmware update file and you have to load it into ODIN.
Don't change any default ODIN options and make sure that 'Re-Partition' option box is not enabled, as if it is, then you need to disable it.
Press the 'Start' button to begin the Android 4.1.2 XXELKC update on your Galaxy S3. Do not press any other buttons and simply wait for the install process to finish."
JustMikeOnlyMike said:
sorry for being semi oblivious and hope im not bothering BUT. .with that exe. file, it will update my phone and allow me to multi task right?
also will these same steps work for the installation on odin?
"In ODIN window you have to click on 'PDA' and then browse your PC for the '.tar.md5′ file you've extracted at step 2. That's the Android 4.1.2 XXELKC firmware update file and you have to load it into ODIN.
Don't change any default ODIN options and make sure that 'Re-Partition' option box is not enabled, as if it is, then you need to disable it.
Press the 'Start' button to begin the Android 4.1.2 XXELKC update on your Galaxy S3. Do not press any other buttons and simply wait for the install process to finish."
Click to expand...
Click to collapse
Yes that's the newest update with MultiWindow. And when I said it takes the guesswork out I mean you don't have to worry about what boxes to tick or slots to load. There is only one button in the one click and its "start". And thats all you have to worry about pressing (after you put the phone in download mode of course)
Hope I answered your question
See here for an pic of what the one click looks like. (Altho yours will differ slightly)
im still a little confused. So when i have my phone in download mode and connect it to my pc, i just push start? i dont have to load the exe. file into "Bootloader, PDA, Phone, or CSC" ? i ask this because id be shocked if odin found the exe. automatically for me and loaded it lol.
JustMikeOnlyMike said:
im still a little confused. So when i have my phone in download mode and connect it to my pc, i just push start? i dont have to load the exe. file into "Bootloader, PDA, Phone, or CSC" ? i ask this because id be shocked if odin found the exe. automatically for me and loaded it lol.
Click to expand...
Click to collapse
You got it. Your exactly right. And it's not that odin finds the file and loads it. The one click is a special made file with the firmware and odin program combined into one.
alright thanks alot man i appreciate the quick replies and hope this works.
JustMikeOnlyMike said:
alright thanks alot man i appreciate the quick replies and hope this works.
Click to expand...
Click to collapse
Yup np. Don't expect any problems the one clicks are very reliable. And should any problems occur just come back here or shoot me a pm.
JustMikeOnlyMike said:
i do have sprint. the one in that link you've posted looks like its for rooted phones or will root my phone. I have and dont want either.
Click to expand...
Click to collapse
Please be very careful as to what you try to load onto your device. The file you originally attempted to use was for the International S3 if by any chance it would have worked you would own a very expensive paper weight right now.
Transmitted with a portable device using Xparent Blue Tapatalk 2
I just picked this up and it's build number P5220XXUAMI2 out of the box.
I'm a little confused regarding firmware versions and I've found a few threads for the P5200 and P5210 builds, but nothing for the P5220. Is it possible to root and flash a custom recovery on the model/build I have?
Sorry of this is a super n00b question. Tablets are not my strong point.
EDIT:
I was able to root using the method here
http://forum.xda-developers.com/showthread.php?t=2432467
I wasn't sure it would work as the files are for the P5210 but it was fine.
thank you!
@ebue
I am trying to help ebue to find out exactly what this OLDDDD tread is about:
What is the safe way to root a GT-P5220 Tab3 10 4G .
I decided to move here to stop hijacking ( not really) or taking to much attention for P5220 on the original question of ebue at => http://forum.xda-developers.com/showpost.php?p=55315126&postcount=157
So in this tread we have the ONLY testimony in this forum, where our friend parker_dhd claims he got it
parker_dhd;48219938...[COLOR="Red" said:
I was able to root using the method[/COLOR] here
http://forum.xda-developers.com/showthread.php?t=2432467
....
Click to expand...
Click to collapse
Now it is true that http://forum.xda-developers.com/showpost.php?p=55315126&postcount=157 is an old and abandon thread. But we can guess that in fact as expected P5220 share same partition arrangement for recovery.img with P5210/P5200. Be careful with what I said. I am talking only about recovery.img. There are in fact some other partition that are specifically different like for example the modem one.
Still many had ask the same. In particular I saw moonbutt74 in another thread asking the same compatibility question I have:
moonbutt74 said:
S,
could you tell me jf the following is correct on the 5220 ?
/system = /dev/block/mmcblk0p8
/data = /dev/block/mmcblk0p9
/boot = /dev/block/mmcblk0p10
/recovery = /dev/block/mmcblk0p11
thanks, m
Click to expand...
Click to collapse
The answer is easy to find if we get a Champion owner to help us. I am hoping @ebue can help us help him.
Well at the moment I do not have a good internet connection I am really limited in bandwith.
So we need a champion that can download a Stock Samsung 4.2.2 Firmaware. In particular I need the recovery.img.
So @ebue
1)You should had downloaded a Stock Rom yourself just in case you need to go Back to Stock.? Don't you?
2)Clearly in your case your Stock Official Samsung Rom will not start with
5210xxxxxxx_P5210Xxxxxxx_xxx.zip instead will be with "5220" or something 5220xxxxxxx_P5220Xxxxxxx_xxx.zip
Listen still the name may be in another format. That is the usual name for sammobile files.
3)In my case I downloaded: 5210UEUAMH1_P5210XARAMH1_XAR.zip long time ago.
4)In my case if I can unzip this file I will see inside 2 files:
P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5
SS_DL.dll
Ignore "SS_DL.dll"
5) Now extract "P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5"
6) Now Rename the extracted "P5210UEUAMH1_P5210XARAMH1_HOME.tar.md5" to "P5210UEUAMH1_P5210XARAMH1_HOME.tar". Yes no ".md5"
7) Now open "P5210UEUAMH1_P5210XARAMH1_HOME.tar" with winzip or any other zip app. You will see it contains
"boot.img, cache.img, hidden.img, recovery.img and system.img". ".
8) Now Extract just/only "recovery.img. And using winzip/winrar Zip ONLY "recovery.img" to "recovery.zip".
We zip it back because this forum will not allow to upload files that are not in zip form.
It should be a file of less than 20Megs. Usually around 10megs. Uploads files are done tru "Manage Attachments" link at the bottom on the advance Replay window.
Listen If you have trouble uploading it to this forum you can try to upload in
Code:
http://d-h.st/
9) Post that file in here, so that i can look at it.
Please see that you may have to use Code to not show your Hot Link like this
Code:
http://d-h.st/
Ok,
I spent my time overnight to download a P5220 Stock rom. I did
P5220XXUAMJ8_P5220VFGAMK1_VOD.zip
I think is a Vodaphone from Germany. But as I said the Recovery Info that we need should be the same in all roms.
1) Warning
Now before I say anything more, I want to make clear that there are many people with Tab3 7", 8" and even 10" that claims that had no trouble installing recovery and rooting. But when they decided to go back to Samsung Stock they lost Wifi or Cell capabilities. I know sound serious, and I have no Idea why so many claims. Lets say more, Most of those claims you can find them here in QA and are 7" and 8" that has nothing to do with the TWRP used in 10". I just have to say this because I seen it and have no understanding on the facts.
I will strongly suggest to backup modems and efs partitions as soon as you install a recovery. This can be done using dd command under Recovery. We could even make a update.zip to do that if any is interested.
You need to be sure that you have downloaded your exact Stock Rom. Even more If I was in your case with a Tab3 with cellphone capabilities I will take my Stock Rom and eliminate the modem.img from the package. There is no reason as to have that in the Stock Rom, unless you have in fact a bad modem. This is only my personal opinion. This is personal suggestion from some one that have no Idea of what he is saying. It is opt to you to research in the area.
Click to expand...
Click to collapse
I have compare "fstab.recovery" from both P5210 and P5220 and show exact information.
/recovery emmc /dev/block/mmcblk0p11
I guess we can conclude that all P5200, P5210 and P5220 have "recovery.img" in "/dev/block/mmcblk0p11"
Code:
# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# mount point fstype device [device2]
/efs ext4 /dev/block/mmcblk0p2
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
[COLOR="Red"]/recovery emmc /dev/block/mmcblk0p11[/COLOR]
/modem emmc /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/boot emmc /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
2) So the first question: Can I install and used a TWRP Recovery made for P5200 or P5210 in P5220? Its seems yes, you can install and used it.
3) BUTTTTT
There is no TWRP or any other Recovery that had been made specifically for P5220. So once install your Recovery will think it is a P5200 or P5210 depending in the file you use.!!! This may result in that some "update.zip" type of installation will fail due to mismatch of Model. This should not be a big problem. You can always install back your Stock Recovery. And we can ask moonbutt74 to build a TWRP recovery using the P5220 particular files in ramdisk of recovery.img.
4) If you want to root I sugest you fallow the only sucefull claim in this forrum, see first post of this thread. I will the install Recovery from
http://forum.xda-developers.com/showpost.php?p=45552913&postcount=1
Then I suggest you backup your sensitive partitions using dd if TWRP do not have that capability.
and I guess you can then root using
http://forum.xda-developers.com/showthread.php?t=2642796
Please stick around, I am very interested in getting a copy of you pit file. I had made a WIN7 batch file that will copy that file from your tablet. A soon as you are rooted notify us and I will post the batch file.
I am attaching the recovery.img of P5220 in Odin tar.md5 in the hope that @moonbutt74 can help us, As soon as moonbutt74 has a P5220 you could upgrade as a TESTER! and report your findings.
This is great news because I was having problems trying to copy the requested files from my phone. So I can just go ahead and install the 'Odin_SGT3_recovery' from the thread you linked. Then use Rest3ssroot.zip to root, right? Or should I just wait until moonbutt74 looks at the file?
Lets talk about us first.
ebue
Your record shows" Posts: 138 and Join Date: Feb 2010". So you should have some experience. But you are sounding so afraid that I wonder.
Most of us here take risk, you know thinks can go wrong. The important is to try to be prepare, Read, read and read. Then make sure you have the appropriate tools and files to recover in case of trouble. Understand that if something goes wrong you and only you is responsible. Do not blame anyone else. At this point you should had check what firmware is your device, and had downloaded you OWN particular 4.2.2 Stock Recovery from Samsung. Do you have?
Please tell us the the firmware version of you device. Just to at least force you to look at it. jijij
Most important, Are you in original 4.2.2? For me this is important. I personally do not trust 4.4.2.
Please tell us that you have ODIN 3.07 and that you have downloaded your correct stock rom from samsung.
Please tell me that at this point you had backup all essential information from your P5220.
Please tell me you have an External Sdcard with at least 4g for ease zip installations.
r2d23cpo
I am an unemployed user. I have some technical background. I have a GT-P5210 -Tab3 10 wifi.
I like to help people but please understand I am no expert. I do know that I learn a lot while helping others.
moonbutt74
There a bunch of good I mean good developers here that I bet you are double as smart as moonbutt74. jijiji I am kidding I do not know.
But what I know is that moonbutt74 will take a problem by himself and spent hours, days,weeks.. until hi find the solution. I admire him.
I do not know why any of the developers had comment yet, I can assume that the lack of FEEDBACK from P5220 owners reporting the result make us be in safe mode. But believe they are out there watching us. jijiji
You know moonbutt74 had read this, look at the thanks. He has been around. But please understand that he has not commit to create for you a new recovery!! I have faith that he will help P5220 in the near future. But when I do not know. So if you what to wait, that is smart. I just do not know when it will happen.
Listen this is what I am going to do. I am going to test the P5220 4G Stock Recovery I downloaded in my P5210 wifi. I see how it behaves. This is not a fill probe that it can work, but at least we can see if the TAB bootloop failing!
As for procedures.
Remember I am no expert!!! If you want to follow me is at you own risk.
Please understand the difference in installing a Custom recovery.img (TWRP) vs root process.
*Just installing Custom recovery.img (TWRP).
First booting in recovery do not affect normal boot process(Android). Is like a X-ray, you can inspect and take x-rays ( backups) without injury Android OS. You cam always replace the original recovery.img and no harm done.
** rooting - Is like an organ replacement operation at the table, you are installing new software that Android could reject and bootloop!!
A) So first step:
Download and have ready all tools and files. No harm done to the TAB3.
B)Watch this video: it is for TAB3 7" but give you an Idea of the procedure you need to follow:
Code:
http://youtu.be/BDShwBHRjUE
C)installing
[RECOVERY][TWRP_2.7] SGT3 Recovery[FINAL]=>http://forum.xda-developers.com/showthread.php?t=2442915
1) Once you download file you received:
Code:
recovery.tar.zip
2) Unzip you will see:
Code:
recovery.tar.md5.tar
this is the file will be using with Odin.
If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.
Odin
1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown in Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acknowledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "recovery.tar.md5.tar"
9) "Message" window . Odin tell you the status in this window. you should see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.
11) Now after you see Successful Odin is ready. If you do not see there is something wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!!
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automatically since we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS.
16) navigate if you like to see your new recovery
Now do not install root yet. Just use TWRP to backup to External SDCARD. yes external so that if something fails you still have recovery files in your External SDCARD.
So once you have done this report to us.
Good luck.
ebue
Keep an eye on moonbutt74. He have not make any comment but, he just edited his thread today around 03:52 PM around 4 hours ago.
And I see a link that reads
Code:
dev-host link - http://d-h.st/4bN TO RECOVERIES - GT-P5220 ODIN -extract then flash.
Usually I do not post other user work "Breaking News", but if I am you I will wait to see if he in fact is helping you!.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
I feel like I am talking by myself.
But I have to say that I did test the STOCK P5220 Recovery and it seems to work nicely. Clearly I have a "Custom" Rom and Recovery shows the Triangle over Android!! Tha we know it happens.
I did also test new h__p://d-h.st/4bN TO RECOVERIES - GT-P5220 ODIN in my P5210 for test purposed and Philz seems to work correctly too.
I did extracted "recovery.img" from "TO RECOVERIES - GT-P5220 ODIN" and seems to shows correct data for P5220 device.code="santos10lte".
At this point I still like TWRP because moonbutt74 TWRP has the ability to accept adb shell commands on the PC! A nice addition while testing.
r2d23cpo said:
Lets talk about us first.
ebue
Your record shows" Posts: 138 and Join Date: Feb 2010". So you should have some experience. But you are sounding so afraid that I wonder.
Most of us here take risk, you know thinks can go wrong. The important is to try to be prepare, Read, read and read. Then make sure you have the appropriate tools and files to recover in case of trouble. Understand that if something goes wrong you and only you is responsible. Do not blame anyone else. At this point you should had check what firmware is your device, and had downloaded you OWN particular 4.2.2 Stock Recovery from Samsung. Do you have?
Please tell us the the firmware version of you device. Just to at least force you to look at it. jijij
Most important, Are you in original 4.2.2? For me this is important. I personally do not trust 4.4.2.
Please tell us that you have ODIN 3.07 and that you have downloaded your correct stock rom from samsung.
Please tell me that at this point you had backup all essential information from your P5220.
Please tell me you have an External Sdcard with at least 4g for ease zip installations.
r2d23cpo
I am an unemployed user. I have some technical background. I have a GT-P5210 -Tab3 10 wifi.
I like to help people but please understand I am no expert. I do know that I learn a lot while helping others.
Click to expand...
Click to collapse
Although I have been a registrant since the said date, I am still a novice. I have no technical ability what so ever. I am kinda busy with my family and work constantly. My kids do not give me a lot of time to do trails and errors and I do not have so much time on my hands. That is why I thought a root would have been available for download so I can just root and get on with my life. I do not have time to experiment lie you guys do. All I want to do is root to remove apps that I do not use or want. That's all. I used to try out different different ROMs a long time ago. But that is when I had time. I do not want to be bother with trying out different ROMS if I am not forced to. That is why I leave these things up to people who have the time and resources and who are dedicated to these things. So, if I have to wait to get a proper root so I do not have to risk anything, than I will. So, I can give you the little info that I have for my pad. Here they are:
1. I have downloaded Odin already and in the process of downloading my Stock Firmware.
2. I do not have an external car yet for my pad. Only for my Note 3, which I am using. I will buy one soon.
2. My Android -Version is 4.2.2 ; Basbandversion is P5220XXUANE1 ; Kompileringsnr is JDQ39.P5220XXUANB4
Anything else you request?
I understand you, not enoght free time. Do not feel presure from me. Wait for others to report a valid solution is no bad, in many cases is the smart thing todo.
As I said moonbutt74 build Philz Advance CWM for P5220. But some one with a P5220 need to test it and report. I see in his last page some interested, but if no one reports we will never know. Reporting Feeback is the most value tool after a developer has done his work.
Sent from my GT-P5210 using XDA Premium 4 mobile app
I just tried Moonbutt's Philz and TWRP recoveries. I was trying to flash the stock roms for p5220)LTE as posted by Restl3ss. In both cases I got errors and am now waiting for a TWRP version that works on the p5220.
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
---------- Post added at 04:32 PM ---------- Previous post was at 04:04 PM ----------
quijote1 said:
OK, I installed PhilZ and it seems to work fine. First I tried to flash your deodexed rom. Part way through the flash I got the message:
set_metadata_recursive: some changes failed
E;Error in /sdcard/download/P5200-4.4-stock-deodexed-rooted.zip
(Status 7)
E: Installation aborted
So now I'm going to try the totally stock one.....
Same error again. Bummer because I forgot to make a PhilZ backup of my 4.2.2. I have a TWRP backup, but that's all.
Click to expand...
Click to collapse
The above is a message that I sent to Restl3ss, but repeat it here since it shows the error messages that I got with Philz by Moonbutt.
Just to provide feedback, the version of Philz recovery worked very well for the most part. I like it better than TWRP. If I could get it to install roms, I would stick with it.
Off topic, I am in Spain and Orange is my carrier but my tablet is not linked to Orange. There is a stock rom on Sammobile that is for Orange in Spain. Would that work on a tablet that is unlocked?
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
To add more detail, it turns out that Restl3ss left out a few lines of code for the p5220. Since he didn't have one he never noticed. Now he has added that code and now his rom loads with TWRP.
Samsung Galaxy Note 2
Dr. Ketan v12.1 4.4.2 NI1
Kernel: Stock
Apex Launcher
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.
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!
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.