Database Info

[ROM][ODIN] Stock ODEXED T839UVKD1 (Sidekick 4G) Firmware [6/12/11]

Hello Everyone, This is Now an Instructional Odin ROM to flash Back to Factory Stock and/or Recover your Broken System.
This is 100% STOCK Odexed T839UVKD1 firmware For the Sidekick 4G and needs to be flashed through Odin. Odin is attached below along with the Sidekick 4G pit.
How to Install/Flash.
Code:
0. Download the KD1OdinSTOCK.tar.md5 File (Find link Below)
1. Remove the .md5 tail
2. Open odin with phone not connected yet
3. Boot in to download mode using Trackpad+Vol down then power
4. Connect phone to pc
5. KD1OdinSTOCK.tar in pda slot, Use SK4G pit file from below in Pit Slot
6. Double check that only auto-reboot is checked (if it doesnt work the first time, click re-partition)
7. Click flash
First boot may take around 3-5 mins. Wait it out and then you should be good to go.
KD1OdinSTOCK.tar.md5 >> DOWNLOAD
UPDATE: FOOL PROOF WAY TO GET INTO DOWNLOAD MODE
ayoteddy said:
Try this, take the battery sim and sd card out of your phone.
Open odin, put the tar in pda and pit into pit.
Plug your phone into the usb.
Now bare with me, this part is a bit akward but you can do it.. hold the vol down key and trackball *with one hand* and put the battery in while holding them. You will be in download mode and Odin will detect your phone. Then flash
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Thanks to Xda Members Datlilboricua and tweeklulz for testing these files for me.
Use the Thanks button if this was helpful ; post below if you have feedback/questions ect, Thank you and please enjoy!

Nice one! Keep at it. There are a bunch of us waiting for this!
Sent from my SGH-T839 using XDA Premium App

downloading now, i'll package them
thanks for pulling these man
edit: just got back from the bar and I work in 6 hours i'll upload it later

Can anyone teach me how to install it in sidekick
Sent from my SGH-T839 using XDA App

Mirrors:
Part 1: http://gititbit.ch/skgi
Part 2: http://gititbit.ch/skgi2

Is this still being packaged Blu? I could really use a working odin tar right now... accidentally soft bricked trying to use a recovery.tar to get rid of ClockworkMod and get back to a stock recovery.

sduvick said:
Is this still being packaged Blu? I could really use a working odin tar right now... accidentally soft bricked trying to use a recovery.tar to get rid of ClockworkMod and get back to a stock recovery.
Click to expand...
Click to collapse
Just packed now sorry. You flashed the one from the restoring stock recovery thread? What was your method of flashing it? Does it boot up at all or stick at the samsung boot screen? (i packaged that one and am curious as I heard reports of it working)
Download link: still uploading
Pit file attached in case you need it (unrar it first)
I do not guarantee that this will work, all I did was tar the files and upload them (and edit the pit). I did not trim the datafs.rfs file due to lack of ability to test it. Flash AT YOUR OWN RISK! so If this fails you now own a fancy brick!
edit:Not posting the tar yet for privacy of ayoteddy and potentially his logins to websites. The data wasn't wiped and has all his info, waiting for a clean one.

damn those files shouldnt contain any data since i had factory wiped just before pulling those images. *shrug* there might be a more in-depth way to clear all data
anyways im sure we can have a functional odin image with only the following files included
zImage
modem.bin
factoryfs.rfs
Recovery.bin
Param.lfs
i doubt anybody will be messing with anything else in their file sys but that should be able to recovery anybody from a soft brick.
Edit: Also dis-include the sbl and boot.bin as it could be very dangerous overwriting those files.. not really necessary anyhow.

I'm actually stuck at the black screen with a phone and a computer with a yellow triangle in the middle. Yeah, I was trying to flash a stock recovery from the stock recovery thread. Got a little desperate and tried to flash the recovery tarred for Odin, and that sent me to where I am now. I appreciate all your hard work guys, and have learned my lesson not to flash unless there's a lot of backups handy ;]
I'll try the pit, not sure if I may need more or not, you guys probably know better than me.
EDIT: as I am not skilled in using Odin and do not wish to cause further damage to my phone, I will await instructions from you guys/ayoteddy's image.

