Always getting either "Not authorized by Verizon" or "Upgrade encountered an issue" - Verizon Samsung Galaxy Note II

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

Related

Stock Restore File Question

Ok, so yesterday my phone was unable to be rooted and unlocked for some unknown reasons. So, stupidly, I flashed the back to bone stock restore file realizing that it was a custom rom file and soft bricked my device. Luckily, with the help of google, I used root66 in which made my device able to boot up back to normal while rooted.
I then took the 2 OTA updates to get to Android 4.1.2 with the build VRAMC3 and now I know for a factho its completely stock according to odin mode. Im ready to unlock this device and get roms up.
Although, Im still scared at when I soft bricked my device. Im wondering if there is any sort of restore file that is compatible for VRAMC3 or if I can use root66 or a downgradeable pda file if I were to soft brick my device again somehow? If someone can link me to it, that would be appreciated.
Thanks.
http://forum.xda-developers.com/showthread.php?t=2024207.
Read through this has everything u need
Sent from my SCH-I605 using xda premium
Wow, you have now created 3 different threads and posted in 2 different casual threads. Just stick to the most current casual thread and stop the unnecessary multiple threads. Use the current version of casual to unlock your phone. Don't worry, your phone isn't going to blow up from using it
AldenIsRad said:
Ok, so yesterday my phone was unable to be rooted and unlocked for some unknown reasons. So, stupidly, I flashed the back to bone stock restore file realizing that it was a custom rom file and soft bricked my device. Luckily, with the help of google, I used root66 in which made my device able to boot up back to normal while rooted.
I then took the 2 OTA updates to get to Android 4.1.2 with the build VRAMC3 and now I know for a factho its completely stock according to odin mode. Im ready to unlock this device and get roms up.
Although, Im still scared at when I soft bricked my device. Im wondering if there is any sort of restore file that is compatible for VRAMC3 or if I can use root66 or a downgradeable pda file if I were to soft brick my device again somehow? If someone can link me to it, that would be appreciated. Thanks.
Click to expand...
Click to collapse
In this case I would only use the alternate restore to return to stock if you have to. Then you can accept updates or not.
Ridin' a Note 2 blast

Returning to Stock

Before everyone goes on to say that I need to read the forums, please understand that I've tried everything I could think of or find in the last week trying to get this thing back to stock.
Background:
I was on the leaked 4.3 firmware and the skynote ROM without problems. I tried switching to N3bula and flashing the official 4.3 firmware from Beanstown. I still couldn't get the N3bula ROM past the verizon logo and so i restored my backup from skynote. I (possibly mistakenly) unchecked the option to restore boot.img thinking i wouldn't need it. Everything booted into the backup just fine with the exception of WiFi. I tried rebooting into recovery and I soft bricked.
Things I've done since the brick:
- I used Odin and restored my phone to the root66 ROM (rooted VRALJB) - this allowed my phone to boot into a weird recovery program (probably some kind of stock) and it allowed me to actually use my phone as a phone.
- I tried flashing a new recovery in Odin (which probably should've been my first step instead of restoring to stock)
- I repartioned my PIT to the one from the forum on returning to stock
- I've (unsuccessfully) tried casual for VRALJB and VRAMC3
- I've (unsuccessfully) tried using Odin to go to either VRAMC3 and (normal) VRALJB
Device Info (from the app I downloaded named, "Device Info"):
These just seem peculiar to me...
- My bootloader is VRALL4
- My Baseband is VRAMC3
- My Incremental version is VRALJB
Help: - note that I do have root access
- Should these match? ^ and would those listed above cause casual to fail?
- Did i lock my bootloader when I unchecked the option to restore it in my backup after flashing the 4.3 firmware in Odin?
- Since my bootloader and my baseband are on different versions, would that cause casual to fail?
- Is there a way to downgrade my Baseband or upgrade my bootloader to make casual work?
I know these questions are probably way out of most people's leagues to answer, but anything helps guys!

[Q] Soft bricked after 4.4 OTA update Please help

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

[Q] Bricked VZ s4 I545 between mk2 and FNC5

I think my beloved s4 may be bricked beyond hope... I attempted to upgrade to NC5 from MK2 following the thread http://forum.xda-developers.com/showthread.php?t=2735172 for the no-wipe TAR. I started flashing and walked away briefly and the Mrs sharked the computer and I think x'd off ODIN (Why does she compulsively close everything in sight to get on the internet? I don't know!!!! Grrrrr). I'm not sure how long in the process it might have gone, whether it finished or not but regardless when I came back ODIN was closed. Now the phone will only boot into recovery mode and the screen indicating "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Now I've attempted to reflash the stock NC5, doing the no-wipe and full wipe TARs as well as the MK2 recovery tar from http://forum.xda-developers.com/showthread.php?t=2578209. I tried to downgrade as well as shown here http://forum.xda-developers.com/showthread.php?t=2578209 as it looked like it described my problem (being stuck between mk2 and NC5). Any attempts at flashing anything at all in ODIN get an almost immediate "Succeed 0 / Failed 1" within less then a second. Attempts to use Kies have been no use either. Kies tells me immediately that the connected device is not supported. The Kies Emergency Firmware recovery does not show a device listed to recover. And lastly manually entering the model and MEID into the Firmware upgrade and initialization screen also gets a quick "This device's version could not be updated." Any ideas other then dig up my old Droid Bionic or heaven forbid my Droid Eris? Hmmmm... maybe my old windows mobile clamshell...
Salvation!
Fixed! after trying over and over I tried from a different computer altogether and the update went smooth as could be. Now updated to 4.4.2... Time to root!

[Q] Reverting to stock FAIL

Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Bascotie said:
Hi guys,
I am trying to help someone get their phone back to stock. It's a verizon galaxy note 2 and all the information I have is that they tried to root or rom it and now it doesn't start (and to get it to boot you have to remove/put in the battery)
I'm following droidstyle's guide and I can get as far as starting the odin flash process to stock, but it goes for a few minutes and then I just get a FAIL.
UPDATE1: So I tried again but with the root66 stock VRALJB and it passed but I'm getting the system software not authorized message. I'll keep trying some things..
Anyway I can get this thing up and running again?
UPDATE2: I'm flashing the stock roms semi-successfully, but even after a PASS on the flash, I get the "Verizon has detected unauthorized software" message. Any ideas?
Click to expand...
Click to collapse
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
BluGuy said:
What version of stock firmware was on the phone when the person tried to root it? If it was mj9 4.3 or above you will have to flash the version that was installed through Odin to get it to work. The bootloader starting in mj9 4.3 doesn't allow to downgrade to previous version.
Click to expand...
Click to collapse
Good question. He doesn't really know as he was even newer to this than I am (I've done it on a couple phones in the past only a few times, so I do kinda have the hang of it, but this phone's a bit different).
Can I just try flashing 4.3 or above and see if that works? What would be the way to go if I don't know what was flashed previously?

Categories

Resources