Develop Bugs

[Q] Trouble with OTA, can't find answer anywhere

Howdy all,
This here is my first post, and I'm pretty new to the android world as I just recently switched from the iphone to the GS3.
I have my phone rooted and had CWM installed, and some of the bloatware apps disabled. I tried to get the latest OTA from ATT and it wouldn't install with CWM. I went back to the stock recovery and re-ran the update. It got about 31% into the update and stopped, restarted, and said the update was interrupted. Then I tried the newest CWM (6. whatever) and that didn't work either. I've also enabled all the bloatware. Lastly, I tried Kies and it says that my phone is up to date even though I know the update was not applied.
I've searched high and low for the answer to this and can't find anything. I'm at the point where, since I'm new to the android scene, I'd like to get my phone back to the factory settings (unrooted and such) but I can't even find clear instructions on how to do that, either.
I'm used to the ease of jailbreaking the iphone, then restoring it via itunes whenever needed, but it seems that it may not be that simple with the GS3.
Any help will be greatly appreciated.
Thank you.

Maybe this thread will help: http://forum.xda-developers.com/showthread.php?t=1896773

Thanks! I'd still like to know how to restore to complete factory.

The ota is failing because of the frozen bloatware. There's a guide I wrote in the general section explaining how to go from rooted stock to rooted ota.

gunnyman said:
The ota is failing because of the frozen bloatware. There's a guide I wrote in the general section explaining how to go from rooted stock to rooted ota.
Click to expand...
Click to collapse
I was able to apply the OTA with bloatware frozen. It will fail if it's been removed, but freezing (through Titianium Backup) didn't break the process for me.

drothenberger said:
I was able to apply the OTA with bloatware frozen. It will fail if it's been removed, but freezing (through Titianium Backup) didn't break the process for me.
Click to expand...
Click to collapse
ahh that's what I did differently. I got rid of it. Thanks

slicetwo said:
Thanks! I'd still like to know how to restore to complete factory.
Click to expand...
Click to collapse
Download the unrooted, completely stock LG1 image from here: http://samsung-updates.com/device/?id=SGH-I747
Flash that with Odin, then boot and install the OTA as normal. In the end, you'll be at LH9 completely stock, with the stock recovery and no root. If that's really what you want.

drothenberger said:
Download the unrooted, completely stock LG1 image from here: [/url]
Flash that with Odin, then boot and install the OTA as normal. In the end, you'll be at LH9 completely stock, with the stock recovery and no root. If that's really what you want.
Click to expand...
Click to collapse
thank you so much. honestly, right now i think i should learn more about android and everything before i start really messing with it. it seems a lot different and, perhaps, more complicated and delicate than just jailbreaking an iphone, and right now, i just want a fully working phone that i don't need to worry about.
i really appreciate your help. thank you.
also, i never had any bloatware frozen except from the disable action in the application manager, it still never worked. thanks to everyone else who replied with some assistance.
UPDATE: I followed your directions, and went to check the ABOUT section of the phone. It still says my kernel is a USER one. My wife's un-messed-with GS3 does not say that. I think I may have missed something.

slicetwo said:
thank you so much. honestly, right now i think i should learn more about android and everything before i start really messing with it. it seems a lot different and, perhaps, more complicated and delicate than just jailbreaking an iphone, and right now, i just want a fully working phone that i don't need to worry about.
i really appreciate your help. thank you.
also, i never had any bloatware frozen except from the disable action in the application manager, it still never worked. thanks to everyone else who replied with some assistance.
UPDATE: I followed your directions, and went to check the ABOUT section of the phone. It still says my kernel is a USER one. My wife's un-messed-with GS3 does not say that. I think I may have missed something.
Click to expand...
Click to collapse
If you want to go back to stock and get update just use Kies.
Open Kies ( do not connect phone yet)
From Tools open Firmware Upgrate and Initalization
In model write exacly w/o quotes " SGH-I747" click OK
then write your Serial Number from under battery all capital letters click ok.
Put phone in download mode ( like for ODIN) click ok.
On next screen you see info about deleting data and if you want to procced. click OK
and connect phone you have in download mode to PC.
Follow instruction
After you get software installed this will look like new phone you get from store. Get update and enjoy.

