Related
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
Good morning
I Bought a used phone that is already root, i would like to sell to a friend that wants it stock . From my understanding to unroot i must fist make sure the phone is running samsung stock kernel.
Under about device it says
Kernel version
3.4.0-880525 [email protected]#1 sat mar 1 01:36:11 kst 2014
is this stock samsung kernel?
Thanks ahead of time for the help guys
yes its stock kernel
how to i know what provider the phone is
Thank you very much AL_IRAQI
Now I'm at the step where i need to download the stock provider files for the phone but i have no idea what the original provider was.
Is there a way to find out what the stock provider was and can i install a different provider firmware ?
are you sure it was , the phone is stuck in boot screen and it says
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT:KERNEL
akatheproducer said:
are you sure it was , the phone is stuck in boot screen and it says
KERNEL IS NOT SEANDROID ENFORCING
SET WARRANTY BIT:KERNEL
Click to expand...
Click to collapse
The kernel not seandroid enforcing is just a minor thing. Ignore that.
For if you cannot boot in your phone, i suggest flashing ANY AREA's latest 4.4.2 for your phone.
The country/region does not matter till you dont have a carrier branded firmware.
"If someone helps, never forget to hit thanks ?"
DeepankarS said:
The kernel not seandroid enforcing is just a minor thing. Ignore that.
For if you cannot boot in your phone, i suggest flashing ANY AREA's latest 4.4.2 for your phone.
The country/region does not matter till you dont have a carrier branded firmware.
"If someone helps, never forget to hit thanks ?"
Click to expand...
Click to collapse
originally i used odin mobile to flash the latest firmware. at this point the device won't go past SAMSUNG GALAXY S4 logo so i can't use odin mobile.
Since i have a mac and don't have access to a pc to use odin for pc is there a way to flash the s4 with my mac ?
akatheproducer said:
originally i used odin mobile to flash the latest firmware. at this point the device won't go past SAMSUNG GALAXY S4 logo so i can't use odin mobile.
Since i have a mac and don't have access to a pc to use odin for pc is there a way to flash the s4 with my mac ?
Click to expand...
Click to collapse
Flashing via mobile odin will softbrick or brick your device.
Why did you even try that before reading? Uneducated experimenting is not supported here.
Now you must have a pc for odin to work. Or else if you can create a virtual machine, do that in your mac and proceed
"If someone helps, never forget to hit thanks ?"
DeepankarS said:
Flashing via mobile odin will softbrick or brick your device.
Why did you even try that before reading? Uneducated experimenting is not supported here.
Now you must have a pc for odin to work. Or else if you can create a virtual machine, do that in your mac and proceed
"If someone helps, never forget to hit thanks ?"
Click to expand...
Click to collapse
I'm going to install windows on my mac, what version of windows is idea for odin.
Could i just put the firmware on the sd card an click the update from sd card option ?
Or you just use heimdall to flash using your mac. It's not that hard.
I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?
fajrero said:
I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?
Click to expand...
Click to collapse
Check the github, theres some forks you can try, i have a thread about this you can check.
Sent from my SM-G900A using Tapatalk
Rakuu said:
Check the github, theres some forks you can try, i have a thread about this you can check.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?
fajrero said:
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?
Click to expand...
Click to collapse
EDIT: I appologize, i didnt reread my reply, heres the link to thread i waa referring to http://forum.xda-developers.com/galaxy-s5/help/unofficial-linux-support-thread-t2832106
Sent from my SM-G900A using Tapatalk
I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?
fajrero said:
I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?
Click to expand...
Click to collapse
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.
Sent from my SM-G900A using Tapatalk
Rakuu said:
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.
However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.
fajrero said:
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.
However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.
Click to expand...
Click to collapse
Same as my last post, havent used it so i wouldnt know. Also if you do softbrick youll need to get heimdall working or find a windows computer, which honestly, you can beat around the bush sith apps and stuff but at the end of the day i think youll need to use heimdall or odin.
Sent from my SM-G900A using Tapatalk
I went through the TWRP installation with the installer from the Play store, installing the latest version of TWRP. Just as it got to the step for the actual installation, it crashed...
So, I try to reboot into recovery, and I'm greeted by these words: "RECOVERY IS NOT SEANDROID ENFORCING. Set Warranty Bit: recovery". My heart sinks, but then I see the Team Win splashscreen come up, and I'm in TWRP. I tap the Reboot button, and it boots back into Android. Everything seems to be fine, aside from the crash during installation and this mysterious error.
I'd like to install Cyanogen, but I prefer deciphering this error first. From what I've been reading, most of the people getting this error have bricked their phones. Maybe I just got lucky? What is this error, and should I worry about it?
Posted first on reddit but didn't get to much help there. Someone suggested a debrick image, however i have not found one for the SM-G900P model of the Galaxy S5(I have found the image for other carriers though :crying
"Long story short I got stuck in a bootloop and now want to go back to stock rom for the Sprint Galaxy S5(SM-G900P). However, before this bootloop I believe I forgot to turn usb debugging on so every time I try to flash stock rom in Odin it hangs on setup connection for 10-15mins then says FAILED. I've tried all the Odin fixes(different usb cable, different usb port, different computer, etc.) and still same issue, I did however notice in BLUE: Secure Download:Enable(I never noticed that while flashing the phone before and think it may be the issue). Phone was rooted, on lollipop 5.0, and had TRWP Recovery on it but booting to bootloader takes me to Odin Mode for some strange reason. Please send any help you can my way."
My Odin Mode looks like this(Sorry for no picture):
--------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SM-G900P
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
-------------------------------------------------------------------
~Android Logo
~Downloading..
~Do not turn off target!!
If you need any more info about phone please let me know.
MrHundreds said:
Posted first on reddit but didn't get to much help there. Someone suggested a debrick image, however i have not found one for the SM-G900P model of the Galaxy S5(I have found the image for other carriers though :crying
"Long story short I got stuck in a bootloop and now want to go back to stock rom for the Sprint Galaxy S5(SM-G900P). However, before this bootloop I believe I forgot to turn usb debugging on so every time I try to flash stock rom in Odin it hangs on setup connection for 10-15mins then says FAILED. I've tried all the Odin fixes(different usb cable, different usb port, different computer, etc.) and still same issue, I did however notice in BLUE: Secure Download:Enable(I never noticed that while flashing the phone before and think it may be the issue). Phone was rooted, on lollipop 5.0, and had TRWP Recovery on it but booting to bootloader takes me to Odin Mode for some strange reason. Please send any help you can my way."
My Odin Mode looks like this(Sorry for no picture):
--------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SM-G900P
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
-------------------------------------------------------------------
~Android Logo
~Downloading..
~Do not turn off target!!
If you need any more info about phone please let me know.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best available help, I'm going to move this thread to your device's Q&A forum. Good luck!
Hi @MrHundreds......
First of all, USB debugging has absolutely no impact on Odin flashing....
Whether it's enabled or disabled makes no difference.....
Second...
Don't give up on trying to odin flash.....
Perseverance is the name of the game...
Do the usual things....
Make sure antivirus and firewalls are disabled.
Make sure you have the Samsung usb drivers installed.
If you have Kies on your PC/Laptop, disable it in task manager before running Odin.
Run Odin as an administrator.
Only use usb sockets that are directly connected to the PC/Laptop main board.
Try multiple usb cables.....The one that came with the phone should be your primary choice though.
Try different versions of Odin (though the newer versions will have a better chance of working)
Re download the firmware package....just to rule out the possibility of a corrupt file (it does happen)
Try all of the above on different PC's with different OS versions.....it *can* be as simple as that....xp, vista, 7 & 8 all have successful track records....can't vouch for 10 though.
You could (as a last resort) try flashing a pit file with the firmware....this will erase every trace of the previous OS from your device as it flashes the new OS.....normally all odin does is overwrite what is already on the device.....but a word of caution.....If you flash the wrong pit, or the pit flash fails, it will permanently brick the device.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Hi @MrHundreds......
First of all, USB debugging has absolutely no impact on Odin flashing....
Whether it's enabled or disabled makes no difference.....
Second...
Don't give up on trying to odin flash.....
Perseverance is the name of the game...
Do the usual things....
Make sure antivirus and firewalls are disabled.
Make sure you have the Samsung usb drivers installed.
If you have Kies on your PC/Laptop, disable it in task manager before running Odin.
Run Odin as an administrator.
Only use usb sockets that are directly connected to the PC/Laptop main board.
Try multiple usb cables.....The one that came with the phone should be your primary choice though.
Try different versions of Odin (though the newer versions will have a better chance of working)
Re download the firmware package....just to rule out the possibility of a corrupt file (it does happen)
Try all of the above on different PC's with different OS versions.....it *can* be as simple as that....xp, vista, 7 & 8 all have successful track records....can't vouch for 10 though.
You could (as a last resort) try flashing a pit file with the firmware....this will erase every trace of the previous OS from your device as it flashes the new OS.....normally all odin does is overwrite what is already on the device.....but a word of caution.....If you flash the wrong pit, or the pit flash fails, it will permanently brick the device.
Click to expand...
Click to collapse
I will continue to try to get Odin to work with the methods you suggested above, but as far as other different OS's go I have a slim selection(Windows 7, Windows 10, Ubuntu Mate and Arch Linux). Also would Heimdall have a better chance of working opposed to Odin? I have tried Heimdall once with a pit I found for my device but it also failed. Looking around XDA I found some programs like skipsoft, go thru the whole process up until it is about to flash and replies with waiting for USB debugging to be enabled. Anyways I appreciate your response to my question and will try your "fixes" and see how that goes.
From everything I have read, Heimdall has less of a success rate than Odin....
I've also read that unless you know exactly how to handle it, it is considerably more complicated than Odin.......as such I've never used it and can't really comment on this method.
My (limited) experience stretches as far as multiple Samsung devices and Odin.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
From everything I have read, Heimdall has less of a success rate than Odin....
I've also read that unless you know exactly how to handle it, it is considerably more complicated than Odin.......as such I've never used it and can't really comment on this method.
My (limited) experience stretches as far as multiple Samsung devices and Odin.....
Click to expand...
Click to collapse
Okay i was not able to flash stock rom however I did get TWRP Recovery installed on it after the third try, can I somehow use TWRP to get stock rom back on the phone?(I had all important info backup on pc so i have no problem wiping the phone clean)
MrHundreds said:
Okay i was not able to flash stock rom however I did get TWRP Recovery installed on it after the third try, can I somehow use TWRP to get stock rom back on the phone?(I had all important info backup on pc so i have no problem wiping the phone clean)
Click to expand...
Click to collapse
You can download a custom, TouchWiz-based ROM and flash it to TWRP.
^agreed.....
You can't flash an official firmware through recovery.....wrong file type....
But custom roms aren't a problem.
As mentioned, some of those custom roms are Samsung Touchwiz based, so you'll have the look and feel of stock, but without the disadvantages.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
^agreed.....
You can't flash an official firmware through recovery.....wrong file type....
But custom roms aren't a problem.
As mentioned, some of those custom roms are Samsung Touchwiz based, so you'll have the look and feel of stock, but without the disadvantages.....
Click to expand...
Click to collapse
Okay i was able to get Cyanogenmod installed thru twrp with no issue, phone works good but can i get stock rom on device now that it is no longer in a boot loop.
MrHundreds said:
Okay i was able to get Cyanogenmod installed thru twrp with no issue, phone works good but can i get stock rom on device now that it is no longer in a boot loop.
Click to expand...
Click to collapse
I've read of a couple of cases on XDA (just recently) where a firmware flash just simply will not (for some reason) 'take'.....it's looking like your device may well have to be added to that list.....
Nobody has been able to work out why a firmware flash is unsuccessful....it just *is*......
My advice would be (for the moment) to stay away from official stock, and to experiment with the various available custom roms until you find one that suits you.....
If you *really* want the stock touchwiz 'look' try one of the stock based custom roms.......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
I've read of a couple of cases on XDA (just recently) where a firmware flash just simply will not (for some reason) 'take'.....it's looking like your device may well have to be added to that list.....
Nobody has been able to work out why a firmware flash is unsuccessful....it just *is*......
My advice would be (for the moment) to stay away from official stock, and to experiment with the various available custom roms until you find one that suits you.....
If you *really* want the stock touchwiz 'look' try one of the stock based custom roms.......
Click to expand...
Click to collapse
Oh okay, thank you for all your help you have no idea how grateful I am. I'll stick with Cyanogenmod since I have used it before and like it in general. Thank you from help me get from softbrick to a working phone
No problem fella......it was you doing the sweating though.....I just made some suggestions and handed out some info.....
Glad it's sorted though......
http://i.imgur.com/rVnFwJM.jpg