I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Related
I was waiting to root my continuum until I got the new upgrade, which I expected months ago. Anyway I got the upgrade (froyo 2.2) and everything works great. I would like to root the phone, so I can tether it to my laptop.
I have seen older videos for other phones, but I was not sure they would work for the continuum, or if there is a newer easier way, as I am not tech savvy. I just want to work on my laptop as I run my kids to their after school activities.
Finally, which app works best for turning the phone into a hotspot.
Thanks in advance
The easiest way is to find superoneclick 2.3.3 That roots, nothing else.
The slightly more complicated way, is to flash a rooted version in Odin. And there are tutorials all over. You can also swing into IRC, and we can get ya going.
webchat.freenode.net
#samsung-continuum
Or....manual root
Sent from my SCH-I400 using Tapatalk
rooting problem
I was originally having problems tethering, but I figured it out. Too bad there is not an option for deleting posts, but I am excited that I can now tether.
abby_nitewolf said:
Or....manual root
Sent from my SCH-I400 using Tapatalk
Click to expand...
Click to collapse
How is that done? I've dabled with Linux on my PC so I'm familiar enough to be dangerous, but this question has been bugging me for a while now.
LGartrell said:
How is that done? I've dabled with Linux on my PC so I'm familiar enough to be dangerous, but this question has been bugging me for a while now.
Click to expand...
Click to collapse
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adbreboot
There you go, you need a few files:
psneuter
su
busybox
Superuser.apk
Adb
But its easier and faster with SuperOneClick,
Sent from my SCH-I400 using Tapatalk
The kernel I included with the CWM recovery file will install the su binary for you. Get busybox and then install Superuser from the market and you'll be rooted.
Sent from my Galaxy Nexus
imnuts said:
The kernel I included with the CWM recovery file will install the such binary for you. Get busybox and then install Superuser from the market and you'll be rooted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks. I've been playing with my Continuum now for several months with everyone's mods. Love the work you're all doing!
Question about installing ClockworkMod Recovery on Continuum.
Hi,
I am trying to figure out which version of CWM recovery is the appropriate, and most recent one for the continuum.
Can anyone point me to the correct file for the Samsung Continuum SCH-i-400.
Also, after I root the phone, how do I install CWM. Should I use a ROM manager, or do it manually?
Someone please help.
Thank you!!
You should try reading through the forums. I believe there is a thread that will have all necessary files.
Sent from my SCH-I400 using XDA
I used imnuts froyo rom.flashed with no problem.its not 100% stable,but it got the job done.
Sent from my SCH-I400 using Xparent ICS Blue Tapatalk 2
I figured I'd post in this thread instead of making a new one since it seems to be a similar issue. I rooted my phone ages ago right when I got it using the super one click program. Everything was working fine as far as I could tell, until I had a app on my phone tell me that it wasn't in fact rooted. I assume it was because my phone updated to 2.2.2 by it self one evening causing me to lose root. I checked with a few other apps that used to work fine (Titatium Back being one of them) which also told me my phone wasn't rooted.
I downloaded the newest version of SuperOneClick (2.3.3) and tried to re-root my phone. The program said my phone was already rooted and asked if I wanted to continue. I clicked no and then tried the 'Unroot' option. The program hung up and stopped responding so I did a factory reset and tried again. When I tried to root it again the program still said my phone was rooted and Superuser was still in my app list with no option to uninstall. I went to the market to try and uninstall that way but there wasn't an option either. I tried the un-root option again and SOC still would ended up not responding at a certain point (Installing BusyBox Step 2).
I pulled my battery and just tried to root again, it gets to the point of installing Superuser and freezes. I tried downloading an uninstall root app which didn't even show superuser. I also downloaded root explorer and tried to delete the superuser.apk from the system/apps folder and it failed to DL.
I am at a loss for what to do and would really appreciate any help in getting my phone rooted. I am in USB debugging and never installed any ROMS or anything previously. If there is any other information that would help troubleshooting this please let me know.
Vsoup25 said:
I figured I'd post in this thread instead of making a new one since it seems to be a similar issue. I rooted my phone ages ago right when I got it using the super one click program. Everything was working fine as far as I could tell, until I had a app on my phone tell me that it wasn't in fact rooted. I assume it was because my phone updated to 2.2.2 by it self one evening causing me to lose root. I checked with a few other apps that used to work fine (Titatium Back being one of them) which also told me my phone wasn't rooted.
I downloaded the newest version of SuperOneClick (2.3.3) and tried to re-root my phone. The program said my phone was already rooted and asked if I wanted to continue. I clicked no and then tried the 'Unroot' option. The program hung up and stopped responding so I did a factory reset and tried again. When I tried to root it again the program still said my phone was rooted and Superuser was still in my app list with no option to uninstall. I went to the market to try and uninstall that way but there wasn't an option either. I tried the un-root option again and SOC still would ended up not responding at a certain point (Installing BusyBox Step 2).
I pulled my battery and just tried to root again, it gets to the point of installing Superuser and freezes. I tried downloading an uninstall root app which didn't even show superuser. I also downloaded root explorer and tried to delete the superuser.apk from the system/apps folder and it failed to DL.
I am at a loss for what to do and would really appreciate any help in getting my phone rooted. I am in USB debugging and never installed any ROMS or anything previously. If there is any other information that would help troubleshooting this please let me know.
Click to expand...
Click to collapse
Here's the problem. SOC see's the superuser.apk in your app drawer, so it thinks you are still rooted. You aren't because you no longer have the su.bin (which is the reason none of the apps you have - including the 'unroot' app will work.). The fix for this is easy. When SOC says 'you are already rooted, would you like to root again', or whatever that message is, click yes. The worst thing that will happen is it will overwrite existing files with the same one (Have you ever opened a word document, and when you close it, it asks if you want to save, even though you haven't made any changes? Same thing). In this case, the files you need (su.bin and busybox) AREN'T there. So you don't even overwrite anything.
For the most part, rooting this phone is a pretty failsafe, and innocuous process. You can do it over and over again, and you won't hurt the phone in the slightest.
Txwolf1980 said:
Here's the problem. SOC see's the superuser.apk in your app drawer, so it thinks you are still rooted. You aren't because you no longer have the su.bin (which is the reason none of the apps you have - including the 'unroot' app will work.). The fix for this is easy. When SOC says 'you are already rooted, would you like to root again', or whatever that message is, click yes. The worst thing that will happen is it will overwrite existing files with the same one (Have you ever opened a word document, and when you close it, it asks if you want to save, even though you haven't made any changes? Same thing). In this case, the files you need (su.bin and busybox) AREN'T there. So you don't even overwrite anything.
For the most part, rooting this phone is a pretty failsafe, and innocuous process. You can do it over and over again, and you won't hurt the phone in the slightest.
Click to expand...
Click to collapse
Are there any other programs to use than SOC? When the dialog window pops up saying my phone is rooted I click yes, it goes through the process until it tries to install SuperUser. Once it get to that point it just freezes and is flagged as not responding by windows. Is there anything I should double check settings wise on my phone other than USB Debugging that could be causing the problem?
Vsoup25 said:
Are there any other programs to use than SOC? When the dialog window pops up saying my phone is rooted I click yes, it goes through the process until it tries to install SuperUser. Once it get to that point it just freezes and is flagged as not responding by windows. Is there anything I should double check settings wise on my phone other than USB Debugging that could be causing the problem?
Click to expand...
Click to collapse
As far as straight rooting programs, soc is the only one I know of that works. You said a factory reset didn't remove superuser from your app drawer? It should have. I spills try a factory reset in recovery, as opposed to the privacy section of settings.
The other option is to flash a pre rooted rom. A little more dangerous, if you don't know what you are doing, but gaurunteed to work. I have a territorial in this section that seems to with for everyone that's tried it. Our, if you want I can meet you in irc tomorrow evening, and we can look at it.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
As far as straight rooting programs, soc is the only one I know of that works. You said a factory reset didn't remove superuser from your app drawer? It should have. I spills try a factory reset in recovery, as opposed to the privacy section of settings.
The other option is to flash a pre rooted rom. A little more dangerous, if you don't know what you are doing, but gaurunteed to work. I have a territorial in this section that seems to with for everyone that's tried it. Our, if you want I can meet you in irc tomorrow evening, and we can look at it.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
That's why I'm getting frustrated, after two factory resets through the privacy menu superuser is still in my app drawer. I think because it's flagged as a system file it isn't really touched when the phone restores it self. Are there any programs that would give me root folder access through my PC?
I really don't know much about doing anything with these phones, so I'd be a bit apprehensive about flashing new ROMs or anything that could brick my phone if I mess up. How can I reset it through the recovery menu? That at least sounds like something has a low chance of causing any irreparable damage.
I'm not sure if I think I'll be around later this evening, I'm on the east coast and don't think I'll be available until after 9pm.
Vsoup25 said:
That's why I'm getting frustrated, after two factory resets through the privacy menu superuser is still in my app drawer. I think because it's flagged as a system file it isn't really touched when the phone restores it self. Are there any programs that would give me root folder access through my PC?
I really don't know much about doing anything with these phones, so I'd be a bit apprehensive about flashing new ROMs or anything that could brick my phone if I mess up. How can I reset it through the recovery menu? That at least sounds like something has a low chance of causing any irreparable damage.
I'm not sure if I think I'll be around later this evening, I'm on the east coast and don't think I'll be available until after 9pm.
Click to expand...
Click to collapse
To reset in recovery, power down completely. Then hold the vol up, vol down, and power at the same time, until samsung logo comes up. It will color you into stock recovery (3e)
Using volume down to scroll, and camera button to select, choose wipe data/factory reset.
Next, scroll to yes, and select. Not sure if that will work to get rid of super user, but it's worth a shot.
If that direct with, let new knits, and I'll walk you through flashing a custom recovery, then a deodexed rom, if you'd like.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
To reset in recovery, power down completely. Then hold the vol up, vol down, and power at the same time, until samsung logo comes up. It will color you into stock recovery (3e)
Using volume down to scroll, and camera button to select, choose wipe data/factory reset.
Next, scroll to yes, and select. Not sure if that will work to get rid of super user, but it's worth a shot.
If that direct with, let new knits, and I'll walk you through flashing a custom recovery, then a deodexed rom, if you'd like.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
I tried the wipe from the recovery menu to no luck, superuser is still in my app drawer. I'll probably have time tomorrow afternoon to jump on IRC. I really appreciate all your help so far, thank you.
Vsoup25 said:
I tried the wipe from the recovery menu to no luck, superuser is still in my app drawer. I'll probably have time tomorrow afternoon to jump on IRC. I really appreciate all your help so far, thank you.
Click to expand...
Click to collapse
I'll be around. Just pm me, when you know what time you will be on
Sent from my SCH-I400 using Tapatalk 2
I got the ota the other day and debated installing it because my M is rooted and the bootloader is unlocked and I have flashed ClockworkMod recovery. I searched for a while to see what others were saying and didn't really find anything of note so I decided to go ahead and run the install. When the phone rebooted into recovery and tried to install the update, it gave me the following Error: E: Failed to verify whole-file signature. Then there was an option to apply unsigned update (or zip, I can't remember the wording exactly). I chose not to do this and went back in the recovery menu and rebooted back into system. The phone booted normally and then immediately rebooted on its own back into recovery to try to install the update again, ending in the same results. This happened 2-3 more times before I finally formatted the Cache Partition through cwm which ended the bootloop (not sure that you can really describe that as a bootloop since it was actually doing what it thought it should be). My question is this, is it safe to go ahead and install the unsigned update via CWM? I have also since seen threads stating that if you had removed some of the bloatware apps, that the update would fail. I have removed many of these unneeded apps, should I reinstall them? I have seen a link or two to the bloat apks...
Having a unlocked bootloader doesn't matter. You just need to be stock 4.1.1 bloatware and all.
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
bobcheeks said:
Do you have to unroot first to get it to install? I have TWRP recovery on mine and can't get the update to install.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No. You don't have to unroot. You must have modified something else.
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
what he said^
you can update it with cwm but you have to have all the crapware that came stock still present.
Click to expand...
Click to collapse
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
bwat1009 said:
So if I restore the bloatware, it is ok to choose the "install unsigned zip"?
Thanks for the quick reply, you guys rock!
Click to expand...
Click to collapse
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
antp121 said:
If its all there, yep. It'll be fine
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
I RSDed back to 4.1.1 because mine hung on the clock app. I had installed the 4.2 clock.
bwat1009 said:
Well I tried it and it failed the check for the Amazon MP3 app. I reinstalled it from the play store but according to another post I found later this doesn't work because it isn't installed to the /system/app directory. The only way around this that I have seen is to use the RAZR M utility to return back to out of box status and start over. Not worth it to me but if anyone has another idea, I am all ears...
Click to expand...
Click to collapse
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
sloosecannon said:
You could try grabbing the apk from /data/app and moving it to /system...
Or grab it from one of the many /system dumps around here...
Someone should turn the OTA into a flashable zip from CWM/TWRP that doesn't check for that.
I may do that...
Click to expand...
Click to collapse
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
bwat1009 said:
I had the same thought about moving the apk to the system/app directory and did just that. My expectation was that I would still get the error but for a different app since I just tested with the one that had been throwing the error but it didn't change, still gave the error for the amazon mp3 app even though it was successfully installed in the correct directory. Thanks for the thought though. If you could turn it into a flashable zip, I would be much appreciated. I would love to do that myself but I have no idea how. I know just enough through trial and error (and a lot of forum reading) to be dangerous...
Click to expand...
Click to collapse
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Alright, thanks for the tip and the link, I will give it a try and let you know...
tehjolly81 said:
After installing 4.1.2, I can no longer fastboot back to 4.1.1 or 4.0.6. They put in some sort of backrev check.
Click to expand...
Click to collapse
I'm pretty sure you need an unlocked boot loader to downgrade.
netizenmt said:
Have you tried using mattlGroff's DROID RAZR M Utility? Worked for me.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
I did. It fixed an issue where my phone wasn't booting, but it did not revert me to 4.1.1. Just found your comment in the other thread about modifying the xml file.. I'll try that next. Thanks.
patehi nice
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
That worked at getting the system apps that I had removed back into the /syste/app directory and now the update appears to be installing... Will let you know if it works.
*UPDATE*
Well that worked like a charm, update installed successfully, root access maintained, cwm allowed me to prevent reflash of stock recovery so all is right with the world... Thanks you guys!
Snow02 said:
There is a 4.1.1 system dump here. Download it, transfer any missing apps in /system/app over to your phone.
The reason you have to have those is that the current one from the playstore will be different, causing the update check to fail and abort.
Click to expand...
Click to collapse
Thank you! I had missing Amazon_IMDb.apk, Facebook.apk, Kindle.apk, PlusOne.apk files. Copied these to my phone and updated successfully!
Today I had to restart my phone because it dropped data connection, the moment I restarted it said my phone was being updated and I should wait, it wasted my time and it shoved 10o update down my throat.
If I had recovery installed, this could have been disastrous, no?
Not only for recovery related problems, but this may also prevent people from being able to install certain things, or even one day in the future with a different update just block root?
How do we uninstall then disable OTA updates on an unrooted phone? When I disabled and cancelled notifications for Software Update app, I thought it was fixed, but it probably made it worse, it just installed without any notification or prompt.
I was planning to root and install twrp this weekend, now with all the horror stories I've been reading, I don't want to do it. :crying:
How is AT&T even allowed to push it without explicit permit to install on device.
hydeah said:
Today I had to restart my phone because it dropped data connection, the moment I restarted it said my phone was being updated and I should wait, it wasted my time and it shoved 10o update down my throat.
If I had recovery installed, this could have been disastrous, no?
Not only for recovery related problems, but this may also prevent people from being able to install certain things, or even one day in the future with a different update just block root?
How do we uninstall then disable OTA updates on an unrooted phone? When I disabled and cancelled notifications for Software Update app, I thought it was fixed, but it probably made it worse, it just installed without any notification or prompt.
I was planning to root and install twrp this weekend, now with all the horror stories I've been reading, I don't want to do it. :crying:
How is AT&T even allowed to push it without explicit permit to install on device.
Click to expand...
Click to collapse
Pull down the notification bar and tap and hold on the notification. App info will pop up and tap it and scroll all the way to the bottom and uncheck show notification.
Sent from my LG-LS980 using Tapatalk
oldpreowner said:
Pull down the notification bar and tap and hold on the notification. App info will pop up and tap it and scroll all the way to the bottom and uncheck show notification.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I did that when I first got the notification. Notification disappeared. 2 days later I restarted my phone for the first time in over a week, and bam, it installed without any notification at all. So disabling notification won't stop it from installing, it seems..
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
hydeah said:
I did that when I first got the notification. Notification disappeared. 2 days later I restarted my phone for the first time in over a week, and bam, it installed without any notification at all. So disabling notification won't stop it from installing, it seems..
Click to expand...
Click to collapse
If you have the ota, you could use root explorer or browser to go into the Cache folder and delete it(ota) then try to install it will fail or do nothing then hit cancel
How can I downgrade?
I don't mind paying for titanium to freeze the app. This is nonsense, enjoyment just update by itself, lucky I didn't install recovery.
Sent from my LG-D800
nybmx said:
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
Click to expand...
Click to collapse
What version of the G2 do you have? I'm on Sprint and I don't have "Software Update", I have "Update Device 4.5.1.10" which I just froze.
Does anyone know if I install the update can I still flash TWRP to my device? I'm not sure if I should install TWRP now and use the flashable ota zip or install it after I update it.
nybmx said:
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
Click to expand...
Click to collapse
I don't have tibu pro.. I went in to system/app and deleted LGDMSClient.apk.
Sent from my LG-D800
I'm asking the same question OP is asking, is there a way to disable the update on non-rooted phones? And from experience with several other Android phones... I know it's pretty much impossible to downgrade unless you start flashing, but I'm gonna ask anyways. Is there a way to downgrade the upgrade that was forced down OP's throat and my own throat? For me it actually updated in my sleep, I woke up and it said my phone was updated. OP and I are on AT&T's D800 variant.
btm fdr said:
I don't have tibu pro.. I went in to system/app and deleted LGDMSClient.apk.
Sent from my LG-D800
Click to expand...
Click to collapse
On Verizon it is called MobileUpdateClient.apk. I changed the file extension to .old and then moved it to a new folder called old so I would know what I had changed.
Sent from my VS980 4G using xda app-developers app
zzandrewst said:
On Verizon it is called MobileUpdateClient.apk. I changed the file extension to .old and then moved it to a new folder called old so I would know what I had changed.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Does anyone know the name of the file for T-Mobile? I can't find any of the names listed in this thread.
Thanks
What do I disable on Sprint?
Sent from my LG-LS980 using xda app-developers app
zzandrewst said:
On Verizon it is called MobileUpdateClient.apk. I changed the file extension to .old and then moved it to a new folder called old so I would know what I had changed.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Looks like this worked for me also of my Verizon phone. It seems to have also remove the manual check option in the About phone section in settings.
nybmx said:
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
Click to expand...
Click to collapse
Well, it would still help to avoid further OTA's from being applied if we are rooted and do not use custom rom, there is always a risk of getting OTA and messing everything up, therefore if freezing above app worked for you, it should be all we need. Is Software Update the actual app which checks for version and receives pushes from AT&T when a new OTA is available, or if there are other apps/modules that does this. The problem is, if it is incorporated into android system like some of the other stuff AT&T incorporated, it would be impossible to completely eliminate it without running a custom rom.
RubbleTea said:
If you have the ota, you could use root explorer or browser to go into the Cache folder and delete it(ota) then try to install it will fail or do nothing then hit cancel
Click to expand...
Click to collapse
Awesome the above instructions worked great! Thank you very much brother
disable ota on at&t
Did you totally remove the apk, or rename it? Also, if removed, will it cause other problems?
I only ask cause i had a g2 that was pushed an ota and bricked my g2. Had to get a new one, now trying ti disable the ota's from doing that again..
Then when kitkat is released, am i not able to update it, then root again?
btm fdr said:
I don't have tibu pro.. I went in to system/app and deleted LGDMSClient.apk.
Sent from my LG-D800
Click to expand...
Click to collapse
Att
I have Lg G2 (Att) & hours b4 I have reflash'd back 2 stock and applied root about an hour later i got OTA so I click'd 2 recieve OTA it came back sayin Cant download OTA on rooted device if that helps and thatt was almost 24\hrs ago n still runnin smoothly but file was only like 16MB
So will a bigger OTA push current root'd stock rom out n brick my fone¿
this seems to work for G Flex users.. worth a shot on G2
http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3
hydeah said:
How can I downgrade?
I don't mind paying for titanium to freeze the app. This is nonsense, enjoyment just update by itself, lucky I didn't install recovery.
Sent from my LG-D800
Click to expand...
Click to collapse
you have to flash the old version by using LG Flash Tool, like I did.
So, I have a question for you guys. I got my phone yesterday and I'm on 10o. I installed the CWM recovery for 10o via Flashify, and now I'm concerned about OTAs - I disabled it via the Hidden Menu, but if there's an OTA to update the phone to 4.3 or 4.4, I'd like to receive it and not worry about bricking my phone.
I don't plan on doing a lot of custom ROM flashing, I really just wanted to root and install Xposed. Do I need to flash a stock ROM and go back to stock recovery, so I don't have to worry about OTAs? Or should I be good with CWM and the stock ROM that I rooted?
i have a sprint Samsung gs4 on mk2 that i have just rooted and the hotspot mod on. the update symbol is in the notification bar and says tap to install. my question is can i install it being rooted or what do i do ? sorry for the noob questions.
13jkilgo said:
i have a sprint Samsung gs4 on mk2 that i have just rooted and the hotspot mod on. the update symbol is in the notification bar and says tap to install. my question is can i install it being rooted or what do i do ? sorry for the noob questions.
Click to expand...
Click to collapse
You have to unroot. Follow this guide to get the ball rolling: http://forum.xda-developers.com/showthread.php?t=2509605
13jkilgo said:
i have a sprint Samsung gs4 on mk2 that i have just rooted and the hotspot mod on. the update symbol is in the notification bar and says tap to install. my question is can i install it being rooted or what do i do ? sorry for the noob questions.
Click to expand...
Click to collapse
Or go download a NAE rom and install it, or there is a thread that people have posted their Nandroid backups of the full rom to keep your root.
Darnell0216 said:
You have to unroot. Follow this guide to get the ball rolling: http://forum.xda-developers.com/showthread.php?t=2509605
Click to expand...
Click to collapse
Not quite true. You CAN install an OTA if you are rooted, though you WILL lose root and so have to re-root afterwards. Yes, the OTA MAY fail, that's true, but that's usually only the case if you're running an older version of SuperSU that had an issue that's since been fixed.
The trick that messes people up and will cause a failure (though almost definitely not a bricked phone) is you can't have actually made any changes to system files in any way. That obviously means you can't have edited any system files, used any tweaks or mods, etc. It ALSO means you can't have disabled apps using something like Titantium... if you can't disable an app via the standard system app manager but you do through Titantium then that will cause the OTA to fail.
I know this all because I've installed the last three OTAs with root with no issues, but I'm very careful about all of the above because I was burned a few times in the past until I learned
fzammetti said:
Not quite true. You CAN install an OTA if you are rooted, though you WILL lose root and so have to re-root afterwards. Yes, the OTA MAY fail, that's true, but that's usually only the case if you're running an older version of SuperSU that had an issue that's since been fixed.
The trick that messes people up and will cause a failure (though almost definitely not a bricked phone) is you can't have actually made any changes to system files in any way. That obviously means you can't have edited any system files, used any tweaks or mods, etc. It ALSO means you can't have disabled apps using something like Titantium... if you can't disable an app via the standard system app manager but you do through Titantium then that will cause the OTA to fail.
I know this all because I've installed the last three OTAs with root with no issues, but I'm very careful about all of the above because I was burned a few times in the past until I learned
Click to expand...
Click to collapse
so saying that i could update just by hitting install because i left the original files i the framework and just made them a bak file which i can go back and remove the mod files and delete the .bak and i should be able to hit install correct? and is there already root and hotspot mod avaliable for kitkat?
Well I unrooted through supersu n then updated n I put the nae hotspot mod into the framework n backed up the old file by .bak n restarted n the wifi nor the hotshot work ?? N I undid the mod n put the stock back n they still don't work so I unrooted again n they both still don't work
Sent from my SPH-L720 using xda app-developers app
Yes it is go to the development section and look.
Sent from my SPH-L720 using Tapatalk
INFO: Rooted Version of NB4, I was on 4.4.2 Kit Kat leaked. I reverted to MJ5 from the leaked version then updated to NB4 and rooted with kingo.
Thanks to...
@smokeystack76
@Otisrhw
@Jakman85
@Azrael.arach
@Budrweber
UPDATE: 3/30/14
The same method has been confirmed by @Budrweber but instead of using adb, just flash from your ext sd card.
NOTE: ADB SIDELOAD WILL NOT CAUSE A WIPE, BUT PUSHING THE UPDATE FROM EXTERNAL SD WILL WIPE ALL DATA.
Few users have reported unrooting on NB4 after changing files and downloading the OTA and updating normally.
USB DEBUGGING MUST BE ENABLED, if you are this far there is no need for me to explain how to turn it on. If your phone is unresponsive to your computer even though you have installed, re-install via Kies 3. Turn Kies 3 off before running ADB.
First of all, you are going to need an ADB Sideloader and it can be found here.
Install to directory C:\Mini-SDK
We'll come back to ADB later.
Now you're going to need the update file found here.
Rename the file to update. (DO NOT NAME UPDATE.ZIP, JUST "UPDATE".)
Place "UPDATE" into the same directory as your ADB C:\Mini-SDK
Now lets leave ADB and the Update file alone and start replacing the files on your phone!
You'll need the following files.
system/xbin/dexdump (if deleted you can find the file here or you can copy/paste & replace)
system/csc/feature.xml (If deleted find it here.
Delete the original "feature.xml" and rename "feature.xml.bak" to "feature.xml")
Download the fix.zip from this page.
You do not have to reset permissions, I did not how ever do as you feel and works for you.
Step 1 copy the mobicore-presetup.sh to /system/bin
Step 2 copy all the APK files to /system/app.
Now navigate to system/bin
You should have a "ddexe" file, if it is named "ddexe_real", rename it to 'ddexe".
This should fix all the known errors in the process of adb side loading.
If you continue to get more errors use the file dump located here.
UPDATE: app_process is another recurring error, please grab this file from the dump uploaded from @smokeystack76
Now to the fun and most anticipated part of the day...
Volume + button up, power and home button all at the same time. Release once you see Recovery mode.
Navigate to Update from ADB.
Plug up to USB.
Now, when you start windows cmd prompt, you can either start from the ADB folder is located in by control, shift + right clicking or manual cmd.exe in "run" or "search"
Once command prompt is loaded,
Type in the following command.
"CD /D C:/MINI-SDK"
Then if you are in the right directory and you placed the "update" file accordingly... type...
ADB SIDELOAD UPDATE.ZIP(the file name should not have .zip or you will get a "can not read" message.)
and now you should be on your way to 4.4.2 Kit Kat.
Not bad. The system dump is here.
Now you need to post links to this thread in the other thread
Thanks for the step by step. I'll try this tomorrow.
You were on a rooted NB4, correct? You restored to MJ5, updated to NB4, rooted, and then did this?
clownfart said:
Thanks for the step by step. I'll try this tomorrow.
You were on a rooted NB4, correct? You restored to MJ5, updated to NB4, rooted, and then did this?
Click to expand...
Click to collapse
Correct.
For anyone trying to find an easy way around this whole update mess. Just go to your local best buy store and talk to one of the Samsung reps. They don't have the kit kat update yet but however they can reflash 4.3 on your phone wiping out all your data (make sure you do a back up from home) and this will let you get the OTA update with no problems. My note 3 has been rooted twice one being last night and it worked. Just make sure your not rooted when you take your phone.
Ciberious42 said:
Correct.
Click to expand...
Click to collapse
I think you should mention that in the OP for perfect clarity.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
incisivekeith said:
I think you should mention that in the OP for perfect clarity.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I did actually...
Ciberious42 said:
I did actually...
Click to expand...
Click to collapse
I didn't see in the OP that you rooted the NB4.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
incisivekeith said:
I didn't see in the OP that you rooted the NB4.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU
smokestack76 said:
Not bad. The system dump is here.
Now you need to post links to this thread in the other thread
Click to expand...
Click to collapse
How do I flash this?
xuanphucn said:
How do I flash this?
Click to expand...
Click to collapse
you don't, it is used by DEV's to make a flashable update
carl1961 said:
you don't, it is used by DEV's to make a flashable update
Click to expand...
Click to collapse
Did we have any safe method yet? I want to keep root
xuanphucn said:
Did we have any safe method yet? I want to keep root
Click to expand...
Click to collapse
knoxraid
http://forum.xda-developers.com/showthread.php?t=2577273
I am currently updating the UrDroid Stock KitKat
carl1961 said:
knoxraid
http://forum.xda-developers.com/showthread.php?t=2577273
I am currently updating the UrDroid Stock KitKat
Click to expand...
Click to collapse
is this one use the official 4.4.2 or the leak?
Has anyone tried doing an emergency restore (or whatever it's called) through kies first then trying to get the OTA to work without failing?
It seems like it's 50/50 on who's works and who's fails. Am I right?
xuanphucn said:
is this one use the official 4.4.2 or the leak?
Click to expand...
Click to collapse
yes custom rom with latest OTA kitkat
Thanks OP. Worked for me. I'm ok with stock on the Note 3 that's why I got a nexus
Ciberious42 said:
Oh sorry I thought it would have been pretty clear when I mentioned you would be stuck with SU
Click to expand...
Click to collapse
So did you root with Kingo too when you were on NB4? I didn't want to use Kingo, but I thought what the heck, and used it for quick rooting. Then after the Kitkat update, I realize I have SuperSU as a system app even after factory reset. Apps like CPU-Z reports my devices is rooted when it's not.
Is this the only thing that's not same as pure stock NC2?
hp79 said:
So did you root with Kingo too when you were on NB4? I didn't want to use Kingo, but I thought what the heck, and used it for quick rooting. Then after the Kitkat update, I realize I have SuperSU as a system app even after factory reset. Apps like CPU-Z reports my devices is rooted when it's not.
Is this the only thing that's not same as pure stock NC2?
Click to expand...
Click to collapse
you can re-run and use kingo to remove the root
Also if you are weary of the update, back up your files and apps then factory reset. Once you are factory reset, download the OTA but just hit "remind me later".
Do the instructions in the OP and after it installs it tells you that you have an update pending, install the update and it covers any files that may have went missing in the update.zip.
If you wanted to be 200% sure.
I am set at official and with no custom lock and Knox is 0x0.