Okay I am thoroughly peeved at Verizon. I avoided allowing the 4.4.2 update forever had a rooted 4.3 until the other day my charger cable got wet while charging somehow. My charging port burnt up and stopped charging. So I unrooted using the unroot option in SU to return my phone to Verizon because I am still under warranty. They said the water damage voided the warranty. But now my phone will not work, it is the actual phone that is not working. I ordered a new charging port and now OS starts up fine and everything appears normal charging and applications. When I would dial a number it would say call canceled 0:00. I tried to update to 4.4.2 to see if that would solve issues after a recovery and a soft reset did not work. Still no luck phone is now saying Mobile network not available in a window. I have now completed a factory reset and removed every part to replace it with no luck still the same result I cannot change any of the IOT hidden menu options bc I am no longer rooted. I can not think of anything else to try. I have seen that there is a way to flash to a stock 4.1.2 or something then unlock bootloader not sure how this is possible if I am locked up now. Anyone have any great suggestions better than paying my $100 insurance deductible and getting a new device that is also unrootable at this point?
If you are on 4.4.2 there is no going back unless you send it to a shop and pay them. Big thread here about them.
ZacharyKBurton said:
Okay I am thoroughly peeved at Verizon. I avoided allowing the 4.4.2 update forever had a rooted 4.3 until the other day my charger cable got wet while charging somehow. My charging port burnt up and stopped charging. So I unrooted using the unroot option in SU to return my phone to Verizon because I am still under warranty. They said the water damage voided the warranty. But now my phone will not work, it is the actual phone that is not working. I ordered a new charging port and now OS starts up fine and everything appears normal charging and applications. When I would dial a number it would say call canceled 0:00. I tried to update to 4.4.2 to see if that would solve issues after a recovery and a soft reset did not work. Still no luck phone is now saying Mobile network not available in a window. I have now completed a factory reset and removed every part to replace it with no luck still the same result I cannot change any of the IOT hidden menu options bc I am no longer rooted. I can not think of anything else to try. I have seen that there is a way to flash to a stock 4.1.2 or something then unlock bootloader not sure how this is possible if I am locked up now. Anyone have any great suggestions better than paying my $100 insurance deductible and getting a new device that is also unrootable at this point?
Click to expand...
Click to collapse
Sounds like you need to reflash a modem. The above poster is correct, if you accepted the 4.4.2 update, you can not return to 4.1.2. Not sure why you did that, accepting a OTA would not fix anything that Odin'ing a Stock 4.1.2 img would not. But anyway, see if re flashing 4.4.2 will help. Go to SamMobile, then Firmwares, then download for you device, which is SCH-I605. Build number will end in ND7
?
lacoursiere18 said:
Sounds like you need to reflash a modem. The above poster is correct, if you accepted the 4.4.2 update, you can not return to 4.1.2. Not sure why you did that, accepting a OTA would not fix anything that Odin'ing a Stock 4.1.2 img would not. But anyway, see if re flashing 4.4.2 will help. Go to SamMobile, then Firmwares, then download for you device, which is SCH-I605. Build number will end in ND7
Click to expand...
Click to collapse
Okay so I checked out Sammobile and the firmware you are saying to re-flash the entire ND7 OTA rom correct. I am not sure why this would work, can you explain your thoughts? My thought:The modem was not working on 4.3 and is now not working on 4.4.2 why would a re-flash of 4.4.2 fix it, I am more than willing to try it as I have nothing to lose at this point.
I do however wonder if I can re-run the 4.4.2 without an unlocked boot-loader?
Also my reasoning was that I had inadvertently updated to 4.3 with a locked boot-loader so I was rooted but I did not have an unlocked boot-loader so I figured that another locked boot-loader was not going to be any worse than the one I already had? I guess I was wrong again. I am just really irritated that they would lock up such a powerful device and keep us from using it for what we intended at purchase. #VerizonN'SamsungSuck.
Update
ZacharyKBurton said:
Okay so I checked out Sammobile and the firmware you are saying to re-flash the entire ND7 OTA rom correct. I am not sure why this would work, can you explain your thoughts? My thought:The modem was not working on 4.3 and is now not working on 4.4.2 why would a re-flash of 4.4.2 fix it, I am more than willing to try it as I have nothing to lose at this point.
I do however wonder if I can re-run the 4.4.2 without an unlocked boot-loader?
Also my reasoning was that I had inadvertently updated to 4.3 with a locked boot-loader so I was rooted but I did not have an unlocked boot-loader so I figured that another locked boot-loader was not going to be any worse than the one I already had? I guess I was wrong again. I am just really irritated that they would lock up such a powerful device and keep us from using it for what we intended at purchase. #VerizonN'SamsungSuck.
Click to expand...
Click to collapse
Okay. "Mobile network not available" still....
All I tried was a factory hard reset through volume up+home+power menu. And then a Odin flash of tar.md5 from Sammobile.
The download was succesfull it shows a new hidden.img, modem.bin that were flashed succesfully below is messages from Odin...
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I then tried restarting, removing battery, removing simcard(w/ boot), adding simcard(w/ boot)
Phone is still popping "mobile network unavailable" window on phone calls. SMS messaging, 4G, and WiFi all appear to work as normal but no phone calls and it automatically keeps switching to a global network setting.
Is it possible that it is a hardware issue? Not sure where all the other applications work fine I would assume not, but I could be wrong.
Simcard? (phone recognizes sim card and allows 4G on my MIN)
Modem?
Battery?
Any ideas on this what I should try next?
lacoursiere18 said:
Sounds like you need to reflash a modem. The above poster is correct, if you accepted the 4.4.2 update, you can not return to 4.1.2. Not sure why you did that, accepting a OTA would not fix anything that Odin'ing a Stock 4.1.2 img would not. But anyway, see if re flashing 4.4.2 will help. Go to SamMobile, then Firmwares, then download for you device, which is SCH-I605. Build number will end in ND7
Click to expand...
Click to collapse
I saw that you commented on the recent rooting thread Ghettoroot, which BTW works after some efforts. I am now rooted again and would like to try and solve this issue on some other routes. I am wondering what happens if I flash an older stock firmware via odin? I have heard this does not work but would like to try maybe. I can now safestrap which is my next move probably tomorrow with a different rom. What do you know about flashing older firmware 4.1 say after locked bootloader what happens specifacally does it soft brick and say unauthorized software from Verizon? Just playing devils advocate to save me some time.
ZacharyKBurton said:
I saw that you commented on the recent rooting thread Ghettoroot, which BTW works after some efforts. I am now rooted again and would like to try and solve this issue on some other routes. I am wondering what happens if I flash an older stock firmware via odin? I have heard this does not work but would like to try maybe. I can now safestrap which is my next move probably tomorrow with a different rom. What do you know about flashing older firmware 4.1 say after locked bootloader what happens specifacally does it soft brick and say unauthorized software from Verizon? Just playing devils advocate to save me some time.
Click to expand...
Click to collapse
If you took the ota or used Odin to flash the stock 4.4.2 image then you can't use Odin to flash back to older. Bootloader is designed to not allow it.
Edit: Also, as far as I am aware safestrap hasn't been updated to work with 4.4.2 nd7. I believe it only works with 4.3 mj9.
Related
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
want relocked BL running newest stock via odin flash without tripping flash counter
Edit; I never did manage to relock the bootloader. However, Verizon still accepted the device since it appeared close enough to stock. I used the alternative restore and triangle away to bring it 95 percent to stock. So I can safely say from my experience that if this is your problem you will probably be fine. It's been a few months and still no new charges on my bill for out of warranty device but YMMV
Shawnkanan said:
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Click to expand...
Click to collapse
I am in a similar situation. I am sending the device back for warranty service since the screen must have burnt out or something. The digitizer catches a touch but there is no light emanating from the screen and since the device was purchased March 28th it is completely under warranty. As it is obvious the root modifications did not cause the screen issue, I do not wish to get a new device via insurance claim and so I am getting another sent.
but my issue is after managing to run triangle away via screencast/adb, how the hell does one relock the device if it's been upgraded to vramc3? from what I have searched, and trust me I have been searching the past two days, which led me here and a few other threads btw, it appears that once the device is on vramc3 it cannot odin back to anything else or it will fail on sboot.bin. And I am not finding any stock odin packages for vramc3, so how the hell does a person take this bad boy back to stock and relock the bootloader for sending to vzw for service? not only that but I can no longer activate recovery since I wouldnt have access to screencast and there is absolutely no way I am sending this device back with even the most minute amount of data in tact so it can be sold to the highest bidder or handed over via an illegal court order for mass search and seizure. anybody have experience with this? i am at the point where i think the only thing I can do is flash the alternate restore for vral but wouldnt that trip my flash counter, and then when they check the device it would probably OTA and softbrick, which I do not want them to have to deal with.
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
androidy_guy said:
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
Click to expand...
Click to collapse
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
spc_hicks09 said:
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
Click to expand...
Click to collapse
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
tech_head said:
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
Click to expand...
Click to collapse
hmm, interesting. perhaps i should try my luck with VZ first? i guess it can't do any harm. currently when it turns on it shows knox status 0x0, which is apparently good. perhaps VZ can flash it somehow? i have no idea what kind of support they provide for this kind of thing.
edit: also it seems this KNOX is mainly relevant for creating a secure zone for corporate applications? i am not using it in that setting. perhaps it would just reduce the resale value somewhat? or is there something i'm not understanding about it.
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
tech_head said:
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Flash the Odin posted in post 2. Then you can root and use safestrap the same as it being on me7 like it was.
androidy_guy said:
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Click to expand...
Click to collapse
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
^^^^^^^^^ what he said
tech_head said:
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
Click to expand...
Click to collapse
will do - downloading the package now. should be able to fool around with it after work today. i feel like a real idiot for rushing into this without knowing enough about the OTA firmware that i ignorantly accepted.
at this point i don't really care if the KNOX is triggered or whatever - i always purchase my devices out of warranty and activate them so i can keep my grandfathered unlimited. it's the risk i run for wanting stock android on verizon with unlimited data
ooooook, the package in that thread worked. thanks a lot guys! i was really kicking myself all day over this one, and really had only myself to blame. my only questions now are:
how can i check my KNOX status?
is it likely that there will be a root/CM version for this phone, post UMI1?
Reboot into download and read the tiny text with a magnifying glass
Sent from my SCH-I545 using Tapatalk
Im glad the odin image worked...pulling that thing was kinda difficult lol.
ok i booted into ODIN again and KNOX comes up 0x0, so it looks like i came out unscathed all around. too bad i inadvertently locked my phone down with this update. i got the GS4 so i could upgrade from my GN, in hopes of flashing the latest CM10 on a phone with some nicer hardware.
It's been 3 days since I had my phone soft bricked. Here's what happened. I had rooted 4.1.2 and my sister accepted OTA when 4.3 (MJ9) came out so I lost my root access. Everything was working fine and I wasn't doing much on my phone so I didn't bother to root it back. 4.3 (VRUAND3) OTA failed on my phone when it came out and I didn't care about it because it was still on 4.3. When 4.4 came out, I decided to do OTA update and everything went fine except when it rebooted. It will pass the samsung logo but when it got to Verizon logo, it was just stuck there. So I searched this forum and tried everything that I found about unbricking the soft bricked phone. All stock roms will fail at sboot.bin except for root66_VZW_stock_system.tar (I did try with and without .pit and I only checked autoreboot F. Reset time) but when I do that then I will get the system software not authorized by Verizon Wireless has been found error (with yellow triangle). Here's the list of stock roms I tried and odin versions.
ROM: root66_VZW_stock_system.tar, I605VZWEMJ9, I605VRALJB, I605VZWAND3 (all with and without .pit)
Odin: 1.85, 3.07, 3.09
The only good thing is that I still have my odin mode and the number of binary didn't change. And I didn't get the knox.....
I really need you guys' expertise... any suggestion will help at this moment... Sorry for the lengthy post I really tried to be specific on what I tried so far.... I'm currently downloading VRAND7 (4.4) and I'm out of the option after I try this one with odin.... Thank you.
gomtingeee said:
It's been 3 days since I had my phone soft bricked. Here's what happened. I had rooted 4.1.2 and my sister accepted OTA when 4.3 (MJ9) came out so I lost my root access. Everything was working fine and I wasn't doing much on my phone so I didn't bother to root it back. 4.3 (VRUAND3) OTA failed on my phone when it came out and I didn't care about it because it was still on 4.3. When 4.4 came out, I decided to do OTA update and everything went fine except when it rebooted. It will pass the samsung logo but when it got to Verizon logo, it was just stuck there. So I searched this forum and tried everything that I found about unbricking the soft bricked phone. All stock roms will fail at sboot.bin except for root66_VZW_stock_system.tar (I did try with and without .pit and I only checked autoreboot F. Reset time) but when I do that then I will get the system software not authorized by Verizon Wireless has been found error (with yellow triangle). Here's the list of stock roms I tried and odin versions.
ROM: root66_VZW_stock_system.tar, I605VZWEMJ9, I605VRALJB, I605VZWAND3 (all with and without .pit)
Odin: 1.85, 3.07, 3.09
The only good thing is that I still have my odin mode and the number of binary didn't change. And I didn't get the knox.....
I really need you guys' expertise... any suggestion will help at this moment... Sorry for the lengthy post I really tried to be specific on what I tried so far.... I'm currently downloading VRAMC3 (4.4) and I'm out of the option after I try this one with odin.... Thank you.
Click to expand...
Click to collapse
The reason they all fail at sboot is bc you are attempting to downgrade to fix it..that's not possible.. so here is what you need to do.
Go to Sammobile.com
Go to Firmwares (top of page)
Scroll down to Search
Type "SCH-I605"
Select & download ND7 4.4.2
Flash via Odin w/ pit
It should pass and you will be good to go
Sent from my SCH-I605 using XDA Free mobile app
lacoursiere18 said:
The reason they all fail at sboot is bc you are attempting to downgrade to fix it..that's not possible.. so here is what you need to do.
Go to Sammobile.com
Go to Firmwares (top of page)
Scroll down to Search
Type "SCH-I605"
Select & download ND7 4.4.2
Flash via Odin w/ pit
It should pass and you will be good to go
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I saw this post on the development forum [ROM][I605VRUFND7][4.4.2]OFFICIAL STOCK ROOTED ODEX/DEODEX[6/19/2014]
so that rom won't work on mine? just asking out of a curiosity...
gomtingeee said:
I saw this post on the development forum [ROM][I605VRUFND7][4.4.2]OFFICIAL STOCK ROOTED ODEX/DEODEX[6/19/2014]
so that rom won't work on mine? just asking out of a curiosity...
Click to expand...
Click to collapse
Nope. You taking the 4.3 and 4.4.2 OTA locked your bootloader.. so therfore no flashing custom roms like that one and I don't believe there is even a root method yet..
Oh okay thank you for your info. I flashed it to 4.4 and it`s working. I`ll wait for the developer`s to come up with the rooting method for 4.4 thank you guys for everything
Sent from my SCH-I605 using XDA Free mobile app
Always getting either "Not authorized by Verizon" or "Upgrade encountered an issue"
Hey guys, hoping someone can help me out with what appears to be a soft brick on my phone.
Background
Bought phone in January 2013, immediately rooted and installed custom recovery. Phone stayed this way until yesterday, when I restored with ODIN and then installed all OTA's to prepare for a replacement under a Best Buy service plan, expecting it to work like it used to where I go into the store and drop off the phone, then a new one is sent to the store. I then installed all OTA's up to 4.4.2 (I think that one is ND7 but not sure as I was using AOSP-based ROMS while rooted). The ODIN restore brought me back to saying the firmware was all official.
Currently
Replacement process changed and I am stuck with this phone for another week while a replacement gets mailed to my home, so I decided to play around with ODIN to restore to MJ9 since most root methods seemed to work for MJ9, but I accidentally chose the LJB image that I had downloaded yesterday for the PDA in ODIN. When running this, it failed on sboot.bin.
I restarted the phone and it said "Firmware Upgrade encountered an issue" and tells me to connect it to Kies, which I tried, but for some reason Kies just runs on Connecting to Device and won't do anything else. I didn't spend a whole lot of time on that though, as it also changed the "System Status" to Custom while leaving Current Binary as Official, and from what I read Kies will refuse to do a recovery if anything is Custom.
I tried to install MJ9 through ODIN and it also fails at sboot.bin, resulting in the same message as above. I downloaded the alternate MC3 from this thread and it ran through ODIN fine since it does not have an sboot.bin, but it gives the error about the firmware not being authorized by Verizon and changes both Current Binary and System Status to Custom (I think MJ9 was the first locked bootloader, so I would assume that is why, but I don't know for sure). There was no alternate for MJ9 so I tried to make my own by extracting, removing sboot.bin, and then putting the rest of the files in a new tar file, but ODIN won't run it and gives an error about the MD5 not matching.
At this point the phone working is not so much of an issue since I already have a replacement on the way to my house, but I would prefer to fix this so a) I have a phone for the next few days, and b) so I don't have to go short something inside on purpose to hard-brick it and prevent them from refusing my replacement claim.
Any help would be greatly appreciated.
Thanks,
Michael
Once you updated the phone to factory stock 4.4.2, you permanently locked the bootloader and you can't downgrade to any other pre 4.4.2 ND7 firmwares. The easiest thing to do now would be to use Odin to restore the device back to to factory 4.4.2 stock firmware. There is GhettoRoot for 4.4.2 if you're wanting to root the device again on 4.4.2... and people are reporting that safestrap works as well for flashing 4.4.2 touchwiz roms. Good luck!
Ahh, I wasn't aware that ND7 couldn't be downgraded at all; I thought anything past MJ9 would work since that was when the bootloader became locked. I don't see any ND7 ODIN images available anywhere and Kies won't allow me to restore the device. Is there another method I should be using to restore? My wife has an i605 on 4.1.1 right now (same background as mine, just not bricked and no OTAs downloaded); if we updated until ND7 was downloaded but not installed, would I be able to pull the OTA from hers and flash in ODIN, or are they not ODIN-compatible?
opalelement said:
Ahh, I wasn't aware that ND7 couldn't be downgraded at all; I thought anything past MJ9 would work since that was when the bootloader became locked. I don't see any ND7 ODIN images available anywhere and Kies won't allow me to restore the device. Is there another method I should be using to restore? My wife has an i605 on 4.1.1 right now (same background as mine, just not bricked and no OTAs downloaded); if we updated until ND7 was downloaded but not installed, would I be able to pull the OTA from hers and flash in ODIN, or are they not ODIN-compatible?
Click to expand...
Click to collapse
Here's a link to the Verizon stock 4.4.2 firmware from Sammobile. You'll have to register, but the download should be free. You should be able to use Odin to restore the device with this firmware file and the pit file from Droidstyle's restore guide. If Odin 3.07 doesn't work, try Odin 3.09 from Sammobile... or try Odin 3.10, which I've been using lately with no problems.
Thanks for that link, I was able to download and restore my phone with the ND7 download. I wasn't aware that SamMobile keeps a firmware database, so I also appreciate that piece of info.
Thanks,
Michael
Hey,
Sorry total noob at messing with my phone, buuuuuut I tried to (foolishly) downgrade my Verizon sch-i545 from OC1 because I hate it. I tried to flash back to MDK using ODIN 3.4, 3.7, AND 3.9 all of which failed. From what I can find it seems like flashing to anything from a Verizon sch-i545 running OC1 is destined to fail due to something contained in the update. Is this correct? Since the failed flash, I can't get my phone to turn back on normally, it just gives me the "Software Update Failed, use verizon software repair assistant..." which from what I can find is downloaded from the phone when you plug it in? But it didn't seem to do so for mine when I initially plugged it in to back up files. I can't find an online source to download the verizon software from. So basically I'm asking for help on just getting my phone functioning again? It doesn't seem like I've bricked it, but I don't know what to do after a failed flash? Can I download the 5.0.1 firmware and flash it using odin and it will actually work because it's 5.0.1? I'm tired of waiting 2 hrs to download a firmware to have it immediately fail haha. Or is there another much simpler way to get it out of this mode and back to just running normal ****ty lollipop? I can get the phone back into download mode, but that's it. Thanks for any help. Sorry if anything is silly or redundant, tried searching for hours without finding much.
Thanks.
Try This
BreakThroughCity said:
Hey,
Sorry total noob at messing with my phone, buuuuuut I tried to (foolishly) downgrade my Verizon sch-i545 from OC1 because I hate it. I tried to flash back to MDK using ODIN 3.4, 3.7, AND 3.9 all of which failed. From what I can find it seems like flashing to anything from a Verizon sch-i545 running OC1 is destined to fail due to something contained in the update. Is this correct? Since the failed flash, I can't get my phone to turn back on normally, it just gives me the "Software Update Failed, use verizon software repair assistant..." which from what I can find is downloaded from the phone when you plug it in? But it didn't seem to do so for mine when I initially plugged it in to back up files. I can't find an online source to download the verizon software from. So basically I'm asking for help on just getting my phone functioning again? It doesn't seem like I've bricked it, but I don't know what to do after a failed flash? Can I download the 5.0.1 firmware and flash it using odin and it will actually work because it's 5.0.1? I'm tired of waiting 2 hrs to download a firmware to have it immediately fail haha. Or is there another much simpler way to get it out of this mode and back to just running normal ****ty lollipop? I can get the phone back into download mode, but that's it. Thanks for any help. Sorry if anything is silly or redundant, tried searching for hours without finding much.
Thanks.
Click to expand...
Click to collapse
Ok I have already gone down this road myself.
First can you get your phone into download mode ? If so re-flash the original firmware. This file is on the XDA site somewhere ,I remember seeing it. I loaded mine at a very slow download took hours , did it over night . I have had to redo my phone several times trying with Odin after countless lockups.
The OC1 can not be changed it has a locked boot-loader that can not be unlocked @ this time. So no downgrade changes of ant kind. You CAN NOT GO BACK I highly suggest you read more on this site to help you better.
There is only a handful of ROMs you can install & they have to be OC1 compatable
traco1 said:
Ok I have already gone down this road myself.
First can you get your phone into download mode ? If so re-flash the original firmware. This file is on the XDA site somewhere ,I remember seeing it. I loaded mine at a very slow download took hours , did it over night . I have had to redo my phone several times trying with Odin after countless lockups.
The OC1 can not be changed it has a locked boot-loader that can not be unlocked @ this time. So no downgrade changes of ant kind. You CAN NOT GO BACK I highly suggest you read more on this site to help you better.
There is only a handful of ROMs you can install & they have to be OC1 compatable
Click to expand...
Click to collapse
Thanks! That worked like a charm. If anyone else sees this and is in a similar situation, flashing the OC1 back definitely work the first time. I had to try and try again, different USB ports, pull the battery out, wait, and try again. Eventually with persistence it worked.