This morning my phone notified me that there was an update available. I ran the update, and now my phone is pretty much completely unusable. If I try to make a call the phone app closes. If I try to text the messaging app closes. The phone also reboots every few minutes on its own.
I did the samsung support chat, they had me put the phone in safemode which didn't help at all. They suggested I do a factory reset, but I haven't been able to backup my phone without it restarting.
I'm skeptical the factory reset would help, anyway.
I'm thinking about just taking it into the verizon store and having them replace it (it's still under warranty), but I'm wondering if I could get an upgrade for the inconvenience.
Any ideas? Thoughts?
Thanks!
JMBush1007 said:
This morning my phone notified me that there was an update available. I ran the update, and now my phone is pretty much completely unusable. If I try to make a call the phone app closes. If I try to text the messaging app closes. The phone also reboots every few minutes on its own.
I did the samsung support chat, they had me put the phone in safemode which didn't help at all. They suggested I do a factory reset, but I haven't been able to backup my phone without it restarting.
I'm skeptical the factory reset would help, anyway.
I'm thinking about just taking it into the verizon store and having them replace it (it's still under warranty), but I'm wondering if I could get an upgrade for the inconvenience.
Any ideas? Thoughts?
Thanks!
Click to expand...
Click to collapse
I would Odin using home_csc to avoid wiping all data and either use qc5 or qa4 depending on which is available. Doubtful they'd offer an upgrade over a replacement
gunz.jones said:
I would Odin using home_csc to avoid wiping all data and either use qc5 or qa4 depending on which is available. Doubtful they'd offer an upgrade over a replacement
Click to expand...
Click to collapse
Okay, thanks. I did some rooting and ROMing back when I had a rezound, but haven't done anything of the sort on my S7. This method won't void my warranty, will it?
I know it's probably wishful thinking for the upgrade, but dang. Having to go a day without a phone and then through the trouble of replacing it seems like it should be worth something!
JMBush1007 said:
Okay, thanks. I did some rooting and ROMing back when I had a rezound, but haven't done anything of the sort on my S7. This method won't void my warranty, will it?
I know it's probably wishful thinking for the upgrade, but dang. Having to go a day without a phone and then through the trouble of replacing it seems like it should be worth something!
Click to expand...
Click to collapse
The rezound was a beast for this process. Like Simon says to get soff. But, know won't trip with Odin at all if you are using.stock fw
gunz.jones said:
The rezound was a beast for this process. Like Simon says to get soff. But, know won't trip with Odin at all if you are using.stock fw
Click to expand...
Click to collapse
I would think having s-off or root would be grounds for not covering on warranty, no? Or you're just saying that it's easy to get off on this device, not that I should?
I just got back from the Verizon store and the guy helping me saw the SuperSU app, which was there simply from being transferred over from google automatically from my last phone, and warned me that I may have tripped Knox and may not be covered by warranty if I had. He tried to look on the phone to see if it had, and he thought it was but said he wasn't sure because he hadn't done it in a while.
Like I said, I haven't done any thing like that, except today I did press pwr dwn + pwr + home, then I hit continue, so maybe that did it?
Anyway, if I can fix this myself I would like to just for times sake. However, since (presumably) it's under warranty still I don't want to do anything to it that will void that.
We got it to do a factory reset with much effort, finally having to copy paste my pin after typing it into the calculator and pasting it in the pin screen for the reset. Now it is stuck in the initialization mode, of the reset process and rebooting.
So, sorry to press further, but if you're sure this will not void my warranty, I will try the odin tool. I'm getting conflicting information on the interwebs about this. I want to make sure I get the right files and do it right, so do you mind linking? I've seen some stock flashes say they void the warranty. Although maybe I have already anyway?
Thanks again.
JMBush1007 said:
I would think having s-off or root would be grounds for not covering on warranty, no? Or you're just saying that it's easy to get off on this device, not that I should?
I just got back from the Verizon store and the guy helping me saw the SuperSU app, which was there simply from being transferred over from google automatically from my last phone, and warned me that I may have tripped Knox and may not be covered by warranty if I had. He tried to look on the phone to see if it had, and he thought it was but said he wasn't sure because he hadn't done it in a while.
Like I said, I haven't done any thing like that, except today I did press pwr dwn + pwr + home, then I hit continue, so maybe that did it?
Anyway, if I can fix this myself I would like to just for times sake. However, since (presumably) it's under warranty still I don't want to do anything to it that will void that.
We got it to do a factory reset with much effort, finally having to copy paste my pin after typing it into the calculator and pasting it in the pin screen for the reset. Now it is stuck in the initialization mode, of the reset process and rebooting.
So, sorry to press further, but if you're sure this will not void my warranty, I will try the odin tool. I'm getting conflicting information on the interwebs about this. I want to make sure I get the right files and do it right, so do you mind linking? I've seen some stock flashes say they void the warranty. Although maybe I have already anyway?
Thanks again.
Click to expand...
Click to collapse
It will not trip knox. So far the only thing that would trip knox is flashing a custom recovery, which we can't do. I have used the eng boot kernel a few times and still haven't tripped knox. What you're doing is flashing stock firmware back to the device in the same manner that they would at any phone shop to repair it.
gunz.jones said:
It will not trip knox. So far the only thing that would trip knox is flashing a custom recovery, which we can't do. I have used the eng boot kernel a few times and still haven't tripped knox. What you're doing is flashing stock firmware back to the device in the same manner that they would at any phone shop to repair it.
Click to expand...
Click to collapse
Alright, thanks for the reassurance.
Unfortunately, after apparent successful attempts using odin, the phone is still exhibiting the same behavior with closed app notifications, not showing the keyboard at times, and restarting. Guess I will be make a service request tomorrow, unless you have any other ideas?
Odin is a factory Samsung tool and will not flash anything to your phone that isn't allowed, due to the locked bootloader. What is your full build number? I can walk you through the steps of reflashing with Odin.
CVertigo1 said:
Odin is a factory Samsung tool and will not flash anything to your phone that isn't allowed, due to the locked bootloader. What is your full build number? I can walk you through the steps of reflashing with Odin.
Click to expand...
Click to collapse
I tried flashing QC5 a few different times, and also QA4 after that, and it just kept rebooting after the initialization screen. I loaded all 4 files, and got (1 succeeded / 0 failed) message from odin each time.
However, just now I went on Verizon's support chat to get a warranty replacement issued. I entertained Jennifer, the tier two from the windy city, and booted up in safemode. Everything seems to be working fine now! Although I did get a few close app notifications after changing from high performance mode to optimized.. but the phone is still up and running fine since then. I've been able to text and make calls for the first time since running the update yesterday morning. I'm hoping everything stays stable.
Also, I'm wondering whether it makes sense to try running the update again through the phones system update mechanism.
Thanks for the help!
The only option now is to force factory reset and clean out everything after flashing
From what I gather, you have already done a factory reset, haven't you? When you flashed with Odin, did you use HOME_CSC or CSC_VZW?
CVertigo1 said:
From what I gather, you have already done a factory reset, haven't you? When you flashed with Odin, did you use HOME_CSC or CSC_VZW?
Click to expand...
Click to collapse
Yes, yes, and yes. I did a factory reset and everything has been erased. I tried using both at different times. My last one was with QA4, and I used CSC_VZW iirc.
My phone is still going strong with no reboots since I started it up this morning!
Welp, things still seem to be running smoothly.
I do keep getting update notifications though. I'm tempted to press my luck and install the update.
Opinions? I'd be a lot more confident had it started working immediately after I flashed with Odin. The fact that I finally turned it off for the night after it cycled through several boot loops with different installs makes me wonder what the problem/solution actually was.
I guess I'll try it. It is still under warranty, and would probably be best to find out if there's an issue with it now rather than later.
I have the latest update and never exhibited the issues you have. Since you've done the factory reset, it probably wouldn't hurt to do the update. I have a feeling it should be good now. If not, then you know the update is bad. Only way to know is to try. Hoefully, it should work for you. It's been excellent for myself and many others.
iBolski said:
I have the latest update and never exhibited the issues you have. Since you've done the factory reset, it probably wouldn't hurt to do the update. I have a feeling it should be good now. If not, then you know the update is bad. Only way to know is to try. Hoefully, it should work for you. It's been excellent for myself and many others.
Click to expand...
Click to collapse
Yup, ran the update and everything is good!
Thanks for all the help, everyone.
Related
I rooted my Epic 4G with the new Epic Experience Rom recently. I am going to return the phone, but they won't take it back rooted. I couldn't find anything in search. Does anyone know how to erase any trace of my phone being rooted?
Thanks everyone.
Edit: nm read his post wrong.
RootTheWorld said:
I rooted my Epic 4G with the new Epic Experience Rom recently. I am going to return the phone, but they won't take it back rooted. I couldn't find anything in search. Does anyone know how to erase any trace of my phone being rooted?
Thanks everyone.
Click to expand...
Click to collapse
ODIN, and an official release, not Froyo.. Use the DI18 Package..
Also remember to wipe your SD card too which will not be touched during install. ODIN will flash over EVERYTHING making it brand new.
Why would you want to return your Epic? I hope not to get an EVO.. The EVO is a good phone and I wanted it when it first came out, my gut kept telling me to wait and the EPIC really is a good phone.
brian_hoffman said:
ODIN, and an official release, not Froyo.. Use the DI18 Package..
Also remember to wipe your SD card too which will not be touched during install. ODIN will flash over EVERYTHING making it brand new.
Why would you want to return your Epic? I hope not to get an EVO.. The EVO is a good phone and I wanted it when it first came out, my gut kept telling me to wait and the EPIC really is a good phone.
Click to expand...
Click to collapse
Last time I had to take my phone into a sprint store, I ODIN'ed back to DI18 and thought that it removes root as I've read in multiple posts but apparently it doesn't because the technician said the phone is rooted and although they will service the phone this time, root voids warranty and they put a note on my account to check if phone is rooted if i ever take it back again. My speaker just died, so I ODIN'd and used this to remove root.
http://forum.sdx-developers.com/epi...ecovery-1-13-for-windows-intel-mac-and-linux/
When I took it in, they didn't mention anything about root. So either they didn't check or they saw phone wasn't rooted.
For you those going back to stock or are stock and u flashed 2.2 and want to downgrade or resort back to stock use this method.
Rooted/clockwork users skip the first step...
1. Do the one click root/clockwork/etc Here
2. Flash the d118 modem Here
3. Then Flash the zip file Here
4. Then flash the get rid of clockwork zip Here
5. Your are back to stock without using odin yay!!!
Now all links work!!! and added a step use this method to return to stock with out odin.
viper786 said:
Last time I had to take my phone into a sprint store, I ODIN'ed back to DI18 and thought that it removes root as I've read in multiple posts but apparently it doesn't because the technician said the phone is rooted and although they will service the phone this time, root voids warranty and they put a note on my account to check if phone is rooted if i ever take it back again. My speaker just died, so I ODIN'd and used this to remove root.
http://forum.sdx-developers.com/epi...ecovery-1-13-for-windows-intel-mac-and-linux/
When I took it in, they didn't mention anything about root. So either they didn't check or they saw phone wasn't rooted.
Click to expand...
Click to collapse
Perhaps,
If you ODIN to an offical "virgin" Rom you will lose root.. Period. If you dont believe me do it then try and run any app that requires root "like wifi tether" it will not work. There are roms that work with odin that are pre rooted.
What I got from the other thread was Sprint can tell by some method what OS version and build you have been using while connected to thier network... so if this is true they may be able to tell your running an "Epic Experience" build and put 2&2 together that you have rooted.
The fact of the matter is, if you are running software not designed for the phone or not ready to be released and things do not work then they waste countless man hours trying to figure our why things force close on a product that is no longer thiers.
So, it is not hard to see why they do not like people rooting thier devices.
If you ODIN back and still have the speaker problem then it is SAFE to assume its a hardware rather than a software problem regardless of your past programs that have run on the phone.
brian_hoffman said:
Perhaps,
If you ODIN to an offical "virgin" Rom you will lose root.. Period. If you dont believe me do it then try and run any app that requires root "like wifi tether" it will not work. There are roms that work with odin that are pre rooted.
What I got from the other thread was Sprint can tell by some method what OS version and build you have been using while connected to thier network... so if this is true they may be able to tell your running an "Epic Experience" build and put 2&2 together that you have rooted.
The fact of the matter is, if you are running software not designed for the phone or not ready to be released and things do not work then they waste countless man hours trying to figure our why things force close on a product that is no longer thiers.
So, it is not hard to see why they do not like people rooting thier devices.
If you ODIN back and still have the speaker problem then it is SAFE to assume its a hardware rather than a software problem regardless of your past programs that have run on the phone.
Click to expand...
Click to collapse
I was not aware that they can see what OS i've been using. Anyway, they are replacing the phone and said i should receive the replacement at my house tomorrow. Normally all replacements are sent to them this is the first time i'm getting a replacement sent to my house instead of the store.
Are you sure you searched? One of the very first threads in the development forum...
Sent from my SPH-D700 using Tapatalk
updated instructions to goto stock without odin, see post 5.
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.
If you repeat three times "owaa tagoo siam" it might magically appear.
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless
So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app
You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2
chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:
add myself to the thread for future fixes...
Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app
agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.
Thank you! I knew that little bit of advice would help somebody one day.
Very sorry to post this in such a panic, I have been researching Google and XDA forums for a couple of hours now and just can't find the information I need.
I dropped my phone and broke the proximity sensor. It is making the phone all but unusable. I have the Total Equipment Protection from Verizon, which covers damage, theft, and loss. However, the problem is I have rooted the phone, and I am concerned they will say I have voided the warranty.
I tried doing a hard reset, and it still shows up as rooted. I have downloaded the files to 'restore to stock', but I don't know if that will unroot the device, or not.
I had previously installed Voodoo Rootkeeper when I had rooted it the first time. Now, after doing the hard (factory) reset, I installed Voodoo Rootkeeper from the Play store and it says I have Superuser installed, but I don't see it in my apps list. I am guessing that I just need to reinstall it from the play store because there is a button in Rootkeeper that says, "Google Play".
There's also a button that says "Temp un-root". Will this unroot my phone so that I can return it to the store under warranty?
Is there a way to completely un-root this phone, once it has been rooted?
Just FYI, I did not use the Chinese root. I used the root where you plug your phone in to the USB and use adb to run a program, which then asks you if you want full root or the partial root that you can only access via USB/abd.
I'm sorry if this seems confused... Basically, I want to unroot this phone and return it as quickly and simply as possible. Any help would be greatly appreciated!
Thanks!
Use the LG flash tool to return to stock (detailed somewhere on these forums) and you will become completely unrooted. I've done it before and it does reset the status flag in the settings screen.
Sent from my VS980 4G using XDA Premium 4 mobile app
usefulidiot127 said:
Use the LG flash tool to return to stock (detailed somewhere on these forums) and you will become completely unrooted. I've done it before and it does reset the status flag in the settings screen.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
THANK YOU! I had hoped it would be that simple. I tried to read through that thread to see if that was the case, but couldn't see anything definitive. I was in a bit of a panic and distracted too, so it's possible I missed it. Hopefully, this thread will get indexed by Google and other people who may have the same problem can see this.
Will try that and report back!
George
This worked great and is VZW specific.
http://forum.xda-developers.com/showthread.php?t=2448960
Broken screen for me and needed an insurance replacement.
Thanks, hard brick?
willyjay said:
This worked great and is VZW specific.
http://forum.xda-developers.com/showthread.php?t=2448960
Broken screen for me and needed an insurance replacement.
Click to expand...
Click to collapse
Do you think I should try that one specifically instead of the generic instructions here:
http://forum.xda-developers.com/showthread.php?t=2432476
?
I didn't know what a TOT file is, so I Googled it and found some warning to be very careful with TOT files because they can hard brick the phone?
Not working
Ah, heck!
I tried the first generic 'restore to stock' from this link:
http://forum.xda-developers.com/showthread.php?t=2432476
and when I get to the step where I click 'ok' to proceed and flash the rom, the program stops and the phone displays a "B100" and then "ROOTED" in red letters!
I'm going to read through all 27 pages of that thread to see if anyone else has had this problem, but in the meantime, does that Verizon specific thread fix this problem, would either of you happen to know?
Thanks!
Total protection is not warranty. You breaking your phone is not a manufacturer defect which warranty covers.
Regardless, neither method cares if it's rooted or not. I have returned more phones than I can count that have been rooted and not once have I had a charge.
gwbyrd said:
Do you think I should try that one specifically instead of the generic instructions here:
http://forum.xda-developers.com/showthread.php?t=2432476
?
I didn't know what a TOT file is, so I Googled it and found some warning to be very careful with TOT files because they can hard brick the phone?
Click to expand...
Click to collapse
The VZW specific method worked perfectly for me....also, shows unrooted in the settings and download mode.
Just make sure to verify the md5 checksum on the tot file.
Verified, flashing the stock tot resets back to pure stock including a reset of the root flag. I used the VZW specific writeup and it went exactly as advertised. Recommend you use that one.
Thanks
06stang said:
Total protection is not warranty. You breaking your phone is not a manufacturer defect which warranty covers.
Regardless, neither method cares if it's rooted or not. I have returned more phones than I can count that have been rooted and not once have I had a charge.
Click to expand...
Click to collapse
Thanks, I was wondering about that! I've never been a Verizon customer before and I've heard stories that made me nervous. You have definitely made me feel a bit more reassured. Of course, I still want to unroot it a) to show myself I can, and b) just to be safe.
gwbyrd said:
Thanks, I was wondering about that! I've never been a Verizon customer before and I've heard stories that made me nervous. You have definitely made me feel a bit more reassured. Of course, I still want to unroot it a) to show myself I can, and b) just to be safe.
Click to expand...
Click to collapse
Can't hurt to do it. When I had my Incredible 1 I asked my buddy about it and he told me when he gets the phone they check for physical damage, check the water damage indicators, plug it in and flash the new software, then test it to send back out. I went through 6 incredibles, 4 incredible 2s, 4 rezounds, and 4 galaxy nexus. All rooted all returned without resetting no charges.
But i can say 100% guaranteed without a doubt your total protection insurance does no care what you do to the phone because it's not a warranty issue anyway. If you return your current device for a new one you're paying the $99 fee anyway. If you send it in as warranty they'll charge you full pop if they see physical damage.
HOORAY!
HOORAY!
I followed the steps at this link: http://forum.xda-developers.com/showthread.php?t=2448960, and it worked!
Thanks again, everyone!
Hello folks. Unsure weather or not i post this in the correct place. So i rooted my SM-N9005 the other day just because well i"had" to. Ofcourse the next day the 4.4 update got released and i couldn't upgrade since my by now unfriendly phone told me i had tampered with it. I tried to restore it without really knowing what the hell i did and feeling a bit stupid for not getting it. I managed to remove root but it still says it's tampered with. Reckon i triggered the flash counter somehow. I could really use your help removing root and get my little phone back to "original" shape. Talk to me like a 3 year old since i apparently couldn't figure it out on my own. Cheers!
(And yes I have been reading so much about this my head spins now. I tried different ways to recover but i cant get it to work. I intentionally left out all the different apps i used here from the forum since that will probably confuse you guys aswell.)
how did you root?
download the kitkat firmware from sammobile then flash it using odin (so you don't need to upgrade via ota) then re-root
toinktoink said:
how did you root?
download the kitkat firmware from sammobile then flash it using odin (so you don't need to upgrade via ota) then re-root
Click to expand...
Click to collapse
Ok, it started when i tried to root it by following an online gtuide. However it didnt work so I tried another one and "semi-bricked" it. Using odin. I tried readiing up on it as much as i could but the more i read the more different ways i found. Long story short, i rooted it. It worked fine. But removing root didnt seem to do the trick. I would just like to return it to stock without ruining anything. And be able to upgrade OTA if possible.I love fiddling with these things but since i pay so much for this damn phone I rather not do anything more that can destroy warranty etc. As i understood it rooting it wouldnt leave a trace and should be easy to undo. Now I understand that wasnt the case. I know I am the one to blame but would love if anyone could just try to explain what to do in a simple step by step way. If you need any info on what i did I can try to explain but i ended up with like 12 different webpages open with different solutions and to be honest I am not sure I can explain everything i tried...
JFKruuse said:
Ok, it started when i tried to root it by following an online gtuide. However it didnt work so I tried another one and "semi-bricked" it. Using odin. I tried readiing up on it as much as i could but the more i read the more different ways i found. Long story short, i rooted it. It worked fine. But removing root didnt seem to do the trick. I would just like to return it to stock without ruining anything. And be able to upgrade OTA if possible.I love fiddling with these things but since i pay so much for this damn phone I rather not do anything more that can destroy warranty etc. As i understood it rooting it wouldnt leave a trace and should be easy to undo. Now I understand that wasnt the case. I know I am the one to blame but would love if anyone could just try to explain what to do in a simple step by step way. If you need any info on what i did I can try to explain but i ended up with like 12 different webpages open with different solutions and to be honest I am not sure I can explain everything i tried...
Click to expand...
Click to collapse
Solved
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
I don't think there is a revert method (inside or outside the store). I know it's after the fact, but on your next device, you may want to figure out exactly what you'd want to do with root before you go through with it. I typically only do it for TB backup purposes and XPOSED, but I've found that I can back up in other ways, and I dig stock enough not to risk rooting. I don't knock you for rooting (there are plenty of good reasons to), this is just my advice going forward. In the meantime, you should look around XDA, you may find your golden goose app that you can leverage root for. Good luck.
bgibson72 said:
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
Click to expand...
Click to collapse
hey sorry to hear that your having issues,
but you and the other poster are correct, sprint never released a restore file that wasn't encrypted.
And to my knowledge the repair centers would not be able to fix this issues, and sadly lg would more then likely deny a
warranty claim as this was modifications done by the end user.
A good chance in the future that we will get the files needed or a process to revert back to stock, but currently there is no SAFE method to try, and pushing the stock aboot and system.img back to the device WILL hard brick the device.. @me2151 attempted the restore process once, and failed, so please be careful as you may have issues.. The red warning triangle is due to your aboot "bootloader" being swapped for the debug version and will never go away, unless we get a dev willing to risk his device for a .png swap of the warning RED img. Other wise its there forever.
The static on boot up can be removed using a custom kernel but be aware it WILL break things in return. Typically update to prl and profile
fm radio, comfort view and a few other little things..
Hey, thanks for the reply. I can deal with the red warning screen, I just get a little anxious when I can't use the touchscreen or my cellular data gets hosed. As long as there are fixes here (which there have been--thanks to all) and I can use my phone, we're good. I figured if someone could break encryption on government files then why would an encrypted KDZ file be such a challenge? At any rate, I appreciate the help. I'll just keep my fingers crossed for a PNG swap!