Custom Binary blocked by frp lock - Galaxy Note5 Q&A, Help & Troubleshooting

So I rooted my phone and rebooted. The OEM unlock must've been disabled somehow, and now I can't get the phone to start up. I tried flashing stock firmware, and it fails with SW REV check fail device 2 binary 1.
I tried getting stock firmware from sammobile but it's always corrupted, despite me watching the download very closely and watching it finish. I tried everything right down to flashing a new bootloader and frp lock blocks all of it. I have scanned google for the past 48 hours and contacted sammobile about the corrupted zip. I haven't gotten anything back yet, but I really want to get this phone fixed asap.
2 questions:
1. what does the error SW REV check fail device 2 binary 1 mean.
2. Can I flash any official firmware or does it have to be my specific firmware, and if I force it what damages are there.
If at all possible, does anyone have a copy of the note 5 rogers (nougat) rom. So I can try to flash something not corrupted.
Any help I can get is appreciated.
On a side note, I haven't been in the rooting scene for a long time (since kitkat) what new developments should I watch out for to prevent further issues.

TheVampkid said:
So I rooted my phone and rebooted. The OEM unlock must've been disabled somehow, and now I can't get the phone to start up. I tried flashing stock firmware, and it fails with SW REV check fail device 2 binary 1.
I tried getting stock firmware from sammobile but it's always corrupted, despite me watching the download very closely and watching it finish. I tried everything right down to flashing a new bootloader and frp lock blocks all of it. I have scanned google for the past 48 hours and contacted sammobile about the corrupted zip. I haven't gotten anything back yet, but I really want to get this phone fixed asap.
2 questions:
1. what does the error SW REV check fail device 2 binary 1 mean.
2. Can I flash any official firmware or does it have to be my specific firmware, and if I force it what damages are there.
If at all possible, does anyone have a copy of the note 5 rogers (nougat) rom. So I can try to flash something not corrupted.
Any help I can get is appreciated.
On a side note, I haven't been in the rooting scene for a long time (since kitkat) what new developments should I watch out for to prevent further issues.
Click to expand...
Click to collapse
You can download the latest stock firmware update N920CXXU3CQE1 For note 5 in samupdate or samsung mobile or any other websites to fix frp lock and the error SW REV check is about the sboot file when you update your phone you update sboot too , so samsung won't let you flash older firmware with older sboot file ....

mala96 said:
You can download the latest stock firmware update
For note 5 in samupdate or any other websites to fix frp lock and the error SW REV check is about the sboot file when you update your phone you update sboot too , so samsung won't let you flash older firmware with older sboot file ....
Click to expand...
Click to collapse
I got an email back from sammobile saying they fixed the file. Downloaded it, flashed it everything works fine now.
Stuff I learned.
1. MAKE SURE YOU DO NOT TURN OFF OEM UNLOCK
2. Always keep a stock backup.
3. first thing you should re-flash bootloader.

TheVampkid said:
I got an email back from sammobile saying they fixed the file. Downloaded it, flashed it everything works fine now.
Stuff I learned.
1. MAKE SURE YOU DO NOT TURN OFF OEM UNLOCK
2. Always keep a stock backup.
3. first thing you should re-flash bootloader.
Click to expand...
Click to collapse
I hope my tips where usefull

mala96 said:
I hope my tips where usefull
Click to expand...
Click to collapse
They were, I already knew about sammobile, but I wasn't particularly trustworthy of the ones you mentioned.
Thanks though.

TheVampkid said:
They were, I already knew about sammobile, but I wasn't particularly trustworthy of the ones you mentioned.
Thanks though.
Click to expand...
Click to collapse
Good to hear that , did you get your phone install the update ???

Yep. Everything work 100%
Made this reply on the phone.

And for anyone who hasn't kept OEM unlock enabled..
Once I ran my battery down to 0% on MM. Upon charging I was FRP locked. Go figure..

mala96 said:
I hope my tips where usefull
Click to expand...
Click to collapse
Hello people. I hope I can get some advice. I seem to have done a REALLY DUMB THING and unchecked the box in developer tools and .... sigh ... turned off OEM lock (there was an instruction about unlocking the screen. I know. DUMB). But now I have a bricked brand new note 5. I am downloading the firmware that should go with my nougat 7.0 and am hoping to be able to use Odin 3.11. I tried to use the Mac version Jodin but that didnt work
Any thoughts> advice? I know ... I screwed up big time and should have known better
Thanks !!!!!

What was the firmware before you bricked it?
I'm not sure what the security is on the frp lock but I'm sure it's either a tag in firmware or checksum. If it's checksum you might be screwed unless you were running stock. Did you update the device to nougat before you turned off the oem unlock?
Try the actual odin. I'm pretty skeptical of other versions. If you need another firmware I still have mine.

TheVampkid said:
What was the firmware before you bricked it?
I'm not sure what the security is on the frp lock but I'm sure it's either a tag in firmware or checksum. If it's checksum you might be screwed unless you were running stock. Did you update the device to nougat before you turned off the oem unlock?
Try the actual odin. I'm pretty skeptical of other versions. If you need another firmware I still have mine.
Click to expand...
Click to collapse
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?

AlvinT said:
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?
Click to expand...
Click to collapse
Extract the zip and try to flash the tar.md5 file.

AlvinT said:
I was running the most recent Nougat that was OTA after I bought the phone and then used tdunham;s [How-to] Root your Device - all versions + All Firmware Download
I managed to get that to work and it was fine (rooted) but then I did the dumb OEM uniock
I did an android backkup on the phone befire I screwed it up but dont know how to get to it. Maybe flash a TWRP tar file?
The sprint firmware I downloaded is a zip file. But I guess thats not going to work with Odin
So ,what next?
Click to expand...
Click to collapse
You will not be able to use your phone again until you flash a complete firmware via Odin. You, me and many other are having the same problem on the latest Sprint Nougat firmware (DQF1). Heck, I had it twice yesterday until I noticed OEM Unlock was disabled.
Flash the DQF1 via odin, you won't loose personal files like photos but after that the phone will be buggy so you may want to do a factory reset.
I had to ask: https://forum.xda-developers.com/note5/help/fml-custom-binary-blocked-frp-happening-t3637070
And this guy: https://forum.xda-developers.com/note5/help/sm-n920p-frp-fap-lock-help-asap-t3637438
And you.
Fix: Flash a complete stock unmodified firmware via Odin.

TheVampkid said:
Extract the zip and try to flash the tar.md5 file.
Click to expand...
Click to collapse
When I try to extract the zip (on my mac) I get a message that says "unable to expand .... into Downloads". It could of course be a corrupted file, but I dont think so.
Any chance or way of getting to TWRP (maybe odin) and reaching my nandroid backup (which i figured was "insurance" against a screwup"? I could try to odin that, and am thinking of doing ir later
If all fails, do I just throw the phone away? I hate that idea
So, how do I get the firmware that I can flash via Odin???
As always, suggestions welcome.

AlvinT said:
So, how do I get the firmware that I can flash via Odin???.
Click to expand...
Click to collapse
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)

cachanilla86 said:
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)
Click to expand...
Click to collapse
I downloaded that file (it took a long time but I do have it) it's a zip file but when I try to open it my mac says I can;t. I have an old Pc that I installed odin with but for going back and foth and downloading my mac is much faster, (I transfer files to the PC using a USB)
I'll check to see if sammobile has a md5 for their file. But I guess I MUST havve that tar file

AlvinT said:
I downloaded that file (it took a long time but I do have it) it's a zip file but when I try to open it my mac says I can;t. I have an old Pc that I installed odin with but for going back and foth and downloading my mac is much faster, (I transfer files to the PC using a USB)
I'll check to see if sammobile has a md5 for their file. But I guess I MUST havve that tar file
Click to expand...
Click to collapse
Thanks so much but there is now NO NEED
Here's a happy ending: I went to the local NYC Sprint store, the tech guy in charge was terrific, no sermonizing, he took the phone in back and after maybe 15 minutes came back with the very recent (QE1) firmware installed
I have it back, unrooted. But WORKING
Thanks much. And I must say I found the level of service from the Sprint store guy a real relief
Al

