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
Related
Hello Community,
I tried to install custom recovery using this manual "wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx" (<- cannot use the link function, because it's my first post). I followed every step. At point 9 I have to make commands using the cmd. Unfortunately the result is an Error:
Failed to access device. libusb error: -12
I had two insecurities while following the manual:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
To point 5: I deinstalled Kies and the device driver in the Windows operating system. Since I've done this, there are appearing two devices in the zadig.exe when I connect my S4. I installed the zadig driver for both of them.
Im using Windows 7 x64
I hope someone can help me, for this moment I don't know what to do further...
greets
Dr. Bob! said:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
Click to expand...
Click to collapse
I don't know about the libUSB error, and I haven't modded a Galaxy S4 mini, but I have installed CM on Galaxy Player. The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
I flashed the Galaxy Player with Odin 3 v. 3.04, after having installed Kies to have the drivers installed. The Player showed in Odin with something like "ID:0 COM"; I then clicked on the "PDA" button, then pointed to the tar.md5, and clicked flashed, and it worked.
Here are my 2 cents :^)
Is your phone rooted? If rooted already it easy! For the most noob method, install ROM Manager from https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager and ROM manager will install the CWM for you. From there, its pretty simple.
If it not rooted, that the first thing you'll have to do.
fdelente said:
[...] The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
Click to expand...
Click to collapse
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
TNCS said:
If it not rooted, that the first thing you'll have to do.
Click to expand...
Click to collapse
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Dr. Bob! said:
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Click to expand...
Click to collapse
No, custom recovery is not rooting. Not my favourite method but it easy enough, try this: http://www.kingoapp.com/
It a universal root for JB and it will prompt you to install CWM afterwards.
After installing the CWM I rooted the device. I succesfully installed Canogenmod 10.2.1. The Tutorial says explicit, that it only helps for 10.2.x but I want to install the Nightly version which is running at CM version 11. If I could, I would ask this questions in the threat but I'm not allowed yet to post in the developers section. "forum.xda-developers.com/showthread.php?t=2474054"
Can I use this tutorial for flashing CM version 11?
Tried searching the forums on this topic but could not find anything that could resolve my problem
attempting to install a ROM on my phone for the 1st time.
I am using i9082 on android 4.2.2
my OS is ubuntu 12.04 hence used Heimdall 1.4
Tried to Flash ClockworkMod recovery using Heimdall 1.4
i am trying to flash this by using baffin.pit file (otherwise the options dont show up) and into the partition named "RECOVERY" but i always get an error "setting up interface failed!"
the device is detected on heimdall and the phone is on download mode but yet it does not go further
could someone help me out please
also since odin has been suggested on many forums, tried to run it with wine but it does not detect the phone(no com port in yellow)
yogneo said:
Tried searching the forums on this topic but could not find anything that could resolve my problem
attempting to install a ROM on my phone for the 1st time.
I am using i9082 on android 4.2.2
my OS is ubuntu 12.04 hence used Heimdall 1.4
Tried to Flash ClockworkMod recovery using Heimdall 1.4
i am trying to flash this by using baffin.pit file (otherwise the options dont show up) and into the partition named "RECOVERY" but i always get an error "setting up interface failed!"
the device is detected on heimdall and the phone is on download mode but yet it does not go further
could someone help me out please
also since odin has been suggested on many forums, tried to run it with wine but it does not detect the phone(no com port in yellow)
Click to expand...
Click to collapse
Hope you are using recovery.img(*.img) huh?
What you get when you execute heimdall detect command in Terminal.
And definitely you cant install recovery without PIT, so baffin.pit is essential. It looads the Partition Information Table.
Once the PIT has been loaded, the "Partition (Files)" field will be clickable. Click "Add", now the "Partition Details" field becomes clickable. Under "Partition Name", select "KERNEL". Click "Browse" on the "File" field directly underneath.
And i guess this is what you had done till now.
See whether the img or tar file which u used is correct and that is for Galaxy Grand Duos.
And using wine wont help.. may be because driver identification may be a mess in emulators. also try installing Kies in Wine and Odin.
If u have access to Windows, Odin, that would be the best choice.
DMJoh said:
Hope you are using recovery.img(*.img) huh?
What you get when you execute heimdall detect command in Terminal.
And definitely you cant install recovery without PIT, so baffin.pit is essential. It looads the Partition Information Table.
Once the PIT has been loaded, the "Partition (Files)" field will be clickable. Click "Add", now the "Partition Details" field becomes clickable. Under "Partition Name", select "KERNEL". Click "Browse" on the "File" field directly underneath.
And i guess this is what you had done till now.
See whether the img or tar file which u used is correct and that is for Galaxy Grand Duos.
And using wine wont help.. may be because driver identification may be a mess in emulators. also try installing Kies in Wine and Odin.
If u have access to Windows, Odin, that would be the best choice.
Click to expand...
Click to collapse
- the file has been extracted and i am using recovery.img
- the command displays "device detected"
- I am using the baffin.pit file of the internet for this particular device, will that be a problem? if so then how do i get this file.
- i've tried under kernal and it displays the same error
i do not have any access to a windows computer, is there anyother way i could load the recovery?
cheers
yogneo said:
- the file has been extracted and i am using recovery.img
- the command displays "device detected"
- I am using the baffin.pit file of the internet for this particular device, will that be a problem? if so then how do i get this file.
- i've tried under kernal and it displays the same error
i do not have any access to a windows computer, is there anyother way i could load the recovery?
cheers
Click to expand...
Click to collapse
Baffin.pit wont be a problem.
Make sure you are doing the correct procedure. I am not that good in the process, so you should research a bit in this.
You can Get pit from here. But I dont think that its the problem of the pit u use.
By the way from where you got the IMG file?
got it from the thread below
http://forum.xda-developers.com/showthread.php?t=2563557
yogneo said:
got it from the thread below
http://forum.xda-developers.com/showthread.php?t=2563557
Click to expand...
Click to collapse
Are you using the frontend Heimdall or by executing commands in Terminal.
If you are using terminal try the frontend app too, i guess u are well aware of this.
And its too hard for me to get my device detected by Ubuntu, and so i prefered Odin later.
As you said it wont go further can you post the log messages in Heimdall window
Hi all,
just having some problems flashing my tab 10.1 3 p5220.
Kies is refusing to do it as I suspect it is because the rom in it is
currently a german one.
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
I seem to remember being able to do this on the htc and assume
we can do the same with the samsung. This way I hope I can I
reflash it via odin.
Many thanks in advance,
Andrew
Just download a firmware from sammobile and flash through odin
BennyCat said:
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
Click to expand...
Click to collapse
Not sure if you've managed it now?
Anyway here is how you do it, also may be useful for others too, I've done this in the past, although I was doing an emergency recovery instead of an upgrade, this works either way.
I take absolutely no credit for this:
Here is a guide to save the firmware during your kies update,so u can save that firmware for future use .i just copy paste this from some where else
1. On your pc, windows explorer, check the option "Show hidden files, folders, and drivers".
2. Now connect your phone to pc via kies to begin the firmware upgrade.
3. Kies will begin to download the firmware files...
a. The files will be saved under a tmp file called "tmp****.tmp"
(NB: **** can be any letters or numbers, e.g. In my two times of upgrade via kies,
first timethe tmp files was "tmpA4CE.tmp", and on the second it was "tmpD900.tmp"
b. In Windows 7, this tmp file is located at, C:\Users\*\AppData\Local\Temp
(NB: * is the pc user session name, e.g. C:\Users\Spacks\AppData\Local\Temp)
4. When download is complete, kies decompresses this tmp file into a folder called
"tmp****.tmp.zipfolder" and begins the firmware upgrading process.
a. The folder has same name as the tmp file but now with an extention of .zipfolder.
(So scroll through the folders in the same directory to locate it).
b. When kies begins the upgrade process starting from 1% until it reaches 100%,
quickly copy the "tmp****.tmp.zipfolder" to your desktop.
You have about 2 to 3 minutes to do this. Kies will delete the folder once upgrade is 100% (completed).
5. The "tmp****.tmp.zipfolder" contains all the firmware files kies has used to upgrade your phone.
Now you have a backup of official firmware from kies. This is also useful in case kies fails to complete the upgrade process.
Click to expand...
Click to collapse
:good: Credit to & quoted guide by blackperl @ androidforums.com :good:
I'm trying to flash stock ROM on my Galaxy Tab A with Heimdall 1.4.0 (Odin doesn't work - see thread https://forum.xda-developers.com/galaxy-tab-s/help/samsung-t550-galaxy-tab-unlock-t3665660)
The first part of Heimdall (as far as I can tell) is to install drivers and then download the PIT file. The drivers have installed without issue but when I try and download the PIT file i get the error below. I have read similar issues online and they suggest using a newer, unreleased version 1.4.2 of Heimdall and something about a the latest commits and master? I'm totally lost with this!! I'm not sure if this will work so I'm open to any ideas... and some guidance
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
jimmisavage said:
I'm trying to flash stock ROM on my Galaxy Tab A with Heimdall 1.4.0 (Odin doesn't work - see thread https://forum.xda-developers.com/galaxy-tab-s/help/samsung-t550-galaxy-tab-unlock-t3665660)
The first part of Heimdall (as far as I can tell) is to install drivers and then download the PIT file. The drivers have installed without issue but when I try and download the PIT file i get the error below. I have read similar issues online and they suggest using a newer, unreleased version 1.4.2 of Heimdall and something about a the latest commits and master? I'm totally lost with this!! I'm not sure if this will work so I'm open to any ideas... and some guidance
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Click to expand...
Click to collapse
Are you using Heimdall on a native Linux machine or Windows?
You need a native Linux PC and the command line version of Heimdall.
ashyx said:
Are you using Heimdall on a native Linux machine or Windows?
You need a native Linux PC and the command line version of Heimdall.
Click to expand...
Click to collapse
Oh I'm using Windows 10. I don't have access to a Linux PC... Where does that leave me? Totally flummuxed?
jimmisavage said:
Oh I'm using Windows 10. I don't have access to a Linux PC... Where does that leave me? Totally flummuxed?
Click to expand...
Click to collapse
Unless you can dual boot a Linux distro with W10 or download one of the Live Bootable from disk Linux distros. There's plenty about.
https://help.ubuntu.com/community/LiveCD
Finding time to try this is proving troublesome. What are the chances this will actually work (more than Odin)?
I'm just trying to work out if it's actually worth the time/hassle?
Hi,
I finally managed to find some time and i'm currently on a lunix machine (from usb boot).
Now, do i need a 'Heimdall Firmware Package' or do i use the Samsung firmware for the SM-T555 you posted before?
jimmisavage said:
Hi,
I finally managed to find some time and i'm currently on a lunix machine (from usb boot).
Now, do i need a 'Heimdall Firmware Package' or do i use the Samsung firmware for the SM-T555 you posted before?
Click to expand...
Click to collapse
Just flash the stock firmware.
Okay, I had a nightmare on this last night.
I was using Ubuntu 14.04 but when i opened a terminal and typed 'heidmall-frontend' it would tell me that it wasn't installed and to try (something like) 'sudo apt install heimdall-flash-frontend' but then it would tell me that it doesn't exist.
What version/build of Linux should i be using (as a USB boot) and how do i install heimdall frontend?
Also, when reading instructions on flashing a rom they all say to use a heimdall firmware but you're saying i can use the stock firmware? How would i install that? Will heimdall recognise the .zip file?
Thanks again, i know i'm being a pain but i was up until 1am last night (waiting for the longest firmware download ever!!) trying to flash this!
jimmisavage said:
Okay, I had a nightmare on this last night.
I was using Ubuntu 14.04 but when i opened a terminal and typed 'heidmall-frontend' it would tell me that it wasn't installed and to try (something like) 'sudo apt install heimdall-flash-frontend' but then it would tell me that it doesn't exist.
What version/build of Linux should i be using (as a USB boot) and how do i install heimdall frontend?
Also, when reading instructions on flashing a rom they all say to use a heimdall firmware but you're saying i can use the stock firmware? How would i install that? Will heimdall recognise the .zip file?
Thanks again, i know i'm being a pain but i was up until 1am last night (waiting for the longest firmware download ever!!) trying to flash this!
Click to expand...
Click to collapse
Don't try and use a fronted. Use the command line. There is no such thing as Heimdall Firmware as far as I'm aware.
Heimdall flashes images which can be extracted from the stock firmware.
If you search Google for Heimdall flash commands you will find the correct syntax required to flash images.
Thanks for that.
I'm not at home to try right now, but i want to be as sure as possible i'm getting this right. I'm going to...
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware)... only my downloaded firmware is .zip rather than .img ???? https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
Do i unzip the firmware file i've downloaded? I've tried to do that in linux but it failed, maybe i need to unzip in windows?
jimmisavage said:
Thanks for that.
I'm not at home to try right now, but i want to be as sure as possible i'm getting this right. I'm going to...
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-select-model?record=3EFD4C401EE211E7963AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware)... only my downloaded firmware is .zip rather than .img ???? https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
Do i unzip the firmware file i've downloaded? I've tried to do that in linux but it failed, maybe i need to unzip in windows?
Click to expand...
Click to collapse
That's more or less correct. You should be able to extract the image from the zip using the stock utility in Linux. Ensure md5 is changed to tar.
If not then Peazip for Linux or 7zip for Windows.
Thanks again! I'll have one more go at this tonight... if it doesn't work then it's going in the bin and I can go back to living my life
Whilst in work i decided to download the firmware again and see if i could extract the image from the zip.
I have successfully completed that. It's currently named 'T555XXS1BPL4_T555BTU1BPE2_T555XXU1BPD7_HOME.tar.md5'. Do i simply delete the .md5 on the end to leave the .tar or is there something more complicated than that? Shouldn't it be a .img or am i just being overly concerned about details?
My head is going to explode!
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-s...3AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware) WHEN I DO THIS I GET A MESSAGE SAYING HEIMDALL IS NOT INSTALLED. HOW DO I INSTALL IT?
jimmisavage said:
My head is going to explode!
1. Download this firmware for my SM-T555 model tablet: http://updato.com/firmware-archive-s...3AFA163EE8F90B (which is a .zip file)
2. Put my tablet into download mode and connect to my linux machine
3. Open a terminal (how do i open as admin?) and according to a Google search, type 'heimdall flash --RECOVERY filename.img' (replacing filename.img with the stock firmware) WHEN I DO THIS I GET A MESSAGE SAYING HEIMDALL IS NOT INSTALLED. HOW DO I INSTALL IT?
Click to expand...
Click to collapse
It seems you are making this more complicated than it needs to be. Admin is the root user on a Linux system.
The instructions at the link below pretty much explain what you need to do.
http://www.dudleymediagroup.com/Detail/id/installing-using-heimdall-on-with-linux-3547
It seems i'm using Ubunto 16.04 and I cannot see a heimdall version for that? I guess I need to try Ubuntu 13.04?
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
jimmisavage said:
It seems i'm using Ubunto 16.04 and I cannot see a heimdall version for that? I guess I need to try Ubuntu 13.04?
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
Click to expand...
Click to collapse
I should think you'll be fine with 16.04 or 14.04
ashyx said:
I should think you'll be fine with 16.04 or 14.04
Click to expand...
Click to collapse
I don't see 16.04 or 14.04 in the download options though. Only 13.04 or 12.10.
What am I missing here? If I download ubuntu13.04-heimdall_1.4.0-0_amd64.deb and click install nothing seems to happen. The same goes for ubuntu12.10-heimdall_1.4.0-0_amd64.deb (I'm running Ubuntu 16.04 Live x64 from a USB drive).
jimmisavage said:
I don't see 16.04 or 14.04 in the download options though. Only 13.04 or 12.10.
What am I missing here? If I download ubuntu13.04-heimdall_1.4.0-0_amd64.deb and click install nothing seems to happen. The same goes for ubuntu12.10-heimdall_1.4.0-0_amd64.deb (I'm running Ubuntu 16.04 Live x64 from a USB drive).
Click to expand...
Click to collapse
From the directory where it is located try:
sudo dpkg -i ubuntu13.04-heimdall_1.4.0-0_amd64.deb
Got heimdall installed but i cannot flash anything.
Time to give up. Thanks for all the help
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