Ok so I was on Albe95 galaxy s6 Rom and i was experiencing alot of lag and got tired of not being able to rotate my screen so I was going back to stock OF1 and I forgot to use FlashFire instead of odin and just installed the the stock rom before wiping the S6 Rom off the system now I get stuck on the verizon Splash screen and Can't do anything is there anyway to fix this?
Rone215 said:
Ok so I was on Albe95 galaxy s6 Rom and i was experiencing alot of lag and got tired of not being able to rotate my screen so I was going back to stock OF1 and I forgot to use FlashFire instead of odin and just installed the the stock rom before wiping the S6 Rom off the system now I get stuck on the verizon Splash screen and Can't do anything is there anyway to fix this?
Click to expand...
Click to collapse
Do you have the Verizon Galaxy s4 software assistant installed. If not then you're screwed.
Pixi43 said:
Do you have the Verizon Galaxy s4 software assistant installed. If not then you're screwed.
Click to expand...
Click to collapse
No did i need it before hand, im using my girlfriends old galaxy s4 SCH-I545 right now if thats any help
I'm also in this same mess. Deleted a few too many Knox-related files when not paying attention, got stuck on the redscreen during boot, and then proceeded to royally muck things up with a bad (read: incorrect) PIT and failed downgrades to OC1. No g/f to pull the Software Assistant from, and the (presumably) older version that I managed to find online never detects the device is present.
I'm still able to get into download mode, so I suspect that a full (good) OF1 bundle for Odin would make things right with the world again. Proper attempts with various OC1 bundles are being met with SW REV CHECK hate.
I should have just gone to bed at a reasonable time...
Use samsung kies. It's the easiest way to get back to OF1. It has instructions in the program.
Kies wasn't recognizing the device when I connected it. I finally found a copy of OF1 from AndroidRomUpdate and was able to get it on using Odin 3.10.7, it was even nice enough to keep my data Now to re-root...
Links to OF1 stock: http androidromupdate.com/2015/08/25/i545vrugof1-stock-android-5-0-1-verizon-galaxy-s4-sch-i545-ota-update-with-loads-of-fixes/
(Be warned, the download is SLOW...)
whowatchlist said:
Use samsung kies. It's the easiest way to get back to OF1. It has instructions in the program.
Click to expand...
Click to collapse
Thanks man kies worked for me it erased all my data but im getting my s7 edge in 2 days for Tmobile
gosherm said:
Kies wasn't recognizing the device when I connected it. I finally found a copy of OF1 from AndroidRomUpdate and was able to get it on using Odin 3.10.7, it was even nice enough to keep my data Now to re-root...
Links to OF1 stock: http androidromupdate.com/2015/08/25/i545vrugof1-stock-android-5-0-1-verizon-galaxy-s4-sch-i545-ota-update-with-loads-of-fixes/
(Be warned, the download is SLOW...)
Click to expand...
Click to collapse
For future reference there already is a thread(s) on xda with the download link for the tar
whowatchlist said:
For future reference there already is a thread(s) on xda with the download link for the tar
Click to expand...
Click to collapse
Doh! I must have missed it then, all I could find was the zip file for a non-Odin install (from a working phone), I forget what the framework was called...
whowatchlist said:
For future reference there already is a thread(s) on xda with the download link for the tar
Click to expand...
Click to collapse
Link? I need this
Sent from my SCH-R970 using XDA-Developers mobile app
Linkhttp://forum.xda-developers.com/galaxy-s4-verizon/general/stock-of1-firmware-t3338303
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.
So i have Samsung Galaxy S4 that is stuck in the Firmware upgrade encountered error mode. I was attempted to root it with the Odin and Root_de_la_vega.
My phone is a Galaxy S4 SCH-I545 - VRUDMl1
I already attempted to do a Kies Recovery but it is telling me my S/N is not correct. I tried every word/letter underneath the battery.
I already saw the No-Wipe Factory Image Guide. I tried that but it fails everytime when it gets to the point that says ABoot. Don't really know whats left i can try.
Any help would be much appreciated.
thanks
Tuffguy721 said:
So i have Samsung Galaxy S4 that is stuck in the Firmware upgrade encountered error mode. I was attempted to root it with the Odin and Root_de_la_vega.
My phone is a Galaxy S4 SCH-I545 - VRUDMl1
I already attempted to do a Kies Recovery but it is telling me my S/N is not correct. I tried every word/letter underneath the battery.
I already saw the No-Wipe Factory Image Guide. I tried that but it fails everytime when it gets to the point that says ABoot. Don't really know whats left i can try.
Any help would be much appreciated.
thanks
Click to expand...
Click to collapse
Did you try to upgrade to mj7. If so that is the best option is to flash that odin image. Can't go backwards.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Did you try to upgrade to mj7. If so that is the best option is to flash that odin image. Can't go backwards.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I have not attempting to upgrade yet. I was doing everything that was for ME1.
Tuffguy721 said:
I have not attempting to upgrade yet. I was doing everything that was for ME1.
Click to expand...
Click to collapse
You sure you had the ml1 image when trying to flash a previous firmware it fails at aboot. Verifying the md5 is also good to make sure you didnt get a corrupted download.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
You sure you had the ml1 image when trying to flash a previous firmware it fails at aboot. Verifying the md5 is also good to make sure you didnt get a corrupted download.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I just downloaded and upgraded to MJ7 and to actually completed. Lost everything but got the phone back up and running at least. Now i will go read up but can this new MJ7 be rooted yet?
Thanks for the help
Tuffguy721 said:
I just downloaded and upgraded to MJ7 and to actually completed. Lost everything but got the phone back up and running at least. Now i will go read up but can this new MJ7 be rooted yet?
Thanks for the help
Click to expand...
Click to collapse
It can if you saved root from ml1. People are working on it right now tho theres a thread in the general section about it.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
mzaric said:
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
Click to expand...
Click to collapse
UPDATE: Since i posted this, i tried to flash a stock firmware on Odin (4.1.2 i believe) and it failed halfway through the procedure. with nothing more to be done, i reset my phone, and where before it was just bootlooping, it now shows me an entirely different screen reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Since then i have tried a different firmware file, still 4.1.2, Odin get's to the very end of the procedure, and crashes at what i assume is the reboot portion. Desperately need assistance!
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
akellar said:
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
Click to expand...
Click to collapse
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
mzaric said:
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
Click to expand...
Click to collapse
I cant seem to find the file anywhere. Only on terafile via SamMobile, but the download link doesn't seem to work.
What are my options as far as this bootloader go?
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I did a bunch of searches on the site as i was f****ing my phone up, systematically. Im really sorry if this thread doesn't go here, i just didn't know who else to ask
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
mzaric said:
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
Click to expand...
Click to collapse
Currently the only way to root your OTA 4.3 Note 2 is to use saferoot, read this thread carefully
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
Sent from my SCH-I605 using Tapatalk
I found myself in the same situation. Where might I find the PIT file? I can't reboot the phone to get the PIT file because it's soft bricked like mzaric's phone was. I'm using Mac OS X so I'm having to use JOdin3 to flash the stock 4.3 firmware back, but without the PIT file I can't continue and I've searched endlessly to find the PIT file. Also a somewhat related question, I heard JOdin isn't good for flashing big files, but I have no alternative, is the stock firmware which is 1.1gb too big to flash?
EDIT: I sadly didn't search hard enough thank you droidstyle for the guide. But my next question is I'm unsure of what version the phone is because when I originally tried to do the CASUAL unlock I believe it was on 4.1.2, but I think it softbricked to begin with because it was 4.3. Should I just try doing the 4.1.2 and if it doesn't take, retry with the 4.3?
If you flashed n7100 firmware you are screwed. If not just Odin back to stock. You were on 4.1.2 if you were unlocked using casual. Don't go to 4.3
Sent from my SCH-I605 using Tapatalk
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
Fused 5 means you need to flash either mj7 or mk2 .
I'd do the full wipe at this point. If one doesn't work right at first... Try the other. Do you recall which your phone was on prior to this?
Sent From My Verizon S4
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Yea I don't know either.. I just saw that Odin error then I saw me7. Figured op tried flashing the wrong one. It is a bit confusing though with no actual info to go on.
Sent From My Verizon S4
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
af_nm said:
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
Click to expand...
Click to collapse
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
With the new knox security trying to flash a prior firmware will trip the flag so it's advised to be careful when flashing images via Odin. Flash an earlier version that doesn't take and you'll lose the warranty on your phone.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
would reinstalling the pit files work?
odin mdk
Mistertac said:
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
Click to expand...
Click to collapse
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
af_nm said:
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
Click to expand...
Click to collapse
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
same here, I'm not sure what he has or what he has done........
decaturbob said:
same here, I'm not sure what he has or what he has done........
Click to expand...
Click to collapse
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Mistertac said:
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Click to expand...
Click to collapse
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
k1mu said:
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
Click to expand...
Click to collapse
Yea good call I think I was actually confusing posts when I was responding earlier. Forgot about the fused 5. Thanks .
Sent From My Verizon S4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 and used this http://forum.xda-developers.com/showthread.php?t=2507253. when I ran it in odin it ran until it stopped at system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440]
af_nm said:
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 as well but I can't find one that will work
Click to expand...
Click to collapse
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
af_nm said:
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
Click to expand...
Click to collapse
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Surge1223 said:
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Click to expand...
Click to collapse
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
af_nm said:
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
Click to expand...
Click to collapse
Driver issue 99% of the time make sure you've uninstalled all Samsung drivers. Use windows' control panel option to uninstall programs and make sure all kies, samsung, and verizon related stuff is uninstalled. Then reboot the pc, let your phone install the drivers for your pc, and try using a different usb port with the stock oem cable. Also make sure adb isn't running in the background
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hi all, I recently rooted my Verizon galaxy s4 i545vrufng6 4.4.2 and ever since I did I have had some issues. The way I did it was by flashing the ng5 kernel and using towelroot then reflashing ng6. After I did that my wifi was stuck on the dull green light but I read on a forum on how to fix that by going into the system and deleting one of the wifi files. After I did that everything worked fine for a few days! Then I went out of state and when I got on the airplane my phone was put on airplane mode, by the time I landed and took off airplane mode wifi wouldn't work at all. I tried to do the same thing I did earlier but it didn't work. Matter of fact, i cannot even find that file anymore Wifi will no longer even go dull green, i can hit it as many times as I want and it will stay in the off position. I thought if I flashed a custom rom it would restart the wifi, so I looked up how to install cyanogenmod and followed the YouTube vid from wwjoshdew (30minute). I didn't get through the whole thing because when my phone restarted it had an unlocked padlock at the bottom of the Samsung start up logo and when it went into recovery mode it came up with a yellow triangle saying that system software is not authorized by Verizon wireless. I can boot it up normally or I can go into download mode but I can't access recovery mode meaning I cannot do a factory reset. I took it to Verizon and they said they couldn't help me cuz I void the warranty. If anyone could please help me get my phone back to normal I would appreciate it so much! Thank you!
Garrett11 said:
Hi all, I recently rooted my Verizon galaxy s4 i545vrufng6 4.4.2 and ever since I did I have had some issues. The way I did it was by flashing the ng5 kernel and using towelroot then reflashing ng6. After I did that my wifi was stuck on the dull green light but I read on a forum on how to fix that by going into the system and deleting one of the wifi files. After I did that everything worked fine for a few days! Then I went out of state and when I got on the airplane my phone was put on airplane mode, by the time I landed and took off airplane mode wifi wouldn't work at all. I tried to do the same thing I did earlier but it didn't work. Matter of fact, i cannot even find that file anymore Wifi will no longer even go dull green, i can hit it as many times as I want and it will stay in the off position. I thought if I flashed a custom rom it would restart the wifi, so I looked up how to install cyanogenmod and followed the YouTube vid from wwjoshdew (30minute). I didn't get through the whole thing because when my phone restarted it had an unlocked padlock at the bottom of the Samsung start up logo and when it went into recovery mode it came up with a yellow triangle saying that system software is not authorized by Verizon wireless. I can boot it up normally or I can go into download mode but I can't access recovery mode meaning I cannot do a factory reset. I took it to Verizon and they said they couldn't help me cuz I void the warranty. If anyone could please help me get my phone back to normal I would appreciate it so much! Thank you!
Click to expand...
Click to collapse
Sooooo.... you soft bricked your phone by flashing an unsupported ROM on your particular firmware. Cynanogenmod or ANY OTHER pure AOSP Rom is not compatible with firmwares later than MDK. Don't do that again.
You need to flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin. Instructions are in the thread. You are going to be downgrading back to NC5 (the firmware version before NG6). This may fix your wifi issues as well.
Sent from my SCH-I545
liljoe727 said:
Sooooo.... you soft bricked your phone by flashing an unsupported ROM on your particular firmware. Cynanogenmod or ANY OTHER pure AOSP Rom is not compatible with firmwares later than MDK. Don't do that again.
You need to flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin. Instructions are in the thread. You are going to be downgrading back to NC5 (the firmware version before NG6). This may fix your wifi issues as well.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks so much for the reply. I have downloaded the full wipe and have unzipped it. When i try to put it in Odin it says "md5 error! Binary is invalid" i cannot continue to start the process because of this.
Garrett11 said:
Thanks so much for the reply. I have downloaded the full wipe and have unzipped it. When i try to put it in Odin it says "md5 error! Binary is invalid" i cannot continue to start the process because of this.
Click to expand...
Click to collapse
Download the file zip again and check the md5. You may have a bad download.
Sent from my SCH-I545
liljoe727 said:
Download the file zip again and check the md5. You may have a bad download.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks so much for everything. I got it passed in Odin and everything is working this far . One last question, will I be able to root without it messing up again? Id love to have my phone rooted but if it means it wont work while rooted i would rather have it just be able to work regularly
Thanks for everything!
Garrett11 said:
Thanks so much for everything. I got it passed in Odin and everything is working this far . One last question, will I be able to root without it messing up again? Id love to have my phone rooted but if it means it wont work while rooted i would rather have it just be able to work regularly
Thanks for everything!
Click to expand...
Click to collapse
Towelroot.com will work for you as far as root goes as long as you stay on NC5 firmware. Just download the APK, install it and go into the app to "make it rain"...profit.
Sent from my SCH-I545
liljoe727 said:
Towelroot.com will work for you as far as root goes as long as you stay on NC5 firmware. Just download the APK, install it and go into the app to "make it rain"...profit.
Sent from my SCH-I545
Click to expand...
Click to collapse
Awesome. Much thanks man!!!!