Hello, i purchased android phone called FG8 (Fly Ying) and wifi wont connect sometimes or its stuck on ip, works on some routers and not on majority so i am looking for custom ROM to fix this if its possible.
Does anyone know any roms that are compatible with these devices here are specs:
CPU: Mediatek MTK6516 416 MHz processor
Baseband: MAUI.10A.W10.48.MP.V5.F1, 2011/01/27 16:48
Kernel version: 2.6.32.9
Build number:
ALPS.10Y.W10.48.MP.V1.06.2.04
Thank for help in advance am killing my self to find rom on net for this junk.
Replace your router or AP.
FG8 Wireless is stable with other routers.
All FG8 phones has same MAC!
Is there official firmware download page i think i messed up my firmware and if i do fac reset it remains the same?
wizzardz01 said:
Is there official firmware download page i think i messed up my firmware and if i do fac reset it remains the same?
Click to expand...
Click to collapse
I have messed mine too. I've talked to the people who sold it to me, and they have replied they are going to talk to the manufacturer to see if we can get the firmware and the needed update cable. I'm expecting a reply tomorrow. If I get the firmware and the instructions and tools to flash it, I'll post again.
firmware
hi, i've the same phone and i asked for the firmware....
they sent me this link, but i don't have any idea/instruction in what i've to do in order to flash it to my phone (maybe we need another cable?),
i hope somebody can figure out how to use it (and maybe explain what i've to do...)
sorry but i can't post the link, it's inside the attached file
Where does one get the 65xx Android Phone USB drivers?? Can't seem to find any on the web
oxyre said:
hi, i've the same phone and i asked for the firmware....
they sent me this link, but i don't have any idea/instruction in what i've to do in order to flash it to my phone (maybe we need another cable?),
i hope somebody can figure out how to use it (and maybe explain what i've to do...)
sorry but i can't post the link, it's inside the attached file
Click to expand...
Click to collapse
It's easy, open the txt file with notepad and look for "HYPERLINK" into the document. You'll see a multiupload link after it.
Is it possible to install WM 6.5 on FG8 android ??????????
if it possible which rom ????????????
Another ROM:
http://www.megaupload.com/?d=TILCY50P
NOT TESTED BY ME!
reinstall android 2.2 OS
well ,i get FBI antipracy notice or somthing
so, i ask the question again
can i reinstall the android 2.2 on this phone ,im having problem with the VOICE SEARCH , it give the errors ,how can i get rid of this app or make it to work
Try this ROM:
http://www.multiupload.com/T5HANXLGAO
Instructions:
1- Turn off the phone
2-Connect the phone to PC and install the driver. “Driver - USB VCOM Driver (binary)4”
3-Disconnect the phone from PC.
3- Open: ..\FG8 Android 2.3.1 with tools\SP Flash Tool exe_v1.1052.03\Flash_tool.exe
4- Connect the phone to PC and quick select in Flash_tool the COM port (you have seconds).
5.Click menu “file“ to choose “Open download agent file”, choose “MTK_AllInOne_DA.bin”; Then click menu “file“ to choose “Open Scatter-Loading Files”, choose “MT6516_Android_scatter.txt”;
6. Take off “PRELOADER” from de list.
7. Disconnect and connect the phone to PC.
8. Quick, after the sound Windows makes when something have been connected, press F9 or click "Download", don't worry the phone will keep connected until the process finish.
9. Power the phone (that will take some time).
you will have now custom recovery, too.
netomx said:
Try this ROM:
http://www.multiupload.com/T5HANXLGAO
Instructions:
1- Turn off the phone
2-Connect the phone to PC and install the driver. “Driver - USB VCOM Driver (binary)4”
3-Disconnect the phone from PC.
3- Open: ..\FG8 Android 2.3.1 with tools\SP Flash Tool exe_v1.1052.03\Flash_tool.exe
4- Connect the phone to PC and quick select in Flash_tool the COM port (you have seconds).
5.Click menu “file“ to choose “Open download agent file”, choose “MTK_AllInOne_DA.bin”; Then click menu “file“ to choose “Open Scatter-Loading Files”, choose “MT6516_Android_scatter.txt”;
6. Take off “PRELOADER” from de list.
7. Disconnect and connect the phone to PC.
8. Quick, after the sound Windows makes when something have been connected, press F9 or click "Download", don't worry the phone will keep connected until the process finish.
9. Power the phone (that will take some time).
you will have now custom recovery, too.
Click to expand...
Click to collapse
didnt understand the step 6 ,from which list ??????
when i click download it ask me '' open flash bin before download ''??????
seems like the files are incomplete ,no good
mastmalang70 said:
seems like the files are incomplete ,no good
Click to expand...
Click to collapse
Have you even try it?? It seems you don't.
okay ,i think i have found the problem ,when i connect my device ,installing driver ,that goes fine ,suppose i get com port 4 , when i open the flash tool ,reconnect the device the flash tool doesnt give me that port to read the device ,
it gives like com 3, com 5, till com 10
but always hide the no my device is connected ,
this i tried on my laptop running win7 64 bit and other pc running win7 32 bit
now what ????????
mastmalang70 said:
okay ,i think i have found the problem ,when i connect my device ,installing driver ,that goes fine ,suppose i get com port 4 , when i open the flash tool ,reconnect the device the flash tool doesnt give me that port to read the device ,
it gives like com 3, com 5, till com 10
but always hide the no my device is connected ,
this i tried on my laptop running win7 64 bit and other pc running win7 32 bit
now what ????????
Click to expand...
Click to collapse
Well, if you didn't noticed, the com port will be available JUST FOR A FEW SECONDS... prepare the software, and then, connect the cell phone... the port will be available just for a few seconds
sorry but this is not working with me
thanks for the help
mastmalang70 said:
sorry but this is not working with me
thanks for the help
Click to expand...
Click to collapse
Why not? try opening device manager and then connect the cell phoen.. check if you need drivers
......................
...................................
So I think I may be bricked....
I always had issues installing the drivers for my Spica (Portal here) on my Win7 laptop, but eventually I sorted it out so that Odin would pick it up and I got a pass from Leshak's kernel.
It was operational until I tried installing the firmware; the one that I had packaged with the kernel couldn't install Busybox. I tried a few other firmwires; an older one (which I had to re-root using the spica.ops rather than spica_jc3), CM 7 and CM 7 from this kitchen rom thing.
Those three all returned something like "Could not format system"
So assumedly recovery doesn't actually have root access, and I have tried rerooting it using Odin to no avail.
Any advice? Could it be drivers, is there an alternative PDA file I could use, am I doing a setting in Odin wrong?
Thanks!
Have you read that ? :
Code:
Prerequisites
- Android 2.1 Firmware Login - (Please register to download)
- Odin Multi Downloader 4.03 Odin4_03-Spica_ops.zip
- Spica Drivers Deposit Files (If it doesn't work install Kies and quit Kies when you need to flash)
Or get http://www.strefapc.pl/download/firmware/USB_Driver.rar .This is samsung's USB driver that comes with KIES
- MicroUSB Cable
- Fully Charged Phone
Warning: DATA WILL BE LOST
A more detailed guide can also be found here written by Lorenz (This 3 flash method will also solve any 0KB issues)
Samsung I5700 Galaxy Spica Android 2.1 Flashing Guide | All About Web & Mobile Application Development
1. Backup all your data, copy down your APN settings etc (You can use backup apps which save those into your SD card)
2. Do a factory reset (Menu/App Drawer -> Settings -> Privacy -> Factory data reset)
3. Power off the phone, remove your SIM card and SD Card
4. Press and hold Volume Down, Camera and End Call buttons until you see "Downloading... DO NOT TURN OFF TARGET" (Flash Mode)
5. Connect the phone to your PC (It should start prompting for the drivers)
5-1. For Drivers choose "Select from a list or specific location (Advanced)"
5-2. Select the files that was extracted from "Spica Drivers" (If it fails, unplug the phone and install Kies, quit Kies then plug the phone back)
6. Run Odin Multi Downloader (For Vista and Win7 users please Right click and Run As Administrator) [A yellow box with a COM port should show up if connected correctly]
7a. If the zip you downloaded for Android 2.1 Firmware only contains 1 file check "One Package" and click on One Package to select that file you extracted
7b. If the zip you downloaded for Android 2.1 Firmware only contains many files click on each of the option and choose the files accordingly.
8. Select OPS and select the ops file that came with Odin Multi Downloader (It should be 85 bytes)
9. Select Start
10. The phone will start flashing and automatically restart (If it gets stuck remove the battery and set to flash mode and try again)
Note: it can take a while after it restarts.
11. Please check the storage and ensure it is not 0KB (Menu/App Drawer -> Settings -> SD card & phone storage -> Available space
If you have 0KB please follow this guide written by Lorenz
Samsung I5700 Galaxy Spica Android 2.1 Flashing Guide | All About Web & Mobile Application Development
And that?
Code:
Prerequisites
- Android 2.1
- Odin Multi Downloader 4.03 Odin4_03-Spica_ops.zip
- LK2.08 Kernel by LekshaK, Select "Download: i5700_LK2-08_PDA.7z" from http://forum.samdroid.net/f9/lk2-08-original-firmwares-root-new-superuser-wifi-tether-bb-12-07-2010-a-1193/
- Spica Drivers Deposit Files (If it doesn't work install Kies and quit Kies when you need to flash)
- MicroUSB Cable
- Fully Charged Phone
1. Backup all your data
2. Power off the phone, remove your SIM card and SD Card
3. Press and hold Volume Down, Camera and End Call buttons until you see "Downloading... DO NOT TURN OFF TARGET" (Flash Mode)
4. Connect the phone to your PC (It should start prompting for the drivers)
4-1. For Drivers choose "Select from a list or specific location (Advanced)"
4-2. Select the files that was extracted from "Spica Drivers" (If it fails, unplug the phone and install Kies, quit Kies then plug the phone back)
5. Run Odin Multi Downloader (For Vista and Win7 users please Right click and Run As Administrator) [A yellow box with a COM port should show up if connected correctly]
6. Select PDA and choose LK2-08 PDA file. (You have to extract i5700_LK2-08_PDA.7z)
7. Select OPS and select the ops file that came with Odin Multi Downloader (It should be 85 bytes)
8. Select Start
9. The phone will start flashing and automatically restart
10. You will then see a screen with green text, select the 1st option and restart the phone if you don't intend to do anything.
11. After restarting your phone should have a SamdroidTools and Superuser Permissions in the app drawer.
I never had a problem with flash spica using Odin. The drivers are compatibile with Win7 - i used Win7 64bit myself
Had a read through and it's everything I've done already!
Note: Recovery can't clear the dalvik cache or wipe the SD card either - seems like a permissions kind of thing
So maybe option "fix permission" could help.
You can find it in a advanced settings in recovery.
You can also try flash in Odin cyanogenmod 8.3 for odin. Is avaible on samdroid somewhere.
Sent from my HTC Desire using Tapatalk
Please note that this is only a thread on HOW-TO and not a central place on where you can get your firmwares. There's several websites like SamMobile that can help you getting them.
All the Heimdall's instructions will be at the second post.
1. Q/A's (Introduction)
" I'm afraid I'll break my phone/tablet... "
1. What is download mode?
It's a special mode where the partitions are flashed into your phone. It's functionning is simillar to how fastboot works with other devices. (Nexus/HTC) It's normaly accessible by pressing the three-way button combinaison (Power + Home + Vol-) at the same time when turning on your device.
Click to expand...
Click to collapse
2. What's Odin then?
Odin, in this case, (not the mythologic one) is a windows program, a proprietary software from Samsung to flash numerous partitions. (/system, /cache, kernel etc) It is generally only used when in download mode.
Click to expand...
Click to collapse
3. If we have Odin, then why we do need Heimdall?
Heimdall is a cross-platform open source program that uses the same type of communication protocol that Odin uses to communicate with Samsung devices. It's very useful if for example you're using something like Mac OS or Linux. (in which Odin can't work natively without using some sort of Windows implementation)
Click to expand...
Click to collapse
4. Why sometimes I need to have a PIT file when I flash with either of these programs?
A PIT (Partition information table) which it's name indicates, is a file where regroups all your device's partition information. (such as name, size, offset, etc) It is possible to modify it but NOT RECOMMENDED unless you know what you're doing.
Click to expand...
Click to collapse
2. Odin Instructions for Original Samsung Galaxy S and Samsung Galaxy S II "based" devices
" Considered once before the best of Android... "
Device examples:
Samsung Galaxy S (I9000)
Samsung Galaxy S II (I9100)
Samsung Galaxy Note (N7000)
Samsung Galaxy Player/S Wifi (All)
2.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin3 v1.7
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
2.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset some counter)
Note: those 2 last boxes should always be checked
Dump: Not necessary..
Phone EFS Clear: You do not want to make this..
Phone Bootloader update: Not necessary unless you want to flash only the bootloaders. (you probably won't EVER touch this)
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
2.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract the Odin3 v1.7.exe file from the zip
2. Execute Odin3 v1.7.exe
3. Put your device in download mode. To do so, press vol- while pressing the power button. The result of this combination should be this.
Note: The image is a result for the OG SGS based devices, The SGS II based ones should come with this instead after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms/Firmwares, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the files selected were intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!!
Note: If you're flashing Stock (Original) Samsung firmware, you MUST check the box. Failing to do so will likely brick the device...
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
2.4 Misc. Section:
While the Original Galaxy S isn't related, the Galaxy S II based devices have a flash counter regarding on how much time you flash while in download mode. It's count goes up everytime you flash something in this particular mode. When the number is higher than 0, you LOSE your waranty. Be Warned!!
That said, there are ways to fix those problem by either buying a USB jig, or using an app like Triangle Away made by Chainfire.
3. Odin Instructions for the Samsung Galaxy S III "based" devices
" Designed for humans is the new way to go... "
Device examples:
Samsung Galaxy S III (I9300)
Samsung Galaxy Note II (N7100)
Samsung Galaxy Note 10.1 (N8000)
Samsung Galaxy S III Mini (I8190)
Samsung Galaxy Camera (EK-GC100)
3.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin V3.07
- The files you'll want to flash
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
3.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset a counter in older device...)
Note: those 2 last boxes should always be checked
Flash Lock: Not sure what this does
LED Control: This as well
Nand Erase All: You do not want to touch this...
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
UMS: I'm not sure as what this section does, it is greyed out by defaut so it must have some sort of specific usage. (but not for us anyway..)
Bottom side:
Start: Self explanatory...
Reset: Reset all the values to Odin's default.
Exit: Self explanatory again...
3.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Odin307.zip
2. Execute Odin3 v3.07.exe
3. Put your device into download mode. The result should be like this after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!! (Unless if it's going back to the stock Samsung firmware)
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
3.4 Misc. Section:
All the Galaxy S III based devices have a flash counter regarding on how much time you flash while in download mode. It's count goes up everytime you flash something in this particular mode. When the number is higher than 0, you LOSE your waranty. Be Warned!!
That said, there are ways to fix those problem by either buying a USB jig, or using an app like Triangle Away made by Chainfire.
However be careful with the newer Knox bootloaders that came with the newer 4.3 Touchwiz updates as there's NO way of resetting the counter AND/OR downgrading it.
4. Odin Instructions for the Samsung Galaxy S4 "based" devices
" With the increasing popularity comes more restrictions... "
Device examples:
Samsung Galaxy S4 (I9500)
Samsung Galaxy Note II (N9000)
Samsung Galaxy Note 10.1 2014 Edition (SM-P600)
Samsung Galaxy S4 Mini (I9190)
4.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin V3.07
- The files you'll want to flash
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
4.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset a counter in older device...)
Note: those 2 last boxes should always be checked
Flash Lock: Not sure what this does
LED Control: This as well
Nand Erase All: You do not want to touch this...
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
UMS: I'm not sure as what this section does, it is greyed out by defaut so it must have some sort of specific usage. (but not for us anyway..)
Bottom side:
Start: Self explanatory...
Reset: Reset all the values to Odin's default.
Exit: Self explanatory again...
4.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Odin307.zip
2. Execute Odin3 v3.07.exe
3. Put your device into download mode. The result should be like this after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!! (Unless if it's going back to the stock Samsung firmware)
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
4.4 Misc. Section:
All the Galaxy S4 based devices have the Knox flash counter which is MORE PROACTIVE than the flash counter inside the GSII/GSIII based devices. Upon flashing something that has not been signed numerically by Samsung, the eFuse is burned off and there's NO possible way of reverting the counter back to 0. (because of an HARDWARE failure)
PROCEED AT YOUR OWN RISK!
5. Odin Instructions for the Samsung Galaxy ARMv6 "based" devices
" Underpowered, they're still fighting through the end... "
Device examples:
Samsung Galaxy Ace (S5830)
Samsung Galaxy Gio (S5660)
Samsung Galaxy Mini (S5570)
Samsung Galaxy Fit (S5670)
5.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin Multi Downloader v4.42
- The files you'll want to flash
- An "ops" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.
5.2 Little Glossary:
Left side:
One Package: If you have a one package firmware, (one that has every partition regrouped into one) you may check this box and take your one package file from your computer.
Auto-Reboot: Self-explanatory
Protect OPS: Need further info on that one but looks like it protects the internal OPS file from inside the device if you use a OPS while while flashing something.
Reset time: Don't know really what it is. (it looks like it can restart odin after a set number of time after having initially pressed "start")
Note: those 3 last boxes should always be checked
DEBUG ONLY: Well it is what it says. There's no option you'll really use in this part so I won't describe it as it's not necessary.
Right side:
OPS: This serves as the equivalent of PIT for some devices, it has information for the partitions from your device. it comes with a .ops extension.
BOOT: Not sure what this box is. From what I see, this box isn't even used...
Phone: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
EFS: This is the file that contains the most sensible information of your phone (IMEI, S/N, MAC addresses, etc...) it comes also with the .tar or .tar.md5 extension.
One Package: If you do happen to have a "One Package" file, you can use it to flash all it's contents into your device.
5.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the OdinMultiDownloaderv4.42.zip
2. Execute Odin Multi Downloader v4.42.exe
3. Put your device into download mode. The result should be something similar to this after you maybe had this beforehand.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels) (Modem: Radio/Baseband) (CSC: Csc file) (EFS: EFS file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .opt file was selected when trying to flash, ensure that "Protect OPS" at the left is CHECKED!!
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.
5.4 Misc. Section:
I would need more information. If you could send some, it would be appreciated!
6. Heimdall Instructions
" At last, an alternative has been found... "
Heimdall should work at least with the following devices (I'll add more if necessary)
Samsung Galaxy S (I9000)
Samsung Galaxy S II (I9100)
Samsung Galaxy S III (I9300)
Samsung Galaxy S4 (I9505)
Samsung Galaxy Player (All)
6.1 Heimdall Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers (for Windows only)
- WinUSB drivers installed (From zadig.exe, once again Windows only)
- Udev rules set-up for your Samsung device (for Linux only)
- Heimdall's Official Webpage
- The files you'll want to flash
- An "pit" file (needed for Heimdall to actually flash on your device)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
6.2 Little Glossary:
Load Package Tab:
We won't really use it... Unless you have an Heimdall package but you should already know how to use it...
Flash Tab:
PIT: Self explanatory once again, the file should normally come with a .pit extension. Also you have to select it in order to be able to flash (unless you're using the terminal)
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary to check it when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Add: Pretty simple, Adding the partition you wanted to be flashed according to the "pit" file you've selected
Remove: Pretty simple once again, this time it's to remove the partition you've selected.
No reboot: Won't reboot after all the flashing has been done.
Resume: (use after "No reboot") This is only to continue the session of "flash" as of after you've flashed something with Heimdall and you decided to press "No reboot", Heimdall stops communication with your device and you would need then to reboot it back into "download" mode to get it back working again
Create Package Tab:
Won't really explain because it's not that "much" used so it won't be useful for the purpose of this thread
Utilities Tab:
Detect Device: Obvious but for debugging purposes it can be useful.
Close Pc Screen: This affects more older Samsung devices (like the original Galaxy S) that when something went wrong with a flashing this picture would get in when you turned on your device. This button fixes it.
Download Pit: Here you can grab the .pit file from your device and save it through your computer. (Useful if you do need one but can't find it anywhere or for specific debugging purposes)
Print Pit: Here you can see the content of the .pit file from either two places: From your device or from a pit file you have on your computer. The result will be displayed on the "Output" window.
Partitions:
IBL+PBL: Primary bootloader, you mess with it, your device is a plastic brick... (Normally it should be a file named boot.bin)
SBL: Same thing as IBL+PBL. (It should be a file named sbl.bin)
SBL2: Acts as a backup of the original SBL partition. I don't really know if this could boot up when the first SBL is borked up.
PARAM: It's a file that "controls" the bootloaders on the initial device's boot. (param.lfs)
CACHE: It's actually your cache partition (The older Samsung models would have a file named cache.rfs, newer Samsung models though should be something like cache.img)
EFS: This partition is very important because all the "sensitive" data of your device is there: S/N, IMEI, MAC addresses. (Older models: efs.rfs, Newer models: efs.img)
RECOVERY: That's the recovery partition, where your recovery will be at. It serves as a unused kernel partition for the original Galaxy S. (It should be something like recovery.img for newer devices)
FACTORYFS: This is where your OS (/system) is. (Older models: factoryfs.rfs, Newer models: factoryfs.img)
KERNEL: It is what it is basically. It's where your kernel will be flashed. (Older models would be zImage/boot.img/normalboot.img where's the newer models comes more with boot.img)
6.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Heimdall on the "Flash" tab actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Heimdall zip you download
2. Execute Heimdall-frontend.exe on Windows, the Heimdall executable on Mac OS or on your Linux terminal, type "heimdall-frontend"
3. Put your device into download mode.
4. Plug your device into your computer. If you go to the "Utilities" tab and press the "Detect Device" Button. If it has been detected, you can continue on.
5. Go on the "Flash" tab. From then, you need to take up a .pit file that has been saved into your computer.
6. After taking your .pit file, you'll need to add a partition. Then selecting the partition you'll need to flash from the dropdown menu.
7. Be sure to check carefully each partition so you know that each partition equals their file counterparts.
8. When that is done, depending on if you're going to stock or not, check the "Repartition" box.
9. After you've been SURE that ALL those check-ups have been made, press the "Start" button.
10. Let the program do it's things. Then when it's done, your device should reboot automatically and it's a SUCCESS!!
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
6.4 Misc. Section:
- Heimdall CAN'T possibly work with every device. You mostly have to test for yourself if Heimdall works for you.
- When you install your drivers from zadig.exe, it "overwrites" Odin drivers which will make your device unusable with Odin. It's kinda like a trade. If you want to use Odin, you can't use Heimdall and vice-versa.
- If you happen you have an "Odin" flashable package and you want to flash using Heimdall, you can remove the ".md5" extension from your file and then extract the ".tar" file contents, you should get each of the partitions that can be flashable via Heimdall.
7. Thanks
" The roots provided by them grew into this tree... "
Google
Samsung
@SamHaLeKe
@Benjamin Dobell
@Perseus71
@LuigiBull23
Reserved...
wow great tutorial iknow how hard to be a newbie coz i experienced of hard time flashing when i newly purchased sgs 4 .
btw ur the man, great effort! i know someday we will be crowded here because of this tutorial
keep up the good heart sir
Gonna subscribe and hit 5star.
it should be sticky thread too
Sent from my YP-G1 using xda premium
rockerblood said:
wow great tutorial iknow how hard to be a newbie coz i experienced of hard time flashing when i newly purchased sgs 4 .
btw ur the man, great effort! i know someday we will be crowded here because of this tutorial
keep up the good heart sir
Gonna subscribe and hit 5star.
it should be sticky thread too
Sent from my YP-G1 using xda premium
Click to expand...
Click to collapse
Well I think it should have been better to add it before but it's better now than never. Also I'll put all the pit files here tomorrow so if you want them when you'll flash, they will be there and you wont have to search around and around.
i think thats a good idea
keep up the good heart and work sir
Thanks for posting. I flashed TerraSilent kernel.
However, I still don't have root access. As I posted before, I cannot find a root method for 2.3.6 on the US Player 4, and this seems to still be the case (for whatever reason after flashing, About Phone now reports Android 2.3.5, but I know this is impossible, as I did not flash any ROM).
(Also, right before the TerraSilent boot logo comes up, the upper half of the display shows some lines for a split second. This is not an issue, just wondering why it is there.)
TheTehk17 said:
Thanks for posting. I flashed TerraSilent kernel.
However, I still don't have root access. As I posted before, I cannot find a root method for 2.3.6 on the US Player 4, and this seems to still be the case (for whatever reason after flashing, About Phone now reports Android 2.3.5, but I know this is impossible, as I did not flash any ROM).
(Also, right before the TerraSilent boot logo comes up, the upper half of the display shows some lines for a split second. This is not an issue, just wondering why it is there.)
Click to expand...
Click to collapse
But AFAIK, I never knew that the US player had 2.3.6. Anyway you can root with which ever GB root you can find as this kernel is insecure which means that you have a root shell by default.
zaclimon said:
But AFAIK, I never knew that the US player had 2.3.6. Anyway you can root with which ever GB root you can find as this kernel is insecure which means that you have a root shell by default.
Click to expand...
Click to collapse
Got mine rooted now, thanks. I'm used to rooting and contributing for/with devices like the Samsung Moment and other s3c6410-based devices so this stuff is all new to me.
Yep, mine shipped with 2.3.6. I might make a guide so that others in the same boat as me know what to do.
Hey I said earlier this week I would put some pit files, well it better now than never. Sorry for the delay. With school and ICS porting, I don't have really the time to do it. Anyway the pit are here now.
Posting this in a few places but I recommend you note in the OP that this will always be best accomplished using a STOCK Samsung usb cable. Depending on how close to "bricked" the device is it is very possible the device will not be recognized by the pc unless the stock cable is used. I think this little bit of information will be very helpful and may save a lot of heartache for some in the future.
Jiggity Janx said:
Posting this in a few places but I recommend you note in the OP that this will always be best accomplished using a STOCK Samsung usb cable. Depending on how close to "bricked" the device is it is very possible the device will not be recognized by the pc unless the stock cable is used. I think this little bit of information will be very helpful and may save a lot of heartache for some in the future.
Click to expand...
Click to collapse
Alright it's taking into note. Thanks!
Alright I was given the 4.0 with it running an ICS ROM. I was not familiar with Samsung devices and rooting, and in thinking it was like my DINC2, I put it into recovery and since then I have tried to read all the forums to get it to work and to put it back to a stock ROM....... I haven't found a solution, and I am not sure if I missed a step in a forum, but I can get the device into a different recovery with blue lettering and only a few select options, but as far as getting it to boot up with the actual ROM I have had 0 success on any of it.... Any help?????? P.M. me or I can give my email if it would help at all, or any help what so ever would be great. Thanks.
P.S. It is the US version if that was a question.
Brennon19968 said:
Alright I was given the 4.0 with it running an ICS ROM. I was not familiar with Samsung devices and rooting, and in thinking it was like my DINC2, I put it into recovery and since then I have tried to read all the forums to get it to work and to put it back to a stock ROM....... I haven't found a solution, and I am not sure if I missed a step in a forum, but I can get the device into a different recovery with blue lettering and only a few select options, but as far as getting it to boot up with the actual ROM I have had 0 success on any of it.... Any help?????? P.M. me or I can give my email if it would help at all, or any help what so ever would be great. Thanks.
P.S. It is the US version if that was a question.
Click to expand...
Click to collapse
Sorry for the late reply but try this:
http://forum.xda-developers.com/showthread.php?t=1531850
zaclimon said:
Sorry for the late reply but try this:
http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
Alright thank you. I will have to try it when I get home from the hospital visit.
Sent from my Incredible 2 using xda app-developers app
SGP YP-G70 International Heimdall Froyo Stock Rom with bootloaders
zaclimon said:
Heimdall Instructions
I generally prefer flashing with heimdall because it's better than odin (but less simple) and it's cross platform.
More information on Heimdall: http://forum.xda-developers.com/showthread.php?t=755265
3.1 Heimdall Prerequistes
- Samsung USB Drivers
- Heimdall
3.2 Flashing With Heimdall
3.2.1 Drivers installation (Windows)
These are a FIRST time installation only for the libusb drivers.
1. Extract the heimdall folder somewhere in your computer.
2. Go in the heimdall folder and then drivers. You should see a file named zadig.exe
3. Execute zadig.exe and then check list all devices
4. You should see a samsung device listed.
5. Install the drivers, you should have an error concerning certificate (It's NORMAL, install them anyway). You must do this in home screen and in download mode.
3.2.2 Flashing
6. When this is done, Open heimdall-frontend.exe,
7. Go in the flash section and take your .pit file according to your device.
8. Select the partitions you want to flash and take the file according to it.
9. Ensure that all the partitions you've selected are good.
10. Flash!!
11. Your device should reboot by itself and it should work!:good:
If you have more questions/suggestions, ask them in the thread and I will answer it as soon as I can.
4. Pit Files
Here's the pit files needed if you need to re-partition
4.0 Intl: 4.0 Intl Download
4.0 Us: 4.0 Us Download
4.0 Kor: 4.0 Kor Download
5.0 Intl: 5.0 Intl Download
5.0 Us: 5.0 Us Download
5.0 Kor: 5.0 Kor Download
Thanks:
Google: For such a good OS
Samsung: For making such good devices (and Odin )
Benjamin Dobell: For Heimdall
SamHaLeKe: For the USB drivers
All the uploaders of the pit files
Click to expand...
Click to collapse
Can anyone share the right file or files to flash SGP YP-G70 International (with physical home button) with Stock Froyo (or other ROM) wich inclues the bootloaders?
How should I proceed to flash it?
Despite all information we find here there is always some details we don't know how to handle. I followed the instructions with Odin and the result was: PASS (green) but SGP wont reboot or turn on. I always think there is some missed detail.
Please help me to have it working again so I will right a full restoring procedure from the begining (hard brick) until the end to help our brothers to recover their devices as well.
I thank you very much in advance
mrlightman said:
Can anyone share the right file or files to flash SGP YP-G70 International (with physical home button) with Stock Froyo (or other ROM) wich inclues the bootloaders?
How should I proceed to flash it?
Despite all information we find here there is always some details we don't know how to handle. I followed the instructions with Odin and the result was: PASS (green) but SGP wont reboot or turn on. I always think there is some missed detail.
Please help me to have it working again so I will right a full restoring procedure from the begining (hard brick) until the end to help our brothers to recover their devices as well.
I thank you very much in advance
Click to expand...
Click to collapse
Seems that you never tried with heimdall as I told you right? Also because your case is very rare, (you're the 1st or the 2nd with this particular hard brick case), I never really took the time to write down. Well first of all, is your device recognized by your computer outside of the download mode?
SGP 5.0 YP-G70 wont turn on
zaclimon said:
Seems that you never tried with heimdall as I told you right? Also because your case is very rare, (you're the 1st or the 2nd with this particular hard brick case), I never really took the time to write down. Well first of all, is your device recognized by your computer outside of the download mode?
Click to expand...
Click to collapse
I haven't tried yet cause I'm not sure how to do it. I was searching for ROMs to use in Heimdall and I found just the PIT file.
Can I use the exact same ROM I used to flash with Odin?
The device is recognized by PC just when I have it into download mode using Adam Outlers method (Unbrickable Resurrector)
mrlightman said:
I haven't tried yet cause I'm not sure how to do it. I was searching for ROMs to use in Heimdall and I found just the PIT file.
Can I use the exact same ROM I used to flash with Odin?
The device is recognized by PC just when I have it into download mode using Adam Outlers method (Unbrickable Resurrector)
Click to expand...
Click to collapse
Yeah you can use the same rom as what you used with odin. You can follow this thread instruction on how to. You may need to flash the bootloaders so here's the name of them
IPL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
SGP 5.0 YP-G70 wont turn on
zaclimon said:
Yeah you can use the same rom as what you used with odin. You can follow this thread instruction on how to. You may need to flash the bootloaders so here's the name of them
IPL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
Click to expand...
Click to collapse
Well I'm trying to do that. Heimdall requires a Pack and I'm trying to use the ROM (tar) files I used to flash with Odin. The matter is that Heimdall always says firmware.xls is missing from the package and maybe that the exact point wich drove me flaw (I dont know).
Can you please share with me the right package including the firmware to make me able to flash it?
I already have the PIT file and I remember that the SGP was using Froyo before all my mass (having it bricked). My SGP is 5.0 YP-G70 International with physical home button.
Hi.. I just saw the new TWRP and liked it alot!. So i downloaded the TWRP for Trebon and also downloaded the Odin3 on my pc. And then i put my phone into the download mode and connected by USB. But the ID COM box wont come up.. The ODIN3 is just not detecting my phone .. Dunno why..
I tried installing drivers for my phone but it didnt work.
I also installed Kies after that but no use.. I used 2 versions of Odin3 i.e. Odin3 v1.85 and Odin3 v3.x.. But still its not detecting my phone..
So can anyone pleazz help!!
(Using SGA+ with the cm10)
are you sure you installed the drivers
* disable or remove kies
* Install drivers again (windows) select correctly 32/64 bits
or try this simple method.
INSTALLATION 1:
0. Uninstal previous Samsung USB drivers from Control Panel and Device Manager.
1. Unpack the .rar archive and run the installer from "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.20.0\setup.exe" and proceed with the installation steps.
2. Switch your Samsung phone into download mode
3. Connect it to your computer via USB cable.
4. If your phone is still not correctly recognized by Odin - try the second method.
INSTALLATION 2:
0. Uninstall previous Samsung USB drivers from "Programs And Features" and "Device Manager".
1. This is the "have disk" method. You have to follow every step in this guide.
2. Unpack SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.20.0.rar to some location, eg. C:\.
3. Switch your Samsung phone into download mode.
4. Connect it to your computer via USB cable.
5. Your phone should become discovered by Windows as some device. In my case, Windows has found my SGS i9000 as a "Gadget Serial" device.
6. Go to Windows Device Manager. Right click on the device your phone has been discovered as (eg. "Gadget Serial" in my case) and choose "Update driver" option from the context menu.
7. Choose "Search my Computer...", check "Include subfolders" option and point the updater to the folder where you've had unpacked the drivers .rar archive to, eg. C:\SAMSUNG USB Drivers for Mobile Phones (x86 & x64) v1.5.16.0.
8. The driver should install automatically.
9. It may happen that after the installation some new "unknown device" ("Samsung Modem" in my case) would appear in the Device Manager. Complete 6 & 7 step for that device and any other new device that may appear afterwards.
10. Restart your computer.
11. Done!
drivers link (latest)
source - this helpful thread
Did all that.. but still when i connect my phone via usb , the pc detects it but not ODIN.. Can it be because of the custom rom ??
Suyash1996 said:
Hi.. I just saw the new TWRP and liked it alot!. So i downloaded the TWRP for Trebon and also downloaded the Odin3 on my pc. And then i put my phone into the download mode and connected by USB. But the ID COM box wont come up.. The ODIN3 is just not detecting my phone .. Dunno why..
I tried installing drivers for my phone but it didnt work.
I also installed Kies after that but no use.. I used 2 versions of Odin3 i.e. Odin3 v1.85 and Odin3 v3.x.. But still its not detecting my phone..
So can anyone pleazz help!!
(Using SGA+ with the cm10)
Click to expand...
Click to collapse
seems to be driver issue
try to connct with other pc or laptop
see whether pc detect it or not
Suyash1996 said:
Did all that.. but still when i connect my phone via usb , the pc detects it but not ODIN.. Can it be because of the custom rom ??
Click to expand...
Click to collapse
boot your phone to download mode normaly by pressing the key combo, not from twrp and should recognized.
Had the same issue.Gl
Thanks.. but.. i guess it was a problem wid d rom.. i flashed another one and it wurkd!