I've made some of mistakes and now I need your help determining if I'm screwed or if there's a solution.
1st Mistake: I let my new VZ GS4 update to MJ7.
2nd Mistake: I thought I found a guide to get a rooted MJ7 so I tried using Odin to flash VRUDMI1...which errored.
Well that didn't work. Time to reboot...except now it wont boot. Now it displays:
Firmware upgrade encountered an issue. Please select recover mode in Kies & try again.
At least it's suggesting a solution, right? So I download Kies 3. It connects. I follow a guide which tells me how to re-initialize the firmware.
1. I enter the model "SCH-I545"
2. I enter the IMEI
3. The firmware downloads
4. Nothing. It eventually gives an error that it can't connect.
I've tried that on multiple computers with various cables with the same results.
So do I go back to Staples where I got it on Black Friday and tell them that my phone stopped working?
First off youre in wrong forum. Questions go in the questions section. You need to download the stock mj7 image and flash it in odin.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
I did the same thing was up all night finally found out about Kies but it worked for me. Once you update to mj7 you can't go back. my problem with odin was I was trying to go back to me7 so I have mj7 odin image to try if it happens again.
Sent from my SCH-I545 using Tapatalk
Sorry about posting in the wrong area. I knew better, but was completely exhausted when I made the thread and didn't think about it.
If anyone else makes the same mistake I did, I'm back up and running after downloading SCH-I545_VZW_1_20131023084910_v4vth34m5z_fac.zip and flashing with Odin.
Related
I have a Galaxy Note i717 from AT&T that I rooted. Worked great.
Yesterday I upgraded to ICS via Kies. Worked great.
Then I proceeded to root it again using odin.
Unfortunately even after all the things done it now will not boot up at all.
All I get is the S a m s u n g logo. I can put it into boot mode and the computer see's it but nothing more.
If anyone can point me to any rom/bootloader/ etc. I would be most grateful.
Or just let me know what to do and where to get roms. I did search and there are many for the i700.
I guess I need a bootloader and rom right?
Sorry folks. Point me somewhere else will have to get another phone.
T h a n k s ...
Others would tell you to look in the dev section for the stock rom (its usually called something like "in case of brick) I've had issues issues getting it to work but Im certain it was user error as to why it didn't work for me. But another option that I think could work would be to get your phone into download mode and run the ics upgrade thru kies again. You'll lose everything in your phone but I think it'll get your phone up and running again. But before you do any other that...did you make a nandroid back of? Or have you downloaded any roms to your phone because if you did you can just enter cwm and reflash any rom you may have or just flash your backup, backups are so important when doing these sort of things, saves a lot of head aches.
Edit: after reading your post again it says your phone messed up after rooting, try and re run the root file thru Odin, I kinda sorta remember reading something similar to this were people had issue trying to root. I'll try and find the thread.
Sent from my SAMSUNG-SGH-I717 using xda premium
this happened due to rooting with the Gingerbread method...so using Nash reply run/reinstall your Official ICS...and to root....
see My Links in red in my signature...go the GNote Super page....you should see what is being used to root the Official ICS...I used it and lots others, there prob more methods out there, but I found this is the easiest and more proven method....
Cant miss the info on GNote page regarding Rooting.
so to recap...since your believe you have bricked your phone...
use the method Nash replied to you with...put into download mode....run the official ics, you will need the model, serial number of your phone...
let us know how it works out for you...
mpanwar said:
I have a Galaxy Note i717 from AT&T that I rooted. Worked great.
Yesterday I upgraded to ICS via Kies. Worked great.
Then I proceeded to root it again using odin.
Unfortunately even after all the things done it now will not boot up at all.
All I get is the S a m s u n g logo. I can put it into boot mode and the computer see's it but nothing more.
If anyone can point me to any rom/bootloader/ etc. I would be most grateful.
Or just let me know what to do and where to get roms. I did search and there are many for the i700.
I guess I need a bootloader and rom right?
Sorry folks. Point me somewhere else will have to get another phone.
T h a n k s ...
Click to expand...
Click to collapse
And once you're rooted and all fixed up, enter cwm and create a backup. These are great because no matter what you do to your phone as long as you can enter cwm you'll always be able to fix your phone via backup.
Sent from my SAMSUNG-SGH-I717 using xda premium
I wanted to mention, I'm not sure how you updated thru kies originally (legit update or emergency update) the method you'll be using this time (if you choose to fix thru kies) is the more or less emergency method. I wanted to mention this because when your in download mode and connect your phone to your PC and run kies, kies will try to connect to your device but will time out over time...it took me 2 days of Q and A before I realized kies won't connect with phone in download mode, but that's OK. Once phone is connected click tools/firmware upgrade and initialization, and as bigjoe said youll than need to input model and serial numbers (all caps) than click OK. You'll have a few prompts afterwards but yo basically on your way to a running phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
Brick = nothing at all happening on phone.
Samsung logo = bad flash (corrupt file used)
Brick can sometimes be revived with a JTAG device.
Samsung logo means re download file, re read instructions and relevent thread, and redo your work.
Don't be too anxious -you will fix it.
I suggest using Kies upgrade > emerency firmware method. Download mode is the key.
If you are with Rogers, the following is useful.
http://forum.xda-developers.com/showthread.php?t=1657262
I went through the exact same problem with someone else's Note that I was upgrading, subsequently flashing.
The above process bring the phone back to 100% stock gingerbread.
Thanks All and Resolved.
eugenekim618 said:
If you are with Rogers, the following is useful.
http://forum.xda-developers.com/showthread.php?t=1657262
I went through the exact same problem with someone else's Note that I was upgrading, subsequently flashing.
The above process bring the phone back to 100% stock gingerbread.
Click to expand...
Click to collapse
Thanks all for the replies.
I was able to go to DEV Section and get the full AT&T ICS Rom. Used ODIN to get it back to factory ICS.
Then (with great care ) re-rooted it using ICS root stuff. I have it all in case anyone else needs this route. Else follow instructions above.
Thanks all. I think for now ICS is where this will stay. In fact Gingerbread was good enough except for not being able to use Chrome.
mpanwar said:
Thanks all for the replies.
I was able to go to DEV Section and get the full AT&T ICS Rom. Used ODIN to get it back to factory ICS.
Then (with great care ) re-rooted it using ICS root stuff. I have it all in case anyone else needs this route. Else follow instructions above.
Thanks all. I think for now ICS is where this will stay. In fact Gingerbread was good enough except for not being able to use Chrome.
Click to expand...
Click to collapse
great, can you put solved in the title...thx
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
I literally just posted the same question. Any help would be appreciated if you can figure it out. Ill return the favor if i can get any information :good:
If you took the latest update I'm not sure what the answer is because I haven't been willing to take the update.
If you were in mdk before the yellow triangle then all you have to do is Odin the mdk kernel.
I'd imagine if you are on the latest then odining the latest would take care of it also but again, I won't take the latest so I can't say for sure
sent from my blu vzw gs4
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
richardawood said:
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
Click to expand...
Click to collapse
Im on a search for the updated kernel as well. At least there is someone in the same boat as i am.
richardawood said:
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
Click to expand...
Click to collapse
If the phone was running ME7 then you can ONLY flash ME7 again (at least right now).
Grab the image from this thread...
http://forum.xda-developers.com/showthread.php?t=2357235
and flash it using Odin.
Thank You
That worked great! I am back up in running and waiting patiently w/ the rest of us that updated... THANK YOU!!!!!! :highfive:
Thanks
I can't thank you enough. The S4 is my first Android phone and after 3 weeks, the USB connection on the phone broke and I finally got my new one today. While I was setting up SuperSU/Titanium Backup/ROM Manager, I guess the phone downloaded the ME7 update in the background and I told it to install (stupid me). This will teach me from rushing to get my phone back to the state it was in. (Not that I can do that now because I need SuperSU before I can install ROM Manager). Hopefully once I can get ROM Manager back, I can restore my MDK backup with all my custom settings and apps. I think I will make a visit to the VZ store tomorrow and see if they can revert back to the MDK version. I will make up some lame excuse of why I don't want to be on this new release.
This leads to my question of, is there a way to disable or remove the apk file that controls the software updates?
Thanks again for saving my life!!!
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Thanks
hexitnow said:
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the information about the sdm.apk. When I debloated my phone I used the adb shell to remove most of the *.apk packages that I did not want. This was of course after I took a full Titanium Backup and ROM Backup.
Sounds good and I will not waste my time going to Verizon today.
You make a really good point about not going back to the mdk, but rather move forward with the technology and updates. This leads me to some more questions once I have root again:
1. Is my mdk rom backup totally useless at this point?
2. If yes to 1, since my mdk rom contained all my apps/customized settings, do I have to manually download everything and reconfigure?
3. If no to 2, how would I go about getting the app/customized settings back, Titanium Backup?
4. If yes to 2, if I go about downloading everything manually and configuring, will the new root remove all these settings?
I am sure I will have more questions so thanks in advanced
PS: I think I figured out what caused my USB port to stop working. I take my phone with me when I run so I think some sweat got in from my arm band and corroded the connections. I tried cleaning them with rubbing alcohol and compressed air, but still no dice. If connected to a computer or wall charger, it will charge, but a computer will not detected it. So my guess is there is damage to the board allowing whatever communication is needed to work with a computer.
I have a Verizon Samsung Galaxy S4 (SCH-I545) which I previously rooted via the Open1Your1Eyes0 pwn script. Everything was great except I wanted to update to the latest version and my phone failed with each attempt. I tried to unroot it using Odin to flash the VRUAMDK_NoWipe.tar.md5 stock ROM image.
That failed and now it's stuck on the ODIN MODE "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message screen. The phone won't boot. If I hold Vol Down I can still go to the Downloading firmware screen, but I've tried flashing 3 other stock ROM's and nothing will work.
Any suggestions?
Not 100% sure as to whether this will work but I had this happen to me about 2 months ago and I THINK it was the "Full Wipe ( AKA Emeregency Repair)" file from this thread: http://forum.xda-developers.com/showthread.php?t=2735172 that fixed it. Also since it says Emergency Repair as Kies would if you could fix it using that I assume its for this purpose, may be wrong though but worth a shot. I'd probably be more help if i wasn't like brain dead atm but once it goes away i'll re-think this and if i decide I gave you incorrect advice i'll edit this or post again with the correct information.
Anyways just follow the instructions there on the Full wipe one and report back if it works. Quite confident it will but as with anyone I could be wrong. NO GUARANTEES
waffleking said:
I have a Verizon Samsung Galaxy S4 (SCH-I545) which I previously rooted via the Open1Your1Eyes0 pwn script. Everything was great except I wanted to update to the latest version and my phone failed with each attempt. I tried to unroot it using Odin to flash the VRUAMDK_NoWipe.tar.md5 stock ROM image.
That failed and now it's stuck on the ODIN MODE "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." message screen. The phone won't boot. If I hold Vol Down I can still go to the Downloading firmware screen, but I've tried flashing 3 other stock ROM's and nothing will work.
Any suggestions?
Click to expand...
Click to collapse
Before you flash MDK, you first have to know what build and bootloader you're on. Apparently you're not running a MDK bootloader, and consequently can't flash MDK.
What baseband and bootloader did you start from? If you don't know, then why did you choose to flash MDK?
S1L3nTShaDoWz said:
Not 100% sure as to whether this will work but I had this happen to me about 2 months ago and I THINK it was the "Full Wipe ( AKA Emeregency Repair)" file from this thread: http://forum.xda-developers.com/showthread.php?t=2735172 that fixed it. Also since it says Emergency Repair as Kies would if you could fix it using that I assume its for this purpose, may be wrong though but worth a shot. I'd probably be more help if i wasn't like brain dead atm but once it goes away i'll re-think this and if i decide I gave you incorrect advice i'll edit this or post again with the correct information.
Anyways just follow the instructions there on the Full wipe one and report back if it works. Quite confident it will but as with anyone I could be wrong. NO GUARANTEES
Click to expand...
Click to collapse
I got it working using the Full Wipe instructions you linked to. THANK YOU SO MUCH!
I have a Verizon galaxy note II, and had been running AllianceROM.
AllianceROM seemed to be running pretty good until one day when my accelerometer stopped working. I thought it may be a software bug, so I tried to reflash the ROM. I got a bootloop, and tried again.
I tried to flash cyanogenmod 11 and still got a bootloop. Then I realized I didn't have a safe backup.
I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm.
In the end, I'm stuck with a note II that can't boot. When I try to turn it on, I see the galaxy note II logo, but then the screen goes black (not off, I have to pop the battery out before I can try again.) Power+home+volume up now brings me to android system recovery/manual mode, and power+home+volume down gets me to ODIN mode.
Any suggestions or help would be greatly appreciated. I really wasn't planning on getting a new phone at this point, so I hope it's not beyond fixing! Thanks in advance.
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
mattnmag said:
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
Click to expand...
Click to collapse
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Ethan.S said:
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Click to expand...
Click to collapse
Yes, there's still hope to fix it if you can get the phone into download mode.
Here's some info to clarify before you try something else.... What firmware did you try to install when you used Droidstyle's guide? Also, in your initial post, you said "I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm." What firmware did you flash at that point.... was it one of the Verizon stock firmwares? And what build number was it ( 4.1.2 VRAMC3 , 4.3 VRUEMJ9, 4.4.2 VRUFND7)?
I ask this because, if you flashed 4.3 or 4.4.2, then you can no longer restore back to 4.1.2....you would have to restore back to one of those newer versions (and those newer firmwares actually lock the bootloader and install Knox security features... so that's why I was suggesting not to use them--- unless you already did before you had placed your original post for help).
If you can't restore the phone through ODIN using Droidstyle's guide, then you might try the emergency firmware recovery feature that's available through the Samsung Kies program. You can find Kies at this link: http://www.samsung.com/us/kies/
**The KIES instructions say to use Kies version 2.6 for Firmware recovery back to 4.1.2, and use Kies version 3 for Firmware 4.3 and 4.4.2.
Here's a link to Kies 3 FAQ as well: ( http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00059191&fm_seq=81528 ). Scroll down under Basic Functions and look for the link to "How do I Perform an Emergency Firmware Recovery..." The process should be similar if you plan to use KIES 2.6 instead - (that's only if you're able to restore back to 4.1.2 and you never Odin flashed one of the newer 4.3+ firmwares) .
I hope you can get it fixed. If you're not sure of things, I would suggest researching more and asking more questions before going forward. There is risk that we all take whenever we start modifying our phones, and the more knowledge we can get, the better chances of recovering from errors when we mess something up. (I know I've made plenty of errors as I've tried to learn... I even bricked my Tranformer Prime tablet shortly after receiving it from EBay :banghead: ). If worst comes to worst, you might end up having to pay someone to do a Jtag repair to unbrick it.... but let's hope it doesn't come to that.
Also-- you could try Verizon's Software Upgrade/Repair Assistant found here: ( http://www.verizonwireless.com/support/devices/knowledge_base.html/80201/ ). I have no idea what the differences are between Verizon's software repair assistant and Kies.... **
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Although your thread will probably be moved to the Q&A section, you stated you are able to install older versions...... take it back into DL mode and Odin 4.4.4. There are several threads you can download the NK4 Firmware from including the Sammobile site.
SM-N900P Spint (cdma) 2014 December 4.4.4 N900PVPUDNK4 N900PSPTDNK4
shadowcliffs Thread in the General Section
.
k0ncept said:
So i have a stock sprint note 3 that had 4.4.4 on it.
I attempted to install twrp/cwm through odin, but it failed and now i'm stuck in the failed firmware update loop.
I have tried installing older versions of the stock firmware, seems like i'm stuck looking for a 4.4.4 which seems kinda hard to find right now.
What are my other options, my friend is looking for the serial numbers to see if i can just use keis to recover.
Click to expand...
Click to collapse
Honestly it sounds like you're making this more difficult than it really is.
All you need is;
NK4 .tar
SU
&
TWRP
So i'm fairly new to this the last phone i did was my vz s4 (and it went off with less bumps).
I'm stuck in the boot load loop. I can't flash any ROM on it right now, i think i'm trying to find the right 4.4.4 rom. Any place with good rom support would help. sammobile is far too slow on downloads...also there are a few 4.4.4 roms by now.
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
k0ncept said:
So the phone was purchased in early Nov 2014, already on a 4.4.4.
I dl'd odin and a TWRP, foolishly didn't make sure 4.4.4 could be flashed in the same way. Odin marked it as failed and when i re-start the phone it runs into the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
The phone can get into download mode just fine (cannot boot)...tho i have no idea what to flash onto it now.
Click to expand...
Click to collapse
As Nickitt stated, don't make it more than it is. If you can get into DL mode then you are not fully bricked which is good. You need to flash an " Official 4.4.4 Firmware " to get you out of this situation, whether it be a slow download or not. I provided a link in my original first response of several uploads of 4.4.4 that you could possibly use that were uploaded by member shadowcliffs in his same thread/post. After you have flashed the official firmware and gone through the initial setup once again with the stock firmware, get the phone back into DL Mode and flash TWRP or Philz CWM recovery via ODIN. Once you have your custom recovery loaded, flash the Custom Rom of your choice.
Hey dark,
thanks for the quick and very very useful response. i wish i hit this up way sooner i did find those links after hours of searching through garbage. i've been downloading a few 4.4.4 images for the last 2hours. Hopefully this will help me! sadly those are the same slow connections i've scene. damn 50kb/sec so sad haha
I'll keep the board posted. but mostly bump that og thread
Damn, fails on the nk4 image and the nh7.
fails on the same spot system.img.ext4
any other suggestions board? please?
make sure your using the hltespr version of either TWRP or philz recovery, if its not working on TWRP switch to philiz. Could also be a bad download - re-download and flash again
Why don't you just use TWRP Manager to install TWRP after you root?
Sent from my GALAXY Note 3 via Tapatalk
not being able to root was the problem
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
problem solved
Thanks for updating that you fixed the problem and what it was. It sounded like you were doing everything correctly. i was getting concerned that it wasn't working. I don't use mac, but if i did i would have been very grateful for that knowledge. thanks for the update. too often someone fixes the problem and just quits posting on the thread.:good:
k0ncept said:
FIXED my issues!!
Never use vmware and Mac to run heimdall or Odin... They should more prominently tell you that.
Thank you board for the concern
Click to expand...
Click to collapse
Parallels is a better option imo as far as v-machines are concerned but anything after Mountain lion doesn't work well. The newest mac osx doesn't work at all with Heimdall. It won't download the pit file. If your running mavricks you can try using a program called winebottle
How to Run Odin On Mac: http://youtu.be/j7fpouzMSsk also jOdin is another desktop tool to use. jOdin is a early stage online flashing tool with limited capabilities at this time.Beings its a online flashing tool. I would make sure to have a good internet connection or you could run into trouble im guessing. All in all I think its a good idea I just hope this project keeps going.
JOdin - Using Odin on a Mac: http://youtu.be/MiPRXq207Ug
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
k0ncept said:
It's only right jag.
Goat, thanks for the additional information. I hope there are improved options for the mac and Linux one day
Click to expand...
Click to collapse
Me too bro, me too!