Exactly what I DIDN'T want to happen....

So I've had the S4 for 1 month now and at first I really didn't want to root or change the ROM. I actually like the TW interface and think it's great as it is. I've been rooting and changing ROMs going back to the MyTouch, but for some reason the S4 had me worried. I debated over and over about doing it, but after getting tired of the bloatware, constant ads being displayed and wanting to stop the horrible startup/shutdown music, the time came for me to root it.
So, after pouring over many hours of reading and deciding the method, I went with the Chainfire route. I chose this because from what I read (and this may have been where I misunderstood something??), if I ONLY root the phone, don't install a custom recovery then I will still be able to receive OTAs (when and IF they come from TMO). So after a couple of heart-stopping moments at 2am last night with about 4 ODIN fails, I finally got it rooted. Turns out, the USB cable I was using might have been the problem. I went out to the car and got the original cable that came with the phone and it worked on the first try with that. I thought for sure I had hard bricked the phone when it came up with an error message at startup regarding a firmware problem.
Anyhow, to make a long story short, after doing the rooting, I checked the update option in settings and it's telling me the phone has been modified and is unable to receive updates. I then ran the triangle away program to reset the binary counter back to Samsung Official/Official, which it's reporting now instead of Custom, but then checking the updater it still reports the same thing. This is what I didn't want to have happen!
Any suggestions on how to rectify this or have I crossed that line and might as well just go ahead and put a recovery on there and do a backup and leave it at that until the day comes I decide to slap a custom ROM on it?
Thanks for letting me rant, but I would like some assistance if possible.

patriot1973 said:
So I've had the S4 for 1 month now and at first I really didn't want to root or change the ROM. I actually like the TW interface and think it's great as it is. I've been rooting and changing ROMs going back to the MyTouch, but for some reason the S4 had me worried. I debated over and over about doing it, but after getting tired of the bloatware, constant ads being displayed and wanting to stop the horrible startup/shutdown music, the time came for me to root it.
So, after pouring over many hours of reading and deciding the method, I went with the Chainfire route. I chose this because from what I read (and this may have been where I misunderstood something??), if I ONLY root the phone, don't install a custom recovery then I will still be able to receive OTAs (when and IF they come from TMO). So after a couple of heart-stopping moments at 2am last night with about 4 ODIN fails, I finally got it rooted. Turns out, the USB cable I was using might have been the problem. I went out to the car and got the original cable that came with the phone and it worked on the first try with that. I thought for sure I had hard bricked the phone when it came up with an error message at startup regarding a firmware problem.
Anyhow, to make a long story short, after doing the rooting, I checked the update option in settings and it's telling me the phone has been modified and is unable to receive updates. I then ran the triangle away program to reset the binary counter back to Samsung Official/Official, which it's reporting now instead of Custom, but then checking the updater it still reports the same thing. This is what I didn't want to have happen!
Any suggestions on how to rectify this or have I crossed that line and might as well just go ahead and put a recovery on there and do a backup and leave it at that until the day comes I decide to slap a custom ROM on it?
Thanks for letting me rant, but I would like some assistance if possible.
Click to expand...
Click to collapse
If you've reset your binary counter and have modified nothing else, just unroot and you should be able to receive updates again.

Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2

jbreeze228 said:
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This. It explains this right in the app.

jbreeze228 said:
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. I went ahead and got SuperSU Pro because that's the only way the feature in Triangle Away will work. It was after 2am when I was rooting and having problems so I wasn't too sharp.
Thanks!

[Q] I messed up...... please have mercy?

