Really new to this. I did the verizon root methed for ME7. It says can't complete upgrade. Do I need to unroot in order to upgrade to MI1? If so, how do I do that?
bbroydri said:
Really new to this. I did the verizon root methed for ME7. It says can't complete upgrade. Do I need to unroot in order to upgrade to MI1? If so, how do I do that?
Click to expand...
Click to collapse
You don't need to unroot, but you do need to have the device in a stock condition. If you've debloated and removed stuff, or frozen apps, then the upgrade will likely fail.
I wouldn't be in any rush to install MI1.
Had same problem, now soft bricke my phone and need help
k1mu said:
You don't need to unroot, but you do need to have the device in a stock condition. If you've debloated and removed stuff, or frozen apps, then the upgrade will likely fail.
I wouldn't be in any rush to install MI1.
Click to expand...
Click to collapse
I was in the same position trying to accept the update from ME7. I had re-downloaded the stock apps and was in the process of converting them to system apps when my phone froze. When I tried to reboot I could not get passed the Verizon screen. I have been trying to read about how to fix this but I am unable to get odin to recognize my phone. I have downloaded the Samsung drivers and tried every version of odin but nothing happens when I put my phone into download (odin) mode and connect it with odin open. The rest of the steps seem easy if I could just get it to see my phone. Any thoughts, going on 3 days with no phone.
Related
Hi all, I originally rooted my phone using this post several months ag http://forum.xda-developers.com/showthread.php?t=2380325
I'm still fairly new to the dealings of root, and have found that I only used it to have access to a couple of cool apps that required root and at that rate I don't even use any more. That being said, I finally accepted the most recent update being okay that I would likely loose my root access. The update kept failing, I assumed because of the root. I backed up my personal data, and performed a factory reset from the phone. The phone still has superuser from the reset and still fails to update. Could someone help me return my phone to fully stock configuration? Thanks!
zomsoc said:
Hi all, I originally rooted my phone using this post several months ag http://forum.xda-developers.com/showthread.php?t=2380325
I'm still fairly new to the dealings of root, and have found that I only used it to have access to a couple of cool apps that required root and at that rate I don't even use any more. That being said, I finally accepted the most recent update being okay that I would likely loose my root access. The update kept failing, I assumed because of the root. I backed up my personal data, and performed a factory reset from the phone. The phone still has superuser from the reset and still fails to update. Could someone help me return my phone to fully stock configuration? Thanks!
Click to expand...
Click to collapse
Find out what odin is. Then..
Google "odin emergency tar (your build number here)" or something to that effect.
If you don't know your build number then you have some more research to do. Good luck.
I'd recommend using the Verizon update assistant. Much easier, but takes about half an hour to do:
1) Connect phone to PC using USB cord
2) When prompted for what action to take when this device is connected, select Verizon update assistant. Installation will take a few minutes.
3) Start the update assistant and confirm that you want to update the phone. The update will take a few minutes.
When the update is complete, you should have the most current update (MK2), and no root access. Should you need root again, try Saferoot - it's quick and easy:
http://forum.xda-developers.com/showthread.php?t=2565758
Thanks for pointing me in the right direction guys, I'll do some more research into both and report back soon.
Help! I've researched odin, downloaded and attempted to flash the stock image. Odin failed. My phone as of now is stuck in the downloading screen.
zomsoc said:
Help! I've researched odin, downloaded and attempted to flash the stock image. Odin failed. My phone as of now is stuck in the downloading screen.
Click to expand...
Click to collapse
You need to flash the same stock image as what was previously on your phone.
If you don't know what version you were on previously, flash MJ7 or MK2.
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
cfales25 said:
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
Click to expand...
Click to collapse
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
es0tericcha0s said:
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
Click to expand...
Click to collapse
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
cfales25 said:
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
Click to expand...
Click to collapse
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
es0tericcha0s said:
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
Click to expand...
Click to collapse
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
cfales25 said:
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
Click to expand...
Click to collapse
You'll either need to use Heimdall or the http://casual-dev.com/2014/01/04/jodin3-web-browser-or-offline-flashing-tool/
I just received a notice from Verizonwireless that there is a new software update available. So I went ahead and downloaded the update and attempted to install it. After a few seconds a new window opened showing the stupid Android robot laying on its back and the word "error" displayed. Thinking something bogus is going on with my phone I did a factory erase and retried the software update - same results.
Any way to determine what the error is and correct it so I can do the SW update? Out of curiosity I tried using ClockworkMod Rom Manager to install a custom ROM but got the same error indication.
My phone is a Verizon Galaxy S4 with Andriod version 4.3. The baseband version is I545VRUEMK2.
Thanks.
bmwmcrider said:
I just received a notice from Verizonwireless that there is a new software update available. So I went ahead and downloaded the update and attempted to install it. After a few seconds a new window opened showing the stupid Android robot laying on its back and the word "error" displayed. Thinking something bogus is going on with my phone I did a factory erase and retried the software update - same results.
Any way to determine what the error is and correct it so I can do the SW update? Out of curiosity I tried using ClockworkMod Rom Manager to install a custom ROM but got the same error indication.
My phone is a Verizon Galaxy S4 with Andriod version 4.3. The baseband version is I545VRUEMK2.
Thanks.
Click to expand...
Click to collapse
Sounds like your phone has been rooted / modified. This would be why. Samsung + VZW conspire to make it a mess to update officially when you have modded the phone. Just install the update via the PC and Odin. It is more reliable anyway than OTAs. If there is not an official 4.4 Odin version yet, then install the MK2 update that way and then factory reset then take the OTA.
But sounds like you really aren't sure what you are doing because you should NOT be attempting to use ClockWorkMod Rom Manager on a Verizon S4 with that update!! With the whole locked bootloader fiasco, this operation is not permitted as you can only use the SafeStrap recovery system to load custom roms. Really have to read up some more before you get your phone into a situation it might not find it's way out of...
es0tericcha0s said:
Sounds like your phone has been rooted / modified. This would be why. Samsung + VZW conspire to make it a mess to update officially when you have modded the phone. Just install the update via the PC and Odin. It is more reliable anyway than OTAs. If there is not an official 4.4 Odin version yet, then install the MK2 update that way and then factory reset then take the OTA.
But sounds like you really aren't sure what you are doing because you should NOT being attempting to use ClockWorkMod Rom Manager on a Verizon S4 with that update!! With the whole locked bootloader fiasco, this operation is not permitted as you can only use the SafeStrap recovery system to load custom roms. Really have to read up some more before you get your phone into a situation it might not find it's way out of...
Click to expand...
Click to collapse
Hi es0tericcha0s - Thanks for pointing out that Rom Manager shouldn't be used on a VZW Galaxy S4. I knew that but totally forgot about that fact.
bmwmcrider said:
Hi es0tericcha0s - Thanks for pointing out that Rom Manager shouldn't be used on a VZW Galaxy S4. I knew that but totally forgot about that fact.
Click to expand...
Click to collapse
You're welcome. What you need is here:
http://nasirtech.blogspot.com/2014/04/i545vrufnc5-android-442-kitkat-firmware.html
Or a 100 other places, but that one came up first.
I also find it best to factory reset after the update for best results.
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?
I am giving two VZW GS4's to my parents for Christmas and I would like to make things as simple as possible for them, which means getting rid of all the boatware that Verizon/Samsung includes. I'm familiar with rooting/flashing etc. with my Sprint GS4, but I am still somewhat bewildered by all the info regarding the VZW phones and all the different versions.
These VZW phones are on the NC5 baseband (?) and if I understand correctly they can be rooted with towelroot but cannot install a custom recovery because the bootloader is locked.
Once I root, will the phone still receive OTA updates and install properly, or will there just be a continual message saying that the update failed?
I don't plan on trying to install a custom ROM, but if I understand correctly the only way to do so is by using safestrap?
Is it possible to backup the phone, similar to a ROM backup in TWRP for example? Will I be able to return to a full stock state after root? In other words, after I root what happens if I do a factory data reset?
Thanks in advance.
buckeyestargazer said:
I am giving two VZW GS4's to my parents for Christmas and I would like to make things as simple as possible for them, which means getting rid of all the boatware that Verizon/Samsung includes. I'm familiar with rooting/flashing etc. with my Sprint GS4, but I am still somewhat bewildered by all the info regarding the VZW phones and all the different versions.
These VZW phones are on the NC5 baseband (?) and if I understand correctly they can be rooted with towelroot but cannot install a custom recovery because the bootloader is locked.
Once I root, will the phone still receive OTA updates and install properly, or will there just be a continual message saying that the update failed?
I don't plan on trying to install a custom ROM, but if I understand correctly the only way to do so is by using safestrap?
Is it possible to backup the phone, similar to a ROM backup in TWRP for example? Will I be able to return to a full stock state after root? In other words, after I root what happens if I do a factory data reset?
Thanks in advance.
Click to expand...
Click to collapse
1. You are correct. The nc5 can only be rooted. The bootloader is not unlocked or even possible to workaround; safestrap is your only option.
2. Once you root, your phone will not be stock anymore so OTAs will not work. You must unroot and restore your phone back to stock in order to update via OTA. However, if you learn how to use ODIN, your life will become much easier.
3. Safestrap is the only way.
4. You can backup with Safestrap. Yes you will be able to return back to a full stock state using ODIN. If you use ODIN to factory reset, your phone becomes back to stock i.e. unrooted.
Raymondlikesroot said:
2. Once you root, your phone will not be stock anymore so OTAs will not work. You must unroot and restore your phone back to stock in order to update via OTA. However, if you learn how to use ODIN, your life will become much easier.
Click to expand...
Click to collapse
Thanks. One more question: Once rooted, if I stay on the stock rom, will the phone still receive OTA update notifications (even though it will fail install)?
I'm a little familiar with odin so I should be able to go back to full stock if necessary.
buckeyestargazer said:
Thanks. One more question: Once rooted, if I stay on the stock rom, will the phone still receive OTA update notifications (even though it will fail install)?
I'm a little familiar with odin so I should be able to go back to full stock if necessary.
Click to expand...
Click to collapse
Yes, unfortunately, you will receive constant update messages. However, if you are rooted, you can stop these messages. Download an app called "titanium Backup" and freeze fwupdate.apk. That specific app is what causes all the update messages to appear.