I have been at this for a week now. I've tried Heimdall 1.1.1, 1.3.2, AND Odin3 v1.83, v1.85, to reflash the stock Verizon firmware on my Galaxy Tab SCH-i800. I was an idiot and flashed U.S. Cellular firmware, which changed the boot animation and the cell service text. I've scoured the internet on how to do this and everything I've tried has failed. With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12" I'm getting my files from SCH-I800_VZW_stock.zip, it's been extracted. When trying to flash a .tar file with Odin, it works successfully, then my phone goes into bootloop. I can get back to Download mode, but every time I try flashing a stock .tar, I get the same results. I'm starting to go crazy. Anyone help?
maybe you have missed with your partions? if so, i think you need a specific pit file for this stock rom, i dont know where it is, but you might start looking for it.
edit : look in this thread, you might find it useful http://forum.xda-developers.com/archive/index.php/t-940046.html
and this is also important http://theunlockr.com/2012/06/28/ho...axy-tab-sch-i800-back-to-stock-and-unroot-it/
last one http://gizmoninja.com/2011/04/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
best regards ^_^
Sifou
chrispysaid said:
....With Heimdall, whenever I plug in the stock files to the program (in 1.1.1 only, I can't figure out 1.3.2 for the life of me) and hit Start, I get "Failed to access device. Error: -12"
Anyone help?
Click to expand...
Click to collapse
Did you properly install the Samsung drivers on your PC using the heimdall utility? And you put your Tab in download mode?
The Problem may lie with youe Heimdall setup.
Make sure you have Keis installed. Then make sure you activate the drivers for Heimdall.
This is a great rom to flash to your VZW Tab. follow this thread http://forum.xda-developers.com/showthread.php?t=1325469
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Ryan990 said:
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Click to expand...
Click to collapse
Try these links from this post buddy
http://forum.xda-developers.com/showthread.php?p=46273175
The #1 misfit
of my crew of misfits
Ryan990 said:
I tried installing Cyanogen Mod but it didn't work, I just got stuck at the boot screen and when I tired to flash back to stock something really went wrong.
Now all I see is an error saying "Firmware upgrade encountered an issue. Pleas select recovery mode in Kies & try again."
But I can still access download mode so from what I can tell I can fix this with the right files and right settings in Odin3.
I have the Sprint Galaxy S4 SPH-L720. I am currently running Odin3 v3.07.
I was trying to flash this in Odin3, qbking77.com/development/how-to-unroot-and-unbrick-the-samsung-galaxy-s4. I got as far as system.img.ext4 before it failed.
Any help would be greatly appreciated. I am still somewhat new to hacking my phone but an very tech savvy and feel comfortable following any directions you have for what to flash with odin3 and what options to use.
Thanks in advance.
Click to expand...
Click to collapse
Been there (that screen is still odin mode). Should be recoverable through odin still. In my case, the problem was that I had a bad tar file. I'd start there, make sure you have the right file for your phone. If you have the right file, it may be a bad download. So I would try to re-download, or naybe try a different version.
Cheers.
Sent from my SGH-M919 using xda app-developers app
Oscar_david said:
Been there (that screen is still odin mode). Should be recoverable through odin still. In my case, the problem was that I had a bad tar file. I'd start there, make sure you have the right file for your phone. If you have the right file, it may be a bad download. So I would try to re-download, or naybe try a different version.
Cheers.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I had used the exact file before so I know its correct and uncorrupted. I did figure it out.
Successfully flashed using another computer. Best I can figure, following the CM installation instructions have a step "Run the included zadig.exe in the drivers folder of the Heimdall Suite."
That does something with drivers that odin must not like. I tried uninstalling, restarting my computer than reinstalling the Samsung drivers but that was not enough. A new computer was the answer.
Ryan990 said:
I had used the exact file before so I know its correct and uncorrupted. I did figure it out.
Successfully flashed using another computer. Best I can figure, following the CM installation instructions have a step "Run the included zadig.exe in the drivers folder of the Heimdall Suite."
That does something with drivers that odin must not like. I tried uninstalling, restarting my computer than reinstalling the Samsung drivers but that was not enough. A new computer was the answer.
Click to expand...
Click to collapse
Wow what one file can do to mess everything up and glad you got it working again buddy
The #1 misfit
of my crew of misfits
Bigger question here is:
Why are some phones experiencing corrupt partitions after flashing AOSP-based ROMs? Myself included....
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
I have a galaxy s4 (i337) that is running the 4.4.2 os. I'm trying to downgrade to 4.2.2 due to the SIM issues... the phone will throw the "SIM card removed" error about ten times in a day and force a reboot, then not even register the SIM and stay in emergency mode. i'm fairly certain this is a software issue because i have the exact same model phone running 4.2.2 and have had absolutely 0 SIM errors.
that being said, i have a mac running 10.10.1 and the heimdall 1.4 for mac (i have also tried this with 1.3.1 after hearing that the latest was buggy. it didn't work either). i have tried using the heimdall interface and terminal to flash the stock files. However, it gives me the "failed to confirm end of file transfer sequence" every time... here's the text that pops up in terminal:
sudo heimdall flash --RECOVERY /Users/RaesMac/Desktop/I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar/recovery.img
Password:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
this is my first attempt at flashing a phone, and i really just want to get it over with so i can give the damn thing back to my partner (who is currently using my old iphone 4, poor guy). i'm not sure if there's just something i'm missing or if it's just not going to work.
so, i come seeking the wisdom of the gurus who reside within this forum. what can i do?
P.S.
the files i downloaded to flash are in a .tar folder titled I337UCUAMDB_ I337ATTAMDB_I337UCUAMDB_HOME .tar"
do i need the -AMDL version for this? i have no idea what the difference is, only that there are two options to download.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
icefireinsanity said:
I have a galaxy s4 (i337) that is running the 4.4.2 os. I'm trying to downgrade to 4.2.2 due to the SIM issues... the phone will throw the "SIM card removed" error about ten times in a day and force a reboot, then not even register the SIM and stay in emergency mode. i'm fairly certain this is a software issue because i have the exact same model phone running 4.2.2 and have had absolutely 0 SIM errors.
that being said, i have a mac running 10.10.1 and the heimdall 1.4 for mac (i have also tried this with 1.3.1 after hearing that the latest was buggy. it didn't work either). i have tried using the heimdall interface and terminal to flash the stock files. However, it gives me the "failed to confirm end of file transfer sequence" every time... here's the text that pops up in terminal:
sudo heimdall flash --RECOVERY /Users/RaesMac/Desktop/I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar/recovery.img
Password:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
Rebooting device...
Releasing device interface...
this is my first attempt at flashing a phone, and i really just want to get it over with so i can give the damn thing back to my partner (who is currently using my old iphone 4, poor guy). i'm not sure if there's just something i'm missing or if it's just not going to work.
so, i come seeking the wisdom of the gurus who reside within this forum. what can i do?
P.S.
the files i downloaded to flash are in a .tar folder titled I337UCUAMDB_ I337ATTAMDB_I337UCUAMDB_HOME .tar"
do i need the -AMDL version for this? i have no idea what the difference is, only that there are two options to download.
Click to expand...
Click to collapse
It's failing because you can't downgrade from 4.4.4 to 4.2.2. It has nothing to do with heimdal.
Sent from my Nexus 5 using XDA Free mobile app
So I'm just stuck with a gimpy phone?
icefireinsanity said:
So I'm just stuck with a gimpy phone?
Click to expand...
Click to collapse
If you think it's a software issue try flashing the nb1 tar file in heimdall. http://forum.xda-developers.com/showthread.php?p=56453100
But, you're not the only one with this problem and there is no consistent fix http://forum.xda-developers.com/showthread.php?p=58228851
Sent from my Nexus 5 using XDA Free mobile app
Hi
Phone: Samsung Galaxy GT-i9500 (International). Currently sitting on stock everything.
Years ago, I was able to successfully flash my Galaxy S2 with Cyanogenmod. I really don't know what else to try now with this S4.
Please bear with me. I know this question has been asked before but I've tried all the solutions that have been posted and I've also spent a lot of time trying other methods of rooting my phone with no success.
I started off following the instructions on wiki.cyanogenmod.org/w/Install_CM_for_i9500 to install Cyanogenmod. I have also tried other instructions for using ODIN.
Things that have been posted as solutions that I've tried:
Plugging the phone in the back USB ports instead of front USB
Plugging the phone into different USB ports
Using a different USB cable
Both Heimdall 1.4RC2 and 1.4.0-win32
Tried the various combinations of upper/lowercase --recovery --RECOVERY etc
WinUSB, libusb0 and libusbk drivers provided by Heimdall's zadig.exe
Using Odin3 v1.85
Using Odin3 v3.07
Tried KingoApp
When I tried using KingoApp it sat for about half an hour running through various exploits and not succeeding. Then eventually it said that the final thing it could try was to reboot into Download mode. I let it do that and the phone got stuck in exactly the same place that Heimdall and ODIN gets stuck. Namely the screen shows the following but no blue bar ever appears or fills up:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
RP SWREV: A3
Downloading...
Do not turn off target!!
Click to expand...
Click to collapse
cygwin md5 check said:
$ md5sum recovery.img
4fbc482479f4d91c619be8dbb79cdb84 *recovery.img
Click to expand...
Click to collapse
cmd log said:
C:\Temp\FLASHING\Heimdall-Suite-1.4.0-win32>heimdall.exe version
v1.4.0
C:\Temp\FLASHING\Heimdall-Suite-1.4.0-win32>heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
--urlsnip--
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
--urlsnip--
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Click to expand...
Click to collapse
I really don't know what else to try at this point. Can someone please give some suggestions or point in me in the right direction?
Hi
Thanks for writing to us at XDA assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
http://forum.xda-developers.com/galaxy-s4
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
http://forum.xda-developers.com/galaxy-s4/help
Good luck!
So what are you trying to do? Flash a recovery?
I see you are running Windows. Just use Odin for it or you can even use jOdin3 (web Odin).
https://builds.casual-dev.com/jodin3/
You don't need Kingoroot. It doesnt even work anymore anyway.
Lennyz1988 said:
So what are you trying to do? Flash a recovery?
I see you are running Windows. Just use Odin for it or you can even use jOdin3 (web Odin).
You don't need Kingoroot. It doesnt even work anymore anyway.
Click to expand...
Click to collapse
Yeah I'm trying to flash Clockworkmod Recovery so that I can then install Cyanogenmod. So far every attempt to load CWM has failed because the process in download mode never begins.
I have tried Odin and it had the same problem as Heimdall. I previously used Heimdall to flash Cyanogenmod onto my Galaxy S2, which is why I tried it again for the S4. When that didn't work I tried Odin.
Nobody Hates Firemen said:
Yeah I'm trying to flash Clockworkmod Recovery so that I can then install Cyanogenmod. So far every attempt to load CWM has failed because the process in download mode never begins.
I have tried Odin and it had the same problem as Heimdall. I previously used Heimdall to flash Cyanogenmod onto my Galaxy S2, which is why I tried it again for the S4. When that didn't work I tried Odin.
Click to expand...
Click to collapse
Odin should work though.
Lennyz1988 said:
Odin should work though.
Click to expand...
Click to collapse
It doesn't though. I don't get any error message which makes this very difficult to investigate. It just doesn't start transferring the recovery.
I just tried using towelroot v3 and got a message, "This phone isn't currently supported" - even though Galaxy S4 is supposedly supported. I wonder if I have some weird variant model.
It says the following in the about screen:
Model number: GT-I9500
Android version: 4.4.2
Baseband version: I9500XXUGNF6
Kernel version: 3.4.5-2434847 / [email protected] #1 / Wed Aug 6 16:24:19 KST 2014
Build number: KOT49H.I9500XXUGNH2
SE for Android status: Enforcing / SEPF_GT-I9500_4.4.2_0024 / Wed Aug 6 16:24:19 KST 2014
You are trying outdated root methods. The only root method that will work is cf-root, though you need to flash it. Are you running a virtual machine or something?
You should delete every driver related to the s4 from your pc and try from scratch.
Lennyz1988 said:
You are trying outdated root methods. The only root method that will work is cf-root, though you need to flash it. Are you running a virtual machine or something?
You should delete every driver related to the s4 from your pc and try from scratch.
Click to expand...
Click to collapse
CF-root worked, thank you! Used the one at download.chainfire.eu/326/CF-Root1/CF-Auto-Root-ja3g-ja3gxx-gti9500.zip?retrieve_file=1
I'm not running VM or anything. It frikken sucks that the instructions on Cyanogenmod aren't up to date And also sucks that every other site I went to with instructions doesn't mention that they're outdated root methods. The price of being a noob...
Thanks for showing me the way.