cachanilla86 said:
Firmware are downloaded from http://www.sammobile.com/
Search for the SM-N920P and download one. It will take like 2 o 3 hours to download a .zip, inside the .zip there is a .tar.md5 file you will need to unzip, that file that Odin will recognize and flash. The DQF1 build will work, you just loose all the mods and root. (Avoid Macs if you are gonna tinker with Android)
Click to expand...
Click to collapse
Dear, please help me to recover my note 920C. I was running khongloi rom v11 and when i rebooted phone it just got frp lock notification. so i cant reboot it or go into recovery mode. i tried to flash latest firmware from sammobile via odin 3.12.7 but it fails in last step. Please check and help ;((
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1207)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> cm.bin
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img
<ID:0/010> cache.img
<ID:0/010> hidden.img
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Frp lock bypass on galaxy note 5
First of all you have to download firmware combination file for your galaxy note 5 with the same model number as your device have. Then you can easily flash the AP file with odin3 and your phone will turn on..The user interface will appear different but you will be able to access oem unlock feature in developer options.
Then turn of the oem lock.
Then you can download stock u4 firmware with 4 files AP+CP+CSC+BL
and you have to flash all these 4 files while your phone is in download mode.
After the procedure your phone will be unlocked and you are good to go.
I hope that this article would be helpful for all those people who have got their phone blocked by frp lock

Sinankhan.official said:
First of all you have to download firmware combination file for your galaxy note 5 with the same model number as your device have. Then you can easily flash the AP file with odin3 and your phone will turn on..The user interface will appear different but you will be able to access oem unlock feature in developer options.
Then turn of the oem lock.
Then you can download stock u4 firmware with 4 files AP+CP+CSC+BL
and you have to flash all these 4 files while your phone is in download mode.
After the procedure your phone will be unlocked and you are good to go.
I hope that this article would be helpful for all those people who have got their phone blocked by frp lock
Click to expand...
Click to collapse
Is there any way you can help me with this? I've downloaded 3 different firmwares, created a combinary using the tool with each of them but every time I push them via Odin, it gives me "SW REV. CHECK FAIL. DEVICE: 6, BINARY: 1" and the other two times it was BINARY: 2 and BINARY: 4.
What am I doing wrong?
Do I just have to wait for someone to come out with something flashable?...
My RP SWREV is B:6 K:1 S:2
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED

Related

Flashing my phone to the way it was.

Hello everyone,
I want my phone back to the way it was on android 2.1 so I can update to 2.2.
I got 2.2 on my phone before it was officially released, and had to do it with other CSC etc.
So I want my phone back to the way it was when I bought it, how will I be doing this?
I remember I had JM2 when I got it.
Thanks in advance.
EDIT:
Found this thread. http://forum.xda-developers.com/showthread.php?t=846913
Those are the ones you get when buying the phone right? So, can I just pick the JM2 and flash it?
Please help.
yes the ones in that link are official stock ROMs just flash which ever you desire and your phone is 100% original again.
Alright then, thanks.
I'm trying to find a tutorial on how to flash it, since it's been awhile. But I can only find tutorials for custom roms.
the tutorial is in the link, its relatively easy. have you downloaded the stock rom you want ?? does it come in 1 file or 3
It's still downloading it, but it's 1 file in .exe format.
The CSC's in that thread, does not include a JM2 one. Am I missing something? And what PIT file do I have to use?
im confused ??? its in .exe format ? wait till it download and then open it and make sure... if it needs a pit it should all be in there, a lot of stock roms come in just 1 .tar file.
I think it's a 7zip.
Alright, I'll just reply in this thread when there's something I need. Thanks for the help so far.
The PIT file isn't included, do I really need to use it or is it optional?
I think I have to use the 512.
just make sure re-partition is checked before you flash.
Alright.
But I think I have a little problem.
When I connect my phone, "0:[COM3]" shows up yellow in Odin. Shouldn't it be green?
Screenshot: http://i52.tinypic.com/34j4ufk.png
(I hope it's clear)
And it's just stuck there.
its supposed to be yellow.
Ok, but does it take long for it to go on?
I've tried it without the PIT file but then this happens.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
have you extracted the files ?? or did it come in 1 file ?
Procedure:
1.Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
2.Select the PDA/Modem/CSC/.PIT files in Odin. (For kernel flashes, only PDA is required. For FW flashes, .PIT and at least a PDA is required. Some PDAs have Modem and CSC integrated. Make sure you have the correct .PIT file. Usually 512.pit)
3.Check the "Re-Partition" checkbox.
4.Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
5.Connect your phone with your computer and wait until the drivers are installed.
6.When the drivers are installed, click Start.
7.The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
8.You have successfully flashed your phone.
That's what I forgot, the download mode.
But the Re-partition has to be un-checked? Should it be checked or not?
check it, if you have all 3 files. and pit. then everything will be normal
Ok, it's going good so far.
You have been a great help, I really appreciate it
It did say something about having no access to multi-something. But other went fine.
good, just be sure to let it boot properly. sometimes it can take 15mins to boot up so dont panic. as long as ODIN says PASS, all is well.
I got another question.
Since it's android 2.1 and 2.2 being released. Kies should tell you that there is an update?
But Kies says: This version of the device cannot be updated.
By current firmware version it says: PDA:JM2 / PHONE:JM1 / CSC:JM1
Something wrong?

[Q] bricked galaxy s? which firmware

Hi,
I've got here a bricked galaxy s from a friend of my. he tried to root the galaxy s without knowing how.
But the problem is.. I don't know which firmware he had. So i don't know which .tar file i need for odin3 to restore.
Can i track somehow the firmware? its an europe version with 2.2 he said. Or is there an other way to restore this phone?
When i startup the phone it hangs at the galaxy s logo. I can enter download mode
Use Sammobile.com
You'll need to make a login first and then just follow the click to the files..
There are also stock packages in the general section such as cf-root, to gain root access. And there are other stock firmware threads there.
Try only flashing the code.tar file, I think that's where the kernal is but best to confirm that somewhere. Otherwise just flash the whole stock package.
i bricked my galaxy and i recomand a stock package and from that you can root and you can change to a custom rom if he wants that...
Talon26 said:
Use Sammobile.com
You'll need to make a login first and then just follow the click to the files..
There are also stock packages in the general section such as cf-root, to gain root access. And there are other stock firmware threads there.
Try only flashing the code.tar file, I think that's where the kernal is but best to confirm that somewhere. Otherwise just flash the whole stock package.
Click to expand...
Click to collapse
can you be more specific how to get the right firmware? Do i need to go to SAMFIT? or SAMSUNG LETTER CODE? i have no idea how to find it
Ok, sorry i thought Sammobile.com had complete instructions on how to find the firmware for you like it used to, but I haven't used it in a while..
I don't remember what all those codes mean and tbh it doesn't matter too much. The main thing is to find your CSC code. This will be the factor that would usually cause problems (actually annoyances) if incorrect, e.g. SMS messages not being received with the correct time and date.
Here, Ramad a very respected member of the community has made a collection of firmware generally with multi-CSC's. You can use these downloads or really any of the other downloads from sammobile (link to the Europe section). It doesn't matter much if he doesn't get the correct firmware because they are all available in Europe.
Find your CSC from Samfit samsung letter code. They are the 3-letter codes nearing the bottom. Press " Ctrl + F " and then type in your country. This will highlight your country on the page. Look to see if your carrier has a specific code, if it does then remember is and look at Ramad's list.
Go down to the 2.2 or 2.2.1 section and again " Ctrl + F " and type in the CSC. Look for the firmware that has it listed. Download that firmware and flash using the instructions at the top of Ramad's thread or using the pdf that you can download from sammobile. Generally the latest build date is best to download. But if you don't it doesn't matter because you will be using stock you can plug it into Kies and it will update it for you.
To check your CSC the long way (I cannot remember the short way ) type in *#272*(your imei)#
This will display your current imei and allow you to change it. Changing it to the one you want will factory reset your phone so be ready.
If i have left anything out or you have any more questions then let me know...
Hope all goes well
http://www.google.co.uk/url?sa=t&rc...2ZTkBw&usg=AFQjCNHCNRbuqVFXltW99vQc1_pfPlNr4Q
check this out video guide
Oke. I really bricked the phone now i guess.
If i turn on power.. it doesnt do a thing. can't enter download mode either
i downloaded the right .tar file im almost sure. But when it was flashing.. The phone was constantly rebooting. so the usb connectiong diddnt stay on.
Not to worry. You probably haven't bricked it. The worst you will probably have to do is make a purchase of a USB jig which forces download mode...
Before that however there are multi tricks to try get it into DM. (Obviously make sure your battery is sufficiently charged.)
1. Hold down the combo and then put the battery in, whilst holding the combo. (You will probably need help)
2. Start Odin (make sure all kies apps are closed on the comp first) plug in phone. Hold down combo.
3. Same as number 2 without battery. If it doesn't work. Set up as 2 hold combo then battery in.
4. Same as 2 with charger instead of computer.
I think those are all the combinations but you can search for it. There used to be a thread on general listing all the ways you could be bricked and ways of getting out.
Anddddd if all that fails, then you can make or buy a USB jig. Search general if you want to buy it but also you can find links to buyers members have used.
And in the worst case none of that works.. you can set the unbrickkable mod which means you will loose warranty for ever and never get it back as it is a hardware modification. I'll give the link to that if and when you need it.
Good luck
Sent from my GT-I9000 using XDA
pfjew. it worked. can enter download mode!
But when i want to flash my proper firmware it asks for a pit file this time. But i don;t have a pit file at my firmware that i downloaded from sammobile. only a .tar file and a .dll
Which .pit should i use? I really want the right one this time. Deffenitily dont want to brick the damn thing i grabbed this firmware from sammobile
I9000XWJW1 ## 2.3.6 2012 January I9000XENJV5 Netherlands
I did a quick search because Sammobile is now super crap. Remember reading this..
[GUIDE] [INFO] The reality of PIT files
Having a quick scan of what it says, I believe it does not matter...But best to read to be sure.
Let us know if it works
it worked. flashed the firmware. rom doesnt work.. Boot loop.
Can enter Android system recovery now. But because that doent support my external sd, and i can't boot properly i can't flash a new rom?
I would like to flash CWM with external_sd support. searching for that one now
(i know how at my optimus 2x.. but everything is lots easier at optimus 2x compared to sgs)
Have you tried flashing it again?
Also have you tried flashing an older rom with a multi csc that includes your csc?
And finally [ODIN] DarkyROM 10.2 Resurrection GT-I9000, usually helps people stuck in your situation. Id try the first two though because it keeps stock.
last one worked. thanks A LOT!
Hi,
my SGS seems to be bricked. I have tried everything described in the posts before, but nothing worked.
Here is what I did:
I downloaded several roms (those mentioned in the previous posts and from other forums) and installed them via Odin3 (1.85). The Odin log says everything went fine:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PHONE_XXJW4.tar.md5 is valid.
<OSM> CSC_OXAJW4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
The SGS reboots and stucks at the very first Samsung logo (the one without animation). When I hit the softkeys, the light goes on, but doesn't turn off again.
After each installation I didn't touch the phone for 20 minutes hoping that something happens - but nothing
Only 2 options are left:
- returning to the download mode
- removing the battery
Another strange issue: When I try to load the SGS, the displays turns on and shows the battery symbol, but it is not animated.
Has anyone an idea what else I can do?
Thank you for your help in advance!
@keinfilter:
from samfirmware.com the flash program for i9000 is 1.82 or 1.3 or 1.0
have you used the 512 pit file?
Well you say you have done all of the above...
1. You cant even boot with [ODIN] DarkyROM 10.2 Resurrection GT-I9000??
2. Wipe by going into recovery and doing all these wipes...
wipe date/factory reset + wipe cache + mount and storage>>>format system+cache+datadata+data (I dont wipe boot and you need sdcard)
After doing all the above wipes try Darky or stock with repartition checked...
3. I'm assuming that you used single tar files for flashing via odin, have you tried Odin flashes with 3 files?? If not either find a rom with 3 files or split one of the roms using the following guide by Ramad
Let us know if any of that works...
Good luck
Thanks for the very fast answers!
from samfirmware.com the flash program for i9000 is 1.82 or 1.3 or 1.0
have you used the 512 pit file?
Click to expand...
Click to collapse
I tested all three version (1.82, 1.3, 1.0), each with 3 files roms and the 512 pit file. Nothing changed, still the samsung logo.
1. You cant even boot with [ODIN] DarkyROM 10.2 Resurrection GT-I9000??
Click to expand...
Click to collapse
After trying the DarkyROM with his ODIN again, the DarkyROM logo (Galaxy S GT-I9000 powered by DarkCore & Darky's rom) is displayed instead of the samsung logo. But the boot process doesn't continue
DarkyROMs zip archive contains only the PDA.tar, what about the CHC and PHONE? Do I have to use these from other roms? I haven't tested it yet, because I don't want to make it worse.
Wipe by going into recovery and doing all these wipes...
Click to expand...
Click to collapse
I can't access the recovery mode. Tried it via holding Vol up + Home button + Power button until the Samsung logo was shown the 2nd time and then releasing all buttons, but nothing else than the samsung logo.
3. I'm assuming that you used single tar files for flashing via odin, have you tried Odin flashes with 3 files?? If not either find a rom with 3 files or split one of the roms using the following guide by Ramad
Click to expand...
Click to collapse
All the roms I tried consisted of 3 files but the DarkyROM.
Edit: Btw: I have no micro-sd or sim card inserted because I read in any forum it is better to remove them. I don't know if this makes any difference.
Has anyone further ideas? Any help would be appreciated!
Try to reflash in JVU STOCK with PiT512, MODEM, CSC, etc... with battery fully charged.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Envoyé avec Tapatalk 2.0.1 depuis mon Samsung Galaxy S GT-I9000
ROM : SLIM ICS 3.3
Kernel : Origine ROM
Modem : JW4

[Q] Help me please

Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
andrew59it said:
Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
Click to expand...
Click to collapse
so, what is your question actually??
Mate, I think the question is simple.
From what I understand in your comment, it seems you tried to install the Stock Rom 4.1.2 Italy, when you were the 4.0.4 / 4.0.3 Stock Rom Italy. On installation through ODIN pc you had a problem where it remains in the Samsung logo, will not let you enter the Recovery mode, only the Download mode. Is that so?
I should arrived that case do not leave any triangle would remove the battery, and after 10-15 seconds reintroduce it, and just then press buttons to enter the Recovery mode. If it fails, repeat the removal of the battery, but now when placed connect the DC charger to the phone I tried to turn normally to 20-25 seconds (just outside and away the logo of battery charging), and try to turn it on Recovery mode again, but we will keep down so long that should disappear all as to turn it off, and you press the keys for the Recovery mode, this time releasing anything else lighting appear on the screen, just a moment before letters GT-N7000, now if it really is accessible Recovery should apparate.
If you enter Recovery Mode Stock Samsung, you will have look out if a line appears below indicating the application, or wondering whether to apply the new CSC, we accept without thinking, since it must reaffirm the phone to initiate a Stock Rom.
Now if I come to this moment really was not accessible Recovery mode should get a screenshot of ODIN pc which finishes entering files to mobile, if it were really a fault, and do not leave do the installation, if you checked any box incorrectly, of which are not activated.
Other options include USB cable failure, USB port, lack of USB debugging enabled before starting the installation, do not put at least 10 minutes in the backlight time (this can try to fix running a finger across the screen every 23 seconds if it was 30 seconds off), but that the capture can determine ourselves if the error is only for ODN pc, which can be a failed in the installation and have not really finished the installation, in this case it would be almost insurance problem USB cable used, and in extremis or USB port.
fusionero said:
Mate, I think the question is simple.
From what I understand in your comment, it seems you tried to install the Stock Rom 4.1.2 Italy, when you were the 4.0.4 / 4.0.3 Stock Rom Italy. On installation through ODIN pc you had a problem where it remains in the Samsung logo, will not let you enter the Recovery mode, only the Download mode. Is that so?
I should arrived that case do not leave any triangle would remove the battery, and after 10-15 seconds reintroduce it, and just then press buttons to enter the Recovery mode. If it fails, repeat the removal of the battery, but now when placed connect the DC charger to the phone I tried to turn normally to 20-25 seconds (just outside and away the logo of battery charging), and try to turn it on Recovery mode again, but we will keep down so long that should disappear all as to turn it off, and you press the keys for the Recovery mode, this time releasing anything else lighting appear on the screen, just a moment before letters GT-N7000, now if it really is accessible Recovery should apparate.
If you enter Recovery Mode Stock Samsung, you will have look out if a line appears below indicating the application, or wondering whether to apply the new CSC, we accept without thinking, since it must reaffirm the phone to initiate a Stock Rom.
Now if I come to this moment really was not accessible Recovery mode should get a screenshot of ODIN pc which finishes entering files to mobile, if it were really a fault, and do not leave do the installation, if you checked any box incorrectly, of which are not activated.
Other options include USB cable failure, USB port, lack of USB debugging enabled before starting the installation, do not put at least 10 minutes in the backlight time (this can try to fix running a finger across the screen every 23 seconds if it was 30 seconds off), but that the capture can determine ourselves if the error is only for ODN pc, which can be a failed in the installation and have not really finished the installation, in this case it would be almost insurance problem USB cable used, and in extremis or USB port.
Click to expand...
Click to collapse
Thanks to reply.....
I was not really clear probably.
I tried to install 4.1.2 over 4.0.4 dedicate rom (3 H3G italian operator)
Odin always failed hanging or giving some fault
So I installed the ICS kernel (or rom) everything was fine. So I suppose the cable is ok , odin is ok etc....
But from the moment I downloaded the ICS, at reboot the phone hang on samsung logo with yellow triangle. ANd if I try to switch off the phone it restart and hang on logo.
Download mode is still working but recovery mode not.....
I'm looking for some kernel, rom, cwm to download, to recover the phone.....
The best thing to do is reinstall the ROM 4.1.2 (the 4.0.x are more dangerous if we wipes, JellyBean when they are not), but check that no error appears, if it appears only after installing the Rom rather fails during it, you can download the kernel Philz for you version, right now if you tell me the link to SamMobile I can tell you what, so you can tell which is correct, although it is not hard to tell if you look at the post of Philz above kernel with all links to them. After installation and download the kernel, you turn the phone into Recovery mode, you select mount usb (I think it came out well, but stresses) and connect your phone to your pc, you can pass the kernel to the internal SD and another copy to the SD external (remember to leave both copies at the root of both SD's). You MUST complete the transfer and disassemble with the option displayed on screen, and disconnect the USB cable. You continue by going to install zip, and should be able to select the Kenel Philz to install, after installing (if you get an error: Status 7 quiet, it was not the correct version of the kernel, and not actually installed), you will have to restart the mobile again, but when you start on with the letters GT-N7000, you will have to restart it by pressing Vol + - Power - Home, all at once, and keep it until the letters again, and keep it until it goes - restart, then you press the 3 keys, and when the letters appear, you must drop the 3 keys, and should you appear the menu Recovery kernel Phliz, there as you will see below something that says CSC implemented or instead ask if you want to apply, accept if you ask, and you should be able to restart the phone and wait about 5 minutes maximum to emit sound and vibration as it is booting at all, and then you should be able to start getting bills from Samsung and Google.
Thank fusionero
the problem is I'm not able to install the 4.1.2 , odin hang or fail
The ROM version I need is
sammobile.com/firmwares/download/22314/N7000XXLT9_N7000ITVLT3_ITV
So I think nex step is to install kernel Philz but I don't know which version I need. On the phone was installed 4.0.4 build IMM76D.XXLRL
CIAO
You must enter this http://www.sammobile.com/firmwares/download/22314/N7000XXLT9_N7000ITVLT3_ITV.zip/ address, and you must connect to you account to download that version you mention, I just check and this downloading smoothly on my pc . The problem is that it would open without ending .zip or you caught hours of server failure, just that i found this morning when downloading another who asked me.
As to what you mention about the version you have installed, as you are looking at the correct thread ( http://forum.xda-developers.com/showthread.php?t=1901191 ), the kernel you need for what you indicate ( 4.0.4 build IMM76D.XXLRL CIAO ) is this:
Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99:
http://www.mediafire.com/?3ale6m9q6b6a3
Updated kernels list:
PhilZ-cwm6-BULR1-SWC-v3.99
PhilZ-cwm6-DDLR6-ODD-v3.99
PhilZ-cwm6-DDLR9-INU-v3.99
PhilZ-cwm6-DDLRB-ODD-v3.99
PhilZ-cwm6-DXLP9-OLB-v3.99
PhilZ-cwm6-DXLR2-OLB-v3.99
PhilZ-cwm6-DXLR5-OLB-v3.99
PhilZ-cwm6-JPLPD-OJP-v3.99
PhilZ-cwm6-JPLR8-OJP-v3.99
PhilZ-cwm6-UBLPC-UUB-v3.99
PhilZ-cwm6-UBLR3-PSN-v3.99
PhilZ-cwm6-UBLR5-TCE-v3.99
PhilZ-cwm6-XXLPY-XEN-v3.99
PhilZ-cwm6-XXLQ3-OXX-v3.99
PhilZ-cwm6-XXLRG-DBT-v3.99
PhilZ-cwm6-XXLRI-AUT-v3.99
PhilZ-cwm6-XXLRK-XEU-v3.99
PhilZ-cwm6-XXLRL-HUI-v3.99 - Is this your kernel
PhilZ-cwm6-XXLRQ-DBT-v3.99
PhilZ-cwm6-XXLRT-DBT-v3.99
PhilZ-cwm6-XXLRU-VDI-v3.99
PhilZ-cwm6-XXLRW-SFR-v3.99
PhilZ-cwm6-ZSLPF-OZS-v3.99
PhilZ-cwm6-ZSLPM-OZS-v3.99
PhilZ-cwm6-ZSLPN-OZS-v3.99
Click to expand...
Click to collapse
andrew59it said:
Hello new in this forum.....
The threads I read overwhelmed me.... :cyclops:
I have a N7000 from a friend of mine. It had a dedicated 4.0.4 rom from "3" (italian operator) build IMM76D.XXLRL
I tried to install a new italian rom 4.1.2 via odin but every attempt failed
Unfortunately I ended up into a thread about ICS kernel (sorry if I make some mistakes with names but I'm really lost....)
so downloaded the ICS and with my surprise it was installed into the phone.
From that moment the N7000 hang at samsung logo with the yellow triangle....
And the worst thing It goes in download mode but not in recovery mode.....
I tried to read many post before write, trying to understand waht to do but now I'm totally confused..... md5,tar,img, zip...... kernel,root, cwm., rom ....
Someone may explain to me if there is something to do to save the phone?
Thanks i n advance
Andrea
Click to expand...
Click to collapse
Your phone is not booting since you flashed an ICS kernel over a JellyBean ROM
Android ICS version : 4.0.4
Android JB version : 4.1.2
so I hope you understand the difference.
You are lucky you didn't brick your device or have you already
But since you are able to go in download mode I think its not bricked yet.
It was probably a bad download which failed the installation so download ROM again and this time verify that your download is not corrupt by running it via md5 if provided.
also please provide the link of the ROM thread that you are trying to install so that I can understand better
and if you are not looking to flash a custom ROM or rooting your device in order to do so then in that case the steps are pretty straight forward
download Stock ROM
extract ROM
open Odin
select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC
put phone in download mode and connect
the bar should turn yellow once connected.
once connected click on flash
bar should turn green if successful
REVENGE SOLVES EVERYTHING
tysonraylee said:
Your phone is not booting since you flashed an ICS kernel over a JellyBean ROM
Android ICS version : 4.0.4
Android JB version : 4.1.2
so I hope you understand the difference.
You are lucky you didn't brick your device or have you already
But since you are able to go in download mode I think its not bricked yet.
It was probably a bad download which failed the installation so download ROM again and this time verify that your download is not corrupt by running it via md5 if provided.
also please provide the link of the ROM thread that you are trying to install so that I can understand better
and if you are not looking to flash a custom ROM or rooting your device in order to do so then in that case the steps are pretty straight forward
download Stock ROM
extract ROM
open Odin
select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC
put phone in download mode and connect
the bar should turn yellow once connected.
once connected click on flash
bar should turn green if successful
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thanks everyone....
I think you hit the problem..... but my original ROM version was 4.0.4 .... (H3G)
Anyway probably something went wrong.... I don't need a custom ROM or to root the device.
I need to install N7000XXLT9_N7000ITVLT3_ITV if possible but the flash doesn't start via ODIN
May you explain step by step what have I to do? I really appreciate....
What do you mean "select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC" ?
md5 is not a single file? I read something about more files to place in odin.....
@ fusionero: I already downloaded the files.... also PHILZ XXLRL but the device doesn't start anyway.....
andrew59it said:
Thanks everyone....
I think you hit the problem..... but my original ROM version was 4.0.4 .... (H3G)
Anyway probably something went wrong.... I don't need a custom ROM or to root the device.
I need to install N7000XXLT9_N7000ITVLT3_ITV if possible but the flash doesn't start via ODIN
May you explain step by step what have I to do? I really appreciate....
What do you mean "select appropriate files i.e Choose CODE in PDA, MODEM in PHONE, Multi CSC in CSC" ?
md5 is not a single file? I read something about more files to place in odin.....
@ fusionero: I already downloaded the files.... also PHILZ XXLRL but the device doesn't start anyway.....
Click to expand...
Click to collapse
Did you download the XXLT9 ROM?? or the ROM that you want to flash ??
if so then it should be a zip file, if you extract that zip file you should have 3 files in it (sometimes only PDA file is present and the other two i.e Modem and CSC are not present, dont worry the PDA file alone is enough)
Open Odin, click on PDA button and select the firmware file with .tar.md5 extension (The firmware file look something like: N7000XXDLJ5_N7000ODDDLI7_INU.tar.md5 Select the one that looks similar to the ROM you downloaded)
and if there are CSC and Modem files then select them by clicking Phone and CSC in Odin accordingly. It will be mentioned in the file name if its a Modem or CSC file
if MODEM_XXXX.tar.md5 then select that file by clicking the PHONE in Odin and if XXXX_CSC_XX.tar.md5 then select it by clicking CSC in Odin
remember that you lose all your data
Then just click flash and it should flash
md5 is a single file and is used to check the integrity of the file you downloaded. Its just used to make sure that the file you downloaded doesnt have any errors or is corrupt. you use the .md5 file and compare it with the md5 of the ROM.zip If it matches then its not corrupted or is a bad download. (.tar.md5 and .md5 are different files as in .tar.md5 is a firmware file and .md5 is a hash file used for integrity check)
Just right-click the rar/zip file and select properties and select the "file hashes" tab and if you downloaded a .md5 open that file by clicking "compare file" in the same tab
.md5 is always provided along with file you downloaded and its size is always in kbs , if its not provided then you cant do the hash check
If you dont have "file hashes" tab after right-clicking and selecting properties of the rar/zip file then you should download and install HashTab to get that option
follow this video for a better understanding https://www.youtube.com/watch?v=Ulz-1UYzHBA
the process is same but you should use your ROM files i.e Italian N7000 files to flash your phone and yes Odin version doesnt matter, you can use any version
Hello
I downloaded N7000XXLT9_N7000ITVLT3_ITV.ZIP
Extracted the file into a folder and had N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 (there is also SS_DL.dll)
Tried to flash the md5 file with odin (V.1.85) , but odin returns a fail.....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
andrew59it said:
Hello
I downloaded N7000XXLT9_N7000ITVLT3_ITV.ZIP
Extracted the file into a folder and had N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 (there is also SS_DL.dll)
Tried to flash the md5 file with odin (V.1.85) , but odin returns a fail.....
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
did you follow the video??
did you select N7000XXLT9_N7000XXLT3_N7000ITVLT3_HOME.tar.md5 by clicking PDA??
REVENGE SOLVES EVERYTHING
Yes of course.....
andrew59it said:
Yes of course.....
Click to expand...
Click to collapse
still odin fails?? even after following the video??
are you using the original cable to flash ??
try plugging the cable into a different usb port and flash
Yes it fails
I will try with another cable and port. But if I flash Philz rom it works.....
andrew59it said:
Yes it fails
I will try with another cable and port. But if I flash Philz rom it works.....
Click to expand...
Click to collapse
after trying that try the solution from this post http://forum.xda-developers.com/showthread.php?p=41844601#post41844601
and also try and follow the thread as people have posted different solutions regarding your problem
Also this would be the extent of help i can provide
if that doesnt work i dont know what will
So please forgive me for not being able to help any further :angel:
maybe you should use odin3 v3.04 or v3.09.
usually i use odin3 v1.8X for multiple file roms but in your case, you have only One-file rom.
---------- Post added at 01:12 PM ---------- Previous post was at 01:09 PM ----------
besides, extract all the files in odin archive and place them in one folder dont just start the odin .exe file directly from the archive.
Hello changed the cable the port and ODIN (ver 3.04)
The same problem..... look at the picture attached....
I'm loosing hope.....:crying:
Thanks to all....
solved the problem!!! WOW! :good::victory:
The solution was to change pc, I went on my girlfriend laptop and everything went smooth as silk.....
Thank you all to supporting me !!
andrew59it said:
Thanks to all....
solved the problem!!! WOW! :good::victory:
The solution was to change pc, I went on my girlfriend laptop and everything went smooth as silk.....
Thank you all to supporting me !!
Click to expand...
Click to collapse
congrats
REVENGE SOLVES EVERYTHING

[Q] I9305 4.4.4 to 4.1.1 downgrade with Knox bootloader

I would be very grateful for some assistance with this, after trying many firmwares with Odin (most now blocked because of Knox bootloader), custom recovery etc. etc.
Basically I want to downgrade my I9305 from 4.4.4 to 4.1.1 so that I can use the 'trick' for SIM unlocking the device. This is after finding out that GalaxSim Unlock can't be used with this device, which I tried after rooting under 4.4.4.
I have a 4.1.1 firmware on the way which I can flash with Odin, but I'm conscious that each time I do this since upgrading to 4.3/4.4.4 the Knox bootloader comes up with 'Unsupported version'.
Is it possible for me to copy the boot.img file from the 4.4.4 firmware package and replace the boot.img file in the 4.1.1 package? Will that work? I don't really understand the ins and outs of this yet and it's getting very frustrating when I can't find any answers on Google to these specific questions.
If the above doesn't work, what option do I have to downgrade to stock 4.1.1?
Many thanks for your help.
http://forum.xda-developers.com/galaxy-s3/help-i9305/noob-help-custom-rom-unlocking-t2782118 -here you have a mini tutorial how to make it.
viktorak said:
http://forum.xda-developers.com/galaxy-s3/help-i9305/noob-help-custom-rom-unlocking-t2782118 -here you have a mini tutorial how to make it.
Click to expand...
Click to collapse
Thank you so much for this; I got excited that it might finally be a solution but alas, when I try to install the ROM in CWM recovery (6.0.4.7) I get the following message:
format() expects 5 args, got 4
E:Error in /data/media/0/stock411.zip (I renamed it and copied it again to internal phone storage in case it was a bad transfer to ext SD card previously)
(Status 7)
Installation aborted.
A quick search suggests a bad download perhaps? Will try again in 5m (when the re-download completes) but if that fails I'm back to square one.
Do you think it'd be possible to flash another stock firmware in this manner? If you flash from CWM does it never affect the bootloader/Knox? Or is this error message coming from a Knox-type block, do you think?
Thanks for your input.
Update
Late last night I somehow managed to flash a stock 4.1.1 ROM from a rather messed up 4.4.4 (following CWM recovery backup restore [apps were 'stopping' left right and centre making the phone unusable, even after wiping cache and delvik cache]). This enabled me to do the dialler trick and remove the SIM lock.
Today I've tried 3 different 4.1.2 ROMs and all fail with SW Rev. Invalid Magic String (or something similar) using Odin. After the first failed attempt I thought ok, I'll go back to 4.1.1; however when I tried this the phone got stuck on the first Samsung I9305 boot screen and, oddly, I couldn't get into recovery mode - the only option was download mode. I resolved this by flashing 4.3 (which fails with Device 3, Binary 2 or some such message. After that failure though, flashing 4.1.1 works and got my phone back to where it was before.
This is all rather confusing but I assume the 4.1.1 ROM doesn't come with recovery/boot images and requires these from a failed 4.3 flash, or something like that.
Anyway, I guess the upshot is: there's a specific 4.1.1 ROM out there for I9305 which works through Odin despite Knox bootloader being installed on your phone. It's on TSAR3000.com (I can't post links yet 'cause I'm new, but you can find it through Google if you look hard enough).
Any feedback on the above behaviour encountered during my first foray into the land of rooting, flashing and SIM unlocking that may help me/others understand what's actually going on behind the scenes would be much appreciated!
Thanks.
Clapfish said:
Late last night I somehow managed to flash a stock 4.1.1 ROM from a rather messed up 4.4.4 (following CWM recovery backup restore [apps were 'stopping' left right and centre making the phone unusable, even after wiping cache and delvik cache]). This enabled me to do the dialler trick and remove the SIM lock.
Today I've tried 3 different 4.1.2 ROMs and all fail with SW Rev. Invalid Magic String (or something similar) using Odin. After the first failed attempt I thought ok, I'll go back to 4.1.1; however when I tried this the phone got stuck on the first Samsung I9305 boot screen and, oddly, I couldn't get into recovery mode - the only option was download mode. I resolved this by flashing 4.3 (which fails with Device 3, Binary 2 or some such message. After that failure though, flashing 4.1.1 works and got my phone back to where it was before.
This is all rather confusing but I assume the 4.1.1 ROM doesn't come with recovery/boot images and requires these from a failed 4.3 flash, or something like that.
Anyway, I guess the upshot is: there's a specific 4.1.1 ROM out there for I9305 which works through Odin despite Knox bootloader being installed on your phone. It's on TSAR3000.com (I can't post links yet 'cause I'm new, but you can find it through Google if you look hard enough).
Any feedback on the above behaviour encountered during my first foray into the land of rooting, flashing and SIM unlocking that may help me/others understand what's actually going on behind the scenes would be much appreciated!
Thanks.
Click to expand...
Click to collapse
Can you tell me the country? i will download it myself
Clapfish said:
I would be very grateful for some assistance with this, after trying many firmwares with Odin (most now blocked because of Knox bootloader), custom recovery etc. etc.
Basically I want to downgrade my I9305 from 4.4.4 to 4.1.1 so that I can use the 'trick' for SIM unlocking the device. This is after finding out that GalaxSim Unlock can't be used with this device, which I tried after rooting under 4.4.4.
I have a 4.1.1 firmware on the way which I can flash with Odin, but I'm conscious that each time I do this since upgrading to 4.3/4.4.4 the Knox bootloader comes up with 'Unsupported version'.
Is it possible for me to copy the boot.img file from the 4.4.4 firmware package and replace the boot.img file in the 4.1.1 package? Will that work? I don't really understand the ins and outs of this yet and it's getting very frustrating when I can't find any answers on Google to these specific questions.
If the above doesn't work, what option do I have to downgrade to stock 4.1.1?
Many thanks for your help.
Click to expand...
Click to collapse
Downgrade is very easy. Extract that tar and then select all files except sboot.bin because sboot is the bootloader which causes downgrade fail then compress them into tar agin using 7zip then flash. First do all this with 4.1.2 firmware then you will be able to downgrade to 4.1.1☺
HELP ME !!!!!!!!
qasim799 said:
Downgrade is very easy. Extract that tar and then select all files except sboot.bin because sboot is the bootloader which causes downgrade fail then compress them into tar agin using 7zip then flash. First do all this with 4.1.2 firmware then you will be able to downgrade to 4.1.1
Click to expand...
Click to collapse
hello, sorry but I did not understand. I have a CM11 (4.4.4) You can explain me in detail the procedure? (for example with screenshot)
Thanks a lot, I'm sorry but I'm new ...:crying:
negher80 said:
hello, sorry but I did not understand. I have a CM11 (4.4.4) You can explain me in detail the procedure? (for example with screenshot)
Thanks a lot, I'm sorry but I'm new ...:crying:
Click to expand...
Click to collapse
ok
first when you download the zip fie the firmware from sammobile , extract it using 7zip you will get a tar file also extract it using 7zip you will get many files like boot.img ,syste.img,tz.img and cache.img etc. now you have to select all files except sboot.bin because this file causes problem in downgrading it is bootloader, now select all files and left click and go in 7zip option click add to acheieve then select tar and tap ok.now it will compress it into tar file flash this file with odin put your phone into download mode by holding volume down +home+poweron button you will see download mode press volume up to continue ,download odin 3.9 from google select that tar in AP option install samsung usb drivers first then connection ct with usb cable now you will see id com connected in odin click flash and wait untill it get's finished after perform factory reset.
qasim799 said:
ok
first when you download the zip fie the firmware from sammobile , extract it using 7zip you will get a tar file also extract it using 7zip you will get many files like boot.img ,syste.img,tz.img and cache.img etc. now you have to select all files except sboot.bin because this file causes problem in downgrading it is bootloader, now select all files and left click and go in 7zip option click add to acheieve then select tar and tap ok.now it will compress it into tar file flash this file with odin put your phone into download mode by holding volume down +home+poweron button you will see download mode press volume up to continue ,download odin 3.9 from google select that tar in AP option install samsung usb drivers first then connection ct with usb cable now you will see id com connected in odin click flash and wait untill it get's finished after perform factory reset.
Click to expand...
Click to collapse
Ok qasim, sorry, this Modification is Necessary on the firmware 4.1.1? thanks!
negher80 said:
Ok qasim, sorry, this Modification is Necessary on the firmware 4.1.1? thanks!
Click to expand...
Click to collapse
i have open the file of 4,4 KK firmware.(see enclosed picture).
and now??
negher80 said:
i have open the file of 4,4 KK firmware.(see enclosed picture).
and now??
Click to expand...
Click to collapse
Now select all files except sboot.bin and compress into tar file by using green + button or left click options and the flash with odin google it how to flash with odin there many detailed guides available.
And I don't know that sboot.bin is in 4.1.1 firmware you can check by extracting that tar of 4.1.1 as you done with 4.4 file if any sboot.bin is there remove it and compress all remaining fies into tar again and flash.
PERFECT!!!!!!!!!
qasim799 said:
Now select all files except sboot.bin and compress into tar file by using green + button or left click options and the flash with odin google it how to flash with odin there many detailed guides available.
And I don't know that sboot.bin is in 4.1.1 firmware you can check by extracting that tar of 4.1.1 as you done with 4.4 file if any sboot.bin is there remove it and compress all remaining fies into tar again and flash.
Click to expand...
Click to collapse
Perfect qasim!
it's alright! with your post i have downgraded my i 9305 from 4,4 to 4,1 and with another guide i have removed the simlock!
thanks a lot!!
PERFECT!!!!!
qasim799 said:
Now select all files except sboot.bin and compress into tar file by using green + button or left click options and the flash with odin google it how to flash with odin there many detailed guides available.
And I don't know that sboot.bin is in 4.1.1 firmware you can check by extracting that tar of 4.1.1 as you done with 4.4 file if any sboot.bin is there remove it and compress all remaining fies into tar again and flash.
Click to expand...
Click to collapse
Perfect qasim!
i have used your guide for downgrade from 4.4.4 to 4.1.1.
after, i have removed the sim lock ( tutorial from youtube) and finally, i have mounted the 4,4,4 kitkat without the sim lock!
thanks a lot for your help!
:good:
hello mates, can you upload the rom that you sucessfully flashed to 4.1.1? thanks
Please Help me i have I9305 4.4.4 i want to downgrade also
Please Help me i have I9305 4.4.4 i want to downgrade and i have 4.1.2 firmware over here and i also do that procedure you said but im stuck at nand write start. any help please
Unable to downgrade from 4.4.4
Tried to follow the tutorial but failed.
I have an I9305 with KitKat 4.4.4 that I would like to downgrade to do the Sim unlock trick.
I downloaded I9305XXUENH1_I9305EVRENH1_EVR.zip from Sam Mobile (thats 4.3 for the I9305)
I extracted the files removed sboot.bin and compressed the files to I9305XXUENH1_I9305EVRENH1_I9305XXUENG1_HOME.tar
I then flashed that file with odin but got the following:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have now flashed 4.4.4 and the phone is working again.
Anybody help?
Clapfish said:
I would be very grateful for some assistance with this, after trying many firmwares with Odin (most now blocked because of Knox bootloader), custom recovery etc. etc.
Basically I want to downgrade my I9305 from 4.4.4 to 4.1.1 so that I can use the 'trick' for SIM unlocking the device. This is after finding out that GalaxSim Unlock can't be used with this device, which I tried after rooting under 4.4.4.
I have a 4.1.1 firmware on the way which I can flash with Odin, but I'm conscious that each time I do this since upgrading to 4.3/4.4.4 the Knox bootloader comes up with 'Unsupported version'.
Is it possible for me to copy the boot.img file from the 4.4.4 firmware package and replace the boot.img file in the 4.1.1 package? Will that work? I don't really understand the ins and outs of this yet and it's getting very frustrating when I can't find any answers on Google to these specific questions.
If the above doesn't work, what option do I have to downgrade to stock 4.1.1?
Many thanks for your help.
Click to expand...
Click to collapse
Delete sboot and flash by odin
Use this thread to delete sboot
http://forum.xda-developers.com/android/general/how-to-create-tar-to-md5-tar-t3204511#post63427287
thanks, great job !
Thank you very much for your help installing custom 4.1.1. from 4.4.4. and then sim unlock !!!!!
The method works very fine for official 4.4.4 i9305 phone !
Thanks a lot to spanish guys, I used their 4.1.1. custom rom.
I struggled long time with this sim unlock problem as I was with UK EE network.
Now my phone is free !
Stuck at Samsung logo after flashing 4.1.1 on
I cant get past the samsung logo after flashing the following file:
Product Code: GT-I9305TADEVR (4.1.2) (EE UK)
PDA: XXBMD5
PHONE: XXBMD5
CSC: EVRBLL2
Link: Download (Dev-Host)
Click to expand...
Click to collapse
found on this thread by lyriquidperfection following qasim's suggestion to remove sboot.bin on top of I9305XXUFNI3_I9305DBTFNI3_DBT.zip which is a 4.4.4 stock rom. I have unzipped the tar file, removed sboot.bin, rezipped with 7zip as tar, then used ihsas's script to convert that to tar.md5 and flashed with odin, and stuck at the white logo screen. What is wrong here i am doing? I also need to unlock my carrier
JFV93 said:
hello mates, can you upload the rom that you sucessfully flashed to 4.1.1? thanks
Click to expand...
Click to collapse
You'll find it on sammobilehttp://www.sammobile.com/firmwares/database/GT-I9305/EVR/

Successfully Unlocked FRP of my SM-T377W from Rogers Canada on 7.1.1

I have successfully Unlocked my SM-T377W from Rogers Canada on 7.1.1
I have been Struggling for a while to Unlock the FRP from this device and finally done it
Now its unlocked and I can use whatever sim card i want also
So I have used these 2 files [IT IS IMPORTANT TO USE THE CORRECT COMBINATION AND CORRESPONDING STOCK], maybe you can use the same ones I have used if you do not have a choice
1- Combination "COMBINATION_OYA_FA60_T377WVLU3ARG1"
2- Stock ROM "Firmware SM-T377W T377WVLU3BRG4 [7.1.1]"
So what I have basically done,
1- Turn the device off and put the device in DOWNLOAD MODE
2- Flash the Combination Firmware to your device with Odin
3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
4- Turn it on again normally and it will run the Combination firmware
5- Now Turn it off again and put in "DOWNLOAD MODE" this time
6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
10- Your done
Step number 7 where I was struggling before, did not know which files to extract and to flash, but after search/attempts finally I figured it out.
Hope this help
Combination file download
Thank you for giving me hope that I might still get this tablet in usable condition again. I have been looking high and low and tried so many ways to get passed the frp. I've been searching since you sent me your thread but couldnt find a combination file download anywhere that didnt seem suspicious. I have aquired a lot of other tools for later trials but the combination file is still alluding me. Im sure you looked a long time and I know it must be gratifying to have finally gotten yours working. Dont suppose you can share the site you got the file from? Great job btw and a huge thanks for sharing your success as well as inspiration to keep going!
:good::good::good::fingers-crossed::good::good::good:
DaOnlyHihiNalu said:
Thank you for giving me hope that I might still get this tablet in usable condition again. I have been looking high and low and tried so many ways to get passed the frp. I've been searching since you sent me your thread but couldnt find a combination file download anywhere that didnt seem suspicious. I have aquired a lot of other tools for later trials but the combination file is still alluding me. Im sure you looked a long time and I know it must be gratifying to have finally gotten yours working. Dont suppose you can share the site you got the file from? Great job btw and a huge thanks for sharing your success as well as inspiration to keep going!
:good::good::good::fingers-crossed::good::good::good:
Click to expand...
Click to collapse
Combination from here, you will see link down for T377WVLU3ARG1
(Good luck downloading from the site as there are so many Ads, but this is the link i got it from)
Stock Here
(stock easy to find, there are many sites)
Good luck , hopefully it will work
steps above dont seem too work....
are you sure only the 3 files are required in the new .tar?
I can get to step 9 above, but when I try to flash my new .tar file, I get a failed write error right after it tries to write the boot.img file, which is the first file it tries to wrtite.
At this point, I tried just flashing the original 4 files instead, bearing in mind I have already done steps 1-6 successfully, and when the device boots, it is still FRP locked.....
Issue is my ex gfs gmail was the one logged in on my device, i reset before thinking about FRP and now I cant use my device.... Samsung Service Center wants almosts $100 to fx and id rather do it myself because thats crazy considering it should take only 10min if the real process is anything close to this or just uses odin at all.
SpectorOfDeath said:
steps above dont seem too work....
are you sure only the 3 files are required in the new .tar?
I can get to step 9 above, but when I try to flash my new .tar file, I get a failed write error right after it tries to write the boot.img file, which is the first file it tries to wrtite.
At this point, I tried just flashing the original 4 files instead, bearing in mind I have already done steps 1-6 successfully, and when the device boots, it is still FRP locked.....
Issue is my ex gfs gmail was the one logged in on my device, i reset before thinking about FRP and now I cant use my device.... Samsung Service Center wants almosts $100 to fx and id rather do it myself because thats crazy considering it should take only 10min if the real process is anything close to this or just uses odin at all.
Click to expand...
Click to collapse
Then make sure u r using the correct firmware and combination, because if u r not using matched once u will get error
i know the firmware is correct, but how do I know which combination file to use? there is no description of the difference between them or what each is for.....
I have the exact same device as you, just on Bell... I have the 4 full flashing files, bl ap cp csc, and they work fine but dont remove FRP, but they flash and load without issue.... I even have the .pit file just incase, but am not using it as of yet.....
Ive been using the combination fole you noted above, but should I use the other one then? any idea why it would work for you and not me, carrier shouldnt matter in canada now because they are all unlocked anyways
---------- Post added at 08:34 PM ---------- Previous post was at 08:32 PM ----------
do i need to add the param.bin file too ?
---------- Post added at 08:52 PM ---------- Previous post was at 08:34 PM ----------
i just tried the other combination file, and it wont flash like the first one, i gets errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 959 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the tablet itself i get the error;
SW REV CHECK FAIL. DEVICE: 3 BINARY: 2
---------- Post added at 09:03 PM ---------- Previous post was at 08:52 PM ----------
maybe this could be it??
I just flash the combination files that you referenced that does flash and boot correctly, and when I get into recovery and do the factory reset in there, I noticed somthing....
this combination file says
Android Recovery
MMB29K.FA60_T337WVLU3ARG1
samsung/gtesltebmc/gtesltebmc
6.0.1/MMB29K/FA60_T337WVLU3ARG1 <<<<----------could this be it?
user/release-keys
I see it says 6.0.1, and im trying to flash 7.1.1 stock afterwards... is that the issue? i need to flash 6.0.1 instead maybe? where can I get the 6.0.1 files as they are not n sammbile firmware
---------- Post added at 09:33 PM ---------- Previous post was at 09:03 PM ----------
no that cant be it, you sad in the begining of the post you used 7.1.1....
so yea, im lost now; I can unpack the BL and AP files and get the 3 files you said together and repack them into a NEW_T337W.tar file with 7zip,
but then i get the get write error in odin when trying to write boot.img and no error shown on tablet
OM*******G --- I GOT THIS TOO WORK FINALLY
just had to take some steps back and think a few things over and try a few things...
I had to alter your instructions abit, but not much, you were bang on for the most part for me....
So what I have done is below, minus the underlined parts, took them out....
---> Good 1- Turn the device off and put the device in DOWNLOAD MODE
---> Good 2- Flash the Combination Firmware to your device with Odin
---> Changed 3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
---> Changed 4- Turn it on again normally and it will run the Combination firmware
---> Good 5- Now Turn it off again and put in "DOWNLOAD MODE" this time
---> ADDED 5.5- RESTART ODIN, not just click restart within Odin, but close and reopen, would not flash the new .tar I make next unless I both skip the factory reset underlinded above && Completely close and reopen Odin
---> Good 6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
---> Good 7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
---> ADDED 6.5- Make sure Odin has been completed closed and reopened
---> Good 9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
---> Good 10- Your done
Not sure why I had to skip the factory reset as well as restart Odin, I can understand Odin because its a portable version we all use, not system installed, so issues somtimes....
But the factory reset skip was just a tought, that possibly it wouldnt allow me to flash after a factory reset without booting the OS atleast once, and it eneded up being the clintcher for me....
Now there is only one thing I will say about this way to get around FRP, is that you cant preform a factory reset for within the device afterwards, as it re-locks to the old google account again, which means it technically hasnt REMOVED the existing lock, just somehow ignoring the flag. I know this because immediately after I got my .tar to flash and the OS was running and not locked up, I logged into the Play Store and updated play services, and then shut down and I preformed a hard reset within the recovery, just to completely reset the OS one final time and too see what would happen, and it did reformat fine and boot, but was back in its original state, locked to my ex-gfs account, not mine.
SOo I was forced to go thru my steps above again and get back in... worked fine, and I just finshed updateing all my google apps that needed updating in the playstore and seems like everythign is fine, only comes down to not being too factory reset now if I have an issue in the future......
Also brings up my next concern, will I be able to to any future system OTA updates?
I'm not rooted nor do I have any need to be on this device, my LG v30 is rooted already with TWRP, so I havnt broken Knox as far as I know, counter in Download mode is still 0, so Im PRAYING I can do any updates such as those without getting locked out again afterwards....
What I'm hoping, is that over time, what ever 30-90 days, of updates and syncs, that the FRP lock will change to MY google account, not hers, but I have no idea if it will and that only way I can check is to try it in like April, plenty of time and syncing, and see if locks up and I need to do this all over again.
Yea, i was right, OTA updates are broken even with knox at 0x0...
Any idea how long it takes to attach this device to my account over hers?
When/if that happen, you think its better to flash the OS in full back from Odin or just do internal Factory Reset? Wondering if flashing the OS after 72hrs would be more successful in ignoring the old info and grabbing my account since the old info obv hasnt been removed from the device, just ignored by the Combined Firmware Binary
Update: i confirmed this by logging out of all my accounts, samsung google ect, everything and entering Download Mode, should have shown FRP LOCK: OFF but said : ON, which means the device has FRP information still even tho no accounts are logged in and should have released this.
Everything worked as described. If you are finding it difficult to extract and pack the 3 other firmware files, you can opt yo use free tools like Miracle box to load the firmware and then flash only the files you want(sboot, boot, system).
For the link, just indicate and i send it directly to you or visit ifindhub for free Miracle box software.
Patched odin
SpectorOfDeath said:
steps above dont seem too work....
are you sure only the 3 files are required in the new .tar?
I can get to step 9 above, but when I try to flash my new .tar file, I get a failed write error right after it tries to write the boot.img file, which is the first file it tries to wrtite.
At this point, I tried just flashing the original 4 files instead, bearing in mind I have already done steps 1-6 successfully, and when the device boots, it is still FRP locked.....
Issue is my ex gfs gmail was the one logged in on my device, i reset before thinking about FRP and now I cant use my device.... Samsung Service Center wants almosts $100 to fx and id rather do it myself because thats crazy considering it should take only 10min if the real process is anything close to this or just uses odin at all.
Click to expand...
Click to collapse
You may have to use a patched version of Odin, I had issues with this on my Galaxy s9 plus
SpectorOfDeath said:
OM*******G --- I GOT THIS TOO WORK FINALLY
just had to take some steps back and think a few things over and try a few things...
I had to alter your instructions abit, but not much, you were bang on for the most part for me....
So what I have done is below, minus the underlined parts, took them out....
---> Good 1- Turn the device off and put the device in DOWNLOAD MODE
---> Good 2- Flash the Combination Firmware to your device with Odin
---> Changed 3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
---> Changed 4- Turn it on again normally and it will run the Combination firmware
---> Good 5- Now Turn it off again and put in "DOWNLOAD MODE" this time
---> ADDED 5.5- RESTART ODIN, not just click restart within Odin, but close and reopen, would not flash the new .tar I make next unless I both skip the factory reset underlinded above && Completely close and reopen Odin
---> Good 6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
---> Good 7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
---> ADDED 6.5- Make sure Odin has been completed closed and reopened
---> Good 9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
---> Good 10- Your done
Not sure why I had to skip the factory reset as well as restart Odin, I can understand Odin because its a portable version we all use, not system installed, so issues somtimes....
But the factory reset skip was just a tought, that possibly it wouldnt allow me to flash after a factory reset without booting the OS atleast once, and it eneded up being the clintcher for me....
Now there is only one thing I will say about this way to get around FRP, is that you cant preform a factory reset for within the device afterwards, as it re-locks to the old google account again, which means it technically hasnt REMOVED the existing lock, just somehow ignoring the flag. I know this because immediately after I got my .tar to flash and the OS was running and not locked up, I logged into the Play Store and updated play services, and then shut down and I preformed a hard reset within the recovery, just to completely reset the OS one final time and too see what would happen, and it did reformat fine and boot, but was back in its original state, locked to my ex-gfs account, not mine.
SOo I was forced to go thru my steps above again and get back in... worked fine, and I just finshed updateing all my google apps that needed updating in the playstore and seems like everythign is fine, only comes down to not being too factory reset now if I have an issue in the future......
Also brings up my next concern, will I be able to to any future system OTA updates?
I'm not rooted nor do I have any need to be on this device, my LG v30 is rooted already with TWRP, so I havnt broken Knox as far as I know, counter in Download mode is still 0, so Im PRAYING I can do any updates such as those without getting locked out again afterwards....
What I'm hoping, is that over time, what ever 30-90 days, of updates and syncs, that the FRP lock will change to MY google account, not hers, but I have no idea if it will and that only way I can check is to try it in like April, plenty of time and syncing, and see if locks up and I need to do this all over again.
Click to expand...
Click to collapse
So the file COMBINATION_SPT_FA51_T377PVPU2AQD1_SPTFAC_xxxxxxxxx.tar has these inside it:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
hyp.mbn
NON-HLOS.bin
sec.dat
boot.img
recovery.img
system.img.ext4
persist.img.ext4
carrier.img.ext4
persdata.img.ext4
modem.bin
GTESQLTE_USA_SPR.pit
cache.img.ext4
Click to expand...
Click to collapse
///
Is aboot the other file we ned? Which file is the sboot? Also when I try to just flash that combo tar i get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 786 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I also found these three ROMs none of which work?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
msaithan said:
I have successfully Unlocked my SM-T377W from Rogers Canada on 7.1.1
I have been Struggling for a while to Unlock the FRP from this device and finally done it
Now its unlocked and I can use whatever sim card i want also
So I have used these 2 files [IT IS IMPORTANT TO USE THE CORRECT COMBINATION AND CORRESPONDING STOCK], maybe you can use the same ones I have used if you do not have a choice
1- Combination "COMBINATION_OYA_FA60_T377WVLU3ARG1"
2- Stock ROM "Firmware SM-T377W T377WVLU3BRG4 [7.1.1]"
So what I have basically done,
1- Turn the device off and put the device in DOWNLOAD MODE
2- Flash the Combination Firmware to your device with Odin
3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
4- Turn it on again normally and it will run the Combination firmware
5- Now Turn it off again and put in "DOWNLOAD MODE" this time
6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
10- Your done
Step number 7 where I was struggling before, did not know which files to extract and to flash, but after search/attempts finally I figured it out.
Hope this help
Click to expand...
Click to collapse
worked on my uncles sm-t377w that I stupidly told him to factory reset and that stupidly even though done through the settings menu, it decides it wasn't done properly and promptly triggered the FRP and the sim card in the device was no longer active and he is a super genius, so he didn't know what a google account was, what his email address is, what his email password was... poor guy is dying of cancer and just wanted to play games on his tablet but it was giving ANR messages repeatedly. Must remember in the future to remove google accounts before ever factory resetting a tablet, even if done the proper way. So stupid, I could understand if done from the recovery menu, but from the settings menu while logged in and using a screen lock that he at least knew that password for., that should never trigger FRP.
Thanks for helping me help a dying man.
SpectorOfDeath said:
OM*******G --- I GOT THIS TOO WORK FINALLY
just had to take some steps back and think a few things over and try a few things...
I had to alter your instructions abit, but not much, you were bang on for the most part for me....
So what I have done is below, minus the underlined parts, took them out....
---> Good 1- Turn the device off and put the device in DOWNLOAD MODE
---> Good 2- Flash the Combination Firmware to your device with Odin
---> Changed 3- When the device restarts and it runs the Combination firmware, turn it off again and put it in "RECOVERY MODE" not download, and in "RECOVERY MODE" do factory reset wipe and click yes then It will restart or maybe shut off
---> Changed 4- Turn it on again normally and it will run the Combination firmware
---> Good 5- Now Turn it off again and put in "DOWNLOAD MODE" this time
---> ADDED 5.5- RESTART ODIN, not just click restart within Odin, but close and reopen, would not flash the new .tar I make next unless I both skip the factory reset underlinded above && Completely close and reopen Odin
---> Good 6- From the Stock ROM extract the 3 files (boot, sboot and system) from inside the files of the stock ROM, you will find them inside "AP" and "BL" (cause we have BL, AP, CP, CSC), you need to use 7-zip so you can extract whats inside them
---> Good 7- Create new file/archive (it will be .tar) using 7-zip with these 3 files (boot, sboot and system)
---> ADDED 6.5- Make sure Odin has been completed closed and reopened
---> Good 9- Flash the new file you made .tar (that has the 3 files) in the AP section in Odin.
---> Good 10- Your done
Not sure why I had to skip the factory reset as well as restart Odin, I can understand Odin because its a portable version we all use, not system installed, so issues somtimes....
But the factory reset skip was just a tought, that possibly it wouldnt allow me to flash after a factory reset without booting the OS atleast once, and it eneded up being the clintcher for me....
Now there is only one thing I will say about this way to get around FRP, is that you cant preform a factory reset for within the device afterwards, as it re-locks to the old google account again, which means it technically hasnt REMOVED the existing lock, just somehow ignoring the flag. I know this because immediately after I got my .tar to flash and the OS was running and not locked up, I logged into the Play Store and updated play services, and then shut down and I preformed a hard reset within the recovery, just to completely reset the OS one final time and too see what would happen, and it did reformat fine and boot, but was back in its original state, locked to my ex-gfs account, not mine.
SOo I was forced to go thru my steps above again and get back in... worked fine, and I just finshed updateing all my google apps that needed updating in the playstore and seems like everythign is fine, only comes down to not being too factory reset now if I have an issue in the future......
Also brings up my next concern, will I be able to to any future system OTA updates?
I'm not rooted nor do I have any need to be on this device, my LG v30 is rooted already with TWRP, so I havnt broken Knox as far as I know, counter in Download mode is still 0, so Im PRAYING I can do any updates such as those without getting locked out again afterwards....
What I'm hoping, is that over time, what ever 30-90 days, of updates and syncs, that the FRP lock will change to MY google account, not hers, but I have no idea if it will and that only way I can check is to try it in like April, plenty of time and syncing, and see if locks up and I need to do this all over again.
Click to expand...
Click to collapse
I get an error when trying to flash the 3 files. Now I'm stuck with a tablet with Factory Binary on it...Help plz...
onetimepostmaster said:
I get an error when trying to flash the 3 files. Now I'm stuck with a tablet with Factory Binary on it...Help plz...
Click to expand...
Click to collapse
Download same binary version firmware for your device then flash it using z3x 29.5
hi guys trying to do this on grandsons tablet but i get md5 error binary is invalid no mater what combo firmware i use.
ok so i got the combo file to load and flash, after this i got a screen saying factory binary, i waited but would not load past so i did the fatory recovery part and then went to do the next step but now download recover will not work and power button also soes not work . what can i do now.

Categories

Resources