Related
Hello everyone, before I start, I want to let everyone know I have searched endlessly for a fix, etc.
I have a SideKick 4G that I purchased maybe a month ago, and yesterday I went ahead and tried to flash a custom ROM on it. Now my issue is, I was hap-hazardly strolling through the menus and doing the procedure so I didn't back anything up or check the mounts etc.
My issue is, I have Odin and the sk4g.pit file, but I can't find the KD1OdinSTOCK.tar or KG2OdinSTOCK.tar files, because the file hosts are down... permanently.
I also do not know if I have the KD1 or KG2 firmware, what the difference is, and if any problems could be caused by flashing one or the other onto my device. I'm pretty new to the whole process and I was only looking to make my phone faster and less clunky.
If I get the files, a quick walk-through for my specific situation would be very highly appreciated.
Thanks in advance!
EDIT: I found a newer firmware for the SideKick 4G, called KH1, Not KD1, KG2, or KJ1.
To get the file:
1) Go to SamFirmWare.com and make an account
2) Search T839UVKH1
3) Make sure you find the firmware for this model. "SGH-T839"
4) Download it
5) Make sure to look for what password you'll need to open the file (This one is marked with "##")
6) Input password when extracting the file to wherever you want to put it (The password for this one is samfirmware.com)
That should be it.
My issue now is that Odin isn't recognizing my device. It's in download mode and I have the factory cable but I must be doing something wrong as I can set the PIT file and the PDA file, tick boxes etc. but I can not for the life of me get my device detected.
Alright, later update.
I got Odin to recognize my phone, and now I'm trying to flash it.
I don't seem to be having any negative impact with my firmware (KH1) and sk4g.pit, however it always fails at write boot.sbl OR, it gets stuck at Set PIT file.
My phone changed from the Downloading... mode to the Phone - ! - PC picture, however, I was told I can still flash from this mode. I've been continuing to flash with different settings in hopes of reaching recovery, and so far what has NOT worked:
Auto Reboot
Auto Reboot + Re-Partition
Auto Reboot + Re-Partition + F. Reset Time
I don't believe I've tried Auto Reboot + F. Reset Time without Re-Partition, or Re-Partition with F. Reset Time.
Any advice or comments?
Update #2.
http://forum.xda-developers.com/showthread.php?t=1350060&page=6
This thread seems to have a link to a oneclick stock recovery as well as KG2 firmware, judging by the 254 MB download (THAT WORKS BY THE WAY.)
Hopefully after I download this, I can get the phone running. Will post later to inform a yay or nay.
Edit: I almost successfully flashed to stock KG2 Firmware. All went well (Kernal, Recovery, etc) Except it failed at the modem.
It rebooted after failing modem and now I'm stuck at sidekick boot logo. It's better than having Phone - ! - PC though.
EDIT 2: Seems that it keeps failing at Modem, part 3 of 6. along with that, it does restore the phone to Download mode rather then the broken sync picture. Odin now does not recognize the phone, but I think that's due to the other drivers the oneclick method prompted me to install. I'm going to try to disable those drivers temporarily and see what odin thinks about it.
Update #3.
I discovered the drivers downloaded to run the oneclick as provided by the link in the previous update did infact block connection to odin with the same device.
Uninstalling the driver got the connection going again. Every time in Odin, I fail at writing either boot.sbl or cache.rfs.
I took the files from the KG2 firmware and compiled my own .tar out of them and when I flashed using my compiled tar, that's when I got the cache.rfs write error. Phone has shown no signs of improving or deteriorating. I can go back to oneclick recovery and get the phone out of broken sync picture mode, and back into Download mode. However, here are my 2 issues flashing.
In Odin:
I either have no connection, or
I can't write boot.sbl or cache.rfs and fail.
In Heimdall One-Click KG2:
I need the driver Odin doesn't like, and
I flash almost all the way through, but fail halfway through uploading MODEM.bin.
It's giving me the opportunity to flash Boot Loaders along with KG2 kernal, recovery, modem, etc. It's the only thing I haven't tried yet.
Update #4.
I'm about to flash bootloaders. Wish me luck
EDIT: I'm about to cry :') I THINK IT WORKED. I'm loading boot screen.. got animation and now got samsung screen, waiting for the phone to boot. got a fully successful oneclick and it's looking well at the moment
YEAH!!!!!!!!!!!!!!!!!!!! HOME SCREEN!!!!!
Nice monologue.
Thank you sir. What do you think of the things I did to get my phone working again? Anything you think I shouldn't have done? o_o''
Is there anyway to get out of this. It only shows the Samsung Galaxy Tab Logo, I can also get into recovery. I tried to wipe everything to see if it would boot up, but its still stuck on the startup screen. Any help would be much appreciated!!
kaizasoshi said:
Is there anyway to get out of this. It only shows the Samsung Galaxy Tab Logo, I can also get into recovery. I tried to wipe everything to see if it would boot up, but its still stuck on the startup screen. Any help would be much appreciated!!
Click to expand...
Click to collapse
this is very easy to fix fortunately you have not hard bricked LOL now follow my steps....
step1. download your required firmware package from the development section.
step2. download the odinv1.8 and then unzip and install to desktop
step3. open odin and select PDA and load the unzipped firmware file. (do not touch anything else at all)
step4. power on the device with volume button down and power on (download mode)
step5. plug in to pc via USB 2.0 as this has less chance of failing then press start on odin it will push the firmware on to the device and them reboot
step6. sit back and enjoy lol.
thank me if it helps.
jmar8124 said:
this is very easy to fix fortunately you have not hard bricked LOL now follow my steps....
step1. download your required firmware package from the development section.
step2. download the odinv1.8 and then unzip and install to desktop
step3. open odin and select PDA and load the unzipped firmware file. (do not touch anything else at all)
step4. power on the device with volume button down and power on (download mode)
step5. plug in to pc via USB 2.0 as this has less chance of failing then press start on odin it will push the firmware on to the device and them reboot
step6. sit back and enjoy lol.
thank me if it helps.
Click to expand...
Click to collapse
Thanks Bro, will try this when I get home from church
Do you know where I can find the tmobile firmware file I need?
There you have it :
www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
P_
pakalrtb said:
There you have it :
www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
P_
Click to expand...
Click to collapse
Thanks Bro!! It worked!!
soft brick galaxy tab 7.0 plus
I have the same problem as described by kaizasoshi on a GT-P6210 (WIFI only model) and can get to download mode. I haven't been able to find a copy of Odin 1.8 to download so I have Odin 4.0.3 - hopefully that'll work. The megaupload link for Odin 1.8 gives you software Odin 1.8.2 which turns out to be some sort of MRI operating software.
I used the link provided in the response for the GT-P6200 model, did a search, and I can't find the firmware file for the P6210 anywhere on the site. I found a file elsewhere on XDA supposedly is the firmware file for my model P6210 and when adding to PDA I get an error "Invalid Image File Type" The file name that I found is named GT-P6210_XAR_P6210UEKL1_P6210XARKL1_P6210UEKL1\P6210XARKL1_P6210UEKL1_HOME.tar.md5
Does this sound right? Does anyone have any guidance for me (besides stop bricking my Tab)? Thanks
soft brick galaxy tab 7.0 plus - continued
Well I found a version of Odin 1.8 and it took the tar file without an error message. I started flashing the file to my P6210 and it went well for a couple of minutes (about half a green bar in the first block). Then something went wrong and ODIN started alternating the below messages:
<ID:0/004>Added!!
<ID:0/004>Removed!!
<ID:0/004>Added!!
<ID:0/004>Removed!!
And while showing the above, the P6210 screen started alternating between a black screen and the below message:
Firmware upgrade encountered an issue.
Please select recovery mode in Kies & try again.
I watched this continue for over an hour in this loop (no progress on the green bar), then disconnected and reconnected the P6210. I launched Kies and tried troubleshooting but just got the alternating screen again on the P6210 and starts and stops of Kies troubleshooting. It looks like it's pretty hosed. Any suggestions?
Help would be greatly appreciated.
As an aside, the only thing I've done to the tablet was do a one step root about 3 months ago and I think two product updates afterwards (reapplied the root after each). The tablet ran OK but I started getting the auto shutdowns other have gotten, along with several instances of a warm battery and high battery rates of consumption. It didn't behave this way all the time. Finally two days ago, while on the charge,r I found it locked into the Tab startup screen. I could get it to boot into recovery but kept getting lots of red error messages, like it was looking for files that weren't there, then I'd reboot and it would go back to the locked startup screen.
Can you get into recovery by holding up and power on (release power after it boots, but hold volume up)
Sent from my HTC Glacier using Tapatalk
Yes I can get to recovery now. Since my previous post, I recharged unit overnight and attempted to reflash OS. This time, Odin runs all the way until the first green box says PASS! Odin Message box says <OSM> All threads completed (succeed 1/failed 0). Then message box cycles thru ID 0/004 Removed ID 0/005 added!! then ID 0/005 Removed!!, then ID 0/005 Added!!
At this point Odin doesn't do anything else. The P6210 then starts giving a bunch of failed messages - failed to mount cache(no such file or directory), Can't mount /cache/recovery/command, then goes into Manual Mode then message failed to mount /efs (no such file or directory) install application for customer: Can't mount /efs copy application failed. Then meesage Applying multi CSC then failed to mount /efs, then multi_csc can't mount/efs
Then multi-csc applied failed.then more messages on failing to mount cache can't mount cache recovery log/last log
Then at this point the top of the screen offers rebot/apply update from sd/wipe data-factory reset/wipe cache partition. Through all of this I have not unplugged the P6210 from the PC.
I select reboot system now and press power button (still connected)
Get a bunch more messages about cant open cache recovery log. Then it goes to the Samsung Galaxy tab screen and just hangs.
It seems there's some files missing that is causing the unit to hang.
added/removed sounds like could be faulty wire connection.
which firmware are you trying to flash may we ask?
May be useful to find a .pit file with stock firmware, if there are any around for your device.
kaizasoshi said:
Thanks Bro, will try this when I get home from church
Click to expand...
Click to collapse
no probs my friend happy to help haha
soft brick galaxy tab 7.0 plus - continued
I've also tried changing the usb/samsung cable from aftermarket to OEM and changing USB port used on PC. Reflashed PDA file, No change. The reflash appears to complete but is followed by the error messages identified previously. The file I'm attempting to flash w/Odin 1.85 is named P6210XARKL1_P6210UEKL1_HOME.tar.md5. The file is 894.011 MB. I've downloaded it twice and no difference in flash result. I'm not having any luck finding a PIT file for the P6210.
Still looking for PIT file.
kaizasoshi said:
Is there anyway to get out of this. It only shows the Samsung Galaxy Tab Logo, I can also get into recovery. I tried to wipe everything to see if it would boot up, but its still stuck on the startup screen. Any help would be much appreciated!!
Click to expand...
Click to collapse
May I ask what you did to soft brick? Be good learning experience for everyone. Thanks.
soft brick galaxy tab 7.0 plus - continued
I've also found these 3 other files associated with the P6210. They are:
GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5
P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5
P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5
Would loading these files via Odin possibly help with my problem? I'm not sure which files would be loaded for the different parameters (PIT, BOOTLOADER, etc). It appears the CSC file would be loaded for CSC.
PS: I don't know what happened with kaizasoshi as far as how his TAB problem initiated, but mine had been experiencing SOD, auto shutdowns and warm battery when plugged into charger over night for the previous several weeks. I picked it up one morning off the charger and the P6210 was frozen on the startup screen and wouldn't finish boot or shut down. It would go into recovery using the power and volume switches.
hi all, i have the same similar problem as TS but mine's a P6200 tab, heard that i need a pit file & the firmware ver(singapore) to flash it...
where do i get those files including odin? i got the firmware via sammobile.com, but no idea to get the pit & odin files,... will any kind souls direct me to them?
I found a PIT file a few days ago, supposedly for the P6200 using Google. I don't know if it works or not. I have a P6210, so I don't think I can use a P6200 PIT.
PIT Link:
http://www.sammobile.com/forum/showthread.php?t=2856
ODIN Link:
http://www.cpkb.org/wiki/Samsung_Odin#Samsung_Odin3_download_links
Pick a version. 1.81 and 1.85 seem popular.
any new updates on this? im having the exact same problem and have tried all the previously mentioned files through Odin with no positive results. any help would be appreciated. i have a US version 6210
yeah.. dont flash a tab plus firmware unless you're sure its for your specific model
either T869-Tmobile/WifiGT-P6210/or G version GT-P6200. If youve flashed the previously mention files, you've probably done some serious damage.
Best option now: Find a device specific firmware WITH a .pit file, flash with Odin/Heimdall with fngers crossed.
Other options: tell them you hooked it up to iTunes to sync your media.. lololol
hope you get warrantied..
chrisrotolo said:
yeah.. dont flash a tab plus firmware unless you're sure its for your specific model
either T869-Tmobile/WifiGT-P6210/or G version GT-P6200. If youve flashed the previously mention files, you've probably done some serious damage.
Best option now: Find a device specific firmware WITH a .pit file, flash with Odin/Heimdall with fngers crossed.
Other options: tell them you hooked it up to iTunes to sync your media.. lololol
hope you get warrantied..
Click to expand...
Click to collapse
well that just sucks!! honestly with all the SODs and reboots i just wish samsung would give me my $350 because this thing hasnt worked well from the begining. guess its back to samsung
I need a bit of help, I bought a SGS2 GT-i9100M, with Bell, I'm in Canada, that was displaying 'Firmware encountered an issue' error message thinking it would be an easy fix. I have tried a few things to fix it (and done a ton of reading, currently have 8 threads open) but no luck so far and I have to ask for help. I bought this phone knowing it had issues, was told it wasn't modded, however when I charged it and booted into download mode it showed Custom Binary Download:YES (12 Counts) and Current Binary: Custom, it still shows 12 but Current Binary is now Samsung Official.
The phone will boot into download mode but not into recovery mode, I have tried flashing various roms from gingerbread to jellybean, used ODEN3 v1.83, 1.84, 1,85, and 3.07, tried different usb ports, uninstalled kies entirely, reinstalled samsung drivers, nothing. I came across GT-I9100_ClockworkMod-Recovery_4.0.0.2 from Zubair Ikram and that worked, it was the first thing to pass, but didn't reboot the phone to the startup screen when finished as it did in his video, instead the same error message was displayed. After each rom failed I turned the phone off, took out the battery, boot back into dl mode and try something else. Have tried csc, phone, pda from "SGS2 Canadian Thread (Bell/Virgin/Sasktel/Rogers) Root/Unlock/Firmware/Modems/Mods", same as others, however, when using v1.85 the csc .tar makes it almost halfway through the green bar before freezing (I let these sit for ~1hour each time, unless they say 'fail', once left it for 8 hours, no change).
Each time it seems to hang just after NAND Write Start, which from various threads seems to point to a bad partition. After reading all the warnings not to Re-partition, I tried it but it also failed. Tried u1_02_20120326_emmc_EXT4_8GB.pit as well, failed, have followed exactly, step by step, at least 15 recovery threads (probably more), and now not sure what to try.
I got a number for a local phone repair tech, explained the problem and was told it sounds like a bad partition, or bad efs, and should be easily fixable. Looking for suggestions on what to try next? I have tried to fix this myself, I have 130 threads just from this forum in my history from yesterday alone, I think the next step will be to try to manually repair the damaged blocks (read this in a thread) but wanted to hit you guys up for suggestions first. If there's anything I have been unclear about, or you'd like to know specifics about what roms I've tried, or have any other questions please let me know.
Thanks in advance for your time,
Chris.
EDIT:
Had a friend offer some advice, here's a bit more detail on what I tried.
Reply to the first email- I'm not sure what operating system is currently installed, can't see what it is from the download mode, says custom binary download: currently 14, started out at 12 when I got the phone, and current binary: custom, I flashed with the GB kernel and got it to say current binary: samsung original, then flashed it back to custom.
I tried recovery with kies, then tried with oden shutting down all running applications of kies in task manager, then uninstalled kies entirely, restarted and tried again.
Tried flashing stock firmware with oden, tried flashing custom roms with oden, tried uninstalling drivers, reinstalling them, installing drivers from my working phone, installing custom drivers for i9100m specific, tried multiple usb ports, tried all roms with v1.83, 1.84, 1.85, 3.04 and 3.07 of oden.
Tried reinstalling original kernel, original bootloader, original pit mapping, original rom, again with all versions of oden, all failed, then tried re-partition with segmented original pit, still failed. Tried clockworkMod recovery v4.0.0.2, 5.xxx, 6.xxx, 4.0 passed but didn't reboot into recovery mode. I have let it run sometimes for 8+ hours before it fails, but always fails.
2nd Email - I have tried that guide <<< http://forum.xda-developers.com/showthread.php?t=1457458 >>> with multiple usb ports, multiple versions of oden, failed, haven't tried alternate cables, but since it passed on the one pda flash with CWM4.0.0.2 the cable may be ok (factory htc cable), I did read that the resistance on the cable may have an effect on the upload and the phone will look for stock samsung cable resistance, but have to get hold of another cable before I can try that.
Tried other similar threads to the one that you sent, but that one did seem to be the most complete with the best directions, and working links to the software.
I think the nand is the issue, thought it would be recoverable through a repartition since the clockworkmod v4 passed, but still only boots to download mode. I have a usb jig ordered to see if resetting the custom rom counter will make any difference.
http://forum.xda-developers.com/showthread.php?t=1796807
This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
I might add .. don't forget to run ODIN as administrator.
Also, to avoid this in the future, disable the OEM Lock in Developer Options.
YOUR AN ANGEL :d
Hello there. I got "Custom Binary(RECOVERY) Blocked By R/L, I have odin and firmware but odin can`t see my phone. What i have to do?
1sicgsr said:
This is my first experience with rooting a phone and I think I messed up...big time! All I wanted to do was get rid of preloaded garbage on the phone to save battery life. Now I have a red message, "Custom Binary blocked by FRP lock".
My G920T was completely stock until today when I loaded CF_Auto_Root into it with Odin.
The phone immediately went into a boot loop after the install. I was able to boot into device recovery and did a factory reset at that point. I didn't know until after I reset to factory that I had accidentally installed Auto_Root for the G920F.
No problems here, booted back into initial setup, and I completed all of the setup items. Logged into Google, Samsung, etc. Because this was my first time and ended with a boot loop, I decided I'd just deal with the battery life problems. I turned off USB Debugging and the Bootloader modify option. The phone seemed to be working normally until I unplugged the phone from my computer, plugged it into wall fast charger, the rebooted the phone.
Now all I get is the Samsung home screen with the red message in the upper left corner. It will continually loop between the home screen and a black screen if the phone is plugged in. I cannot get back into the recovery menu as the phone is unresponsive to home + power + vol. up. I can however boot into the download menu.
I have tried reflashing the stock tar file, a stock bootloader, and stock modem with Odin 3.10.6 and 3.10.7. When I attempt the reflash I get the failed message in Odin, and "SW Rev. Check Fail. Device: 3. Binary: 2.
Are there any other options I have at this point, or something I'm doing wrong or incompletely?
Thanks
Edit:
I have fixed the phone after about 10 hours of messing around with stock firmwares, Odin, Smart Switch, Kies, etc. If the option was there, I tried it.
The FRP Lock is easily fixed by flashing in the stock firmware, but it must be the version the phone was at before rooting. This seems to be pretty common knowledge but my problem was I didn't know which version I had. I started with 0F6, that didn't work because I would then get "sw rev check fail device 3 binary 2" in the download screen and Odin would show a red fail almost immediately.
At this point I was getting pretty beat up by the phone and was trying anything I could find. I noticed, when entering the download menu before you press the vol. up button, that you can press the home key and the phone will show the barcode. This was the turning point for fixing my phone. It was in the barcode screen that I found my phone's S/N. Perhaps it is located other places, like behind the battery I can't remove, or on a carriers website (checked T-Mobile and didn't see it), but this is where I found it. I then remembered that Smart Switch had an option for 'Emergency software recovery and installation'. When you enter that menu the program asks you for your phone's model number, then the phones S/N. I could now use this option because I had the required info. I thought I was making progress but this method failed at 60% of downloading the software and drivers and an error in the download screen of "sw rev check fail device 3 binary 2".
The key for Smart Switch is, after you enter your model number and serial number, the program tells you what firmware version the phone was at. The 3 fields that pop up all read "OJC". More progress! The firmware version I was trying to install, which was the newest one I could find without knowing what to look for, was 0F6. I found the OJC .zip file at sammobile.com. It took 2 hours to download to 95% and the download failed. Restarted the download and waited 2 more hours.
While the OJC was downloading I was still messing with options I was reading about from google searches. I read multiple times to try different versions of Odin, try different USB ports, try different sequences of loading/connecting device to pc. I changed USB ports on the PC and the samsung drivers started installing for the device. A second driver installed this time for Samsung Modem 2 (I only particularly remember the Modem 2 part) that I didn't see install on the other USB port. At this point I decided to try Smart Switch again. This time, with the extra driver, the download completed to 100% and started to install some files onto the phone. But, it only got to 20% installed and erred again. This time the error was "sw rev check fail device 3 binary 1". I also noticed that the Current Binary field on the download screen changed from "custom" to "Samsung Official". More Progress. At this point there was nothing more I could do until the OJC was finished downloading.
As soon as I unzipped the OJC I opened Odin v3.10.7 and loaded the firmware into the AP, plugged in the phone, hit start. Red Fail. Then tried loading the firmware with Odin v3.10.6. Loaded OJC into the AP, connect device, hit start. Red Fail, but, I made it past the Nand Write Start and got all the way down to the system installation part before it failed. More Progress! Tried v3.10.7 again and didn't make it past Nand Write before it failed again. Then I started changing the order of when I opened Odin, loaded the firmware, and connected the device. There are tutorials everywhere that specifically say, "CONNECT IN THIS ORDER OR THE FLASH WONT WORK", I found this to not be entirely true.
How I eventually got the OJC firmware loaded back onto the phone was to Restart the phone into the Download screen, connect phone to pc and wait for Odin to recognize the device, then load OJC into the AP, hit start. In v3.10.7 the install failed every way I tried at different points in the install. v3.10.6 is the one that ended completely re-flashing the phone to stock OJC firmware.
If you're new, or stuck, make sure you do the following:
- Verify you are trying to load the correct firmware with smart switch. (OJC is the last 3 characters of the file names)
- Try different versions of Odin
- Try different orders of setup processes
- Try different USB ports and MAKE SURE you have all Samsung device drivers installed
Click to expand...
Click to collapse
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Likebeast said:
HOW can i get The Serial NUMBER AND WRITE IT DOWN ON SMART SWITCH OR KIES ?? IF IT IS A BARCODED IN THE DEVICE ?!??!
Click to expand...
Click to collapse
smh, there is number on top of barcode that saids S/N
After Reading this post i felt dumb, because I thought imei on back of my phone was S/N whole time
I used SmartSwitch Emergency software recovery and installation, went through 2 cycles of installation somehow and it finally fixed my phone.
I'm using SM-920T galaxy S6
Hey sir did u just flash the stock rom u downloaded and it fix the frp lock?? I need ur help i also accidentally activated the oem.. please helppp sir
I inherited a Galaxy S7 from my brother after he recently passed away. He was with T-Mobile, so it's a G930T (I have the original box, too, which has come in handy). I brought it back home with me... to France. I figured I'd have it unlocked and replace my old smartphone with this newer one.
Since I didn't know what his pin was, I did a factory reset... and found myself stuck in FRP!
At that point I called T-Mobile and was able to have myself added as an authorized user on my brother's account. They gave me the pin (too late! gah!) and unlocked the phone on their end, as it had been fully paid for. But as far as the FRP thing they were unable to help.
After a lot of googling, I found a bunch of how-to videos explaining how to bypass FRP, I thought I was in luck... except none of them worked for me. Then I came across a comment stating that flashing the device might do the trick. So I decided to try that... but now I'm locked in a boot loop (on the Samsung Galaxy S7 screen that keeps flashing on and off).
Here's what I did, step by step:
1) I installed Odin 3.13.1 from samsungodin.com
2) I downloaded & unpacked a stock ROM from sammobile.com, more specifically this one:
G930TUVS8CRJ1 - GALAXY S7 SM-G930T TMB USA (T-MOBILE)
3) I connected the phone to the laptop
4) I ran Odin and selected (with the AP button) the AP_GS30T* file & hit "start"
Odin said PASS! and I thought all was good... except it wasn't.
So I went googling some more and found a great page... which I am not allowed to link to yet, apparently, but it's on thedroidguy's website.
Only problem is that I can NOT get into the Recovery Menu. When I try the procedure (Home+Volume Up+Power) all I get is "recovery booting" in a bright blue font and THAT starts flashing on and off instead of the Galaxy S7 screen. If I redo the same button sequence, it just switches back to the other screen.
The ONLY other screen I can get to (unless there's another trick I haven't heard of yet) is the blue 'Warning' screen from which you can install ROM's (Home+Volume Down+Power).
So I tried to reinstall that same ROM two other times. First because I wasn't sure if I'd ran Odin as an administrator the first time around, figured that might be the issue, but that didn't change anything. Then I gave it another shot, this time using the phone's original USB cable (I had initially used mine), hoping that would make a difference... but of course, it did not.
So... is there anything I can do at this stage? Did I maybe go for the wrong ROM? Is there another one I can try?
I just hope it's not permanently bricked :-o
So I managed to unbrick my device, yay me! It took me some time to figure it out, but the solution was quite simple. Up until that point I had only been flashing the AP file alone. What fixed my problem was to also flash the bootloader (BL) file. This got me out of that boot loop.
I still haven't managed to bypass that annoying FRP lock, though. Every technique I've tried has failed.
On the plus side, I'm becoming an expert at flashing :-o
I just came across a method that, I think, could work: flash the factory combination file, enable usb debugging, then flash the regular firmware (with all files except CP).
My problem is that I can only find ONE combination file for the G930T but it doesn't match ANY of the firmwares available on sammobile... is this a problem?
The filename is similar to the v6 firmwares, only the last 4 characters don't match.
The other issue is that none of the v6 firmwares will flash on my device (they all fail pretty quickly while going through the AP file)... will using the combination file fix this?
Any thoughts or suggestions would be greatly appreciated.