Related
Odin Stock Flashing
Odin : http://www.sdx-downloads.com/devs/noobnl/Odin3+v1.61andepic.pit.zip
USB driver, under the Software category here: http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
* IMPORTANT: Make sure you have installed the drivers before starting. Also, remove the SD card from the phone (this may not be necessary, but having the SD card installed has caused Odin to fail for a number of people, so might as well just do it).
1. Open odin
2. Put your phone in download mode (Shut it off, wait for lights to all go out, then hold 1 on the keyboard while powering up)
3. Connect phone (you should see odin put a Com4 or something like that in the first box. The actual number is NOT important what is important is something popped up there when you connected your device, meaning ODIN can see it)
4. Select the victory_8G_100528.pit on the right in the pit section
5. In the PDA Section place the full Stock DI18 tar (SPH-D700-DI18-8Gb-REL.tar.md5 approx 255 MB) for a full wipe and full return to stock. You can get the file from a number of sources here: http://www.multiupload.com/X9AB1U56JV
6. Hit start. It will do its thing. Doesn't take long you can see the progress bar. If it sits on File Analysis for longer than 30 seconds its not going to happen. See the troubleshoot section below.
7. Device should reboot and should be done. You will have to root / install ClockworkMod.
Click to expand...
Click to collapse
I've seen a few youtube vids of people just using the tar in the pda file and flashing to dk28, haven't seen anything on placing the pit file in pit section. LMK please and I THANKS you in advance
No, the pit isn't necessary. Most of the time.
It contains a map for the partitions and can be used to fix partitions or adjust partition sizes (the victory pit made one partition a couple megs bigger and another a couple megs smaller). Most of the time you can get by without it.
DiGi760 said:
No, the pit isn't necessary. Most of the time.
It contains a map for the partitions and can be used to fix partitions or adjust partition sizes (the victory pit made one partition a couple megs bigger and another a couple megs smaller). Most of the time you can get by without it.
Click to expand...
Click to collapse
Great, Thanks! Quick question again ... What will be the exception? (referring to how you said MOST of the time)
All the current upgrade methods involve ODIN or don't explain the heimdall version in depth..
I HAVE NOT TRIED THIS YET - waiting for confirmation from someone who knows more than me.
Heimdall 2.3.3 Update v0.9 - UNTESTED
1) Back everything up. Titanium etc..
2) Download the new Stock 2.3.3 file, as found in Overcome 2.0beta http://www.multiupload.com/F6D7U1RUHD
2) Extract GB-stock-safe.zip into a folder.Go into the folder.
3) Now extract the GB_Stock_Safe_v1.tar file into another folder.
3) Copy the gt-p1000_mr.pit and the correct modem.bin into the extracted GB_Stock_Safe_v1.tar folder. So all the required files in one place now.
4) Plug Tab into computer and go to Download mode. (You can do this, by shutting/powering down your Tab. Once shut/powered down, hold down the Volume Down button and the Power button together until Download screen appears) or much easier if you have adb
Code:
adb reboot download
5) (Once in Downlaod mode) From the command line, run this function from the folder where the GB_Stock_Safe_v1.tar file was extracted, and you copied the gt-p1000_mr.pit and modem.bin file.
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
6) basically the movinand.mst and hidden.rfs files are still in the folder but not referenced.
Is this correct !? Can someone confirm or deny please?
I'll update this post with corrections
Just used these instructions to take a stock Froyo Galaxy Tab to Gingerbread stock version (Overcome restock v5) using only Linux.. and then to CM7.
I installed the deb package from the Heimdall web site and installed it into my Ubuntu 10.10 install. Worked like a charm. Thanks a bunch for posting this. Saved me trying to mess around with Windows.
Can anyone tell me if it's possible to flash/change/update just the baseband modem in my AT&T Samsung Galaxy S3 SGH-I747 without rooting the phone? After installing the latest update via the Samsung KIES software my phone reception has dropped a good bit. I no longer have service where I used to. My phone calls are also very choppy in the fringe reception areas, where before they were significantly better. I live in an area where 4G/3G coverage is fairly spotty, so EDGE is my primary network.
I wish I could remember which baseband version it had before the update so I could roll back to it, but I don't, so it may take a few tries before I can find the correct baseband version. Before the update I know I had ICS v4.0.4......not sure on Baseband version. Now I have Jelly Bean v4.1.1 (which I would like to keep) with Baseband I747UCDLK3.
I've tried using Odin v3.07 and the "AT&T Models Only! (I747U)" files via the link below and inserting the correct file path into the "Phone" section without any luck. Odin detects my phone, starts the process, but fails. http://forum.xda-developers.com/showthread.php?t=1831898
I've read to only use the "PDA" section in Odin to flash, but the files via the link below dont seem to have the proper file to use with the "PDA" seciton in Odin......am I missing something critical here maybe?
I then came across the following link where other people have used Odin to flash the baseband modem and seem to have been successful. http://forum.xda-developers.com/showthread.php?t=927568
Thanks for any help because I've spent hours searching the forum and Internet trying to find an answer!
I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.
I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!
SideWinder4x4 said:
I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!
Click to expand...
Click to collapse
i believe HON-HLOS.bin is your modem
SideWinder4x4 said:
and when I open or extract the files using 7zip,
Click to expand...
Click to collapse
Do not actually extract the files or else you will ruin the MD5 checksum and the flashing process will fail. Simply replace the modem file with the one you want to use by taking a "peek" in the actual TAR file.
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
I've tried this method using Ubuntu Terminal to create a new modem.tar.md5 file, but everytime I try to flash with Odin, it fails. What am I doing wrong. Thanks for any further advice, this is driving me crazy!
My steps are as follows:
1.) I'm unzipping the correct modem files (modem_CWM_I747_UCLH9.zip) from this link - http://forum.xda-developers.com/showthread.php?t=1831898
2.) I'm taking the "modem.bin" file and copying it to Ubuntu desktop folder
3.) I'm opening Terminal
4.) I change to the Desktop directory
5.) First command...without the quotes is "tar -H ustar -c modem.bin > modem.tar"
6.) Second command...without the quotes is "md5sum -t modem.tar >> modem.tar"
7.) Third command...without the quotes is "mv modem.tar modem.tar.md5"
8.) I copy that "modem.tar.md5" file back to my Windows 7 based computer
9.) I rename "modem.tar.md5" to "modem.tar"
10.) I press and hold the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted press the "Volume Up" key
11.) On the screen I see the following: ODIN MODE, PRODUCT NAME: SGH-I747, CUSTOM BINARY DOWNLOAD: No, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, QUALCOMM SECUREBOOT: ENABLE
12.) I then open Odin v3.07 using defaults
13.) Odin recognizes my phone on COM8 with a blue teal colored box
14.) I press the "Phone" button and select the "modem.tar" file
15.) I press the "Start" button and it shows "modem.bin" in the first box in white, but about 5 seconds later it turns red and says FAIL!
The Odin message box indicates the following:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> modem.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Well, try naming it NON-HLOS.bin instead of modem.bin. Also, don't rename it after you make the tar.md5 file.
Solution Found
I finally got this figured out. Thanks for all of the help and ideas along the way!
The key tip was found in this thread - http://forum.xda-developers.com/showthread.php?t=1658809
Just to simplify things for others in the future, the steps I performed were as follows:
1.) Installed Cygwin from http://www.cygwin.com/
2.) Started Cygwin Terminal
3.) Put the SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 firmware file into the following folder I created "c:\baseband"
4.) In Cygwin, typed the following command without the quotes "cd /cygdrive/c/baseband"
5.) In Cygwin, typed the following command without the quotes "tar -xvf SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 NON-HLOS.bin"
6.) In Cygwin, typed the following command without the quotes "tar -H ustar -c NON-HLOS.bin > baseband.tar"
7.) Pressed and held the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted pressed the "Volume Up" key to enter "Download Mode"
8.) I then opened Odin v3.07 using defaults
9.) Connected my phone to my computer using the proper USB cable
10.) Odin recognizes my phone on COM8
11.) I pressed the "Phone" button and selected the "baseband.tar" file I created in step #6
12.) I pressed the "Start" button and about 30 seconds later it finishes and the box turns green and the phone rebooted.
Thanks Sidewinder. Its very informative.. I am facing a strange issue on my Galaxy R ever since I upgraded to ICS and JB (stock/ custom ROMs).
Very often I get my calls disconnected while speaking. This was not the case with Ginger bread..
Today followed your procedure to extract the modem.bin from stock GB rom and flashed to my JB custom ROM (Carbon).. Looks good so far..tried
with test calls - seems to be OK.. Will observe for some more time.
You're Welcome asbalaji. I'm glad what I posted helped you out. My phone reception issues improved a lot after downgrading to an older modem.
Anonymously_Unknown said:
I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.
Click to expand...
Click to collapse
I am in desperate need of a baseband to flash via ODIN for a boostmobile galaxy S3
---------- Post added at 07:00 AM ---------- Previous post was at 06:24 AM ----------
mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
Basebadn boostmobile s3
Hello,
I have a rooted Galaxy Gio (GT-S5660) with CWM and CM10.1 (from
Maclaw). I now need to restore it to factory firmware,
but am running into a brick wall no matter what I try.
I have downloaded S5660XXKTK_S5660COVKS1_COV.zip and tried with
Odin but that fails (don't remember the error message). And
anyway, it seems really unnecessary to boot into Windows to do
this, one should be able to do it all from Linux.
Is there any way to restore factory firmware using adb/fastboot?
adb connect to the phone etc., but fastboot doesn't work, it just
gets stuck in the "< waiting for device >" state.
(Yes, of course I run the adb/fastboot commands as root.)
I haven't found any tutorials/howtos on how to do this in Linux,
can anyone write one or point me in the right direction?
Or, if Odin is the only way, what files do I need to download to
make it all work? Obviously S5660XXKTK_S5660COVKS1_COV.zip isn't
enough.
I have tried the instructions found at android.gs, androidaddition.com
and mobotechie.com (seems I'm not allowed to post links...) but
nothing works.
Thanks,
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Click to expand...
Click to collapse
No I did not extract the S5660XXKTK_S5660COVKS1_COV.zip , I've assumed it's supposed to be used as-is, just like custom ROMs.
But there is no .ops file in the archive:
Code:
$ unzip -t S5660XXKTK_S5660COVKS1_COV.zip
Archive: S5660XXKTK_S5660COVKS1_COV.zip
testing: S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 OK
testing: SS_DL.dll OK
No errors detected in compressed data of S5660XXKTK_S5660COVKS1_COV.zip.
And no .ops file in the .tar.md5 file within the archive either:
Code:
$ unzip -xp S5660XXKTK_S5660COVKS1_COV.zip S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 | tar tvf -
-rw-rw-rw- a.oldak/0 18784256 2012-03-04 09:18 amss
-rw-rw-rw- a.oldak/0 459132 2012-03-21 09:40 arm11boot
-rw-rw-rw- a.oldak/0 6451200 2012-03-21 09:40 boot.img
-rw-rw-rw- a.oldak/0 19116032 2011-10-14 15:08 csc.rfs
-rw-rw-rw- a.oldak/0 786432 2012-03-21 10:11 mibib
-rw-rw-rw- a.oldak/0 566888 2012-03-21 10:11 oemsbl
-rw-rw-rw- a.oldak/0 368640 2012-03-21 10:11 qcsbl
-rw-rw-rw- a.oldak/0 6864896 2012-03-21 09:40 recovery.img
-rw-rw-rw- a.oldak/0 212430848 2012-03-21 09:40 system.rfs
Now what?
http://www.4shared.com/rar/ttIilfrh/Odinv442GIO_v10ops.html
Put .tar.md5 file in one package and flash. Don't forget .ops file
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
URL removed since I'm a new user and as such not permitted to post links...
Put .tar.md5 file in one package and flash. Don't forget .ops file
Click to expand...
Click to collapse
So, I'm supposed to extract the .tar.md5 file from the .zip file, separately download a .ops file from some completely other site (riddled with ads and popups and requiring registration, btw), and create a new .zip file containing the .tar.md5 file and the .ops file? Is that correct, or do I need to bundle more files into the new .zip file?
And in Odin (version 3.07), should I add the file as a PIT, Bootloader, PDA, PHONE, or CSC?
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration http://hotfile.com/dl/140235732/ec749d2/?lang=ro
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration (removed as I'm not allowed to post links...)
Click to expand...
Click to collapse
Well, that almost worked. I put the phone in download mode, connect it to a USB port, start Odin, the phone is detected as COM8, I add the .ops file, check "One Package" box, and add the .tar.md5 file. Odin has up until this point replied with this in the Message box:
Code:
<1> Added!!!
<1> Detected!!!
Check MD5 Filename : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Open File Name : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Check MD5 ...
Tail MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Image MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Check MD5 ... ok
The I click the Start button in Odin. The Message box is cleared, and this appears:
Code:
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
And after a few more seconds, this line is added:
Code:
<1> --- cannot open the usb serial port. code: 32
It doesn't matter whether I start Odin as Administrator or a regular user, the phone is detected but the "error 32" appears when trying to flash. The phone is the only thing connected to any USB port.
Any ideas?
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Click to expand...
Click to collapse
1. USB debugging was not checked. Is it supposed to be?
2. Kies was installed, I guess perhaps drivers come along with that? I just deinstalled Kies, and now Odin doesn't detect the phone any more. Should I install just some drivers and not Kies? If yes, which drivers, where do I find them?
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Click to expand...
Click to collapse
The phone can still boot, and USB debugging is activated.
To solve the error code 32 problem, people on forums suggest killing Kies using the Task Manager, and trying out different USB ports and making sure I use the USb cable that came with the phone. Well, I have tried reinstalling Kies, rebooting, deinstalling Kies but keeping the USB drivers, different USB cables and different USB ports, but no luck... nothing works. The phone is not detected by Odin any more.
It is detected by adb under Linux, though, so USB is still working.
When searching for a 3 file ROM I found the pages
www modaco com /topic/361399-latest-odin-309-odin-185-odin-183-all-versions-samsung-rom-flashing-tools/
and
www modaco com /topic/361286-18072013-latest-samsung-usb-drivers-for-mobile-phones-15270-win-87xp-adb-fastboot/
so I downloaded the latest Samsung USB driver, and made sure I was using an Odin version compatible with my phone.
And still, now after reinstalling Kies, Odin does not even detect the phone any more. Windows chimes when the phone is plugged in, but it does not appear in Odin, regardless of whether I start Odin before or after plugging in the phone, and regardless of whether I run Odin as administrator or not.
Seriously, is there no way to do all this using adb and fastboot under Linux? I get more and more homicidal when I have to spend time using Windows.
I sent you PM
EDIT : http://hotfile.com/dl/106492222/cc53f0f/S5660_XXKB9_OXXKB8.rar.html download this
http://droidangel.blogspot.ro/2011/05/procedure-how-to-flash-updateupgrade.html this is tutorial
Gyovany96 said:
I sent you PM
EDIT : (URL removed as I don't have permission to post them... moronic forum rules...) download this
(URL removed as I don't have permission to post them... moronic forum rules...) this is tutorial
Click to expand...
Click to collapse
Well, I finally managed to flas in Samsung stock firmware.
The instructions on the page
nguyenkieuhung1984 blogspot se /2012/01/how-to-upgrade-samsung-galaxy-gio-s5660_13.html
comes closest to describing what I did, except I used S5660XXKTK_S5660COVKS1_COV.zip and GIO_v1.0.ops .
I don't really know what I did to resolve the USB connections problems, but hey, when using Windows it's all trial-and-error, right?
First, install, deinstall and reinstall Kies a couple of times, and inbetween installs try the Odin procedure described in the nguyenkieuhung1984 blog mentioned above. And download the very latest Samsung USB drivers (I used 1.5.27.0) and install that. Repeat these steps until you feel like vomiting all over your keyboard. Oh, and install Odin 4.42 too while you are at it. And keep SS_DL.dll and GIO_v1.0.ops in the same folder as the Odin executable file. I don't know if it matters, but getting Windows to work is 80% magic, 15% luck and 5% skills, so why not?
Then reboot to Linux, read mails, surf, code, whatever is needed to regain sanity.
Reboot into Windows, install Kies again, including the bundled USB driver. After Kies has installed, verify that the Samsung USB driver version is still 1.5.27.0 and not whatever version came with Kies (I think Kies came with 1.5.23.0 ?). Anyways, 1.5.27.0 is what's on my system now, along with Kies 2.5.3.13043_14.
Start Kies and close it. Do NOT go into Task Manager to kill off any Kies processes; at least I didn't. Other tutorials tell you to, at least if you run into the error code 32 problem. Well, I didn't have that problem on my 30th attempt (on attempts 10-29 I did, though...).
Follow the steps on the nguyenkieuhung1984 blog mentioned earlier in this post, replacing filenames if needed (like I did, I mentioned that at the start of this post...).
The phone might now enter a reboot loop (mine did). Press and hold the Power and Home buttons to reboot the phone into the bootloader(?), and there you wipe settings and caches (two different wipes if I remember correctly).
The phone should now boot to stock firmware. Enjoy Android 2.3.6 or whatever Samsung ROM you selected.
It's recomended to "wipe data/factory reset" in recovery mode after you flash a stock ROM. But, enjoy ROM finally
Sent from my GT-S5660 using Tapatalk 2
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
link is restricted
Bro. Share file pls on your googledrive. We cantdownload it
Flar4eg said:
Bro. Share file pls on your googledrive. We cantdownload it
Click to expand...
Click to collapse
Excuse me, is that I uploaded the files to my google drive cloud and I detect a dll, or part of the flashtool as a virus, now I upload it again and put the link
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
multiuploader error: WinDNWApi.dll file could not be found.
Skyfall191299 said:
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Click to expand...
Click to collapse
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Skyfall191299 said:
https://mega.nz/file/eWRkiCwI#XP0yMOiBsfkUKIoxhKaZkLIgdhkwnEtiyVHqixMu8NI
Click to expand...
Click to collapse
getting error that el3mon_dram not found. can you help me?
Hello someone has the files ? The download link is inactive
The download link is inactive, please active or reupload please.
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
good jod
im follwed to this instruction but all links not woriking
pla give me ur telegram or whtas app
and upload files to the new link plz
eldon301 said:
can anybody please explain how to make these files I have my Sboot.bin which was in the phone, I don't understand how to use hex editor. can some plz assist me, working on a750g. broke bootloader by flashing wrong firmware a750f after MDM bypass. software ver U1ARL3 for sboot
here is my sboot, can someone please create or show me how to create with hex https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=sharing
Click to expand...
Click to collapse
how to create with hex bro ?
links not woriking
link isn't working please fix
akbarshoxdedamirzayev said:
how to create with hex bro ?
Click to expand...
Click to collapse
Find the exact firmware that’s currently in the device, extract sboot from the firmware. You need to find correct location of bl1 bl2 el3 and others, names correspond to which is cut. You need 5 files from sboot. Am stuck on the forth file failing and I still don’t understand how to find them. What I did was follow others with exactly the same problem to see and understand how they got there’s and then tried it on my sboot. I am failing on part4 don’t even know how to make a cfg but from what I understand e for exynos and the number after so mine is e7885. Still not sure like I said
http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip/file download link
Skyfall191299 said:
First of all I want to thank @zogu without him, this guide would not be possible, This guide is for phones with Hard Brick, where the bootloader is destroyed and there are no tools that recognize the phone as odin
When you connect phones without a bootloader, Windows detects them as exynos9820 in device manager.
All of this is accomplished by trial / error method
I repaired my g975f and I have U3 and U8 files only for this model, but I will try to explain how to prepare files for any other model.
We have to use the same bootloader version that was previously on the phone, or if you're not sure, use the latest sboot.bin.
Plug in the phone and press and hold the power button.
Windows will detect the exynos9820 device, install the driver:
click manually,
com and lpt ports,
select the Driver Exynos USB Mode folder
Now we have to copy
WinDNWApi.dll
in:
C: \ Program Files \ Samsung \ Exynos USB Driver \ Drivers
There probably isn't this folder, just create it and copy the files.
Now we have to create the boot files.
Using lz4 1.9.2 we can unzip the sboot.bin.lz4 to sboot.bin and then be able to edit it, everything is explained in a guide inside the file
Download the last sboot.bin that was on your device
Now you have to extract the partitions from this file
In some hex editor, create 4 files and extract from sboot.bin
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
Launch multiuploader.exe
Plug in the phone and press and hold the power button.
Search and find script.cfg
click start and the phone will go into odin mode.
Start odin and flash the firmware (in case of having split the stock rom sboot) or Combination (in case of having split the combination sboot)
the z-zip tool must be downloaded
Binary editor - Multidownload flash tool with files for sm-g975f u8 x32, x64,
https://drive.google.com/file/d/1GzgqNCCEE0e43CniitzuAxKcDax5QLaT/view?usp=sharing
Click to expand...
Click to collapse
Can you check the addresses and lenghts of the partitions cut out of sboot?
I think you've made a mistake.
Can give me the precise partition details?
Are you 100% positive that this is valid at least for most devices of the same chipset?
I'd like to try to make an automated script or a tool of some sort.
Also when I was dividing my A515F U5 sboot I've spotted some long breaks in data which I assumed were empty blocks at the end of partitions.
What confused me about it is that I didn't find those where you said partitions are ending.
Can you demonstrate graphically your partitions in a linear projection?
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
eldon301 said:
It’s been 3 years and still can’t get help with A750G hard brick. I guess XDA is not so friendly and helpful anymore.
The world is slowly dying. Peace to everyone who still cares
Click to expand...
Click to collapse
I'd like to help
NonStickAtom785 said:
I'd like to help
Click to expand...
Click to collapse
Hello my friend I am try to get life back into a A750G, it’s completely hard bricked showing exynos usb in device manager. Can i direct message you or should I keep it in the forums. I was falling on part 4 off the files needed to create, I didn’t even know if my cfg file was correct but I tried my best at understanding the creation of the files. Plz help my brothers