Related
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
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
Hello,
After rooting (flashing) my brand new Galaxy Tab 2 7" via the following link (will not show): androidauthority.com /galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473/, method Heimdall, with the files from this site, the device is stuck at the bootscreen. I did follow the instructions exactly. The ./su in the adb shell segfaults however, so i can't continue, and it won't startup either. So i guess now it's bricked. I read somewhere it has to do with the software version number that was incompatible.
Can i go back to the old firmware, or install another android 'distro' (that was my intent for the long run and the reason to root it first)?
I can still adb shell into it, but no root however.
I'm a newbie in the android world btw.
Hi,
Search for the latest Stock Firmware files of P3110 for your country and flash it with ODIN... Check the development thread and you'll find information on how to flash stock firmware with odin...procedure will be the same only files will differ...
To go into download mode, turn off your device, press vol. down, keep it pressed and with that press the power button...start odin on your computer and connect the tab to your computer and flash the file....
Zeroclick said:
Hello,
After rooting (flashing) my brand new Galaxy Tab 2 7" via the following link (will not show): androidauthority.com /galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473/, method Heimdall, with the files from this site, the device is stuck at the bootscreen. I did follow the instructions exactly. The ./su in the adb shell segfaults however, so i can't continue, and it won't startup either. So i guess now it's bricked. I read somewhere it has to do with the software version number that was incompatible.
Can i go back to the old firmware, or install another android 'distro' (that was my intent for the long run and the reason to root it first)?
I can still adb shell into it, but no root however.
I'm a newbie in the android world btw.
Click to expand...
Click to collapse
I'm downloading 4.1.1. from samsung-updates.com, since that was the latest version for my country (NL). I flash with Heimdall, since i don't have windows, or is there something special with Odin?
Now i'm going to flash it, is it possible to root it in the process? Else i have to flash it later again.
varundave said:
Hi,
Search for the latest Stock Firmware files of P3110 for your country and flash it with ODIN... Check the development thread and you'll find information on how to flash stock firmware with odin...procedure will be the same only files will differ...
To go into download mode, turn off your device, press vol. down, keep it pressed and with that press the power button...start odin on your computer and connect the tab to your computer and flash the file....
Click to expand...
Click to collapse
Zeroclick said:
I'm downloading 4.1.1. from samsung-updates.com, since that was the latest version for my country (NL). I flash with Heimdall, since i don't have windows, or is there something special with Odin?
Now i'm going to flash it, is it possible to root it in the process? Else i have to flash it later again.
Click to expand...
Click to collapse
Idk but I usually flash with odin
The file is 706MB. The boot-bjr.img file that i installed is only 5.6 MB. Can someone explain what is going on here? I don't feel comfortable with this and i cannot find any description of how the flashing actually works, what you are replacing by flashing, what format/partitioning the flash has e.t.c.
qazmed said:
Idk but I usually flash with odin
Click to expand...
Click to collapse
Just for the record, i was able to install cyanogenmod on it, by first installing clockworkmod recovery. Heimdall and adb is all you need if you're a linux user.
Don't worry its not a brick.
Or a hard brick at least.
Download the stock ROM from sammobile or samsung-updates. Doesn't matter which. Extract the zip. Flash the .md5 file with Heimdall or if that doesn't work rename it to .tar.
To root it properly follow my root tutorial but use Heimdall when I use Odin. http://www.youtube.com/watch?v=pAvze-VNzj8&feature=youtube_gdata_player
Sent from my GT-P3113 using Tapatalk HD
I Am unable to mount system or cache either and also i cant flash certain files from my CWM recovery I think it is because I forgot to root my device before flashing the CWM from stock recovery. Now I can't do nandroid backup or root the device either i need help. The data speed is too slow at my home I'll not be able to download stock rom (it would take days to download)... Is there any way??
smartananallavan said:
I Am unable to mount system or cache either and also i cant flash certain files from my CWM recovery I think it is because I forgot to root my device before flashing the CWM from stock recovery. Now I can't do nandroid backup or root the device either i need help. The data speed is too slow at my home I'll not be able to download stock rom (it would take days to download)... Is there any way??
Click to expand...
Click to collapse
Recovery Mode doesn't need root to function. Try the Universal GB Root package and tell me what happens, a bit more information would be helpful, like, if an error shows, or something like that...
EDIT: OH! I just realized what is happening! You are using CWM with a Stock ROM that you want to root, right? Well, CWM does NOT support .EFS file systems. It can't mount the /system/ partition to write on it. When you install a custom ROM with it, it re-formats the system partition to EXT4. So, you can't use both a Stock ROM and CWM. They do not support each other. You need to flash a custom ROM. Or use the Stock Recovery to flash the Root Zip.
another trouble.....
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
smartananallavan said:
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
Click to expand...
Click to collapse
Ok, i'll wait for the screenshot =)
Also, this is a first i have ever heard of this problem. If the drivers are OK, Odin is showing the COM Port, and the Setup begins, my only guess is that you got the wrong flash files... Are you sure you'r device is "s5670"? not some other model? Also, i recommend downloading official firmware from SamFirmware. But for now, i wait for screenie =)
smartananallavan said:
thanks i figured that out but also now there is another problem...please help me.
I downloaded the stock rom and it has only two files ( a .dll and an file HOME.tar) but i loaded the file as PDA in
odin and now there comes the problem.... the drivers are setup and the ID:COM section turns yellow and then in the
logs everything proceeds good and gets stuck at the setupconnection stage. I'll try to post the screen shot
Click to expand...
Click to collapse
Don't load it as PDA, instead load it as One Package(home.tar.md5 file)
my samsung doesnt open
i tried to install cyanogen 10.4.1 jelly bean to my galaxy fit but i didnt root it first i realized that later and it couldnt wipe and couldnt install the update. the problem is that it doesnt open any more. it stays at galaxy fit screen what can i do to restore it?
Stay Calm Bro
koukis32 said:
i tried to install cyanogen 10.4.1 jelly bean to my galaxy fit but i didnt root it first i realized that later and it couldnt wipe and couldnt install the update. the problem is that it doesnt open any more. it stays at galaxy fit screen what can i do to restore it?
Click to expand...
Click to collapse
Hi @koukis32
Dnt wry Bro ur cell is just fine please download the Firmware pages that you want to flash from the link below by entering your phone model number or i shall also paste link where in you can download the package directly also.
You can find the required ODIN Firmware Package as you wish for the ODIN tool
http://www.sammobile.com/firmwares/ and put in the Device Model Number and download it
or complete Firmware Package of Gingerbread 2.3.6 DDKT3 you can find the link below
http://hotfile.com/dl/146050815/b3b9...2_INU.zip.html in case this link doesn't work please download the Packages from above link as I can't check it from my office so dntmnd
For ODIN Flashing Tool:
http://www.downloads.techdiscussion....ting-software/
and Procedure to Flash is:
- Shutdown Galaxy Fit and restart it in Recovery Mode. For that hold the volume down key + Home key and power key. Hold it for some seconds and leave it. The device will boot in recovery mode. When the yellow triangle, connect cell phone and a computer with a USB cable.
- Launch ODIN on your system. In that look under ID:COM section. The section will turn to yellow once the device is connected and detected.
- Now click on OPS. It will ask you to browse the downloaded firmware package. Browse to GIO_1.0.ops. Once it is selected click on One Package and choose S5670DDKT3_S5670ODDKT2_S5670DDKT2_HOME.tar.md5.
- Now click on Start. The update process has started and it will take few minutes to complete.
- Once it is done, the device will reboot itself. Later on you can go in Settings and checkout the firmware version.
And considering still you still in Galaxy Fit Page then go take a break and relax and follow the instructions in the link which I have shared you phone will come back to life.
http://www.androidauthority.com/how...xy-fit-s5670-android-2-3-4-gingerbread-35369/
follow the picture carefully.
:good::fingers-crossed::fingers-crossed::fingers-crossed:
AXAz0r said:
Ok, i'll wait for the screenshot =)
Also, this is a first i have ever heard of this problem. If the drivers are OK, Odin is showing the COM Port, and the Setup begins, my only guess is that you got the wrong flash files... Are you sure you'r device is "s5670"? not some other model? Also, i recommend downloading official firmware from SamFirmware. But for now, i wait for screenie =)
Click to expand...
Click to collapse
thaks for helping sorry for the long Delay. solved the problem!!!! just downloaded a stock deodexed rom.zip and flashed...... booted up fine
Hi,
I've got an Samsung Galaxy S7 which won't boot android anymore. this was after the phone was hot.
Recovery and download mode works. Is there a way to copy photos to a computer or sdcard somehow?
Thanks
arjanv said:
Hi,
I've got an Samsung Galaxy S7 which won't boot android anymore. this was after the phone was hot.
Recovery and download mode works. Is there a way to copy photos to a computer or sdcard somehow?
Thanks
Click to expand...
Click to collapse
If you connect your phone to your computer - Does the computer see the phone?
If you have your music and photos on the external sd card (if your pc doesn't see the phone) you could copy from the external sd card with a sd card reader - I believe that if you can boot into recovery that you can cope files from the phone to the pc as well.
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
If you connect your phone to your computer - Does the computer see the phone?
If you have your music and photos on the external sd card (if your pc doesn't see the phone) you could copy from the external sd card with a sd card reader - I believe that if you can boot into recovery that you can cope files from the phone to the pc as well.
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
no external sd card, otherwise there was no problem
Could we have some more information please?
Is the device Knox tripped or otherwise modified? (Rooted, custom recovery, custom firmware)
What's the model number?
What's the firmware build number?(The stock recovery will say).
Is the device encrypted?
(If you've set up Samsung Cloud or Google Photos backup you might have better luck there)
I don't think you can enter MTP mode with the phone only working from recovery and download mode. Simply install a ROM via TWRP but do not wipe internal storage. Once the phone boots up to android, retrieve your files.
Good luck
I'm able to boot in download mode.
Odin recognize the phone. is flashing possible without loosing data(only care about stuff on the internal SD card. loosing settings and apps is not a problem.
added attachment/screenshot.
arjanv said:
added attachment/screenshot.
Click to expand...
Click to collapse
Official firmware, so likely encrypted. Boot into recovery and take note of the build number and CSC. Download the exact same firmware from a site like SamMobile. Using Odin, flash the BL, AP, CP and HOME_CSC(NOT the plain CSC) packages in the firmware package by placing them in their relevant slots. It will make like it's doing a system update and take long to boot, but should result in a workable device with your data intact.
hi seems that recovery not working either,i've tried but can't get into recovery. sometimes a red text appears on the top left screen. something about sandforcing.
CurtisMJ said:
Could we have some more information please?
Is the device Knox tripped or otherwise modified? (Rooted, custom recovery, custom firmware)
What's the model number?
What's the firmware build number?(The stock recovery will say).
Is the device encrypted?
(If you've set up Samsung Cloud or Google Photos backup you might have better luck there)
Click to expand...
Click to collapse
CurtisMJ said:
Official firmware, so likely encrypted. Boot into recovery and take note of the build number and CSC. Download the exact same firmware from a site like SamMobile. Using Odin, flash the BL, AP, CP and HOME_CSC(NOT the plain CSC) packages in the firmware package by placing them in their relevant slots. It will make like it's doing a system update and take long to boot, but should result in a workable device with your data intact.
Click to expand...
Click to collapse
What about this? https://www.youtube.com/watch?v=cyCileqUVFQ they seems to flash only AP. Whats the different in results of flashing only AP or Flash AP, BL, CP and HOME_CSC?
arjanv said:
What about this? https://www.youtube.com/watch?v=cyCileqUVFQ they seems to flash only AP. Whats the different in results of flashing only AP or Flash AP, BL, CP and HOME_CSC?
Click to expand...
Click to collapse
Samsung old and new style of firmware packaging. They used to place all parts into a single package(AP), customised per region. This had the disadvantage of requiring a complete different firmware package for every region with little actual differences. New Samsung firmware comes broken up into the BL(bootloader), AP(system, kernel, recovery), CP(modem firmware) and CSC(recovery package which applies all region settings) packages. This way only the CSC needs to be changed per region.
At absolute minimum you should flash the AP and HOME_CSC/CSC package. (Though only if you're sure you're flashing the same firmware as the current or you may trip knox)
The general rule is if you flash AP, then CSC must be flashed aswell, otherwise the firmware becomes very buggy.
The regular CSC file wipes storage, while HOME_CSC does not, but will only work if the current CSC matches the firmware package
If you like you may use Smart Switch Emergency firmware recovery instead, but beware, as it's known to mess up more often than not
arjanv said:
hi seems that recovery not working either,i've tried but can't get into recovery. sometimes a red text appears on the top left screen. something about sandforcing.
Click to expand...
Click to collapse
Did it perhaps say "SEAndroid not enforcing"? That means it's an unofficial recovery image. Not sure how that could happen. Seems like firmware was corrupted somehow.
thanks for explaining.
I've download the latest firmware from sammobile which contains these files:
AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar
BL_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship.tar
CP_G935FXXU1DQD7_CL11104523_QB13263377_REV00_user_low_ship.tar
CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
HOME_CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
I want to save photos, so i try to flash AP and HOME_CSC using odin right?
arjanv said:
thanks for explaining.
I've download the latest firmware from sammobile which contains these files:
AP_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship_meta.tar
BL_G935FXXU1DQE7_CL11104523_QB13505684_REV00_user_low_ship.tar
CP_G935FXXU1DQD7_CL11104523_QB13263377_REV00_user_low_ship.tar
CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
HOME_CSC_PHN_G935FPHN1DQD1_CL10939265_QB13310839_REV00_user_low_ship.tar
I want to save photos, so i try to flash AP and HOME_CSC using odin right?
Click to expand...
Click to collapse
Wrong firmware I'm afraid. Notice your screenshot says the device is a SM-G930F, these are SM-G935F files for the Galaxy S7 Edge. Also, since we don't know what firmware revision the device is on, you *need* to flash the BL and CP parts too.
Could you please check the bottom of your box? You need the three-letter CSC code. If you get it wrong your data is toast.
So final process is:
1. Check your box for the CSC code
2. Select your CSC in the "Select Country" dropdown https://www.sammobile.com/firmwares/galaxy-s7/SM-G930F/
3. Download the latest firmware
4. Flash BL, AP, CP and HOME_CSC from the package.
5. Device should auto-reboot and will ask you for your lockscreen passphrase.
oops, sorry. copy paste the wrong files.
i meant these files:
AP_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship_meta.tar
BL_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship.tar
CP_G930FXXU1DQD7_CL11104523_QB13263348_REV00_user_low_ship.tar
CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
HOME_CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
arjanv said:
i meant these files:
AP_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship_meta.tar
BL_G930FXXU1DQE7_CL11104523_QB13505661_REV00_user_low_ship.tar
CP_G930FXXU1DQD7_CL11104523_QB13263348_REV00_user_low_ship.tar
CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
HOME_CSC_PHN_G930FPHN1DQD1_CL10939265_QB13310834_REV00_user_low_ship.tar
Click to expand...
Click to collapse
If your CSC code is PHN then yes.
CurtisMJ said:
If your CSC code is PHN then yes.
Click to expand...
Click to collapse
this says the box. see attachment
tried to flash and now this message(see attachment)
what now?
found this on a other post.
just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
arjanv said:
tried to flash and now this message(see attachment)
what now?
found this on a other post.
just extract your firmware with win rar and copy recovery.img to your desktop
there is a tool for making .tar file from .img called tar-Tool .
with tar tool you can make .tar from .img files
convert recovery.img to recovery.tar with this tool
flash it in pda (AP) in odin . now you can go to recovery mode
then wipe data/factory reset and wipe cache
rebooot
Click to expand...
Click to collapse
That means Odin didnt finish one of its operations. You need to use Odin 3.12+. The device wont let you do anything else until it registers a successful flash in download mode.
I think it's best to just use Smart Switch.
https://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/flash-stock-firmware-using-samsung-t3079176
Video is for S6, but the process is the same.
Beware that the internal SD will be wiped, but since the CSC is nowhere to be seen I think thats the only way, sorry.
EDIT:
Getting back to download mode:
https://forum.xda-developers.com/showpost.php?p=68632831&postcount=5