[Q] I totally messed up my Unroot...HELP! - Verizon Samsung Galaxy S 4

Ok so first of all a disclaimer: This is my very first forum post in my life so excuse any unspoken rules that are not being followed. I took my phone to a phone nerd store and even he couldn't give me answers so he suggested this site where "the phone gods" are as he said. Also feel free to face palm during or after reading this issue because it too, was my first root and clearly I should not have....anyway step by step here is what I did and hopefully someone can tell me where to go from here.
I rooted my phone about a month ago. I am not familiar with flashing ROMs and what not so when the new KitKat came out I wanted to download it but didn't know how with my phone rooted. I looked up on YouTube how to unroot and go back to stock and there as a video for a "One click" unroot. So being unwise and an idiot, I downloaded it and it said unrooted, however it just deleted supersu and my phone no longer has root access however when I boot it up it still has the unlock logo and in recovery mode I get the green android with writing in the top left corner stating that ODIN mode is being ran. My issue is that ever since I did that, I can no longer log into any google apps such as playstore or even a google plus act..it just says there is a problem with the servers. Like I said before , I took it to someone who knew what they were doing and he said he would flash it back to stock unrooted, but during his troubleshooting, he said it kept failing and he didn't want to be responsible for messing it up further. If anyone can tell me what the hell I did so I don't make the same mistake again would be great, even greater if someone can walk me through how to get back to stock. I know this is a lot to ask, but like I said I have zero idea. From reading other posts, I will list all the info I have about my phone so that can be a starting point.
Verizon GS4
Model # I545
Android Version 4.3
MK2 Build
Kernel Version 3.4.0
Any info or ideas would be great! again, feel free to include what a dunce I am because I sure feel like one!
Thanks!

LandonJames7 said:
Ok so first of all a disclaimer: This is my very first forum post in my life so excuse any unspoken rules that are not being followed. I took my phone to a phone nerd store and even he couldn't give me answers so he suggested this site where "the phone gods" are as he said. Also feel free to face palm during or after reading this issue because it too, was my first root and clearly I should not have....anyway step by step here is what I did and hopefully someone can tell me where to go from here.
I rooted my phone about a month ago. I am not familiar with flashing ROMs and what not so when the new KitKat came out I wanted to download it but didn't know how with my phone rooted. I looked up on YouTube how to unroot and go back to stock and there as a video for a "One click" unroot. So being unwise and an idiot, I downloaded it and it said unrooted, however it just deleted supersu and my phone no longer has root access however when I boot it up it still has the unlock logo and in recovery mode I get the green android with writing in the top left corner stating that ODIN mode is being ran. My issue is that ever since I did that, I can no longer log into any google apps such as playstore or even a google plus act..it just says there is a problem with the servers. Like I said before , I took it to someone who knew what they were doing and he said he would flash it back to stock unrooted, but during his troubleshooting, he said it kept failing and he didn't want to be responsible for messing it up further. If anyone can tell me what the hell I did so I don't make the same mistake again would be great, even greater if someone can walk me through how to get back to stock. I know this is a lot to ask, but like I said I have zero idea. From reading other posts, I will list all the info I have about my phone so that can be a starting point.
Verizon GS4
Model # I545
Android Version 4.3
MK2 Build
Kernel Version 3.4.0
Any info or ideas would be great! again, feel free to include what a dunce I am because I sure feel like one!
Thanks!
Click to expand...
Click to collapse
start here
http://forum.xda-developers.com/showthread.php?t=2606501
you will eventually need to understand odin as you will need to start with a clean mk2

decaturbob said:
start here
http://forum.xda-developers.com/showthread.php?t=2606501
you will eventually need to understand odin as you will need to start with a clean mk2
Click to expand...
Click to collapse
Thanks man..I'm currently following the steps on the video, I downloaded ODIN and now the huge recovery file is downloading..ive gotten to this step before and the download kept failing so I will let you know how it goes.

LandonJames7 said:
Thanks man..I'm currently following the steps on the video, I downloaded ODIN and now the huge recovery file is downloading..ive gotten to this step before and the download kept failing so I will let you know how it goes.
Click to expand...
Click to collapse
Download everything to computer and check the md5 checksums
sent by bajarom v2.2 kitkat

Related

[Q] unroot for OTA???

