Related
I flashed my Nexus S with CM7 RC 4. Accidentally my original nandroid backup got deleted. I want to flash my device with the factory android 2.3.3 image. Please let me know the link to download the Android 2.3.3 for SNS 9023 GRI54.
You find it on:
http://forum.xda-developers.com/showthread.php?t=973534
I have already downloaded the rom files and the odin but the odin don't recognise my NS.
Can you tell me how to do a fastboot flash ?
If you want odin to recognize your nexus you have to install the samsung usb drivers .. You can find them here: http://forum.xda-developers.com/showthread.php?t=728929
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
I do not have a fastboot image for you ..btw the google drivers are not the same as the samsung drivers ..for odin you will need the samsung ones ...
To go into downloadmode :
turn on you phone, plug your phone into a sb port ( as if you wanted to put something on the phone) then while your phone is still connected to your pc , switch you phone off and keep holding vol up + vol down ..you will see that if you keep holding them phone will go into download mode after you phone is switched off
jaivinder said:
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
Click to expand...
Click to collapse
You installed the samsung drivers, make sure that your phone is power on,disable the usb debugging, ceheck that microsoft.net framework is installed on your pc. When you connect your phone (on your device manager) you must have "android phone" and below that "nexus s" with out any question symbols.If so then select to update your driver and give the path you installed the samsung drivers (eg c:\program files\samsung ....).
Power off you phone, open Odin and follow the pdf file from samfirmware to load the files (bootloader,pda,modem,csc). Hold your phone from the middle of volume buttons(between vol up and vol down) and immediately connect your phone to your pc with the usb cable .you are going to see the yellow triangle with the android.
Try it
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
hamajiro said:
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
Click to expand...
Click to collapse
What kind of error?on Odin or on your phone?
afilopou said:
What kind of error?on Odin or on your phone?
Click to expand...
Click to collapse
On Odin. The error message is in Korean so I don't know what it says, but it says something about the PDA tar. Please see the attached image.
Thanks
If I do it without PDA, I don't get an error...
hamajiro said:
If I do it without PDA, I don't get an error...
Click to expand...
Click to collapse
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
afilopou said:
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
Click to expand...
Click to collapse
Thank you so much for your help.
I don't have a windows PC, but I'll install Windows 7 to my MBP using bootcamp and see how that goes.
I'll check the md5 check sum as well.
Sent from my Nexus S using XDA Premium App
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
hamajiro said:
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Looks like that the virtual machine (vm fusion) on macosx generates problems.As far as i remember only parallels worked ok.I have imac as well but i have bootcamp win7 in order to avoid all these problems. Hope to help
Sent from my Desire HD using Tapatalk
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
hamajiro said:
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
Click to expand...
Click to collapse
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
thanks, really needed this link
afilopou said:
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
No, I don't remember the initial values...
I'll check them at a Vodafone store when I get a chance.
Sent from my Nexus S using XDA Premium App
OK, so I had a chance to go into a local Vodafone Australia store.
The Baseband version under 'About phone' from the settings was I9023XXXKB1.
Under fastbootmode, the bootloader and baseband versions were I9020XXXKA3 and I9020XXXKB1.
However, CARRIER INFO is 'XSE' for Vodafone Australia, where as the CARRIER INFO from the Samfirmware.com ROM is 'EUR'.
Almost back to factory stock condition! Is it possible to change the carrier info? Does anyone know where I can get the stock Australian ROM for Nexus S?
Hi,
I flashed Litenin (and other custom roms) with Heimdal on Linux flawlessy up to version 1.4 which hangs at boot.
I had to replace factoryfs.img with previous version's one (kernel and modem are from 1.4 still and it works....).
Is it a bug in heimdall or something wrong with Litenin rom 1.4 ?
A factory reset didn't help either, 1.4 can't be installed on my phone, at least not with heimdall.
Ciao
Max
bump !
Nobody using heimdall and litening rom here ?
I have exact the same problem....
tschakk said:
I had exact the same problem....
Click to expand...
Click to collapse
Did you solve it ? Flashing with Odin does the trick ?
No.. I dont have access to a win box...
but i think odin should work - another user reported after switching to odin everything was ok....
weird.
I'll try later on unpacking and repacking the factoryfs.img, maybe there's something on it which makes heimdall behava wrong.
Thank you for feedback
Could u resolve the problem?
Sent from my GT-I9100 using XDA App
Nope, unpacking and repacking didn't work either.
It seems that heimdall don't like 1.4 version
OK. thanks for the try...
I could access a windows computer this weekend. Odin worked fine...
I never got Heimdall working. It cant find my phone.
hmmm I did nothing special. What OS u use?
(Ubuntu)
1. I Install libusb-1.0 like described on the official heimdall homepage.
2. Install the heimdall .deb package.
3. put your phone to download mode
4. Start heimdall like: sudo heimdall print-pit
I only used the console edition (1.2.0) - not the gui edition...
For flashing type:
sudo heimdall flash --<partition identifier> <filename>
Lite'ning Rom v1.5 XXKF2
Lite'ning Rom v1.5 XXKF2 has just been released. Has anybody tried flashing the new version via Heimdall?
The link has been removed before I could try it
Yes, I saw that people were having problems with it. When the new version is up we can try it again.
Ok, just flashed Litening v1.5 with heimdall.
Everything worked as expected...
Nice, I'll try it tonight.
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
TheBishopOfSoho said:
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
Click to expand...
Click to collapse
I've used the same configuration to flash my SG2. But you do realize that VirtualBox is using the same ubuntu (linux) drivers for usb?
And why do you find windows to be more reliable?
TheBishopOfSoho said:
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
Click to expand...
Click to collapse
I cant share your opinion. Im working now for more than a year with Android. We have our own android build. And i had much less problems working with Linux (Ubuntu) than with Windows...
Flashed Litening rom 1.5 just fine with Heimdall in Ubuntu 11.04.
I currently have the EC05 modem with SRF1.2 and Genocide 2.0 kernel. I'm getting some dropped calls, and my bluetooth isn't consistently connecting in my car, so I want to try a different modem. The problem is that I have a Mac. The only Windows machine I have access to is my computer at work, and it for some reason fails everytime I try to install the Epic drivers. I'm aware of using ODIN to flash new modems, but this isn't an option for me. I tried getting Heimdall to work on my Mac, but for some reason it wasn't allowing me to do anything (almost like view only). Are there any update.zip files or some way to flash a new modem using my Mac?
pharmer81 said:
I currently have the EC05 modem with SRF1.2 and Genocide 2.0 kernel. I'm getting some dropped calls, and my bluetooth isn't consistently connecting in my car, so I want to try a different modem. The problem is that I have a Mac. The only Windows machine I have access to is my computer at work, and it for some reason fails everytime I try to install the Epic drivers. I'm aware of using ODIN to flash new modems, but this isn't an option for me. I tried getting Heimdall to work on my Mac, but for some reason it wasn't allowing me to do anything (almost like view only). Are there any update.zip files or some way to flash a new modem using my Mac?
Click to expand...
Click to collapse
I don't believe so. Did you try running Heimdall on linux on the Mac? Heimdall also has Windows drivers if Odin doesn't work on that PC then maybe Heimdall will. You need to use modem.bin in Heimdall....extract it from the .tar file with 7zip.
I couldn't get heimdall to recognize my epic either. I don't believe our secondary bootloader has been fixed with the bug that was preventing Macs from working. I have odined to eb13 and even dg27 and gotten ota updates to ec05 but never get recognized on the mac. Heimdall works fine on my work PC though. You might try Linux on your mac that or bootcamp to XP or 7
stilesja said:
I couldn't get heimdall to recognize my epic either. I don't believe our secondary bootloader has been fixed with the bug that was preventing Macs from working. I have odined to eb13 and even dg27 and gotten ota updates to ec05 but never get recognized on the mac. Heimdall works fine on my work PC though. You might try Linux on your mac that or bootcamp to XP or 7
Click to expand...
Click to collapse
According to the Heimdall website, the second bootloader problem for Mac was fixed with Froyo 2.2. Of course Heimdall doesn't officially support Epic and I don't have a Mac (just Linux and Windows) so I haven't tried it.
To the OP:
What version of Heimdall are you using? Are you using the GUI or the command line?
There may be a problem with the GUI not acting the way it's expected. If nothing else works, I would recommend:
1. install Heimdall 1.2.0 (command line).
2. boot phone into download mode (power + 1 key)
3. attach phone to computer
4. see if heimdall recognizes the phone by using the command
heimdall print-pit
Click to expand...
Click to collapse
. That should give you a listing of the partitions on your phone. It will reboot your phone.
If that works, then repeat steps 1-3. Then to upload a different modem just use
heimdall flash --modem <file name>
Click to expand...
Click to collapse
where <file name> is the file name for the modem. I don't know how you specify the directory for files in Mac, but in linux I just navigate to the file and open the terminal window to save on the cd commands.
I was trying to use the GUI interface. I'll mess with it some more tonight if I get time and see if I can get it to work using command line. I also may try to bootcamp Linux if that works. Just curious, what are most people using for Linux...Ubuntu, Mint, or something else?
Yes it's will do it with ec05
Sent from my SPH-D700 using XDA Premium App
pharmer81 said:
I was trying to use the GUI interface. I'll mess with it some more tonight if I get time and see if I can get it to work using command line. I also may try to bootcamp Linux if that works. Just curious, what are most people using for Linux...Ubuntu, Mint, or something else?
Click to expand...
Click to collapse
I just started to use Mint 11. It's been almost 15 years since the last time I used linux shell.
hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.
MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app
spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip
And it works--
rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:
myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:
Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you
Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Hi im new to this really i recently got the tab 4 and needed to root it so i can mirror my screen with the chrome-cast doggle for an application xbmc . I found guide on internet to use Odin to root it and ive used Odin before to root a few phones but when i tried to use the PDA option within ordin to apply the tar file that was in zip - CF-Auto-Root.tar the process started but then failed for some reason. The device then said i need to kies to emergency firmware restore but kies 3 said it does not support my device. Ive been looking for solution on net to no joy and now device must of died or somit but all i get is black screen and wont turn on. please help....
Tyandroid said:
Hi im new to this really i recently got the tab 4 and needed to root it so i can mirror my screen with the chrome-cast doggle for an application xbmc . I found guide on internet to use Odin to root it and ive used Odin before to root a few phones but when i tried to use the PDA option within ordin to apply the tar file that was in zip - CF-Auto-Root.tar the process started but then failed for some reason. The device then said i need to kies to emergency firmware restore but kies 3 said it does not support my device. Ive been looking for solution on net to no joy and now device must of died or somit but all i get is black screen and wont turn on. please help....
Click to expand...
Click to collapse
Which Tab4 do you have? Tmobile? If so I have a zip file you can use to odin back to stock. I had the same thing happen to me when I tried to root. Once it gets to that point, kies doesn't seem to function. But odin still recognizes the device. I have an SM-T337T. Let me know.
Could you post the link of the rooting method site please?
Sent from my SM-T530NU using Tapatalk
1116
magda623 said:
Which Tab4 do you have? Tmobile? If so I have a zip file you can use to odin back to stock. I had the same thing happen to me when I tried to root. Once it gets to that point, kies doesn't seem to function. But odin still recognizes the device. I have an SM-T337T. Let me know.
Click to expand...
Click to collapse
MY galaxy tab 4 is the wifi version model SM-T230 and ive been trying to get stock file even tho its at that screen where it says
Firmware upgrade uncounted an issue. please select recovery mode in kies and try again.
its still in download mode so odin will fix it in theory. i downloaded this file named ;
T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 but think its for another model coz of the NU after T230 that never worked and been looking for my model to to avail and im still green when you come to this i feel like im out my depth.
now when i connect it to kies it says device not supported and screen flashes on off. im using a win xp machine will that make any difference aswell.
thank you
Tyandroid said:
MY galaxy tab 4 is the wifi version model SM-T230 and ive been trying to get stock file even tho its at that screen where it says
Firmware upgrade uncounted an issue. please select recovery mode in kies and try again.
its still in download mode so odin will fix it in theory. i downloaded this file named ;
T230NUUEU0ANE2_T230NUXAC0ANE2_HOME.tar.md5 but think its for another model coz of the NU after T230 that never worked and been looking for my model to to avail and im still green when you come to this i feel like im out my depth.
now when i connect it to kies it says device not supported and screen flashes on off. im using a win xp machine will that make any difference aswell.
thank you
Click to expand...
Click to collapse
Only think i've found for that firmware is a UK version. Not quite sure why there isn't a US version readily available. Anyhow, You can download it from here. The version from June might be able to be rooted using towelroot. But the May version definately can be rooted using that method. Here is the link Hope it helps.
http://www.sammobile.com/firmwares/1/?model=SM-T230&pcode=BTU#firmware