Ok so background... I used to alway be android... rooted the works.. used to be really into it... then I got pissed one day at my android after it restarted taking what would have been like a nobel peace prize winning picture from inside a blackhawk... Literally... I almost threw this thing out of the doors from 3000 feet.... so next day i went to iphone. Fast forward 3 or so years...
I got pissed at iphone for sucking and releasing crapy phones without working bugs out. so I decided this time i was going back to android for good....
Two months ago i bought the Samsung Note 4 from sprint through their cut your rate in half plan... ($39/mo for unlimited everything... how could i go wrong?!)...
Took her home and started googling how I was gonna root her and get native hotspot for free.. cuz who pays for that ****... Learned what i needed to know (really refreshed my memory as i have done this in the past...) Flashed myself a new ROM and all was good in the world. Rooted and had my native hotspot.
Well, went to go use private mode and it didn't work. Back to the drawing boards... read a few things read the fine print and the ROM I was using didn't support it. No big deal, just gonna look for one that does... Found one that supports and read the page... well, I decided to do this after working all day and i was sick of being on the computer i just wanted to get it done, clicked the link downloaded the ROM I needed and loaded it.... as soon as it said done I realized... I messed up... I thought i had clicked sm-n910P... I clicked n915p..... quick search shows thats a note edge... so i download the correct one and flash that hoping I didn't **** anything up... WRONG.
Heres the problem.
My touch screen works FLAWLESSLY using the s-pen. perfect response, accuracy.. the works. When i use my finger, it responds.. sort of. The top left of my phone is spot on. as you move down and right, the cursor actually moves FASTER than my finger. So by the time I am 3/4 of the way down and to the right of the screen the cursor is actually already in the bottom right hand corner. Making texting or anything IMPOSSIBLE... now, I'm not a CIS major by ANY means and I avoid technical terms sometimes because I don't FULLY understand what some of it is. That being said, I am a tech savvy person in general, just not so much in the software dept. I'm more of a hardware person...
Question:
Did I mess up the phones HARDWARE.. Like would the digitizer be toasted? i figure that is a one way device so i don't see how that could be the case.. just throwing it out there... or did I fry something else? Anyone have FULLY stock EVERYTHING that i can flash onto this thing... (ROM, Kernel...) I found a stock ROM online to load but it isnt the same one and it didn't fix my problem. No i don't have a back up and yes i know shame on me...
Deets:
SM-N910P
Software Version: n910PVPU1BOB7 - last ROM i loaded hoping to fix the problem....
Hardware Version: N910P.05
Andriod: 5.0.1
Kernel Version: 3.10.40-4243283
[email protected] #1
Build Number: LRX22C.N910PVPU1BOB7
Knox is already tripped so IDC about that...
My recovery manager is back to stock. Tried CWM and i'm not sure if that is what screwed me... i did that and my ROM all at the same time i guess... help?
MOD EDIT POST AND TITLE

Use twrp 2.85 for recovery. It's better for me. Read up on how to Odin the stock tar. Should fix it up. Be sure to do a full wipe of everything not on your xternal SD before odining.

galland1 said:
Use twrp 2.85 for recovery. It's better for me. Read up on how to Odin the stock tar. Should fix it up. Be sure to do a full wipe of everything not on your xternal SD before odining.
Click to expand...
Click to collapse
i used Odin to push a stock .tar ... didn't fix it.. thats when i started panicking and started looking for other ROMS

Did you wipe internal before you Odin'd?

galland1 said:
Did you wipe internal before you Odin'd?
Click to expand...
Click to collapse
I followed the little instructions from the .tar
if by "wipe everything" you mean clearing the cache and doing a factory reset yes.

My advise would be to back up everything with titanium backup to your external card, and start from scratch. If you are on 4.4 right now, download a program called SPCUtility to get your msl number. Load a stock tar, either nk2 if you want 4.4 or bob7 if you want lollipop (my recommendation). Once you load the stock tar with odin, reset the who device by going into your dialer and dial ##786#. It will ask for your msl number and ask if you want to reset. Say yes, and you should be good to go. At this point, when you phone restarts, get to the home screen and see if everything is working. If it is not, take the phone to sprint and let them fix it or replace it. If everything is working, you can root the device, and if you want to load a new rom, you can.

