Related
hey guys how the heck do i unroot this phone? flash stock recovery and hard reset maybe?? any ideas?
Which version of rom do you have - v10f?
Sent from my LG-P930 using xda premium
SuperOneClick -> unroot
Ya I'm on v10f. I've heard there's v10k out?
Sent from my LG-P930 using XDA App
[email protected] said:
SuperOneClick -> unroot
Click to expand...
Click to collapse
My p930 is rooted and running the latest CWM recovery and CM10 nightlies. The screen is broken and I 'll need to send it in for warranty/insurance claim. I've run a CWM backup, and transferred that to my PC. Now I need to return to stock/unroot.
This thread, along with other unroot threads, are kinda old. Is SOC > Unroot still the best method? Has anyone unrooted from 4.1/CM10? Are there any other known methods?
ShadowOf said:
My p930 is rooted and running the latest CWM recovery and CM10 nightlies. The screen is broken and I 'll need to send it in for warranty/insurance claim. I've run a CWM backup, and transferred that to my PC. Now I need to return to stock/unroot.
This thread, along with other unroot threads, are kinda old. Is SOC > Unroot still the best method? Has anyone unrooted from 4.1/CM10? Are there any other known methods?
Click to expand...
Click to collapse
If all else fails you could use the LG update tool to update to official ICS... I personally don't know if there's an easier way.
On the broken screen thing, how much are you being charged to replace it? You can get the digitizer glass/frames on eBay for around $40-45. There is a nice guide on how to tear-down the phone floating around the general forum which I have used three times so far : But it's pretty easy to do and would save you some time of being without your phone... and save you the hassle of having to unroot and all.
ShadowOf said:
My p930 is rooted and running the latest CWM recovery and CM10 nightlies. The screen is broken and I 'll need to send it in for warranty/insurance claim. I've run a CWM backup, and transferred that to my PC. Now I need to return to stock/unroot.
This thread, along with other unroot threads, are kinda old. Is SOC > Unroot still the best method? Has anyone unrooted from 4.1/CM10? Are there any other known methods?
Click to expand...
Click to collapse
Best thing to do now is just update using the official LG updater to ICS from download mode. If it refuses to install for any reason, flash the V18f ICS update first.
I'm also wanting to go back to the stock ICS on my optimus LTE. I'm just not 100% sure what I should flash first. Currently if I connect the phone to the LG mobile software it says that my phone is already up to date. Where would I be able to get a V18F ICS update? And also once I've done that will I be able to point the LG software to Telus I don't remember since it's been so long since I upgraded my phone.
drumist said:
Best thing to do now is just update using the official LG updater to ICS from download mode. If it refuses to install for any reason, flash the V18f ICS update first.
Click to expand...
Click to collapse
EzRush said:
I'm also wanting to go back to the stock ICS on my optimus LTE. I'm just not 100% sure what I should flash first. Currently if I connect the phone to the LG mobile software it says that my phone is already up to date. Where would I be able to get a V18F ICS update? And also once I've done that will I be able to point the LG software to Telus I don't remember since it's been so long since I upgraded my phone.
Click to expand...
Click to collapse
Then you should be able to follow the unbrick guide to downgrade to GB, and instead flashing CWM and carrying on from there, try to use the LG updater while on stock GB.
EzRush said:
I'm also wanting to go back to the stock ICS on my optimus LTE. I'm just not 100% sure what I should flash first. Currently if I connect the phone to the LG mobile software it says that my phone is already up to date. Where would I be able to get a V18F ICS update? And also once I've done that will I be able to point the LG software to Telus I don't remember since it's been so long since I upgraded my phone.
Click to expand...
Click to collapse
The v18f version is here: http://forum.xda-developers.com/showthread.php?t=1668476
The nice thing about this is that this exe will flash no matter what ROM you currently have installed. Then, after installing this, the official updater will recognize your phone as out of date and will allow you to flash to the official v20c update easily.
Seems to want to update to V10J and that's about it, never get's to V20E. Also after the update it just stays at the Telus splash screen.
I was able to load the ATT V18F no problem and then get to the point where the LG software wants to update but that's where it end unfortunately.
Guess I'll keep trying and see how it goes.
v
drumist said:
The v18f version is here: http://forum.xda-developers.com/showthread.php?t=1668476
The nice thing about this is that this exe will flash no matter what ROM you currently have installed. Then, after installing this, the official updater will recognize your phone as out of date and will allow you to flash to the official v20c update easily.
Click to expand...
Click to collapse
EzRush said:
Also after the update it just stays at the Telus splash screen.
Click to expand...
Click to collapse
Oh, that's actually fine. You just need to do one more thing: after you get stuck on the splash screen, pull the battery and put it back in. Then hold down volume down + power button to turn the phone on (same way you access CWM if you have it installed). Then press power button twice to confirm and your phone will reboot after a little bit and should work fine from there.
HOWEVER, if it's not even the version you want, then that doesn't help you much. What version of the phone do you have? P935 from Telus?
I have a AT&T Galaxy S3 and I have been searching the forums for a solution to this, and have come up with some answers. From what I've gathered I am by no means at the end of my ropes at recovering the device, but I'm having trouble actually making any ground on it.
I read that flashing back to stock using Odin would get me by the yellow triangle of death, but I can't find a stock download anywhere. All the links I've found link to hotfile, which isn't up anymore so that's been creating some problems. Maybe I'm wrong on that, but all I need is Samsung's stock 4.0.4, right?
I have a HTC Sensation and Nexus 10, both rooted, and I thought I had a pretty good grip on what direction was up from working on those devices but this S3 really has me stumped. Any help would be greatly appreciated.
It might be better if you could mention what exactly you did to get your device to the state it is in.
diablo009 said:
It might be better if you could mention what exactly you did to get your device to the state it is in.
Click to expand...
Click to collapse
Woops, sorry. I flashed CF-Root-SGS3-v6.3.tar using Odin and the process failed.
What OS were you running before trying to root? If it's 4.3, you won't find an AT&T stock 4.3 rom to re-flash your phone. Do not try and flash anything with a bootloader that is older than the phone's current bootloader as that will brick it.
audit13 said:
What OS were you running before trying to root? If it's 4.3, you won't find an AT&T stock 4.3 rom to re-flash your phone. Do not try and flash anything with a bootloader that is older than the phone's current bootloader as that will brick it.
Click to expand...
Click to collapse
Thankfully, I was running 4.0.4.
andrbrks said:
Thankfully, I was running 4.0.4.
Click to expand...
Click to collapse
Stock AT&T firmware files are here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
In my opinion, don't go near 4.3.
I'm sorry, I feel like this should be obvious, but how do I know which of these I want to flash?
So you're sure you were on 4.04 when you tried to root? If that's the case, I would try the July version.
By flashing in Odin, you will wipe everything off the phone, including your data.
audit13 said:
So you're sure you were on 4.04 when you tried to root? If that's the case, I would try the July version.
By flashing in Odin, you will wipe everything off the phone, including your data.
Click to expand...
Click to collapse
100%. On the box the SW-VER is listed as I747UCDLK3, should I still go with the July version? And I use the PDA function in Odin for this, correct?
Wait, DLK3 is 4.1.1, not 4.0.4.
http://androidromupdate.com/2012/12...-s3-android-4-1-1-jelly-bean-official-update/
analysis higionu
Huh. I reset the phone to factory settings last night before I started tinkering with anything, and it was for sure listed as 4.0.4. I could be mistaken though, but I'm fairly certain. I'd rather not go against what's listed on it's box though. I'm sure the factory knows better than me.
I'm not sure what to do now. Does the imei # match the box?
That it does. I have to wait another 2 hours before I can even download the stock firmware, so it'll be awhile before I can even try flashing it.
andrbrks said:
That it does. I have to wait another 2 hours before I can even download the stock firmware, so it'll be awhile before I can even try flashing it.
Click to expand...
Click to collapse
I'm not sure what I would do in your situation since the box indicates you have 4.1.1 while your phone has 4.04.
You were right, I talked with someone who was there last night when I was working on it. The phone is 4.1.1, thanks for the catch.
Okay, at least it is definitely not 4.3 which is good.
What you can do is install a custom recovery and flash a custom ROM.
So should I not even worry about going back to stock then?
andrbrks said:
So should I not even worry about going back to stock then?
Click to expand...
Click to collapse
Did you try returning to stock using Kies?
Stock firmware is here: http://www.sammobile.com/firmwares/1/?model=SGH-I747&pcode=ATT#firmware
Running it right now.
I hope it works for you. Good luck:good:
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
TH3F4LL3N said:
Hey all,
I caught wind of the 4.4.2 update, so I decided to see how it is. I had used saferoot to gain root access to it, but all I did was use Xposed to modify my phone. No recoveries or anything, and the warranty bit is 0 on the download mode screen. Just to be safe, I wiped data/factory reset to make sure everything was gone, then I started the OTA download. All goes as it should until it reboots to install it, where it gets stuck at 25%, then says "update failed". Phone reboots, and then a window pops up saying the update was interrupted. Anyone else having this issue? Anyone know any workarounds? Because if this phone just won't update, there it no reason for my to keep my warranty bit, since I have less than a week on the warranty left anyhow.
Click to expand...
Click to collapse
Did you try re-downloading it?
BWolf56 said:
Did you try re-downloading it?
Click to expand...
Click to collapse
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
TH3F4LL3N said:
This is my 3rd attempt to re-download it. It's currently at 94%, so I'll let you know how it goes.
Click to expand...
Click to collapse
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
TH3F4LL3N said:
After my 3rd attempt, without my sd card inserted this time, the update failed again! This is starting to get irritating. Maybe I should just flash CM11 or something like that.
Click to expand...
Click to collapse
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
BWolf56 said:
It's kinda odd that it still fails after so many downloads (and so close to being complete).
If there's only a week left to your warranty, you can start looking at custom ROM you might like (AOSP or TW). By the time you find one you really like and understand how to flash it (without any issue), you will have time to give the OTA another shot. Will be some good knowledge reading in the meantime
Little advice: Don't flash a custom ROM while annoyed/mad. That's how 80% of bricks happen.
Click to expand...
Click to collapse
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
TH3F4LL3N said:
Ok thanks for the advice, mate. I heard if I take it to Best Buy, they can update it. Do you know if it's free?
Click to expand...
Click to collapse
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
BWolf56 said:
Imo it should be but you can always give them a call to make sure.
Just make sure you aren't rooted when going there lol.
Click to expand...
Click to collapse
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
TH3F4LL3N said:
Haha I know the basics of rooting. If I go, my phone will be the way it is right now: stuck on stock 4.3 with nothing on it but the bloatware from Sammy and AT&T
Click to expand...
Click to collapse
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
You need to run Triangle Away whiule rooted to change it back to official
audit13 said:
You need to run Triangle Away whiule rooted to change it back to official
Click to expand...
Click to collapse
Will this work for 4.3?
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
TH3F4LL3N said:
I just noticed that the device status is custom, even though I've wiped data. Is that what is causing this trouble? If so, is there a way to fix it?
Click to expand...
Click to collapse
crazymonkey05 said:
Yea when you modify the system at all it trips the modified flag and that's probably where its failing (not the warranty bit flag that's at 0 but the one that's in the system itself) try to Odin to full stock and try it again this should revert it back to official
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
One thing, don't downgrade bootloaders doing so. That will result in a brick.
audit13 said:
I never tried it on 4.3, only on 4.1.2. Since you have Knox, rooting and installing SU may trip the knox counter. Did you try uninstalling Xposed and running the update?
Click to expand...
Click to collapse
I have, and I've wiped the phone at least 3 or 4 times!
BWolf56 said:
One thing, don't downgrade bootloaders doing so. That will result in a brick.
Click to expand...
Click to collapse
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
TH3F4LL3N said:
I have, and I've wiped the phone at least 3 or 4 times!
How would I go about this? I have the stock 4.1.1 tar file, and I can't get the 4.3 file because AT&T's update was OTA only, and I can't find the 4.3 tar file anywhere!
Click to expand...
Click to collapse
Is your current baseband LK3? If so, 4.1.1 should be fine.
BWolf56 said:
Is your current baseband LK3? If so, 4.1.1 should be fine.
Click to expand...
Click to collapse
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
TH3F4LL3N said:
I am in the about device section of the settings, and it says the baseband version is I747UCUEMJB. Is this the right one?
Click to expand...
Click to collapse
That would be the 4.3. You can't downgrade from those bootloaders. Therefor, you need stock 4.3
BWolf56 said:
That would be the 4.3. You can't downgrade from those bootloaders.
Click to expand...
Click to collapse
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
TH3F4LL3N said:
Well that's just great. I'm stuck on 4.3. Could I possibly flash something like CM11 to get to kitkat? Of course, I'd like to back up the stock rom in case something goes wrong, but it would be wonderful if I could use CM on my phone again! I used the saferoot method to gain root access in the first place, which disabled KNOX if that means anything.
Click to expand...
Click to collapse
Yes you can, it's fairly simple too. Just gotta follow their instructions (don't skip anything).
As for recovery, I recommend TWRP, which you can get on the Play Store.
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
So I have a Verizon Pixel XL that has been unlocked, TWRP alpha installed, and rooted....
How shall I update my build? Should I even update the build?
My goal is to have the latest update running on my system (manually flashing or OTA I don't care) with an unlocked rooted Pixel XL that can broadcast wifi natively.
I have everthing down except the update piece. Any advice?
You have TWRP and root? How is that working? I was reading that SuperSu needs an update to work with it. Also many people who have taken the OTA (or even flash full system image) are getting stuck in the bouncing balls boot loop. I would hold off on updating. No real major changes as of yet.
Twrp is working fine but I have nothing to flash to test...????
networx2002 said:
Twrp is working fine but I have nothing to flash to test...????
Click to expand...
Click to collapse
Yeah that is what I'm hinting at.... There is no updated ROM to work with TWRP yet that is updated to the latest Google Build
Root is working. I have twrp alpha 2. Root and elementalx 8 all installed. Although, im getting my daydream headset tomm. And when you install the app it tells you to check for updates. It says I have one. But if you look at the OTA updates NDE63 is the newest. Which im on. So I dn at this point. I guess i'll just roll with it for now. The dev that made purenexus that I ran on my nexus 6. Says hes working on it already and gets his on the 21st. So i'll just stick with what I have for now. I'm sure we'll see roms pretty soon
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
s1dest3pnate said:
So, what is the proper/safe way to install an update without breaking anything? Losing root is not a concern since we can just reflash TWRP and SuperSU, but what's the process? Searching is not resulting in a guide that I can be 100% confident in.
Click to expand...
Click to collapse
jreink01 said:
I am rooted in my pixel XL. Can I accept OTA updates without losing root? If not, is there a developer/thread that has a safe update to flash? I am not on a custom ROM, I'm stock. Thanks
Click to expand...
Click to collapse
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
DeathSentinels said:
What i did was download the latest factory image from here from there I used this guide on post two section 8, installed the latest update, restored from cloud back up logged into all my apps (important if you use snapchat), reinstalled TWRP + Root + ElementalX and i was good to go, might seem like a little bit of work, but I've done it so many times I can get it done quickly now.
Click to expand...
Click to collapse
If you edit the flash-all.bat file and take out the -w near the end you wont flash user data. So you can skip restoring your cloud backup and apps. Backup just to be safe though.
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
jreink01 said:
Have a few more questions. If I do this procedure, is there the possibility that I won't be able to reroot with each update? If I do reroot and reinstall TWRP, is that like a factory reset where I will lose all my data? Back years ago when I would flash Roms, you could install a update without having to factory reset each time, Is this possible with the pixel with being stock? I would love to get the updates each month but don't want to do it if each time I have to reroot, reinstall TWRP and having all my data wiped. Thanks
Click to expand...
Click to collapse
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
TonikJDK said:
No, it won't stop you from re-rooting and it will not factory reset your phone. So each month you will not lose your data but you will have to reinstall TWRP and root.
Click to expand...
Click to collapse
OK, thanks, that's good to know. When I lose root, will that mess with any of my apps that need root to work like titanium backup? Or will I just need to grant it user privileges again? I have never done this particular process before so I am a little weiry. Do you know of a step by step guide to do this? Sorry but I would feel more comfortable that way. Thanks for all you help and feedback, it's been years since I last went through the rooting, flashing process so, I guess I am being extra cautious. I have/am learning by the feedback you have given me.
Sent from my Pixel XL using Tapatalk
I am rooted with TWRP RC1
i never sideloaded an OTA before, alway applied factory images. Too lazy, but tired of all the rework.
i folllowed,
https://9to5google.com/2016/12/05/how-to-sideload-android-7-1-1-nmf26o-onto-the-pixel/
no data loss.
just had to use fastboot to reinstall TWRP and reflash SUPERSU.
All is well.
If I choose to side load it, do I root and install TWRP the same way I did when I first did this, with ADB on my windows PC? And side loading will work with a new operating system (when it comes out) along with the monthly security updates? I just checked and my latest security update is from January. If I updated March's update, would that automatically have the February one with it?
---------- Post added at 02:10 AM ---------- Previous post was at 02:02 AM ----------
TonikJDK said:
Hit Google's Android OTA page, the file and directions are there to ADB sideload it. You will have to reroot and install TWRP if tou want that.
Click to expand...
Click to collapse
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
jreink01 said:
I went to the Google page but all of the links are to 7.1.1 which I am currently on 7.1.2. Plus I am just looking for the security update that just dropped for March.
Click to expand...
Click to collapse
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
TonikJDK said:
Ok, didn't know that.
You are on a different path. You wait on Google for updates. There might be, there might not be. Certainly 7.1.2 will go live and we will all be on the same path and then 7.1.2 will get monthly updates, but when that is we don't know.
So for now you stay where you are, or you flash back to 7.1.1. we can do that without data loss if you want.
Click to expand...
Click to collapse
Yes, I am in the beta program, that's why I am on this version. So, I'm assuming the beta's don't get updates then? I have turned off automatic updates since I'm rooted. Would you recommend I turn that back on or no? If I'm correct, I can't take a OTA since I'm rooted so I was correct in turning off automatic updates then? I will probably stay on this version since the difference is improvement and bug fixes. So, when 7.1.2 rolls out to everyone, then I would assume that that version would show up on the Google page then?
Sent from my Pixel XL using Tapatalk