sduvick said:
I'm actually stuck at the black screen with a phone and a computer with a yellow triangle in the middle. Yeah, I was trying to flash a stock recovery from the stock recovery thread. Got a little desperate and tried to flash the recovery tarred for Odin, and that sent me to where I am now. I appreciate all your hard work guys, and have learned my lesson not to flash unless there's a lot of backups handy ;]
I'll try the pit, not sure if I may need more or not, you guys probably know better than me.
EDIT: as I am not skilled in using Odin and do not wish to cause further damage to my phone, I will await instructions from you guys/ayoteddy's image.
Click to expand...
Click to collapse
What did you do while flashing it? What boxes did you tick? Where did you put the tar, etc
@ ayoteddy alright i'll just make one from those, only reason i was including cache before is I heard its where permissions were stored though as you said I'm sure those files work fine

Here it is:
Odin + pit: attached
sk4g_stock.tar.md5.rar: Click here
UNRAR the tar first (i didn't want to trim factoryfs.rfs due to unability to test so I compressed it instead)
Put the extracted sk4g.tar.md5 in the pda slot
make sure ONLY AUTO-REBOOT is checked (unless you are re-partitioning, then use re-partition and the pit file)
1. open odin with phone not connected yet
2. boot in to download mode using Trackpad+Vol down then power (thanks sduvick)
3. connect phone to pc
4. sk4g_stock.tar.md5 in pda slot
5. double check that only auto-reboot is checked (and the pda you selected of course)
6. Click flash
Disclaimer: Flash at your own risk, if you get bricked I am not liable.
The odin tar includes
factoryfs.rfs
modem.bin
param.lfs
recovery.bin
zImage

Thanks blu, @sduvick would prolly be the first to test cause he was waitng for this.. hope everything works out for em
He also figured out how to get into downlode mode ..
Trackpad+Vol down then power
Sent from my SGH-T839 using XDA App

I'm not entirely sure what I did. I think I put the recovery.tar.md5 in the wrong place. anyways, I'm back out of bricked, and now just waiting for a working stock restore tar to get back to stock.
EDIT: just saw the tar, downloading now, will test in around 10 min when the file is downloaded.

sduvick said:
I'm not entirely sure what I did. I think I put the recovery.tar.md5 in the wrong place. anyways, I'm back out of bricked, and now just waiting for a working stock restore tar to get back to stock.
Click to expand...
Click to collapse
Did you try my one click stock in the same post?

Yeah, I didn't have the same root method, so that didn't get rid of Clockwork for me.

First try at flashing failed almost at the end, at recovery.bin if I'm not mistaken. I'm trying to run it again.
EDIT: Failed again, at recovery.bin

sduvick said:
First try at flashing failed almost at the end, at recovery.bin if I'm not mistaken. I'm trying to run it again.
EDIT: Failed again, at recovery.bin
Click to expand...
Click to collapse
Got it working through pm with him.
attach the pit and re-partition. then flash the tar
sduvick wanna post the steps you used?

I can actually give steps based on what you have for symptoms (too much experimenting for me haha)
If you have the "soft brick," that is the small phone and computer icons, just connect to Odin and flash the full image.
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
logo only
1. Download mode
2. Flash full package
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work

sduvick said:
i can actually give steps based on what you have for symptoms (too much experimenting for me haha)
if you have the "soft brick," that is the small phone and computer icons, just connect to odin and flash the full image.
Black screen, no logo.
1. Get into download mode by using voldown+touchpad+power
2. Flash full sk4g.tar.md5 as posted.
Logo only
1. Download mode
2. Flash full package
can't flash recovery/boot/sbl
1. Download mode
2. Use pit only, run with repartition checked
3. Reboot/redownload mode
4. Run the full image in odin.
Anything else
1. Download mode
2. Full tar.md5 flash in odin
3. Ask if it doesn't work
Click to expand...
Click to collapse
sticky this **** mothafuckas!!!

The Pope of Dope said:
sticky this **** mothafuckas!!!
Click to expand...
Click to collapse
good thing some incredibly sexy blu guy made that pit file. I hear he has the face of brad pitt with abs like jesus.

[Q] AT&T SGH-I727 Odin Crashes at "Getting PIT for mapping..."

Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?

Have you tried one of the Odin one clicks, it can be found here... http://www.androidaddicted.com/firm...lc4-ics-4-0-3-leaked-firmware-update-576.html
Sent from my SGH-I727 using Tapatalk 2

worias said:
Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?
Click to expand...
Click to collapse
There is no pit for the skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
There is no pit for the skyrocket.
Click to expand...
Click to collapse
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.

cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.

Great news! Glad you're back up and running.

worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium

cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
i dont/never used adb, can u post the commands(step by step) so i can put it in the 1 stop sticky
worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
to confirm, u didnt use adb to flash the pit file, you used odin to flash the pit file and used the pit option in odin, then you picked pda option for the stock firmware, more details u give the better so i can add it to the sticky

cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
Cool, thanks!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.

Yes please vinvom put it in your stickies, it'll help a lot of us.
Sent from my SGH-I727 using xda app-developers app

cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can

cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Sent from my SAMSUNG-SGH-I727 using xda premium

stoopendis said:
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Click to expand...
Click to collapse
Yes, celox.pit (extracted from the zip) is the actual pit to flash in ODIN. It's from an SGH-I727 and should be the same for Rogers version. Not 100% sure if it's the same for TMO flavor.

vincom said:
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can
Click to expand...
Click to collapse
k in going to use this thread to link from the sticky and also add it in the odin troubleshootibg section in restoring to stock
********************************************
when trying to flash stock firmwares and/or recoveries and it hangs at "Getting PIT for mapping" or getting pit errors in odin, download celox.zip and "unzip" the file, select the extracted "celox.pit" file in the pit option for odin, with all other options unchecked hit the start button in odin, once flashed you can then flash the stock firmware and/or recovery in odins pda section.
thanks cschmitt

Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.

cschmitt said:
Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.
Click to expand...
Click to collapse
k, i reedited the post

stoopendis said:
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I used the attachment from cschmitt, extracted the PIT file from the zip and then used ODIN to flash it. I was then able to flash a Skyrocket Stock ODIN tar to restore to GB and boot the phone. I have since been able to get it rooted, CWTouch on it, and have CM10 running on it well.
Thanks again everyone.

I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1) .
I just tried other laptop to use Odin & stock 4.0.4 to flash back Stock rom.and got getting mapping pit....I still can go to Download mode but I can't flash anything.
Please help . Thank you very much.