dschachm said:
My advise would be to back up everything with titanium backup to your external card, and start from scratch. If you are on 4.4 right now, download a program called SPCUtility to get your msl number. Load a stock tar, either nk2 if you want 4.4 or bob7 if you want lollipop (my recommendation). Once you load the stock tar with odin, reset the who device by going into your dialer and dial ##786#. It will ask for your msl number and ask if you want to reset. Say yes, and you should be good to go. At this point, when you phone restarts, get to the home screen and see if everything is working. If it is not, take the phone to sprint and let them fix it or replace it. If everything is working, you can root the device, and if you want to load a new rom, you can.
Click to expand...
Click to collapse
There is literally nothing on the phone right now. i don't care if anything is backed up... the phone was bascially stock to begin with and i have my contacts and everything saved through kies. im on 5.0 i guess technically... can i still get my MSL?
I would have to Root my phone again, load the SPCUtility, get my MSL flash the stock .tar (any idea where i can get a better one? the one i have isn't the stock i knew)... then follow the rest of this?
BTW thank you SO much for helping me out. I appreciate it. A LOT.

bsil12 said:
There is literally nothing on the phone right now. i don't care if anything is backed up... the phone was bascially stock to begin with and i have my contacts and everything saved through kies. im on 5.0 i guess technically... can i still get my MSL?
I would have to Root my phone again, load the SPCUtility, get my MSL flash the stock .tar (any idea where i can get a better one? the one i have isn't the stock i knew)... then follow the rest of this?
BTW thank you SO much for helping me out. I appreciate it. A LOT.
Click to expand...
Click to collapse
The only way to get the msl number is to call sprint but if you just got the phone they probably won't give it to you. So the other option is to flash this stock tar to go back to 4.4. Here is the tar file for nk2 and bob7.
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go back to nk2, root and intall SPCutility and get your msl. Then flash bob7, and then use the msl number and ##768# and reset the device.

dschachm said:
The only way to get the msl number is to call sprint but if you just got the phone they probably won't give it to you. So the other option is to flash this stock tar to go back to 4.4. Here is the tar file for nk2 and bob7.
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go back to nk2, root and intall SPCutility and get your msl. Then flash bob7, and then use the msl number and ##768# and reset the device.
Click to expand...
Click to collapse
You sir, are a god of sorts. I will try this when i get home. I can't download anything on my work computer or i'd do it right now. THANK YOU! I'll keep you posted.

I will pm you my email address. If you have any questions email me and i can respond faster.

[Q] Factory reset in CM12 now stuck in recovery boot loop

So I'm just getting into the whole ROM thing and I'm pretty sure I've messed up here. I encountered a problem after installing CyanogenMod 12 Unofficial (trltespr NIGHTLY) where I could receive text messages but not send them. I could still load pages and apps over lte and call people but I couldnt send messages. I gave up with the idea of finding a solution after browsing forums and decided to preform a factory reset through settings. The phone was rooted but not after I installed the rom. after rebooting it went into recovery mode and began to loop showing the Team Win screen then going black only to do it again. I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.

diehlkj said:
I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.

xxSTARBUCKSxx said:
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.
Click to expand...
Click to collapse
I went and followed the instructions and odin said it failed due to auth. Any other ideas?

diehlkj said:
I went and followed the instructions and odin said it failed due to auth. Any other ideas?
Click to expand...
Click to collapse
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.

xxSTARBUCKSxx said:
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.
Click to expand...
Click to collapse
Is there any way I can remove or reinstall/repair TWRP so i can properly wipe the system or just get another rom working?

Solved
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP

diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Then you can flash notarize rom per that threads first post... Until an updated tar that will work in Odin.
http://forum.xda-developers.com/showthread.php?p=60506568

diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Yep, the trend seems to be pointing to CF Auto Root after trying to flash stock tar over OE1 build. Although I'm thinking the stock recovery is from way back unless CF updates his build.
About the text sending issue, did you apply the fix found in link below? Check under the spoiler.
http://forum.xda-developers.com/showthread.php?p=57613217
If you want to get back to TW, Noterized is a good OP option. (As mentioned above)
Sent from my SM-N910P using Tapatalk

*Help* I unrooted on a rom and now I can't root my phone.

Device: LG G3
Rom: [AOSP EXTENDED V3.0] [LG G3 - D855] [OFFICIAL] [NOUGAT R9] [by MARCHETTO96]
Hey again,
So i'm running this rom right and I was reinstalling my apps onto my phone and one app I need to log into but it noticed it was running root (Snapchat). So I followed someones advice on here on XDA to fully unroot the device and I did that I fully unrooted the app from the phone and then here comes the worst part that I realized this will kick me out of recovery and i wont be able to get back in because I need to get on to recovery to re install superSU back on. So im stranded on nougat 7.1 and dont have access to root at all except for root access on developer settings but that doesn't nothing at all I re installed the app on play store but its telling me the phone is unrooted of course.
Anyone can help me out here. It would be greatly appreciated .
P.S I did get snapchat working after that method kinda did work/backfire at the same time.

Do you have nandroid backup? If yes, flash that. It will be all well.
Other hard method is to downgrade to KitKat and then root and then TWRP. ?

I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.

HunterTubeHD said:
I do not have a back up for this ROM but I have other back ups on my phone that still works. I can't do it as well cause I neeed root to l get it to work.
Click to expand...
Click to collapse
Backups don't need root. They need TWRP to be flashed.

Jahanzaibawan said:
Backups don't need root. They need TWRP to be flashed.
Click to expand...
Click to collapse
Yeah thats the only thing I can't get access to TWRP. When I fully unrooted It would not let me in my recovery at all just bootloops until i take the battery out then it reboots to the system fine.

Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?

pffcouk said:
Just going to ask a hopefully obvious question that I know doesn't help but I'm intrigued... Why didn't you just unroot using the supersu app?
Click to expand...
Click to collapse
I did do that....now my main problem is I don't have root anymore and I can't get access to my recovery and plus I'm running an Nougat rom so I need to find a way to re-root my phone again to get it all back.

The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed

pffcouk said:
The supersu app doesn't delete the recovery on your phone so something had to have gone wrong. Either way the best bet for you I would imagine anyway would be to follow a guide to install recovery - it's been that long since I had to do it I can't be of much help but I'm willing to look into the easiest options for you if you want. There will be a way, pretty much guaranteed
Click to expand...
Click to collapse
I know that my recovery is still there but It wont allow me on there for some reason. But im thinking that If I factory reset the phone it would PROBABLY fix the problem but theres one risk that it could probably happen and im guessing that it will go straight into a bootloop. If you want to help me It would be great

I'll research for you mate!

Did you modify your ro.product.model in build.prop file and when supersu app asks if you want to flash stock recovery you pressed yes?
For example if you have enabled google assistant by changing your ro.product.model to pixel or pixel xl and after that unrooted and pressed yes to restore stock recovery (to get OTA to work), supersu flashes pixel recovery and thats why you can't get to recovey again.
There are ways to get your phone back to factory clean and start over.

Okay I have spent a whole day figuring out this problem but i finally managed to fix it.
So I went onto download mode
opened up LG Flash Tool 2014
Flashed an LG KDZ File managed to work after the 2nd time
10 or 15 mins later it finally worked
LG started to boot up and started loading in the apps
THEN
I rooted the phone again using this forum: https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268
Then I finally got back onto the glorious TWRP rom.
I re-installed the ASOP rom again.

I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton

HunterTubeHD said:
I'd Like to thank Juhkimo, Jahanzaibawan and pffcouk for helping me out. You guys got my phone back to what it was before so thanks a ton
Click to expand...
Click to collapse
Really good to hear that :highfive: