Related
Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???
Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.
matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!
Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App
Hello,
After rooting (flashing) my brand new Galaxy Tab 2 7" via the following link (will not show): androidauthority.com /galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473/, method Heimdall, with the files from this site, the device is stuck at the bootscreen. I did follow the instructions exactly. The ./su in the adb shell segfaults however, so i can't continue, and it won't startup either. So i guess now it's bricked. I read somewhere it has to do with the software version number that was incompatible.
Can i go back to the old firmware, or install another android 'distro' (that was my intent for the long run and the reason to root it first)?
I can still adb shell into it, but no root however.
I'm a newbie in the android world btw.
Hi,
Search for the latest Stock Firmware files of P3110 for your country and flash it with ODIN... Check the development thread and you'll find information on how to flash stock firmware with odin...procedure will be the same only files will differ...
To go into download mode, turn off your device, press vol. down, keep it pressed and with that press the power button...start odin on your computer and connect the tab to your computer and flash the file....
Zeroclick said:
Hello,
After rooting (flashing) my brand new Galaxy Tab 2 7" via the following link (will not show): androidauthority.com /galaxy-tab-2-7-0-p3110-root-clockworkmod-recovery-96473/, method Heimdall, with the files from this site, the device is stuck at the bootscreen. I did follow the instructions exactly. The ./su in the adb shell segfaults however, so i can't continue, and it won't startup either. So i guess now it's bricked. I read somewhere it has to do with the software version number that was incompatible.
Can i go back to the old firmware, or install another android 'distro' (that was my intent for the long run and the reason to root it first)?
I can still adb shell into it, but no root however.
I'm a newbie in the android world btw.
Click to expand...
Click to collapse
I'm downloading 4.1.1. from samsung-updates.com, since that was the latest version for my country (NL). I flash with Heimdall, since i don't have windows, or is there something special with Odin?
Now i'm going to flash it, is it possible to root it in the process? Else i have to flash it later again.
varundave said:
Hi,
Search for the latest Stock Firmware files of P3110 for your country and flash it with ODIN... Check the development thread and you'll find information on how to flash stock firmware with odin...procedure will be the same only files will differ...
To go into download mode, turn off your device, press vol. down, keep it pressed and with that press the power button...start odin on your computer and connect the tab to your computer and flash the file....
Click to expand...
Click to collapse
Zeroclick said:
I'm downloading 4.1.1. from samsung-updates.com, since that was the latest version for my country (NL). I flash with Heimdall, since i don't have windows, or is there something special with Odin?
Now i'm going to flash it, is it possible to root it in the process? Else i have to flash it later again.
Click to expand...
Click to collapse
Idk but I usually flash with odin
The file is 706MB. The boot-bjr.img file that i installed is only 5.6 MB. Can someone explain what is going on here? I don't feel comfortable with this and i cannot find any description of how the flashing actually works, what you are replacing by flashing, what format/partitioning the flash has e.t.c.
qazmed said:
Idk but I usually flash with odin
Click to expand...
Click to collapse
Just for the record, i was able to install cyanogenmod on it, by first installing clockworkmod recovery. Heimdall and adb is all you need if you're a linux user.
Don't worry its not a brick.
Or a hard brick at least.
Download the stock ROM from sammobile or samsung-updates. Doesn't matter which. Extract the zip. Flash the .md5 file with Heimdall or if that doesn't work rename it to .tar.
To root it properly follow my root tutorial but use Heimdall when I use Odin. http://www.youtube.com/watch?v=pAvze-VNzj8&feature=youtube_gdata_player
Sent from my GT-P3113 using Tapatalk HD
Hey guys I need some help. I'm trying to flash BeanStalk 4.4.2
I flashed "Heimdall oneclick BML ROM/kernel" as instructions said, but when I'm trying to flash BeanStalk from CWM (v5.0.2.7) it says:
This package is for aries.galaxys4.gmtd.SGH-T959V,SHG-T959W devices: this is a herring
Installation aborted
What I'm doing wrong?
miguelangelcg25 said:
Hey guys I need some help. I'm trying to flash BeanStalk 4.4.2
I flashed "Heimdall oneclick BML ROM/kernel" as instructions said, but when I'm trying to flash BeanStalk from CWM (v5.0.2.7) it says:
This package is for aries.galaxys4.gmtd.SGH-T959V,SHG-T959W devices: this is a herring
Installation aborted
What I'm doing wrong?
Click to expand...
Click to collapse
Re download the ROM again. You might have gotten a bad download. If that does not correct it. I would suggest flashing all the way back to stoc Gingerbread, then flashing it again.
miguelangelcg25 said:
Hey guys I need some help. I'm trying to flash BeanStalk 4.4.2
I flashed "Heimdall oneclick BML ROM/kernel" as instructions said, but when I'm trying to flash BeanStalk from CWM (v5.0.2.7) it says:
This package is for aries.galaxys4.gmtd.SGH-T959V,SHG-T959W devices: this is a herring
Installation aborted
What I'm doing wrong?
Click to expand...
Click to collapse
Seems like u have a T959W but as I remember the updatescript should have included the T959W @ assert lines. But maybe I am wrong. Open the zip and browse to meta or so folder and find a file name updater-script then open it with Notepad++. Please use notepad++, not Windows' notepad. Then look at the first line (assert tons of things) and delete it then zip it back and flash again
Sent from my GT-N7000 using Tapatalk 2
I think there might be a problem with the Beanstalk build. I flashed Slimkat for the 1st time without any problems. Then, from TWRP I flashed Beanstalk as expected.
I checked the MD5 sum of the zip and it's ok. I have the SGH-T959V for sure.
daothanhduy1996 said:
Seems like u have a T959W but as I remember the updatescript should have included the T959W @ assert lines. But maybe I am wrong. Open the zip and browse to meta or so folder and find a file name updater-script then open it with Notepad++. Please use notepad++, not Windows' notepad. Then look at the first line (assert tons of things) and delete it then zip it back and flash again
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I tried this, and it doesn't work. The installation just aborts with no indication as to why. Was there anything specific I was supposed to delete, or just everything in the first five lines of updater-script?
Okay, I figured out the problem in case anyone else runs into it and needs help.
CWM will always not register the phone as the one you want, but TWRP does. So if you use another ROM that installs TWRP first (like say, SlimKat), you can then install Beanstalk from TWRP.
Flash bhundvens blastoff 2.5 kernel or antonxs then flash kk reboot recovery flash again
Sent from my SGH-T959V using Tapatalk 2
I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
edit: The file use is actually a port to the Tab 3 by gr8nole. I was wrong about a couple of things. So, credit goes to TeamWin for original dev, and to gr8nole for porting it to the Tab 3 for us
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
This method is for KitKat users.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)
Worked well, thanks
Greaper88 said:
I took a little time playing around with Heimdall. It's....... different.
I have taken the time to simplify some of the steps for everyone, and built the required file myself.
I used TWRP 2.8.0.0 "img" file from their website. All development credit go to TeamWin, I've just converted it to the proper file format for Heimdall.
Before reading farther, please remember:
ALL FLASHING IS DONE AT ONE's OWN RISK, I'M NOT RESPONSIBLE.
Please take adequate precautions to be able to recover your device from a soft brick.
I used the Pit mapping for the T210. The recovery partition is "mmcblk0p10." I checked the partition info on my T210R using Partition Table by Lakshman. The T210R also has its Recovery partition on "mmcblk0p10," so I expect it to work no problem. And TWRP Odin flashables tend to be compatible with several 7.0 variants.
1. Open Heimdall. Reboot your device into download mode (power+volume down+home, then volume up).
2. Attach tablet to computer.
3. Select "Load Package" tab if it isn't already.
4. Click the "Browse" button under "Heimdall Firmware Package."
5. Select the ".tar.gz" file attached to this thread.
6. Click "Load/Customize." This will jump you to the "Flash" Tab.
7. Make sure that the "Repartition" check-box is unselected.
8. Click "Flash."
9. After flashing, reboot into your new recovery and install SuperSU and BusyBox.
As of this point, I have not been able to test this. I hope it goes well for anyone who tries it
Update:
As of now, I have been able to test this file on my own T210R. I already had this version of TWRP installed, so can't confirm actual update, but Heimdall said it flashed, and it didn't brick it, so I'd say good to go! (Take appropriate precautions anyways, because you never know what will happen.)
Click to expand...
Click to collapse
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.
gr8nole said:
You say you took TWRP from TeamWin's website? Can you show me that, because I'm pretty sure they don't support this device.
Click to expand...
Click to collapse
Maybe not their official website... oops.
The file I used you've uploaded... my mistake, thought you were part of their project.
Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.
xaueious said:
Well the TWRP image file worked well enough for me... Either way...
I think this is the main way to root the T210(R) if updated to KitKat. Since it is quite possible that it's the last update it's ever going to see, I'd say it's good time to root it now and put Xposed on it for good measure.
Click to expand...
Click to collapse
This version of TWRP is still compatible with JellyBean. I restored and booted my stock OS using this flash. And this is the same method that I had used to root before the update. (using Odin rather than Heimdall though.)
@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.
mkaymuzik said:
@Greaper88 did you test other files to confirm that functionality is working well (just curious) ?
Heimdall is interesting tool but i haven't tested it myself.
Click to expand...
Click to collapse
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...
Greaper88 said:
Do you mean other Heimdall installer files?
I've not tested other files as I've only messed with my Tab 3, and any flash files have to be built from a raw ".img" (image) file and the device's PIT (Partition Information Table). This presents challenges that I haven't tried to overcome.
I saw a request somewhere in another thread for a walkthrough on rooting the Tab 3 with Heimdall, and I figured out and posted this since it was only the recovery, and that much was actually somewhat easy.
My idea was, if you get custom recovery, you can then install your choice of ROM. Although I don't know if there is a TWRP flashable stock KK ROM yet...
I'm confident that the method in this thread for mentioned devices works based on my own flash and on "xaueious'" posts.
To port this method to other devices, one just needs the device's PIT and the recovery image file, "recovery.img" for example in order to build a flash file. The process is actually easy once you know how.
Full ROMs would be more difficult I think because there are other files besides ".img" files that have to be written to the flash, and a XML file has to be built as well to handle all of that. I haven't had time to mess with all of that...
Click to expand...
Click to collapse
Thx for the info mate. Going test this out.
I'm lost, I was working on my hubby's tablet and somehow the backup I made got wiped when I tried to Samsung Galaxy Tab 3 7.0 WiFi SM-T210/T210R Performance Upgrade MOD. I'm assuming that it doesn't work under KitKat as I was running TranchidaKat v2.2 [4.4.2 SM-T210/R Rom. Anyway whatever I did no matter what I wipe I keep getting one error from Odin, ""can't mount ES' I'd sure appreciate a hand on this thing if your around. I've been trying to run Heimdall but it always fails in Odin. What really confused me on your directions is you saying to open the package and select Load the Package. I'm not sure exactly what that means but I have Odin 3.07 through 3.10 and I don't see anything like that, could you clarify. I can load the regular 2.8 TWRP using the img file that has nothing to do with Heimdall so I can get into recovery but that's where I'm stuck. Any thoughts???
Krissy
Odin is leaked Samsung Software. Heimdall is an open source substitute, and is not related to Odin. Heimdall requires the TWRP file posted in the OP in this thread to work, but it will not work in Odin.
If you have a custom recovery installed that you can boot into, check out:
http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-twrp-t2951850
If you've lost your backup files, then these ones might work for you unless the device flash has been overly corrupted.
If that doesn't work, check out:
http://forum.xda-developers.com/galaxy-tab-3/general/tab-3-7-0-sm-t210-r-stock-4-4-2-kitkat-t2930075
That's intended to be flashed directly from Odin, and will make the device stock KitKat.
I then like to use the Werewolf Kernel, since it overclocks the Tablet and improves overall speed that way.
Other thoughts: have you tried another USB cable/port? I've had similar errors simply because Odin didn't like my USB cable, or the USB port I was connected to.
Hi there,
since there is an official cwm on their website I wanted to ask how to flash it.
1. There's only a N8013 package, can I flash that on my N8010, since these two are basically the same?
2. It's an img file. Do I need to flash this with fastboot or can I just rename it to recovery.img and flash it with Odin? I've looked at some Odin tar files from twrp and there's nothing in there except an recovery.img. Or has the img file to be specific for Odin?
Kamairo said:
2. It's an img file. Do I need to flash this with fastboot or can I just rename it to recovery.img and flash it with Odin? I've looked at some Odin tar files from twrp and there's nothing in there except an recovery.img. Or has the img file to be specific for Odin?
Click to expand...
Click to collapse
IIRC fastboot does not work for the Note 10.1. Anything for this device should be ODIN specific.
mendacium said:
IIRC fastboot does not work for the Note 10.1. Anything for this device should be ODIN specific.
Click to expand...
Click to collapse
I definitely read a guide where the img file was pushed manually. But you might be right about fastboot, I think it was an adb command.
I still think *repacking* for Odin is just naming the file recovery.img and zipping it into a tar. Can any of the devs confirm that? I mean, I must be able to flash CWM img somehow...
Hmm...
You might be right about adb push....
I can't help you with Odin, but I have flashed img files onto my N8010 using heimdall. That is sort of the Linux and Mac alternative to Odin. It runs on Windows as well so maybe it's worth a shot.
Just stumbled across this: http://forum.xda-developers.com/showthread.php?t=2102677
All there in the manual!
mendacium said:
Hmm...
You might be right about adb push....
I can't help you with Odin, but I have flashed img files onto my N8010 using heimdall. That is sort of the Linux and Mac alternative to Odin. It runs on Windows as well so maybe it's worth a shot.
Just stumbled across this: http://forum.xda-developers.com/showthread.php?t=2102677
All there in the manual!
Click to expand...
Click to collapse
Yeah, I know that thread, but that's not the latest version. Anyways, I found a guide on how to make flashable tars. So either I try that or heimdall. Thx so far!
Sent from my Galaxy Note 10.1