If I understand, you're trying to flash 4.0.4 with odin. And it's a md5 file, right? Keep trying it. Sometimes it takes more than one try.
And check the check sum of the stock rom file you downloaded it could be a bad download
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

[Q] P6810 Problem! - Won't go to Recovery - Bootloop

Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.

edwing29 said:
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
Click to expand...
Click to collapse
You don't need a bootloader, it was already "flashed" when he flashed the stock official firmware - bootloader would have been included in that and PIT
If done correctly, the PIT should work, if not - unfortunately, most likely back for repair............ bummer
Without actually checking the above is HC, have you tried the official HoneyComb firmware ? Just don't factory reset in HC recovery

P6810 ICS LPP Bootloader
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure ONLY "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.

UpInTheAir said:
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
Click to expand...
Click to collapse
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:

edwing29 said:
Hi, thanks for your assistance...
I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the has is invalid.
Can you check them and re-upload if there's no problem?
Thanks again! :good:
Click to expand...
Click to collapse
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium

UpInTheAir said:
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, I just edited the previous reply.
Check it out, Thanks.

edwing29 said:
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
Click to expand...
Click to collapse
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.

UpInTheAir said:
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
Click to expand...
Click to collapse
Tried the steps above and still the same.
I had to flash back to the stock HC firmware because the ICS led into an infinite loop, at least HC let me turn off the device.
I'll wait for any other suggestions, thanks!
Sent from my GT-I9100 using xda app-developers app