I've rooted my GT 10.1 but I have two questions that I can't find the answer.
1. Has anyone discovered how to unroot back to stock?
2. If rooted, will I be able to get the OTA of touchwiz by checking for updates under settings?
PS I flashed the TouchWiz UX found in this forum. Got to say it is really nice and I can't wait to get the version from Sammy. I then restored a backup using Rom Manager and restored fine except when checking for software updates. It used to say no update available, but today it says failed to connect to servers. Anyone else getting this error?
I guess that is actually 3 questions.
Thanks
1. Unrooting is pretty simple. Just flash the 3.1 OTA in the dev forum, after doing a full wipe. If you feel the need to go back to full stock, you'll also want to nvflash back to the original retail recovery, which you undoubtedly saved when you first rooted.
2. No one knows yet, but rest assured, within a day (less probably) of the update being released, it'll be available here as a rooted flashable ROM. If you learn one thing from your time on XDA, it should be "never accept an OTA update." Let the devs pull it apart and repackage it in a nice root-safe download.
Undoubtedly! (I wish) I wasn't planning to root but while playing with Odin, I thought I was locked at the downloading screen while testing odin. (Didn't hold down the power button long enough to shut off tab) I thought my only solution was to continue and root. No problems rooting, it was easy. I just wanted to make sure I get the TouchWiz update. Now I learned my lesson I will never do an OTA update.
Glad you told me that, otherwise I probably would have screwed up my GT. I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
pmsrefugee said:
Glad you told me that, otherwise I probably would have screwed up my GT.
Click to expand...
Click to collapse
It's not so much that you'll screw up your device by accepting an OTA, but rather that you might lose root and/or your custom recovery (perhaps permanently). Nevertheless, there are some cases of OTAs screwing up devices when accepted over non-stock installs, so IMHO its always best to wait for a flashable ROM.
pmsrefugee said:
I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
Click to expand...
Click to collapse
Yes, I believe the stock retail recovery is posted in the CWM recovery download package here: http://forum.xda-developers.com/showthread.php?t=1130574. You'll note that Step 3 is where you were advised to backup your original stock recovery, although the step is (correctly) noted as optional. No big deal, in any event. Glad I could help.

[Q] System software not authorized by Verizon

l have searched the forums however haven't seen any threads on how to deal with the situation I'm having specifically on the Verzion N2.
It started after I used the easy root method found in droidstyles guide which worked fine. I was able to achieve root however when I restarted the phone prior to moving on to Adams unlock/bootloader method I got a "System software not authorized by Verizon" message on my screen and the phone is stuck on that screen. Needless to say I have a problem and I don't know what to do. :crying:
I have been able to connect to Odin however when trying to run Adam's method to unlock the bootloader (so I could install revision 3) the phone flashes back to the system software error message so I can't get any further. At this point I don't want to mess things up more than they already are so I am at a loss at what to do. I assume this is considered a softbrick situation so I am hoping there is a work around to get the phone running again...any advice, suggestions, links that the experts can point me to get me back on track?. I am obviously a novice at this however I have rooted other phones in the past (thunderbolt, windows) but I can't figure out what caused this nor do I know what to do...HELP!!!
follow section 1 and odin back to stock.
droidstyle said:
follow section 1 and odin back to stock.
Click to expand...
Click to collapse
THANK YOU!!!

[Q] Can't believe I'm that guy...

My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
I literally just posted the same question. Any help would be appreciated if you can figure it out. Ill return the favor if i can get any information :good:
If you took the latest update I'm not sure what the answer is because I haven't been willing to take the update.
If you were in mdk before the yellow triangle then all you have to do is Odin the mdk kernel.
I'd imagine if you are on the latest then odining the latest would take care of it also but again, I won't take the latest so I can't say for sure
sent from my blu vzw gs4
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
richardawood said:
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
Click to expand...
Click to collapse
Im on a search for the updated kernel as well. At least there is someone in the same boat as i am.
richardawood said:
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
Click to expand...
Click to collapse
If the phone was running ME7 then you can ONLY flash ME7 again (at least right now).
Grab the image from this thread...
http://forum.xda-developers.com/showthread.php?t=2357235
and flash it using Odin.
Thank You
That worked great! I am back up in running and waiting patiently w/ the rest of us that updated... THANK YOU!!!!!! :highfive:
Thanks
I can't thank you enough. The S4 is my first Android phone and after 3 weeks, the USB connection on the phone broke and I finally got my new one today. While I was setting up SuperSU/Titanium Backup/ROM Manager, I guess the phone downloaded the ME7 update in the background and I told it to install (stupid me). This will teach me from rushing to get my phone back to the state it was in. (Not that I can do that now because I need SuperSU before I can install ROM Manager). Hopefully once I can get ROM Manager back, I can restore my MDK backup with all my custom settings and apps. I think I will make a visit to the VZ store tomorrow and see if they can revert back to the MDK version. I will make up some lame excuse of why I don't want to be on this new release.
This leads to my question of, is there a way to disable or remove the apk file that controls the software updates?
Thanks again for saving my life!!!
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Thanks
hexitnow said:
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the information about the sdm.apk. When I debloated my phone I used the adb shell to remove most of the *.apk packages that I did not want. This was of course after I took a full Titanium Backup and ROM Backup.
Sounds good and I will not waste my time going to Verizon today.
You make a really good point about not going back to the mdk, but rather move forward with the technology and updates. This leads me to some more questions once I have root again:
1. Is my mdk rom backup totally useless at this point?
2. If yes to 1, since my mdk rom contained all my apps/customized settings, do I have to manually download everything and reconfigure?
3. If no to 2, how would I go about getting the app/customized settings back, Titanium Backup?
4. If yes to 2, if I go about downloading everything manually and configuring, will the new root remove all these settings?
I am sure I will have more questions so thanks in advanced
PS: I think I figured out what caused my USB port to stop working. I take my phone with me when I run so I think some sweat got in from my arm band and corroded the connections. I tried cleaning them with rubbing alcohol and compressed air, but still no dice. If connected to a computer or wall charger, it will charge, but a computer will not detected it. So my guess is there is damage to the board allowing whatever communication is needed to work with a computer.

What did I just do...

So I was getting really frustrated with ROMS not working right so I followed someones advice and used ODIN to upgrade to NC5. I got my phone right after launch and rooted it the day I got it, installed TWRP and I have always had an icon on the Samsung screen that is a little lock with the word custom under it and that is the only thing I have retained after upgrading. I can no longer flash a custom recovery via GooManager, the phone simply won't let me. I am guessing when I updated it put me on the latest bootloader and locked it. Is this the case? I really don't like the idea of safestrap, but if I have to use it now I guess I will. If it did indeed upgrade my bootloader, wouldn't the "Custom" icon have disappeared from my lock splash screen?
So what exactly have I done to my phone? Can anyone help me figure out where to go from here?
Custom splash screen only represents that the phone's flash counter has been triggered. Means nothing.
I can't believe you updated from an MDK phone man. If you want to continue to use custom rom's you'll have to use towel root and AT&T's 3.72 safestrap. And get comfortable with Odin. Unfortunately there's no way to get a true custom recovery back on your device.
TB13 said:
So I was getting really frustrated with ROMS not working right so I followed someones advice and used ODIN to upgrade to NC5. I got my phone right after launch and rooted it the day I got it, installed TWRP and I have always had an icon on the Samsung screen that is a little lock with the word custom under it and that is the only thing I have retained after upgrading. I can no longer flash a custom recovery via GooManager, the phone simply won't let me. I am guessing when I updated it put me on the latest bootloader and locked it. Is this the case? I really don't like the idea of safestrap, but if I have to use it now I guess I will. If it did indeed upgrade my bootloader, wouldn't the "Custom" icon have disappeared from my lock splash screen?
So what exactly have I done to my phone? Can anyone help me figure out where to go from here?
Click to expand...
Click to collapse
what you did wrong is not research what you were doing.......I can;t believe you followed someone's advice to rid your phone of MDK...
.
this thread contains links and info you best read before proceeding any further
http://forum.xda-developers.com/showthread.php?t=2606501
Another one bites the dust. That's too bad. Sorry nothing can be done now
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Another one bites the dust. That's too bad. Sorry nothing can be done now
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
if we had a dollar every time we see same or similar post....the aversion to reading and research is compelling
Aaaannnnddddd idiot of the day award goes to me. It had been so long since I had messesd with my phone that I didn't even know I still had an MDK device, I will miss it and I will be shunned for killing it, but life goes on.
I wish I had the power to sticky the threads that people should look at before attempting something like this instead of having useless, unupdated threads stickied in every subforum.

[Q] Soft Bricked Verizon Galaxy S4 i545 Help Please!?

Hey guys, I am a newbie to rooting and I messed up big time. I used TowelRoot.com to Root my Galaxy S4. Everything went smoothly. I did a little research on custom roms and back ups but couldn't fully understand it. Sorry to sound like a complete noob! But I am. Let's get to the point. So I read online about someone editing the system file Build.Prop and got the new Samsung Galaxy S5 Notification bar which I attempted. I ended up screwing up because i edited the NAME of the file and not the actual string attached in the folder. Anyway, now my phone is not starting up. I see the Galaxy S4 Logo then it goes all black. I am able to boot to recovery and also download mode. But I'm stuck here. Is there a easy solution for this? I read about downloading Odin and doing a custom rom / flash. But I wanted to avoid all the difficult stuff if i could. Any suggestions????
that413trini said:
Hey guys, I am a newbie to rooting and I messed up big time. I used TowelRoot.com to Root my Galaxy S4. Everything went smoothly. I did a little research on custom roms and back ups but couldn't fully understand it. Sorry to sound like a complete noob! But I am. Let's get to the point. So I read online about someone editing the system file Build.Prop and got the new Samsung Galaxy S5 Notification bar which I attempted. I ended up screwing up because i edited the NAME of the file and not the actual string attached in the folder. Anyway, now my phone is not starting up. I see the Galaxy S4 Logo then it goes all black. I am able to boot to recovery and also download mode. But I'm stuck here. Is there a easy solution for this? I read about downloading Odin and doing a custom rom / flash. But I wanted to avoid all the difficult stuff if i could. Any suggestions????
Click to expand...
Click to collapse
For future reference, let's not go editing files on your phone when you don't know what you're doing.... just saying.
You're gonna need to Odin flash, which is not difficult, what was your baseband version?
liljoe727 said:
For future reference, let's not go editing files on your phone when you don't know what you're doing.... just saying.
You're gonna need to Odin flash, which is not difficult, what was your baseband version?
Click to expand...
Click to collapse
Not sure cause the phone is turned off. I google searched it's either I545VRUFNC5 or I545VUFNC5. How will I go about finding the correct one? I know my phone was 4.4.2 before it was bricked and that the model number is i545
that413trini said:
Not sure cause the phone is turned off. I google searched it's either I545VRUFNC5 or I545VUFNC5. How will I go about finding the correct one? I know my phone was 4.4.2 before it was bricked and that the model number is i545
Click to expand...
Click to collapse
What did you Google search to get this information? You should have known this prior to doing anything with your phone
If your baseband is NC5, this link http://forum.xda-developers.com/showthread.php?t=2735172 will have your Odin downloads and your wipe/no wipe factory images. Make sure you read through the thread and you should be golden. Also, make sure you only flash the NC5 images, do not click on the links for MJ7 or MDK.
liljoe727 said:
What did you Google search to get this information? You should have known this prior to doing anything with your phone
If your baseband is NC5, this link http://forum.xda-developers.com/showthread.php?t=2735172 will have your Odin downloads and your wipe/no wipe factory images. Make sure you read through the thread and you should be golden. Also, make sure you only flash the NC5 images, do not click on the links for MJ7 or MDK.
Click to expand...
Click to collapse
It worked like a charm! Thank you so much!!
Not to be a dumb A** but saying not to play around with your phone if you don't know what your are doing is ... will there would be no need for this forum. Trying things and getting in trouble is part of learning. Education is expensive.
I sis the same thing this guy did in changing part of the Build.Prop.
aknisley said:
Not to be a dumb A** but saying not to play around with your phone if you don't know what your are doing is ... will there would be no need for this forum. Trying things and getting in trouble is part of learning. Education is expensive.
I sis the same thing this guy did in changing part of the Build.Prop.
Click to expand...
Click to collapse
90 percent of the "problems" people have on here are answered by simply copying and pasting a link to the corresponding thread that can be found in the forums for our device. I am not saying to "remain ignorant and not mess with your phone", but to do research and take the time to read the information, which is readily available, that pertains to what you're trying to do. That's all. Not trying to sound like a jerk or anything.
Jesus loves you!
Odin is very simple to use. You just download the correct tar file for your phone, put you phone into download mode, and hit start and it runs everything it self.
The only downside is you have to start from scratch.
liljoe727 said:
What did you Google search to get this information? You should have known this prior to doing anything with your phone
If your baseband is NC5, this link http://forum.xda-developers.com/showthread.php?t=2735172 will have your Odin downloads and your wipe/no wipe factory images. Make sure you read through the thread and you should be golden. Also, make sure you only flash the NC5 images, do not click on the links for MJ7 or MDK.
Click to expand...
Click to collapse
I so am loving you right now, thanks for the info.
The linked thread did not work for me, and I can't figure out why... was running hyperdrive 18, flashed blackbox 3.2.3 and then I got softbricked. The recovery thread tars keep failing in odin. How do I diagnose this?
Hi guys,
I have the same question. My phone is stuck on Verizon logo and I did some research and it says it soft bricked. I want wipe/reset it using Odin and the OS file. But my question is that my phone was originally US cellular and then flashed to Verizon I545. So should I be using the Verizon OS file or the US Cellular file? Newbie here, appreciate your responses.
P.S. I did not mess with the phone like the original poster, I woke and the phone would not start.
tojikjon said:
Hi guys,
I have the same question. My phone is stuck on Verizon logo and I did some research and it says it soft bricked. I want wipe/reset it using Odin and the OS file. But my question is that my phone was originally US cellular and then flashed to Verizon I545. So should I be using the Verizon OS file or the US Cellular file? Newbie here, appreciate your responses.
P.S. I did not mess with the phone like the original poster, I woke and the phone would not start.
Click to expand...
Click to collapse
if you had the red verizon splash screen at startup then go ahead and
flash the verizon odin package (make sure you use a package the same version or lower as to what was previously on the device) to avoid blowing a qfuse
Thanks, it worked

Categories

Resources