I was able to downgrade from the NG6 update released a few days ago back to NC5.
Knox Warranty Void: 0x0
I used the info and tut from this post
I used the full wipe method, I'm unsure if the no wipe one works
Information:
1. ROOT METHOD can be found here
2. Otherwise, Download Odin 3.09 here (Note: Bootloader = BL , PDA = AP , Phone = CP)
Download: VRUFNC5 No-Wipe SCH-I545_VZW_1_20140330160240_yni63xq6zh.zip
MD5: 71d1c7ea58d2ba81ccadd965b54a2215
Download: VRUFNC5 Full-Wipe SCH-I545_VZW_1_20140330160240_8il17ls9o2_fac.zip
MD5: 8a22dd4a47c2c5f890227fd952657d38
Directions:
No-Wipe
1. Unzip the file and you should have a tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Click start and wait for it to say Pass!
Full Wipe ( AKA Emeregency Repair)
1. Unzip the file and you should have a ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.tar.md5
2. Select the tar.md5 in Odin under PDA (or AP if using Odin 3.09) and keep Odin's default settings
3. Extract the PIT file from your phone or Odin tar, also I've uploaded it here just in case.
4. Put the PIT file in PIT and load the the Odin tar.md5 in PDA (or AP if using Odin 3.09) then click start.
Click to expand...
Click to collapse
Just confirming that this downgrade from ng6 worked for me too. im back to nc5 and yet to see if there will be no more reboots that everyone is having issues with on ng6.
Is there a way to do this with out using odin on a computer?
Im trying this right now via odin..... wish me luck.
brewer15650 said:
Im trying this right now via odin..... wish me luck.
Click to expand...
Click to collapse
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
snickerzz said:
I was able to downgrade from the NG6 update released a few days ago back to NC5.
Knox Warranty Void: 0x0
I used the info and tut from this post
I used the full wipe method, I'm unsure if the no wipe one works
Click to expand...
Click to collapse
No-Wipe works fine.
jwhistler said:
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
Click to expand...
Click to collapse
Worked like a charm. I did the full wipe and repartion(PIT). Took me a 1st timer using odin maybe 30mins to do.
npjohnson said:
No-Wipe works fine.
Click to expand...
Click to collapse
I am having a hellish time with no-wipe. Constant errors prevent input of even the lockscreen PIN. I've tried different cables, ports, running Odin as administrator and not... Ideas?
posaune76 said:
I am having a hellish time with no-wipe. Constant errors prevent input of even the lockscreen PIN. I've tried different cables, ports, running Odin as administrator and not... Ideas?
Click to expand...
Click to collapse
turn on usb debugging in the settings and turn off the lock code
snickerzz said:
turn on usb debugging in the settings and turn off the lock code
Click to expand...
Click to collapse
Damn. That probably was the thing that was killing me. After the first attempt, though, I could barely fight through the errors to a home screen, let alone change settings (delete corporate account to get rid of PIN, turn on dev mode, etc.). Ended up doing full wipe. Thanks for the thought. Lesson learned in case there's a next time.
Using Odin 3.09 for the no-wipe method, I load the NC5 .md5 file, and select it as instructed, but once I hit start, I get message stating "All threads completed. (succeed 0 / failed 0) " instantaneously without anything actually happening. I have both developer mode and USB Debugging enabled.
Am I missing something?
Ignore all of that. I loaded the .md5 file up before the phone was connected in Download Mode. Re-loading it fixed everything.
I flashed NC5 over NG6. constant ERROR!! process.acore HELP
It flashed successfully via ODIN. MD5 checker matched. So no corrupt rom. After booting, i keep getting non-stop android.process.acore & android.process.media stopped working every 1 sec, and hitting ok keeps bringing it back and I cannot do anything !!! This is so frustrating. I specifically wanted no wipe. Please tell me i dont have to Full Wipe it. How did it work for you, tell me the step by step. My NG6 was rooted, should I have unrooted first. Tell me what to do!!!
I tried to do this method,but I have had no luck. My phone returned the error "fused 6 binary 5" - What is it that I'm missing?
i keep getting errors
Going to try it.
fyi, after error upon error I tried a different cable using a different USB port. Worked like a charm!
I did the no-wipe method and got the android.process.acore & android.process.media errors. I ended up doing a full wipe and it worked fine. Unfortunately my Titanium Backup I ran the night before didn't run quite right ><. Live, learn and check backups!
NG6
Was NG6 released with a new update from VZ, or was this ported from the S5?
jwhistler said:
Good Luck!!
Let everyone know how it went. I don't intend to take this update, but others will and will, undoubtedly, need to take the path you are now on...
Click to expand...
Click to collapse
Is there a way unrooted to stop the update??
I had to take the wipe method but no biggie.
rfd177 said:
Is there a way unrooted to stop the update??
I had to take the wipe method but no biggie.
Click to expand...
Click to collapse
Are the problems with NG6 isolated to rooted phone, custom roms, or both at the same time?
Related
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
ebsk8er06 said:
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
villainous said:
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
Click to expand...
Click to collapse
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
villainous said:
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
Click to expand...
Click to collapse
I'm sure it will. In a few days. I'm surprised the verizon repair tool doesn't have MJ7.... maybe that'll take a while too.
antisomnic said:
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
Click to expand...
Click to collapse
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
tech_head said:
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
Click to expand...
Click to collapse
yeah i actually did that and have been using my s4 for a few days
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
This is an ODIN factory image similar to the one posted here but this is an emergency recovery image that will help you recover and restore your device from nearly ANY possible soft-brick by entirely wiping, refreshing, and repartitioning your device to out-of-box OEM firmware.
WARNING: Please use this with caution as this will wipe your ENTIRE device with no chance of restoring back old data afterwords!
How to Use
Download file from: http://www.androidfilehost.com/?fid=23203820527944861
Unzip file to your computer (desktop or some location)
Use ODIN v3.09 to flash in AP section once your device is connected
Click to expand...
Click to collapse
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
antisomnic said:
yeah i actually did that and have been using my s4 for a few days
Click to expand...
Click to collapse
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
mickrg123 said:
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
Click to expand...
Click to collapse
Untested, but you can unzip the attached and flash it in ODIN - it's the stock MJ7 recovery. With a bit of luck that'll get you repaired.
If not, flash the no-wipe MJ7 ROM from the Android Development forum, but that'll probably cause you to lose root.
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
wrong post
Awesome
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
SmOoThEm said:
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
Click to expand...
Click to collapse
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
emtownsend said:
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23203820527944861
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
antisomnic said:
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
Click to expand...
Click to collapse
antisomnic said:
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Click to expand...
Click to collapse
Just an FYI. Whenever you take an OTA from the Carrier it's written so you cannot revert back to an earlier build or a soft and possible hard brick can occur. This has been discussed numerous times in various forums. You were lucky this time.
Hi everyone,
First of all, please forgive me of my noobishness as this is my first post on the XDA forums.
My Galaxy S4 (SCH-I545) was working fine today. It was also rooted. As some of you may know, you are not able to recieve software updates if your phone is rooted, so I decided to try unrooting it and flash the unrooted stock firmware.
I booted into download mode and started Odin with the stock firmware in the PDA section. No other settings were changed. I attempted to flash the phone, and it failed with "sw rev check failed".
I tried restarting the phone. It came to the screen "Firmware Update Encountered an Issue".
Later, I was reading about the PIT file. I downloaded the PIT file for the SCH-I545 and flashed it. It failed on the phone with "Secure Check Fail: PIT". It failed on Odin with "Re -Partitioning Failed".
I restarted the phone again. It now displays "Samsung Custom" with a little unlocked padlock under it. I left it there for 20 minutes, it stayed on the same screen.
I tried booting into the stock recovery with success. I immediately selected "Wipe Data/Factory Reset". After this, I restarted the phone.
When the phone came back up, I booted into download mode and tried flashing again. This process failed with the same error "sw rev check failed". It again went to "Firmware Update Encountered an Issue". I repeated flashing the PIT, which failed again, but I was then able to boot into recovery once more.
At this point, I have wiped the data. The phone is sitting on my desk right now, completely wiped and able to boot into recovery, I just need to get this fixed ASAP because it is my only means of contact.
Can anyone help me as far as not being able to flash the phone? I apologize if I am confusing you, I just want to be as descriptive as possible to get the best help.
Thank you everyone for your time.
Squerl101 said:
Hi everyone,
First of all, please forgive me of my noobishness as this is my first post on the XDA forums.
My Galaxy S4 (SCH-I545) was working fine today. It was also rooted. As some of you may know, you are not able to recieve software updates if your phone is rooted, so I decided to try unrooting it and flash the unrooted stock firmware.
I booted into download mode and started Odin with the stock firmware in the PDA section. No other settings were changed. I attempted to flash the phone, and it failed with "sw rev check failed".
I tried restarting the phone. It came to the screen "Firmware Update Encountered an Issue".
Later, I was reading about the PIT file. I downloaded the PIT file for the SCH-I545 and flashed it. It failed on the phone with "Secure Check Fail: PIT". It failed on Odin with "Re -Partitioning Failed".
I restarted the phone again. It now displays "Samsung Custom" with a little unlocked padlock under it. I left it there for 20 minutes, it stayed on the same screen.
I tried booting into the stock recovery with success. I immediately selected "Wipe Data/Factory Reset". After this, I restarted the phone.
When the phone came back up, I booted into download mode and tried flashing again. This process failed with the same error "sw rev check failed". It again went to "Firmware Update Encountered an Issue". I repeated flashing the PIT, which failed again, but I was then able to boot into recovery once more.
At this point, I have wiped the data. The phone is sitting on my desk right now, completely wiped and able to boot into recovery, I just need to get this fixed ASAP because it is my only means of contact.
Can anyone help me as far as not being able to flash the phone? I apologize if I am confusing you, I just want to be as descriptive as possible to get the best help.
Thank you everyone for your time.
Click to expand...
Click to collapse
wut? Take 2 minutes to search for the Odin file of the build you were on, boot into odin mode and on 3.09 odin version load it to the ap section.
You CAN take OTA on rooted software.
sorry if I sound rude but you shouldn't root your phone if you can't even Google a solution to the possible problems that can occur.
gnubian said:
wut? Take 2 minutes to search for the Odin file of the build you were on, boot into odin mode and on 3.09 odin version load it to the ap section.
You CAN take OTA on rooted software.
sorry if I sound rude but you shouldn't root your phone if you can't even Google a solution to the possible problems that can occur.
Click to expand...
Click to collapse
Did you even read the whole post?
I CANNOT FLASH THE PHONE WHATSOEVER. It fails with "sw rev check failed" EVERY TIME.
As far as your saying of being able to take OTA on rooted firmware, it really isn't applicable to me right now considering my phone does not have an operating system on it.
Maybe someone that actually has useful information can help me?
Squerl101 said:
Did you even read the whole post?
I CANNOT FLASH THE PHONE WHATSOEVER. It fails with "sw rev check failed" EVERY TIME.
As far as your saying of being able to take OTA on rooted firmware, it really isn't applicable to me right now considering my phone does not have an operating system on it.
Maybe someone that actually has useful information can help me?
Click to expand...
Click to collapse
You haven't indicated what base is your phone originally and what stock image you were trying to flash.. Also...try to understand the frustration so many of us have with people that are jumping into something without researching as best as they could.
safestrap enabled, Hyperdrive driven
decaturbob said:
You haven't indicated what base is your phone originally and what stock image you were trying to flash.. Also...try to understand the frustration so many of us have with people that are jumping into something without researching as best as they could.
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
That's your problem. You can't revert to an older build. You have to flash the build you were originally on.
Sent from my NCC 1701 using Tapatalk 4
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
There's a guide telling you to flash down from mj7??
I don't think so..
Sent from my SCH-I545 using XDA Premium 4 mobile app
Squerl101 said:
Sorry for the lack of info. The phone was running MJ7 before everything died. I have been trying to flash back to ME7 as this is what almost every guide I have read has told me to do.
Thank you.
Click to expand...
Click to collapse
Can't flash backwards...bootloader changes from 1 version to the next makes impossible
safestrap enabled, Hyperdrive driven
I will see how this comes out when i get home from work. I will have to look for mj7. I'm sure it's out there floating around on the internet somewhere.
I will post after i try to flash mj7 with the outcome.
Please stand by
Squerl101 said:
I will see how this comes out when i get home from work. I will have to look for mj7. I'm sure it's out there floating around on the internet somewhere.
I will post after i try to flash mj7 with the outcome.
Please stand by
Click to expand...
Click to collapse
There is full wipe and no wipe version of mj7 stock image here somewhere
safestrap enabled, Hyperdrive driven
decaturbob said:
There is full wipe and no wipe version of mj7 stock image here somewhere
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Just to be clear, is MJ7 the firmware the one before MK2? I just want to be sure that I am flashing the right firmware.
Squerl101 said:
Just to be clear, is MJ7 the firmware the one before MK2? I just want to be sure that I am flashing the right firmware.
Click to expand...
Click to collapse
Correct.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
Correct.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Found it here http://forum.xda-developers.com/showthread.php?t=2507253 , will be flashing within the next 30 minutes...
Squerl101 said:
Found it here http://forum.xda-developers.com/showthread.php?t=2507253 , will be flashing within the next 30 minutes...
Click to expand...
Click to collapse
Just go to MK2.
No Wipe MK2 -> http://forum.xda-developers.com/showthread.php?t=2578209
Saferoot -> http://forum.xda-developers.com/showthread.php?t=2565758
GS4 Tether Unlock -> http://forum.xda-developers.com/showthread.php?t=2512981
tech_head said:
Just go to MK2.
No Wipe MK2 -> http://forum.xda-developers.com/showthread.php?t=2578209
Saferoot -> http://forum.xda-developers.com/showthread.php?t=2565758
GS4 Tether Unlock -> http://forum.xda-developers.com/showthread.php?t=2512981
Click to expand...
Click to collapse
I would, but I have been downloading MJ7 for about an hour (slow internet ) so it's probably not worth starting over. Hopefully everything works out!
Cool, the problem no longer exists. It took about 5 minutes to flash, and after that, it started working perfectly again. Thank you everyone for your help!
Sent from my SCH-I545 using Tapatalk
Have you tried using Kies to fix your phone?
Sent from my SCH-I545 using Tapatalk
Little info I have a verizon galaxy s4 that I brought already rooted running a stock rom and safestrap recovery
Well at the doctors office letting my son play on my phone he some how got into the recovery amd installed a eclipse rom I guess the guy before me had on the device I never dealed wirh root before so now my ohone stuck on the boot screen and it seems I don't have the safestrap recovery no more somehow
Now I tried to just used odin mode to get back to completly stock but everything I do fails I got the tar file for my phone I put the phone in download mode and odin does this
Osm enter cs for md5
Osm check md5 do not unplug
Osm please wait
Osm i545vruemk2_i545vzwemk2_i545vruemk2_home.tar.md5 is valid
Osm chexkimg md5 sucessfully
Osm leave cs
Then I hit start and it says
Odin v.3 engine
Intialzation
Get pitnformmappimg
Complete (write) operation fail
All threads completed (succeed 0/failed 1
On my phone says after fail
Product name sch-i545
Current binery samsung official
System status custom
Knox kernel lock 0x0
Knox warrenty void 0x0
Csb-config-lsb 0x30
Write protection enabled
Emmc burst mode enabled
Start (224, 1448)
Pkease help me I domt have a clue whatnim doimg wrong I folowed the video
eddieq2922 said:
Little info I have a verizon galaxy s4 that I brought already rooted running a stock rom and safestrap recovery
Well at the doctors office letting my son play on my phone he some how got into the recovery amd installed a eclipse rom I guess the guy before me had on the device I never dealed wirh root before so now my ohone stuck on the boot screen and it seems I don't have the safestrap recovery no more somehow
Now I tried to just used odin mode to get back to completly stock but everything I do fails I got the tar file for my phone I put the phone in download mode and odin does this
Osm enter cs for md5
Osm check md5 do not unplug
Osm please wait
Osm i545vruemk2_i545vzwemk2_i545vruemk2_home.tar.md5 is valid
Osm chexkimg md5 sucessfully
Osm leave cs
Then I hit start and it says
Odin v.3 engine
Intialzation
Get pitnformmappimg
Complete (write) operation fail
All threads completed (succeed 0/failed 1
On my phone says after fail
Product name sch-i545
Current binery samsung official
System status custom
Knox kernel lock 0x0
Knox warrenty void 0x0
Csb-config-lsb 0x30
Write protection enabled
Emmc burst mode enabled
Start (224, 1448)
Pkease help me I domt have a clue whatnim doimg wrong I folowed the video
Click to expand...
Click to collapse
It could be a bad tar file. I would download it again and reflash in Odin. Use the Full Wipe Method
http://forum.xda-developers.com/showthread.php?t=2578209
cbmggm said:
It could be a bad tar file. I would download it again and reflash in Odin. Use the Full Wipe Method
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Thanks I'm going to trynthis now
ok guys i tried getting the new tar file and same results nothing in the progress bar it gets to set partion then it fails saying completed(write)failed i cant do anything on the phone it self i did figered somehow i can get into stock recovery but cant do anything odin keeps failing please please help me
eddieq2922 said:
Thanks I'm going to trynthis now
Click to expand...
Click to collapse
I just sent you a PM
You might be flashing the wrong firmware, check this thread out:
http://forum.xda-developers.com/showthread.php?t=2524883
eddieq2922 said:
ok guys i tried getting the new tar file and same results nothing in the progress bar it gets to set partion then it fails saying completed(write)failed i cant do anything on the phone it self i did figered somehow i can get into stock recovery but cant do anything odin keeps failing please please help me
Click to expand...
Click to collapse
Do you have a known good PIT file for your phone?
I wouldn't put anything into the PIT slot, flash just the .tar.md5 in the AP slot, and don't select "Re-partition".
Since it seems to be failing when trying to repartition, let's skip that (as above) and see if it's any better.
k1mu said:
Do you have a known good PIT file for your phone?
I wouldn't put anything into the PIT slot, flash just the .tar.md5 in the AP slot, and don't select "Re-partition".
Since it seems to be failing when trying to repartition, let's skip that (as above) and see if it's any better.
Click to expand...
Click to collapse
okay im going to doit again and make sure it not check or anythig thanks ahead
still no luck i check everything i dont see what im doing wrong it get s to the set partion and fails everytime i dont have the box checked i got the right tar file just wont flashed really need help
Bumb please help
eddieq2922 said:
Bumb please help
Click to expand...
Click to collapse
Are sure the download is good? Did you check the MD5? Maybe try downloading it again.
Sent from my NCC 1701 using Tapatalk 4
eddieq2922 said:
Bumb please help
Click to expand...
Click to collapse
Things to try :
Different USB Cable
Different USB Port on PC
A Different version of Odin
Heimdall instead of Odin
Re-download the full wipe MK2
Worth a shot...
Sent from my SCH-I545 using Tapatalk
I tried different ports I tride differemt odin I downloaded the md5 again full wipe and still same result
eddieq2922 said:
I tried different ports I tride differemt odin I downloaded the md5 again full wipe and still same result
Click to expand...
Click to collapse
Well I'm out of ideas myself. Heimdall can be found here http://glassechidna.com.au/heimdall/
Some have had much better luck with it from what I've seen. I'm not an expert in Odin errors just was thinking of what I'd try. You can go between MK2 and MJ7 as well, may be worth trying MJ7 full wipe, just for the hell of it.
Hopefully that works or maybe someone else here will have another idea.
Sent from my SCH-I545 using Tapatalk
The video looked so easy on going back to stock I'm doimg exactly as there doing just can't get it to pass
eddieq2922 said:
I tried different ports I tride differemt odin I downloaded the md5 again full wipe and still same result
Click to expand...
Click to collapse
Sounds dumb, and sorry if you tried already, but did you try a different usb cable? Just trying to throw something against the wall and hope it sticks.
Coycaine said:
Sounds dumb, and sorry if you tried already, but did you try a different usb cable? Just trying to throw something against the wall and hope it sticks.
Click to expand...
Click to collapse
No need to say sorry Im willing to try anythimg I greatly apreciate the help still that didn't make a difference same results I don't get it at al if I could get a custom recovery back on I have a back up but I lost the safestrap recovery somehow now I only got stock recovery damn kids
Bump
eddieq2922 said:
Bump
Click to expand...
Click to collapse
First, everyone: asking him to check the MD5 is a waste of time. It's a .tar.md5, and ODIN verifies the MD5 when it reads it. Since ODIN isn't finding a problem, it's OK. (There's no chance whatsoever that a file could be corrupt and still have a MD5 that verifies while still being a valid tar file.)
What I would do is to go read this thread for the MK2 files.
Given what you're seeing, try the emergency recovery. Download the .PIT file from there (remember me asking about that?) and use that when flashing the full-wipe file in ODIN.
This might sound crazy, but are you using the samsung OEM USB cable when your trying to odin? I had the note 2 before getting this phone and every time I used oden with a 3rd party USB cable, I always ran into problems. I always had to use the OEM cable. Also, if it's bootlooping or hanging at the boot screen, you should be able to get it working again. The only time you worry is if it doesn't do anything at all. When you said you can't get into safestrap, what about the stock recovery?
Sent from my SCH-I545 using Tapatalk
Bradh024 said:
This might sound crazy, but are you using the samsung OEM USB cable when your trying to odin? I had the note 2 before getting this phone and every time I used oden with a 3rd party USB cable, I always ran into problems. I always had to use the OEM cable. Also, if it's bootlooping or hanging at the boot screen, you should be able to get it working again. The only time you worry is if it doesn't do anything at all. When you said you can't get into safestrap, what about the stock recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
im using the the oem cable and as far as stock recovery yes i can get into stock recovery no problem
Wondering if this is just me having problems with these updates and keeping root. My first phone I only had for a couple of months. I was rooted on NF6 and updated to BNG3 through Mobile Odin pro, after which VoLTE disappeared and WiFi calling just stays grayed out on "enabling". Completely wiped the phone, re-installed stock software and still could not get these options to work or enable. T-Mobile replaced the phone.
I now have another phone, rooted and was on NF6 and was worried about updating to BNG3 due to what happened on my first phone. I got an update notice about BNG4 and decided to download the full .tar and update through Mobile Odin pro and then flash the firmware via PC Odin. Did that and now I cannot use WiFi calling again and VoLTE is gone from call settings once again.
Is anyone else having this issue, or does it seem like I am doing something wrong? Any help or responses would be helpful before I go back to T-Mobile again.
..
You are right, my initial information was not very detailed. I was writing in a hurry at the time. I did not notice these problems as I was out of state on business and calling over WiFi was not needed. I only use it at home as signal is not the greatest, and that is when I noticed the issue and from reading I could not find an issue relating to mine.
When I have updated, I have not cleared cache or so forth. I just used Mobile Odin with the stock .tar to get the latest update and inject root/superuser and that is pretty much it. I have after the fact, done a factory reset and PC Odin back to a stock state (no root, etc) and this has not fixed my issue with WiFi calling. I have seen other threads in regards to WiFi calling, however I have not seen anything that refers to my issue at hand after updating in the manner that I have.
Can you actually do a full backup while running a stock ROM? I have used other custom recoveries on other phones and completed backups that way but not on a stock rooted phone.
..
Cleared cache as recommended through recovery (no change). Used PC Odin to revert back to the stock .tar the phone came with (ANE6), as well as not having root. Also no change with the problem, still cannot use Wifi calling.
Something very interesting just happened. I got a notice from T-Mobile about an update after restoring to ANE6 and I let it download and now I'm on BNG3 and Wifi calling is working, just no root right now. I can take care of that later.
Thanks for you time with trying to help and giving good information.
legendindisguise said:
Cleared cache as recommended through recovery (no change). Used PC Odin to revert back to the stock .tar the phone came with (ANE6), as well as not having root. Also no change with the problem, still cannot use Wifi calling.
Something very interesting just happened. I got a notice from T-Mobile about an update after restoring to ANE6 and I let it download and now I'm on BNG3 and Wifi calling is working, just no root right now. I can take care of that later.
Thanks for you time with trying to help and giving good information.
Click to expand...
Click to collapse
It definitely seems like a problem with mobile odin pro.
How exactly have you gone about the update process with mobile Odin?
What I would do is simply follow the threads on here that explain in details what you need to do to update and keep root. The flashing process is what is preventing you from using those features. Something is definitely not being flashed properly and carrying over from the update.
elesbb said:
It definitely seems like a problem with mobile odin pro.
How exactly have you gone about the update process with mobile Odin?
What I would do is simply follow the threads on here that explain in details what you need to do to update and keep root. The flashing process is what is preventing you from using those features. Something is definitely not being flashed properly and carrying over from the update.
Click to expand...
Click to collapse
These are the steps that I went by: I used this method when going from NE6 to NF6 (worked great). When I did these same steps trying to update to NG3 or NG4 is when I had problems.
Download the NF6 Full Stock TAR
Extract the single *.tar.md5 file from the downloaded ZIP in step 1
Copy this extracted file (G900TUVU1BNF6_G900TTMB1BNF6_G900TUVU1BNF6_HOME.ta r.md5) to your sdcard (I used my external sdcard)
Throw down the $4.99 and purchase Chainfire's Mobile ODIN Pro from Play Store (link)
Open Mobile ODIN PRO and click 'OK' to the warning about bootloaders and grant it root access when prompted
Scroll down to 'Open file ...' and click it.
Here I was prompted for either 'Internal SD-card' or 'External SD-card'. Select which ever location you copied the TAR to in step 3
Now select the actual folder and file for the location of the TAR you copiend in step 3
You'll be presented with the list of partitions your TAR contains. Click 'OK'
Leave all partitions as-is and be sure to check/tick both 'Enable EverRoot' and 'Inject Superuser (SuperSU)'
Optionally, you may also check to wipe Dalvik and/or data & cache. <-- Not required, but I checked 'Wipe Dalvik cache' because it's harmless.
Click 'Flash firmware'
legendindisguise said:
These are the steps that I went by: I used this method when going from NE6 to NF6 (worked great). When I did these same steps trying to update to NG3 or NG4 is when I had problems.
Download the NF6 Full Stock TAR
Extract the single *.tar.md5 file from the downloaded ZIP in step 1
Copy this extracted file (G900TUVU1BNF6_G900TTMB1BNF6_G900TUVU1BNF6_HOME.ta r.md5) to your sdcard (I used my external sdcard)
Throw down the $4.99 and purchase Chainfire's Mobile ODIN Pro from Play Store (link)
Open Mobile ODIN PRO and click 'OK' to the warning about bootloaders and grant it root access when prompted
Scroll down to 'Open file ...' and click it.
Here I was prompted for either 'Internal SD-card' or 'External SD-card'. Select which ever location you copied the TAR to in step 3
Now select the actual folder and file for the location of the TAR you copiend in step 3
You'll be presented with the list of partitions your TAR contains. Click 'OK'
Leave all partitions as-is and be sure to check/tick both 'Enable EverRoot' and 'Inject Superuser (SuperSU)'
Optionally, you may also check to wipe Dalvik and/or data & cache. <-- Not required, but I checked 'Wipe Dalvik cache' because it's harmless.
Click 'Flash firmware'
Click to expand...
Click to collapse
I think that's right. It definitely seems like something isn't being flashed properly though preventing you from using WiFi calling. After you update, what does your baseband version say?
elesbb said:
I think that's right. It definitely seems like something isn't being flashed properly though preventing you from using WiFi calling. After you update, what does your baseband version say?
Click to expand...
Click to collapse
I'm not 100% right now, I believe that when I was using Mobile Odin to do the updates, the baseband was staying the same. On my last attempts I used Mobile Odin to update versions and then used PC Odin to update the firmware as so everything was the same.
The phone is working now since I restored back to NE6 and it connected with T-Mobile to do OTA updates and now on NG4. I might just use CF Auto Root and not worry about Knox.
legendindisguise said:
I'm not 100% right now, I believe that when I was using Mobile Odin to do the updates, the baseband was staying the same. On my last attempts I used Mobile Odin to update versions and then used PC Odin to update the firmware as so everything was the same.
The phone is working now since I restored back to NE6 and it connected with T-Mobile to do OTA updates and now on NG4. I might just use CF Auto Root and not worry about Knox.
Click to expand...
Click to collapse
You can flash just the modem using the PC Odin. I think that is why you weren't able to use WiFi calling and such when upgrading with just mobile odin.
elesbb said:
You can flash just the modem using the PC Odin. I think that is why you weren't able to use WiFi calling and such when upgrading with just mobile odin.
Click to expand...
Click to collapse
I understand that. But wouldn't PC Odin the firmware include the modem when flashing? I will try just doing the modem next and see how it goes. Thanks for the advice.
legendindisguise said:
I understand that. But wouldn't PC Odin the firmware include the modem when flashing? I will try just doing the modem next and see how it goes. Thanks for the advice.
Click to expand...
Click to collapse
It does include the modem, however, they don't always get applied. I know you need to boot to stock recovery after flashing the modem, and the recovery does something, then you can reboot and it should be applied. But I am 99 percent confident that is why those things weren't working for you.
elesbb said:
It does include the modem, however, they don't always get applied. I know you need to boot to stock recovery after flashing the modem, and the recovery does something, then you can reboot and it should be applied. But I am 99 percent confident that is why those things weren't working for you.
Click to expand...
Click to collapse
Cool, thanks for the info and help. I will try flashing tonight and see how it goes and report back.
I appreciate both of you trying to help. I do try to read as much as possible before posting and cluttering the forums, but I could not figure this one out.
Cheers
elesbb said:
It does include the modem, however, they don't always get applied. I know you need to boot to stock recovery after flashing the modem, and the recovery does something, then you can reboot and it should be applied. But I am 99 percent confident that is why those things weren't working for you.
Click to expand...
Click to collapse
THANK YOU! That was the issue. Flashing the modem individually and now everything is working as it should. I owe you a beer my friend.
Thanks again.
legendindisguise said:
THANK YOU! That was the issue. Flashing the modem individually and now everything is working as it should. I owe you a beer my friend.
Thanks again.
Click to expand...
Click to collapse
I don't drink, but I will definitely take a starbucks or Cinnabon xD Haha glad you got it all resolved! That's what xda is for my friend
heya Legend,
I just had the same thing happen to me today when i ran pc odin to upgrade to NH5. I previously was stock rooted with NG3 and everything worked fine. Ran the firmware, rebooted to download and then installed bootloader. wifi calling was sitting at Greyed out saying enabling. never would turn on. installed TWRP 2.8 to wipe cache and dalvik and also ran a fix permissions. at that point phone wouldnt reboot, sat at Galaxy s5 splash screen. pulled battery, went back and tried to wipe again. still hung at splash. so i downgraded back to NG3 doing firmware, then bootloader. now phone boots fine but wifi calling still will not turn on. Which sucks because i just got my personal Cellspot up and runnin yesterday.
Can you tell me exactly what you did to get your wifi calling running again? or anyone else have any ideas/thoughts?
Thanks in advance
erider
erider said:
heya Legend,
I just had the same thing happen to me today when i ran pc odin to upgrade to NH5. I previously was stock rooted with NG3 and everything worked fine. Ran the firmware, rebooted to download and then installed bootloader. wifi calling was sitting at Greyed out saying enabling. never would turn on. installed TWRP 2.8 to wipe cache and dalvik and also ran a fix permissions. at that point phone wouldnt reboot, sat at Galaxy s5 splash screen. pulled battery, went back and tried to wipe again. still hung at splash. so i downgraded back to NG3 doing firmware, then bootloader. now phone boots fine but wifi calling still will not turn on. Which sucks because i just got my personal Cellspot up and runnin yesterday.
Can you tell me exactly what you did to get your wifi calling running again? or anyone else have any ideas/thoughts?
Thanks in advance
erider
Click to expand...
Click to collapse
I used PC Odin to just install the modem. Technically the firmware flash should load the modem but it didn't work for me.
This is what was recommended to me and it fixed the problem.
Damn, that did not work for me. tried flashing a few different modems too.
legendindisguise said:
I used PC Odin to just install the modem. Technically the firmware flash should load the modem but it didn't work for me.
This is what was recommended to me and it fixed the problem.
Click to expand...
Click to collapse
erider said:
Damn, that did not work for me. tried flashing a few different modems too.
Click to expand...
Click to collapse
When you flashed the modems are you sure they actually installed? A lot of people are having problems with getting modems to stick when flashed. You have to pull the battery for several seconds before you boot into download mode then flash the modem, and after it boot go to your about device screen to make sure you have the new modem.
gspears said:
When you flashed the modems are you sure they actually installed? A lot of people are having problems with getting modems to stick when flashed. You have to pull the battery for several seconds before you boot into download mode then flash the modem, and after it boot go to your about device screen to make sure you have the new modem.
Click to expand...
Click to collapse
Yeah i got into the habit of pulling battery every time i've flashed modems on this phone just for that reason. :/
"Firmware Upgrade Encountered an Issue" "Device not responding" Samsung Kies
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Bumping for others to hopefully see... I've still made no progress and am in the same situation and simply can't find what I need to do.
What build were you on before you started? What file are you trying to flash with Odin?
Jmick363 said:
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Hightower24 said:
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Click to expand...
Click to collapse
Crap. You're right. I completely forgot about that last night. I was getting frustrated with Hyperdrive because when I was trying to install version 20, the WiFi would never work no matter which modules.zip I flashed.
I got fed up and just wanted to flash something else and I did this without even thinking about it... I can get the phone into download mode, but when I try to flash this in odin, it fails.
I saw someone with the same screen as me with a Note 2 and someone said something about flashing a PIT file or something like that? I think I'm going to look into that next, hopefully I can find some useful links.
riker147 said:
What build were you on before you started? What file are you trying to flash with Odin?
Click to expand...
Click to collapse
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Jmick363 said:
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Click to expand...
Click to collapse
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Hightower24 said:
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Click to expand...
Click to collapse
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Jmick363 said:
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Click to expand...
Click to collapse
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Hightower24 said:
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Click to expand...
Click to collapse
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Jmick363 said:
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Click to expand...
Click to collapse
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
So right now things aren't going as smoothly as I would've hoped.... The first time I flashed Hyperdrive and then that modules zip you linked, and the phone got stuck on the Samsung custom screen in some sort of loop. I reset it with odin and just the PDA from the link from before, and I then installed towelroot and safestrap again then flashed hyperdrive and modules and now I'm stuck on the hyperdrive red screen... It's just the boot animation and nothing else. When I take out the battery, the power button does nothing if the phone is not plugged in. When I plug the phone in and hold down the power button, it just shows an empty battery with a loading icon in the middle. I can't do anything else.... I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Jmick363 said:
I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Click to expand...
Click to collapse
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Jmick363 said:
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Click to expand...
Click to collapse
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Hightower24 said:
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Click to expand...
Click to collapse
No need to apologize!! Your job isn't to monitor me, and I can't thank you enough for all the help. I'm going to give this a shot at some point today, hopefully it'll work. I'll comment back in the thread whatever happens... As you can probably tell, I typically have horrible luck with these things.
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
madhavok09 said:
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
Click to expand...
Click to collapse
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
riker147 said:
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
Well the OP said he did the wipe with that link I listed, and I would assume it's a good link. I am flashing the full wipe with the PIT file, using the cable that came with the phone, and I have tried using a different USB port. I have tried 3 different MD5 files as well and still have had no luck.
Edit (2:13 PM Eastern): Had the wrong file after some digging, and got the NC5 instead of the MK2. Phone is booting normally. Thanks for the help.