All I can suggest is to send it away for repair.
JTag (riff box) by a 3rd party or Samsung.
If it's NOT a hardware issue, JTag should be much cheaper, and if successful, faster.
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
Sent from my GT-I9500 using xda premium

[Q] Need help! Can't unroot/unbrick Galaxy S3!

So let me start from the beginning;
I have Verizon's Galaxy S3 and had CyanogenMod 10.2 installed on it. After installing CM 10.2, I no longer had 4G/3G connection. After some research, I had discovered that it had to do with my device's APN. Anyways, what I found online was to unroot, and flash to a stock ROM, and wipe/reset factory settings, etc.
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop. After pulling the battery, I tried flashing the image again in ODIN, but the same thing happened, I figured this is what was known as a "soft brick". I followed another guide on here to unroot/unbrick the phone, which had me download another stock rom (stock.vzw_root66), as well as VRALEC.bootchain.tar.md5, and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5. Following the instructions had me PDA flash the VRALEC-bootchain.tar.md5 first, followed by the bootloader, and finally the stock image. However, I continued to get "FAIL!" after attempting to flash the VRALEC-bootchain.tar.md5.
Following another guide, it said to just try flashing the stock.vzw_root66 file, which I had done, and it succeeded, however, after the phone reboots, it says that I am using unauthorized firmware on my device, and to bring my phone to the nearest Verizon store.
Now, I have no idea what to do.
I'm using ODIN3 v3.07
Both the VRLEC.bootchain.tar.md5 and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 fails when trying to flash them onto my phone, and I don't want to proceed from here unless I know how to fix it, as to not damage the phone any further. Any help would be greatly appreciated!
The phone still boots into a stock recovery, and can still enter download mode. At this point, I just want my phone completely stock, as if I had just purchased it.

You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?

Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2

BattsNotIncld said:
You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?
Click to expand...
Click to collapse
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
BadUsername said:
Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!

I'm pretty sure those download mode stats you have are from the new bootloader. When you said this:
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop.
Click to expand...
Click to collapse
... I'm thinking you flashed a stock 4.3 ROM in ODIN and therefore locked your bootloader. This would also explain the yellow triangle when trying to flash root 66 afterwards. If I am correct, the good news is all you have to do is flash a stock 4.3 ROM to get back up and running. The bad news is you re-locked your bootloader and are stuck with TouchWiz.

WildWildWest42 said:
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!
Click to expand...
Click to collapse
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You're a life-saver! I just did this and my phone now works again! I couldn't thank you enough!

[Q] Status 7 Error flashing Cyanogenmod 11

Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq

Zackpip said:
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Click to expand...
Click to collapse
Flash the latest @Android-Andi Philz Touch or TWRP recovery and that should solve the problem (I recommend flashing the recovery with Odin or Heimdall.) Status 7 error usually means outdated recovery.
Link to @Android-Andi's recovery thread: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989

Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.

Zackpip said:
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Click to expand...
Click to collapse
What exactly did you do that it did this? Did you attempt to flash the recovery in Odin or Heimdall? If Odin, which version?
Sent from my SGH-T989

Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.

Zackpip said:
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Click to expand...
Click to collapse
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989

jrc2 said:
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
Click to expand...
Click to collapse
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.

Zackpip said:
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Click to expand...
Click to collapse
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989

jrc2 said:
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
Click to expand...
Click to collapse
I do not have a Linux machine anywhere.. Would that be the only way to fix it?

Zackpip said:
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Click to expand...
Click to collapse
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989

jrc2 said:
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.

Zackpip said:
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Click to expand...
Click to collapse
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989

jrc2 said:
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
Click to expand...
Click to collapse
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.

Zackpip said:
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Click to expand...
Click to collapse
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.

jrc2 said:
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
Click to expand...
Click to collapse
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!

Zackpip said:
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Click to expand...
Click to collapse
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989

jrc2 said:
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did exactly that.

Zackpip said:
Yes, I did exactly that.
Click to expand...
Click to collapse
So it must have been a bad download then. You used Odin v1.87 or what? Also, you should add [SOLVED] to the thread title.
Sent from my SGH-T989