So I rooted my Note II but I left the stock ROM on the phone, and AT&T just pushed a big OTA update. What steps do I need to be able to install an OTA update now? After a bit of research, it seems I need to unroot? I've just never had to do this before because I usually just use custom ROMs, but on the Note I wanted to leave the stock ROM in place.
rtatum said:
So I rooted my Note II but I left the stock ROM on the phone, and AT&T just pushed a big OTA update. What steps do I need to be able to install an OTA update now? After a bit of research, it seems I need to unroot? I've just never had to do this before because I usually just use custom ROMs, but on the Note I wanted to leave the stock ROM in place.
Click to expand...
Click to collapse
I used MrRobinsons' root injected ROM which was UCAMA4 (I think) and left the recovery alone, used the root access app that I bought to keep root. I did not remove any AT&T apps and was able to update to UCAMC3 without any problems. And the app that I bought kept my root access.
CodeNameRedNeck said:
I used MrRobinsons' root injected ROM which was UCAMA4 (I think) and left the recovery alone, used the root access app that I bought to keep root. I did not remove any AT&T apps and was able to update to UCAMC3 without any problems. And the app that I bought kept my root access.
Click to expand...
Click to collapse
Well -ALL- I did was root, install clockwork recovery, and Super SU. So I'm wondering what I need to do to be able to install an OTA update now, because I currently cannot.
It is my understanding that you must leave the recovery stock. I have also read that you must leave the AT&T apps in there but I am not sure about that. So if you want the update go back to stock then update then change your recovery.
CodeNameRedNeck said:
It is my understanding that you must leave the recovery stock. I have also read that you must leave the AT&T apps in there but I am not sure about that. So if you want the update go back to stock then update then change your recovery.
Click to expand...
Click to collapse
Well it's been a while since I've messed with this, so I just need to find instructions on how to return to stock.
Edit: Found a thread to remove root and factory reset, but my OTA update still won't install.
Edit2: Goes to the AT&T Updating progress screen and fails at about 25% and then reboots and starts up as normal.
rtatum said:
So I rooted my Note II but I left the stock ROM on the phone, and AT&T just pushed a big OTA update. What steps do I need to be able to install an OTA update now? After a bit of research, it seems I need to unroot? I've just never had to do this before because I usually just use custom ROMs, but on the Note I wanted to leave the stock ROM in place.
Click to expand...
Click to collapse
I don't have a solution to your problem, but I am very curious which AT&T update you are referring to.
Npsacobra said:
I don't have a solution to your problem, but I am very curious which AT&T update you are referring to.
Click to expand...
Click to collapse
Me too. Whatever it is it isn't a major upgrade. . .
Npsacobra said:
I don't have a solution to your problem, but I am very curious which AT&T update you are referring to.
Click to expand...
Click to collapse
No idea, it's a ~65mb update that just came up yesterday for me. I was looking to reset my phone back to factory anyways lately, so I just decided to do it now on account of there being an update. Since it's not working anyways, I might just re-root and flash a custom ROM, but then I lose S-Pen functionality, but I don't use the pen much these days anyways.
The update has two possibilities...
Either it's the latest UCAMC3 update for UCAMA4.....or...
If updating from the UCAMA4 to C3....and the update has an interrupt...or errors....it "can" complete the update process and show a finished status...but will prompt the user again later and download the update again....minus the updater files placed to cache....because they already exist...
I've had this happen twice in so many months as I returned to stock for various reasons...
The file size is roughly 65 meg.....while the complete update is 68.86 meg..
Just take the update...as it's the UCAMC3 minus the updater...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Same problem here. I just made a thread asking on a fix. So I'll let u know if I get one. And I'll check back here to see if u do
Sent from my Motorola starTAC
What's the easiest way to return my note to completely stock? Its currebtly rooted running jellybean rom. I just got the note 3 and gesr and my dad is taking my note 2 and would like it compleyely stock. I dont have any of my backups cuz they were all on my pc which crashed and has been replaced.
Hi,
Search for Dr. ketan guide on restocking, it's well explained.:good:
SS4Luck said:
What's the easiest way to return my note to completely stock? Its currebtly rooted running jellybean rom. I just got the note 3 and gesr and my dad is taking my note 2 and would like it compleyely stock. I dont have any of my backups cuz they were all on my pc which crashed and has been replaced.
Click to expand...
Click to collapse
Use a file manager with root permissions(root explorer etc) to delete busybox from Xbin directory and then select full unroot option from SuperSU setting.
Its the quickest way to full unroot.
Go to Sammobile and download any rom for your Galaxy Note N7100
Open Odin, click on pda and open your downloaded sammobile rom, press volume down+home+power on your Note and flash it. You will keep your data but all mods and root will disappear if you choose for 4.1.2 or lower.
Hi, im new on XDA but have quite a lot experience whit phone.
I tryed to root my samsaung galaxy s3 from Rogers (same as att) i747M whit CF-Auto root (im on android 4.3 jellybean).
I did it my phone is still working. I didnt flash a new recovery or anything.
Now i woudlike to remove root finally.
*the counter of the new Knox is set now to 0X1 but personnally i dont really mind.
The problem is that i woudlike to remove the root. I dont whant to downgrade i like 4.3 jellybean. (Anyway Att s3 cant be downgraded it will result to a soft brick)
I dont know how to remove the root and i woudlike to learn how to do it on my Samsung galaxy s3.
Thanks
(i was wondering about if i download the 4.3 stock Rom and i flash it will odin will it brick even if its on the same bootloader? because thats not downgrading...)
Thank you in advance for helping me out fast!
killer0123 said:
Hi, im new on XDA but have quite a lot experience whit phone.
I tryed to root my samsaung galaxy s3 from Rogers (same as att) i747M whit CF-Auto root ( su in the app itself4.3 jellybean).
I did it my phone is still working. I didnt flash a new recovery or anything.
Now i woudlike to remove root finally.
*the counter of the new Knox is set now to 0X1 but personnally i dont really mind.
The problem is that i woudlike to remove the root. I dont whant to downgrade i like 4.3 jellybean. (Anyway Att s3 cant be downgraded it will result to a soft brick)
I dont know how to remove the root and i woudlike to learn how to do it on my Samsung galaxy s3.
Thanks
(i was wondering about if i download the 4.3 stock Rom and i flash it will odin will it brick even if its on the same bootloader? because thats not downgrading...)
Thank you in advance for helping me out fast!
Click to expand...
Click to collapse
Im having the same problem. Cant downgrade to any version. Can't unroot phone, I have yhe the s3 i747 also on 4.3. Im kind.of.sad nobody has.replied to this. I tried unrooting removing.supersu via inapp permanent unroot option, then using rootbrowser to delete su files from system/bin and system/xbin. ( there wasnt any), root checker said my phone didny have root access.all I wanna do is upgrade to thr newest version lol then root that. Why does it.habe ti be so hard?
Nico de Pontiac said:
Im having the same problem. Cant downgrade to any version. Can't unroot phone, I have yhe the s3 i747 also on 4.3. Im kind.of.sad nobody has.replied to this. I tried unrooting removing.supersu via inapp permanent unroot option, then using rootbrowser to delete su files from system/bin and system/xbin. ( there wasnt any), root checker said my phone didny have root access.all I wanna do is upgrade to thr newest version lol then root that. Why does it.habe ti be so hard?
Click to expand...
Click to collapse
This will get you to the 4.4.2 stock update: http://forum.xda-developers.com/showthread.php?t=2789917
It depends on you having a custom recovery. It does provide a way to go back to the stock recovery once you are updated. I believe the same devolper has also posted the most recent update to NJ1 in a separate thread.
wifi not working now, and didnt update.
dawgdoc said:
This will get you to the 4.4.2 stock update: http://forum.xda-developers.com/showthread.php?t=2789917
It depends on you having a custom recovery. It does provide a way to go back to the stock recovery once you are updated. I believe the same devolper has also posted the most recent update to NJ1 in a separate thread.
Click to expand...
Click to collapse
it let me flash from mjb or whatever to the ne4. all that did was **** up my wifi. switch it to on and it just goes right back off. plus the files for the stock recoveries were spam.
Nico de Pontiac said:
it let me flash from mjb or whatever to the ne4. all that did was **** up my wifi. switch it to on and it just goes right back off. plus the files for the stock recoveries were spam.
Click to expand...
Click to collapse
Check that your bootloader and modem/baseband are matching in version number, this seems to be important in some of the newer kernels. If they do not match, flash the modem to correspond to the bootloader. If they are matching you may want to reinstall the modem on the off chance that it flashed incorrectly the first time.
Since you didn't mention any issues with calling or data I take it that the correct APNs are installed.
I don't understand why you call the stock recovery files spam. The link at 4. leads directly to the androidfilehost page to download the file. The other is an attachment to directly download the file from xda. To each his own.
I recently rooted my phone, Samsung Galaxy S4 SGH-M919, and I edited the build.prop folder to get soft keys on my device. After I restarted my phone, the wallpaper changed to all black and about every 5 seconds I would get a message saying "Unfortunately, System UI has Stopped" so then I Un-rooted my phone through SuperSU and i still ended up getting the same problem. So then I decided to Factory Reset my phone, and afterwards the problem still didnt go away, I still got the same annoying message. I don't know what to do, please help ASAP, Thanks.
Rooting wasn't the problem, it was the edit.. So you can either edit the build prop back to what it was, or restore to stock/reflash your ROM
Sent from my SGH-M919 using Tapatalk
bkboss1 said:
I recently rooted my phone, Samsung Galaxy S4 SGH-M919, and I edited the build.prop folder to get soft keys on my device. After I restarted my phone, the wallpaper changed to all black and about every 5 seconds I would get a message saying "Unfortunately, System UI has Stopped" so then I Un-rooted my phone through SuperSU and i still ended up getting the same problem. So then I decided to Factory Reset my phone, and afterwards the problem still didnt go away, I still got the same annoying message. I don't know what to do, please help ASAP, Thanks.
Click to expand...
Click to collapse
That build.prop edit doesn't work on TouchWiz. From my research I saw that Sammy gutted the framework for the soft keys, so enabling them on TW causes nothing but problems. AOSP is the only way to have the real-deal soft keys.. you can use LMT on TouchWiz, although, to me, the whole pie thing is clunky compared to having dedicated soft keys.
serio22 said:
Rooting wasn't the problem, it was the edit.. So you can either edit the build prop back to what it was, or restore to stock/reflash your ROM
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I can't edit the build prop anymore, because I'm un-rooted now. Are you sure that restoring to stock ROM would make the problem go away, and if so, how would I be able to restore to Stock ROM? I have no idea how to do that, Thanks
bkboss1 said:
I can't edit the build prop anymore, because I'm un-rooted now. Are you sure that restoring to stock ROM would make the problem go away, and if so, how would I be able to restore to Stock ROM? I have no idea how to do that, Thanks
Click to expand...
Click to collapse
Yes if you flash the stock ROM you'll get the original unedited buildprop.
If you made a nandroid backup, restore it(nandroid backup saves headaches ) If not you need to use Odin to flash the original firmware. What firmware are you on, mdl (4.2.2) or mk2(4.3)?
☞ Sent from here☜
baseballfanz said:
Yes if you flash the stock ROM you'll get the original unedited buildprop.
If you made a nandroid backup, restore it(nandroid backup saves headaches ) If not you need to use Odin to flash the original firmware. What firmware are you on, mdl (4.2.2) or mk2(4.3)?
☞ Sent from here☜
Click to expand...
Click to collapse
I'm on 4.3, and how would I use Odin to flash the original firmware and what version of Odin?
You can't edit build.prop because you're unrooted.... couldn't you just re-root, edit build.prop, then unroot again if you just didn't want root?
lordcheeto03 said:
You can't edit build.prop because you're unrooted.... couldn't you just re-root, edit build.prop, then unroot again if you just didn't want root?
Click to expand...
Click to collapse
When I was rooted, I tried to edit the build prop, but every time I tried to open the build prop folder to delete my adjustments, My phone would just keep on crashing, saying that the System UI has stopped working, So then I just un-rooted, hoping the problem would go away, but it didn't.
bkboss1 said:
When I was rooted, I tried to edit the build prop, but every time I tried to open the build prop folder to delete my adjustments, My phone would just keep on crashing, saying that the System UI has stopped working, So then I just un-rooted, hoping the problem would go away, but it didn't.
Click to expand...
Click to collapse
I'd think that you could use adb to pull the build.prop, edit on your computer, then push the build.prop back... I mean, doing a restore would work, but I'm thinking of how to not lose your data.
lordcheeto03 said:
I'd think that you could use adb to pull the build.prop, edit on your computer, then push the build.prop back... I mean, doing a restore would work, but I'm thinking of how to not lose your data.
Click to expand...
Click to collapse
What exactly do you mean by restore? I already factory resetted my phone. I don't really care about losing my data.
bkboss1 said:
What exactly do you mean by restore? I already factory resetted my phone. I don't really care about losing my data.
Click to expand...
Click to collapse
I meant flashing a stock firmware image via Odin. Being you don't care about data loss, that would be the route to take.
lordcheeto03 said:
I meant flashing a stock firmware image via Odin. Being you don't care about data loss, that would be the route to take.
Click to expand...
Click to collapse
Okay, So how exactly would I do that? I'm pretty new to these kind of things.
bkboss1 said:
Okay, So how exactly would I do that? I'm pretty new to these kind of things.
Click to expand...
Click to collapse
Go to sammobile.com to find the M919 UVUEMK2 firmware.
Follow this thread. It's for returning to 4.2.2, but the premise is the exact same for restoring official 4.3 as well. Just use the newest version of Odin and instead of flashing the UVUAMDL tar, use the one you just downloaded from sammobile.
lordcheeto03 said:
Go to sammobile.com to find the M919 UVUEMK2 firmware.
Follow this thread. It's for returning to 4.2.2, but the premise is the exact same for restoring official 4.3 as well. Just use the newest version of Odin and instead of flashing the UVUAMDL tar, use the one you just downloaded from sammobile.
Click to expand...
Click to collapse
Okay, I'm in the process of downloading the firmware. I also had another question. When I go to my phone's software update to check, for an update it says "Your device has been modified. Software updates are not available" and the device status is "Custom" even though I'm not rooted anymore and If I flash the original stock ROM, will this go away, and return to its normal state?
bkboss1 said:
Okay, I'm in the process of downloading the firmware. I also had another question. When I go to my phone's software update to check, for an update it says "Your device has been modified. Software updates are not available" and the device status is "Custom" even though I'm not rooted anymore and If I flash the original stock ROM, will this go away, and return to its normal state?
Click to expand...
Click to collapse
On that note, I don't know for 100% certain but I do believe that will stay. Perhaps someone else can confirm if Triangle Away will at least remove that aspect on 4.3; I know it won't touch your KNOX counter but I'm uncertain if it does anything for your flash counter.
All that device status: Custom means, aside from warranty being void is you can't update via Kies or OTA; but you can still update (when an update is released) by downloading the firmware and flashing via Odin OR using a custom recovery and a flashable zip.
bkboss1 said:
Okay, I'm in the process of downloading the firmware. I also had another question. When I go to my phone's software update to check, for an update it says "Your device has been modified. Software updates are not available" and the device status is "Custom" even though I'm not rooted anymore and If I flash the original stock ROM, will this go away, and return to its normal state?
Click to expand...
Click to collapse
Its still on modified because you altered system files.. Once you restore it should go back to normal
Sent from my SGH-M919 using Tapatalk
Thank you guys so much! I flashed the original stock ROM and everything is back to normal
Hello, I have rooted my stock Galaxy Note 3 T-Mobile 4.3 and now I heard that Samsung is rolling out soon KitKat update for the Note 3.
My questions is, do I have to unroot and return to stock then update then root the exact same way I did before ?
Does updating to KitKat require a different root method ?
Can I restore my apps and how ? I dont seem to know how to use Titanium backup and I even purchased it!
Please help me and thanks
Iorveth said:
Hello, I have rooted my stock Galaxy Note 3 T-Mobile 4.3 and now I heard that Samsung is rolling out soon KitKat update for the Note 3.
My questions is, do I have to unroot and return to stock then update then root the exact same way I did before ?
Does updating to KitKat require a different root method ?
Can I restore my apps and how ? I dont seem to know how to use Titanium backup and I even purchased it!
Please help me and thanks
Click to expand...
Click to collapse
I believe that you can update to Kitkat via Odin when the official update comes to T-mobile while rooted but you will lose root in the process. As far as rerooting, I believe you can flash recovery with Odin and then flash SuperSu in recovery to get rooted again, although, I think I read somewhere that it wasn't recommended anymore?. Not sure though. I used auto root method which I'm sure would still work just fine with kitkat. For restoring apps I would recommend the App backup and restore from the play store. Very easy to use.
Why dont you flash a 4.4 rom that's out there
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Iorveth said:
Hello, I have rooted my stock Galaxy Note 3 T-Mobile 4.3 and now I heard that Samsung is rolling out soon KitKat update for the Note 3.
My questions is, do I have to unroot and return to stock then update then root the exact same way I did before ?
Does updating to KitKat require a different root method ?
Can I restore my apps and how ? I dont seem to know how to use Titanium backup and I even purchased it!
Please help me and thanks
Click to expand...
Click to collapse
I generally NEVER accept OTA updates until Devs have a chance to look at it and okay it, or see what others feedback is after accepting. Don't take for granted that you are rooted and have unlocked boot loader access. And until official KitKat is released its all hearsay as to when it'll come out.