Long Post: tried to include more details.
Phone: Samsung Galaxy S4 SCH 1545 16 GB
OS: Lollipop 5.0.1 up to date through OTA updates from Samsung with OF1 kernel build.
Device was Rooted recently
Wanted to upgrade to Marshmallow using latest CWM nightly, mainly to see how the use SD card as internal memory works. The phone's internal memory was running out and I could not move a lot of apps to the SD card.
Steps Done: Developer mode--> USB Debugging and Unkown sources install checked
1. Root using KingRoot and check root access using Root checker basic. Everything looked good.
2.Install ROM Manager, Flash CWM recovery for S4 I 545 and try to backup current ROM: Could not back up current ROM, android recovery loaded up in
3. Back up app data and transfer to SD card using Titanium backup
4. Rolled back to factory reset through android recovery and retried --> Still booted up in android recovery.
5. TWRP and Rashr and re-tried to flash recovery as well --> No Results
6 Decided to roll back firmware using ODIN using the following builds:
1. SCH-I545_MDK_562219_Stock_Restore This was 4.4.2
2. I545VRUGOC1_I545VZWGOC1_VZW: from samx This was one build older than the latest build with the OC1 kernel
Used the following versions of ODIN to try and re flash:
1. Odin3_v3.10.7
2. Odin307
3. Odin3v185
Same result with all of them:
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Now I have a device that I can no longer use and is stuck in ODIN mode
This is the error message that I see:
Software update failed: Your device did not update successfully. USe verizon software repair assistant on a computer.
Need help with to get S4 back to life and best way to install a custom recovery.
You can not use CM ROMs on this build or any CWM or SS (SafeStrap) we can ONLY use FF (FlashFire) which, unfortunately, very highly limits our choices of custom ROMs compatible for us!
Go here:
http://www.samsung.com/in/support/usefulsoftware/KIES/
Download Samsung Kies 3, install everything (application, drivers, etc.) and open it.
When it fully loads after opening click on Tools in the top menu then click on Firmware Upgrade and Initialisation.
Just follow the on screen instructions.
Try this to root after you restore from above steps:
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
READ!
...and, by what I can tell, the three custom ROMs listed there are all we have a choice of or just stay stock rooted, your choice.
Tell me what happens after.
AlphaTekk said:
You can not use CM ROMs on this build or any CWM or SS (SafeStrap) we can ONLY use FF (FlashFire) which, unfortunately, very highly limits our choices of custom ROMs compatible for us!
Go here:
http://www.samsung.com/in/support/usefulsoftware/KIES/
Download Samsung Kies 3, install everything (application, drivers, etc.) and open it.
When it fully loads after opening click on Tools in the top menu then click on Firmware Upgrade and Initialisation.
Just follow the on screen instructions.
Try this to root after you restore from above steps:
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
READ!
...and, by what I can tell, the three custom ROMs listed there are all we have a choice of or just stay stock rooted, your choice.
Tell me what happens after.
Click to expand...
Click to collapse
Thanks AlphaTekk.
I got it working through an Odin reflash:
Run Odin 3.09 as administrator and with compatibility mode for XP SP 3
Use I545VRUGOF1 stock firmware from Sammobile
The end result showed as failed, but still the phone rebooted into stock OS.
Retaining stock OS without root for now.
Related
Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
You could e-mail the editor of the mag and complain
Sent from my GT-I9100 using xda premium
ultimatebestusername said:
Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
Click to expand...
Click to collapse
I suggest you restart from scratch following these steps:
1. read everything about flashing and rooting you can find on this site (read stickies first)
2. same as 1.
3. same as 1.
4. flash the latest stock firmware for your phone
5. root your phone
6. finally flash some other ROM
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM...
Performs a wipe date , factory reset , then follow the guide;
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
Simple way to root and unroot stock kernel without flashing insecure kernel.
Don't worry about custom counter and yellow triangle, with this method they never appear, because we only rooting, it's a rooting script not a custom kernel.
This rooting script included Busybox installer.
Rooting
Download this File first and put in your SDCARD
- CWM via stock recovery ;( http://dl.dropbox.com/u/34053267/CWM.zip) , or download zip from http://clockworkmod.com/rommanager
- SU-Busybox-Installer.zip ( https://dl.dropbox.com/u/34053267/SU-Busybox-Installer.zip )
Reboot to recovery.
Choose apply update from external storage.
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard or external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Method 2
CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel
Quote:
First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/showthread.php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
Flash the CF_Root kernel with odin
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernels for you? use Mobile Odin free version (see below)
After flashing the stock kernel, root will usually stay and you will be reverted back to your stock recovery instead of CWM recovery
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
porter46985 said:
samsung galaxy s4 sch-1545 vzw
i tried to install a custom rom somthing wrong and now no phone
i can get into download mode but thats it. when i turn on the phone it tells me to connect
to kies to do a recovery but my device is not supported
i have tried to flash stock rom in odin but it fails everytime not sure what im doing wrong please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2735172
Flash the full-wipe version in Odin.
Then if you want custom roms, follow my instructions:
First, obtain root. Go to your Settings/Security, check "allow installation from unknown sources". Go to www.towelroot.com , click on the lambda, install the towelroot.apk, then open it and hit "make it ra1n". After reboot, download SuperSU. Open it, it will prompt you to update binaries, do so using the "normal" option. Congrats, you're rooted.
The only custom recovery you can have on NC5 is Safestrap, no TWRP or CWM. You can only flash TW rom's and a select few GPE rom's. You need to use AT&T's 3.72 safestrap for kit kat rom's, which can be found here: http://forum.xda-developers.com/show....php?t=2448925
To install safestrap, first install busybox. Find it here: https://play.google.com/store/apps/d....busybox&hl=en
Then, change selinux status to permissive. Do this by using selinux mode changer: https://play.google.com/store/apps/d....selinux&hl=en
Now install the safestrap apk, open it and hit the install recovery button.
To flash a kit kat rom with SS 3.72, you must use the "stock" slot. ROM slots don't work. You can still make a backup of your stock rom incase anything goes wrong. Be warned, you should have Odin and an NC5 tar file ready to go at all times on your comp.
So, you install the rom like you normally do with TWRP or CWM. Wipe data, cache, dalvik cache, system. Then flash rom, modules, and SuperSU.
The NC5 modules are here: https://www.androidfilehost.com/?fid=23486521113837640
The SuperSU zip is here: http://forum.xda-developers.com/show....php?t=1538053
If you forget to flash SuperSU, you may lose root. You can still get it back by using towelroot. If Wifi isn't turning on, try going back into Safestrap and flashing this: https://www.androidfilehost.com/?fid=23487008491963696
To install one of the Google Play Edition ROM's, use the directions in this thread: http://forum.xda-developers.com/gala...ition-t2817708
Click to expand...
Click to collapse
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
statikeffeck said:
I seem to have the same exact phone and problem as this guy, so I'll jump in here. I've been working on my un-bootable Verizon Samsung Galaxy S4 i545 phone for about 4 full evenings with no luck.
My history up to this point:
Have Verizon Galaxy S4 i545 with latest OTA stock updates, never rooted. Build number ends with NC5.
Sunday night, performed Towelroot.
Installed SuperSU and SafeStrap.
Performed steps to disable KNOX.
Booted into SafeStrap 3.72.
OK, backed up the Stock Rom to my ext 64gb SD card.
Created a new ROM Slot and tried to install Google Play Edition S4 ROM to it.
On reboots it was booting into the regular Stock ROM (which I had factory reset btw) instead of my custom ROM, even though ROM Slot 1 was active.
Deleted ROM Slot 1 and tried flashing my ROM to Stock ROM slot.
Seem to fail.
SafeStrap now reports this when I click on STOCK ROM:
System partition Size: 0MB (0MB Free)
Data partition Size: 0MB (0MB Free)
Cache partition size: 2046MB (1984MB Free)
OK, so SafeStrap is clearly very messed up.
Booted into Download mode.
Got Odin 3.09 installed on Windows and got the firmware provided here: rootjunkysdl - dot - com/?device=Galaxy%20S4&folder=Firmware that ends in NC5 -- by the way the forum link you posted has dead 404 download links for both Firmwares. Seems like RootJunky was kind enough to mirror them on his server though.
Odin hangs when I try to flash the .tar.md5 file -- it says Device Added and the COM port is there so I know it's connected. After a few minutes with no progress or changes, it says "Complete(Write) operation failed" FAIL.
I think my phone's partitions got screwed up, or else it has a write lock on it. Any help would be MUCH appreciated and will even donate $25 to a project of your choosing upon getting this working.
UPDATE: Sure enough, just 15 minutes after I posted this I gave it one more full go in Odin 3.07 instead of 3.09 and it seems to be working now. Not sure if that had anything to do with it. Sucks that this phone can't work with custom recoveries like ClockWork... SafeStrap takes up a lot of extra space because you have to store both roms on the card at once.
Update 2: You also posted an Error 404 link to the Google Play Edition forum post. I'd like to get that on my phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
liljoe727 said:
You should see about getting this stickied on Q and A. It seems nobody reads anything and maybe a title like "EVERYTHING YOU NEED TO FIX YOUR SOFT BRICKED PHONE" might get some reads.... just a thought.
Click to expand...
Click to collapse
I would but I honestly have no confidence in anyone reading a sticky haha
joshm.1219 said:
http://forum.xda-developers.com/gal...ow-to-install-aosp-s4-google-edition-t2817708
Here you go
I would but I honestly have no confidence in anyone reading a sticky haha
Click to expand...
Click to collapse
That would be.... revolutionary. Lol.
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
I probably shouldn't have even attempted this without more info, apparently, but I wanted to give Cyanogenmod and lolipop a try, so I sort of blundered ahead and now Im soft bricked at the "Firmware upgrade encountered an issue." screen.
So, basically first I tried to update TWRP from 2.7 to 2.8.5 via TWRP updater on the play store. It rebooted and didn't take, so I went and proceeded with installing Cyanogenmod via 2.7 TWRP, wiped the pertinent caches and such, and the flash seemed to take, but when I rebooted, I couldn't get passed the Galaxy S4 screen and I had weird brief flickering when I rebooted to try to get it working again, which it never did.
At this point, I just figured I would flash the backup I made prior to trying to install Cyanogen, but that flash failed and I was stuck at Odin, with no option to boot into recovery.
Here is where I probably screwed things up even more, as I didnt realise there was a specific ROM I was supposed to flash from Odin, so I've tried and failed to flash a bunch of stock images I've found online, none of which appear to be the right one. Im stopping here and deferring to the forum for some help, hopefully. Apologies if this is a common thing, but my searchings haven't turned up anything I can use, and Im afraid to screw up my phone more.
The last image I tried to flash was this:
SCH-I545_VZW_1_20130613171315_24s13crny1_fac
Odin got to aboot.mdn and then failed, with this message
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
the ODIN screen on my phone reads
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
EMAC BURST MODE: enabled
START [224,1440]
SW REV, CHECK FAIL : fused : 6(or possibly 8? it looks more like a 6 though), Binary : 3
Also, I wasn't aware I needed a PIT file, so at this point I pretty much need every relevant file and detailed instructions on what to do. Apologies for my noobishness, this is the first time in 5 years I've needed this much help flashing a ROM... =(
Thanks in advance!
Edit: The problem was indeed that I was trying to flash an older ROM onto my phone. For the stupid inclined, always check what baseband model your phone is before flashing a stock image. If you're locked out of the OS, you can find this on the sticker on the side of the box your phone came it, under the listing "s/w" version, the last three characters will tell you what baseband version your phone shipped with.
Beginning to see where I went wrong in Odin, as I've been trying to flash earlier android versions. Downloading an NC5 factory image now, Will report back.
Christ, Im an idiot.
mort_subite said:
I probably shouldn't have even attempted this without more info, apparently, but I wanted to give Cyanogenmod and lolipop a try, so I sort of blundered ahead and now Im soft bricked at the "Firmware upgrade encountered an issue." screen.
So, basically first I tried to update TWRP from 2.7 to 2.8.5 via TWRP updater on the play store. It rebooted and didn't take, so I went and proceeded with installing Cyanogenmod via 2.7 TWRP, wiped the pertinent caches and such, and the flash seemed to take, but when I rebooted, I couldn't get passed the Galaxy S4 screen and I had weird brief flickering when I rebooted to try to get it working again, which it never did.
At this point, I just figured I would flash the backup I made prior to trying to install Cyanogen, but that flash failed and I was stuck at Odin, with no option to boot into recovery.
Here is where I probably screwed things up even more, as I didnt realise there was a specific ROM I was supposed to flash from Odin, so I've tried and failed to flash a bunch of stock images I've found online, none of which appear to be the right one. Im stopping here and deferring to the forum for some help, hopefully. Apologies if this is a common thing, but my searchings haven't turned up anything I can use, and Im afraid to screw up my phone more.
The last image I tried to flash was this:
SCH-I545_VZW_1_20130613171315_24s13crny1_fac
Odin got to aboot.mdn and then failed, with this message
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
the ODIN screen on my phone reads
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
EMAC BURST MODE: enabled
START [224,1440]
SW REV, CHECK FAIL : fused : 6(or possibly 8? it looks more like a 6 though), Binary : 3
Also, I wasn't aware I needed a PIT file, so at this point I pretty much need every relevant file and detailed instructions on what to do. Apologies for my noobishness, this is the first time in 5 years I've needed this much help flashing a ROM... =(
Thanks in advance!
Edit: The problem was indeed that I was trying to flash an older ROM onto my phone. For the stupid inclined, always check what baseband model your phone is before flashing a stock image. If you're locked out of the OS, you can find this on the sticker on the side of the box your phone came it, under the listing "s/w" version, the last three characters will tell you what baseband version your phone shipped with.
Click to expand...
Click to collapse
My phone stuck in download mode because i install twrp from twrp manager apk. Now it cannot go to recovery or to OS, just download mode.. I have tried to odin some recovery & ROM but no luck..
octantcomp said:
My phone stuck in download mode because i install twrp from twrp manager apk. Now it cannot go to recovery or to OS, just download mode.. I have tried to odin some recovery & ROM but no luck..
Click to expand...
Click to collapse
I had the same problem. I tried to update to 2.8.5.0 via TWRP's Play Store app and got a soft brick. Couldn't get to OS or into TWRP recovery. The phone was stuck at "Booting into recovery" blue text.
This is a common problem: http://forum.xda-developers.com/galaxy-s4-verizon/help/q-twrp-2-8-5-0-t3029191
You'll notice you can only download 2.8.4.0 on TWRP's official website: http://dl.twrp.me/jfltevzw/
I figured I lost the bootloader and the OS since I could only get into download mode. Worst case scenario, I could push the Verizon MDK image again, and push loki'd TWRP recovery back into bootloader with dd command in terminal.
I was in major 'screw it' mode. So I put the phone into download mode and fired up Odin. I tried to push the TWRP 2.8.4.0 tar for the jfltexx firmware via the "bootloader" field. I know the Odin mode isn't compatible with jfltevzw and it did say "failed" as expected, however on reboot I didn't get stuck at the "Booting into recovery" blue text. Everything was intact. Somehow, it fixed the bootloader/recovery on my device.
Once into the OS, I reflashed the jfltevzw img 2.8.4.0 using the "dd" mode in terminal. I didn't want to give it a chance to get stuck at the blue text again on reboot: http://twrp.me/devices/samsunggalaxys4verizon.html
Hope it helps someone!
about: Samsung S5 G901F
I don't know what i am doing wrong, but I cannot install the xposed framework for Android 6.0.1
What I did so far:
1) installed a new stock rom
2) installed CF auto root, I have a confirmed SU.
3) in Recovery mode I try to install all Xposed framework zips from my SD card, but I always get an error message that the file check was not good.
Please give advice .
you can't install xposed framework on samsung devices on lollipop or marshmallow if its had a stock rom,if you try to..
the phone will get bootloop, if you want to install it,i suggest you install a custom rom,
it WILL NOT work on stock samsung devices.
After installing any custom rom,go here
You can install Xposed on stock Samsung roms. You just need the Touchwiz version.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
I succeeded installing CWM (Clockwork mod recovery).
In short what I did:
1a) Download kies 3 from samsung for the USB drivers to connect to your phone.
1b) Download Odin latest version, or older which comes with a specific software you want to install, usually latest works.
http://forum.xda-developers.com/showthread.php?t=2711451
1c) Shutdown phone completely. Press volume down + power button + home button at the same time, to enter ODIN download mode.
1d) connect phone by USB and you should see a blue light and COMX, where X can be any number like COM5, etc. If you see this then
the connection between ODIN and mobile is ok. Please don't touch the USB cable as you can easily loose connection. In worst case
you need to Flash any Android stock rom with ODIN again , which can be found at Sammobile for instance. I had to do this because
my phone lost connection and the flash operation failed. When I boot my phone I only saw ODIN screen. Thankfully you can always
flash stock rom back. In my case, I read something about a locked boot loader etc etc... that would be a bit more work....
Unpack until you see a MD5 file. In Odin you click "Phone" or "AP". The file will be checked, that takes about 10 seconds, after that you can press
"start". After flashing you should clear cache and user data, otherwise you will see the Samsung screen for endless time.
1) I have android 6.01 and the CF auto root works perfectly http://forum.xda-developers.com/showthread.php?t=1980683
Use Odin to flash, put file into phone or AP.
2) downlad CWM from http://forum.xda-developers.com/galaxy-s5/help/sm-g901f-to-s5-how-to-root-t2882104
Put the file, leave it zipped/packed, dont unpack it, put it into phone or AP again and start the ODIN flashing.
3) download Xposed framework, the right version. I am so far. I downloaded version SDK23, because that is the version for Android 6.0.X, but I got a message that it was for android 5.0 SDK 21, I am puzzled. Will try again.....
@es0tericcha0s, thank you will have a look at that.
Ah, i forgot I got sooo frustrated that I downgraded to 5.x to test the power consumption, if its better than 6.01, that I thought I still have 6.01 installed. But my stock rom is 5.x. downloading again, but now 5.x version ARM. Should work now.....
Edit: Flashed 6.01 android and Xposed ARM SDK23 installs fine...
Also installing Amplify, I read it about it that it works well with Greenify...
Amplify seems to be an impressive piece of software. Ir permits me to limit alarms and wakelocks! I can set the period of time it has to wait until it's alarm or is permitted to wake up. Wow....nice.
es0tericcha0s said:
You can install Xposed on stock Samsung roms. You just need the Touchwiz version.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
ooh,thx for correcting me up